You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently this is an issue with Megascans, and I recall Quixel mentioning that they cant give the textures descriptive names due to how they index the file names. It would be extremely helpful to mitigate this when exporting to Painter by either using the name given in Bridge, or coming up with some other naming scheme. As it is, importing several textures will create extremely unreadable filenames in the Shelf.
The text was updated successfully, but these errors were encountered:
@MackenzieShirk i've tried to implement this in the plugin but the current JS API of Substance Painter uses the file path as the display name for imported assets so the only way to implement this kind of feature would be to duplicate the assets in the file system rename them using the configured naming scheme of Bridge and then import them into Painter, this method is far from ideal since it will require write and read access of the file system and thus causing not permitted errors
Currently this is an issue with Megascans, and I recall Quixel mentioning that they cant give the textures descriptive names due to how they index the file names. It would be extremely helpful to mitigate this when exporting to Painter by either using the name given in Bridge, or coming up with some other naming scheme. As it is, importing several textures will create extremely unreadable filenames in the Shelf.
The text was updated successfully, but these errors were encountered: