Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLI: Export prefab at specific path? #50

Open
HeCorr opened this issue Sep 12, 2024 · 3 comments
Open

CLI: Export prefab at specific path? #50

HeCorr opened this issue Sep 12, 2024 · 3 comments

Comments

@HeCorr
Copy link

HeCorr commented Sep 12, 2024

Hello! I have a list of .prefab paths I want to export but searching for those in the (GUI) Asset List doesn't always returns results, but the names do match when searching on the Scene Hierarchy (although very slow, and the tree structure does not match the path).

Is there a way to export a prefab from the CLI given it's specific path (i.e. assets/content/nature/rock_formations/rock_formation_medium_a.prefab), as if exporting it from the GUI as Model > Export selected objects (split)?

@aelurum
Copy link
Owner

aelurum commented Oct 31, 2024

Hi.
The object export mode in CLI version supports --filter-by-name option, have you tried it?

@HeCorr
Copy link
Author

HeCorr commented Nov 1, 2024

I just did, and unless I'm doing something wrong, it does not do what I want.

The problem I'm having is that some asset paths that I want to export contain .prefab files of the same name:

image

...so filtering them by name (as opposed to the whole container path), makes it so I can't tell which is which:

image

I can filter by container, which is sort of what I want, but it only returns MonoBehaviors and if I do -m splitObjects it ignores the filter and starts exporting all the assets:

image

@HeCorr
Copy link
Author

HeCorr commented Nov 1, 2024

the workflow that seems to work for me in the GUI version is to search for the full .prefab path in the Asset List, right-click any MonoBehavior and click Go to scene hierarchy, then find the top of the tree and export that (which is also a workaround for #49).

kind of a lot of steps, which is why it would be nice if I could use the CLI instead (but it seems kinda slow anyway since it has to load all the bundles every time).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants