Skip to content
New issue

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

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

Already on GitHub? # to your account

path IDs in exported file name #25

Closed
portablevampire opened this issue Jan 1, 2024 · 2 comments
Closed

path IDs in exported file name #25

portablevampire opened this issue Jan 1, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@portablevampire
Copy link

hello, me again, sorry i hate to request another feature when i've already got another enhancement request open, but i'm wondering if it might be possible to implement an option to include the path ID of exported assets in their filename? i know it lists path IDs of exported objects if you generate an assets.xml file, but it can be kind of hard to match up the asset listed in the xml file to its exported file especially when a lot of monobehavior objects have the same name. If this is something that can be done in addition to the group assets by source file name option, that would be ideal.

this would be really useful in saving me time—the path IDs are pretty important for a lot of the asset mining i do, and being able to export assets with path IDs somewhere in the filename would allow me to write python scripts that would speed up the process of looking through these assets significantly. even if its just added to the cli version only that would be fine

@portablevampire
Copy link
Author

portablevampire commented Jan 4, 2024

I thought I'd take care of this myself and spare you the trouble, because looking through the source code, I'm pretty certain I know exactly what part of the code to modify and how in order to accomplish this, but I'm woefully inexperienced with C# projects and VSCode, and even with all of the necessary SDKs (yes, including FBX and all of the different .NET SDK versions) I can't seem to figure out how to build the thing without getting hundreds and hundreds of namespace errors. It's a little frustrating that despite being able to figure out how to edit the code to get this to work, I get stuck at building it. My coding experience is mostly with Python, so anything more complicated than hitting "Run Module" in IDLE has me scratching my head.

If you're not interested in adding this, then I would appreciate at least a nudge in the right direction with regards to how to build this myself without namespace errors in the hundreds (I've got about 495 errors) so that I could at least take care of it myself that would be appreciated.

@aelurum aelurum added the enhancement New feature or request label Jan 23, 2024
@aelurum
Copy link
Owner

aelurum commented Feb 1, 2024

Hi
Yeah, I will add such option, you are not the first who wants it.
In fact, even the first version of AssetStudio that I modified (AssetStudio v0.14.38 mod) had it, but only for images, and yes, it's pretty outdated.

As for VSCode, I didn't try to work with it.
As you can see in the readme, you need Visual Studio 2022.
And then there shouldn't be any problems (#26)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants