jeric_synergy
Axes grinder- Dongle #99
Do we EVER hear anything back? The best I get is "Yep, we can replicate, it's in the queue.".
I was also struggling with material names being enumerated with every separate piece of mesh when importing an fbx file. Names like metal__1, metal__2 through metal__238 etc. I wrote a couple of python scripts to clean up some of the worst situations that were easiest to code. These are not 'all-purpose' but may be helpful in some of your FBX import situations.
The 2 scripts are named
SurfaceNameConsolodateQuickFirst.py
SurfaceNameConsolodateAggressiveAsk.py
The first one looks for the shortest matching material name that already exists. So 'metal__238' matches the shorter 'metal__1' and is renamed that. The aggressive ask version looks for the double or single underbar '_' on the right and ask if you want to shorten it with a yes no box. Enter and escape keys work for that but you have to go through a lot of asks for some files. Both of them try to avoid renaming a surface named 'material_155' to a surface named 'material'.
I was also struggling with material names being enumerated with every separate piece of mesh when importing an fbx file. Names like metal__1, metal__2 through metal__238 etc. I wrote a couple of python scripts to clean up some of the worst situations that were easiest to code. These are not 'all-purpose' but may be helpful in some of your FBX import situations.
The 2 scripts are named
SurfaceNameConsolodateQuickFirst.py
SurfaceNameConsolodateAggressiveAsk.py
The first one looks for the shortest matching material name that already exists. So 'metal__238' matches the shorter 'metal__1' and is renamed that. The aggressive ask version looks for the double or single underbar '_' on the right and ask if you want to shorten it with a yes no box. Enter and escape keys work for that but you have to go through a lot of asks for some files. Both of them try to avoid renaming a surface named 'material_155' to a surface named 'material'.
I was also struggling with material names being enumerated with every separate piece of mesh when importing an fbx file. Names like metal__1, metal__2 through metal__238 etc. I wrote a couple of python scripts to clean up some of the worst situations that were easiest to code. These are not 'all-purpose' but may be helpful in some of your FBX import situations.
The 2 scripts are named
SurfaceNameConsolodateQuickFirst.py
SurfaceNameConsolodateAggressiveAsk.py
The first one looks for the shortest matching material name that already exists. So 'metal__238' matches the shorter 'metal__1' and is renamed that. The aggressive ask version looks for the double or single underbar '_' on the right and ask if you want to shorten it with a yes no box. Enter and escape keys work for that but you have to go through a lot of asks for some files. Both of them try to avoid renaming a surface named 'material_155' to a surface named 'material'.
related >