- Since every asset in the content browser has its own file type written, I would love that feature to be used to sort per asset type. This will allow us to remove abbreviations from the filenames and clean up the clutter in our folders. It is also faster when you don’t need to define a name in front of every asset, it speeds up the workflow
- With that said, I would also love if we can have the same name being allowed in the same folder, as long as the file type is different. This will also speed up our workflow.
- Ability to choose what gets written when content is imported or created, as part of the filename default. Nobody, and I mean literally nobody, uses "_Mat" on materials unless they want to be lazy and not rename. Let us define that as a prefix M or none (if the two above suggestions were done) instead.
Wouldn’t Number 2 cause issues with assets in verse asset reflection? Since they would have ambiguous names?
Also don’t materials already come without a _Mat in the end?
This is from a FBX I imported and materials are just using a generic name
If it was designed correctly verse asset reflection would flag the asset based on asset type and add that as an acronym to the filename on its own, without the user needing to do that. Epic always passes their problems to the developers and it’s all very detmotivating when you have to click and type and click and you ve accomplished nothing, because the engine is not smart or intuitive enough to be helpful and speed up the process for you, like other software (FL studio for example).