Maxwell Render | Official public forum

Ciao guys,
downloading packs of '1=2007 campaing' i noticed a problem about duplicate map filenames. Many mxm use files named as "color.jpg" or "diffuse.jpg" and so on...
This causes losing time to all users in re-organizing downloaded material, but this is would be avoidable if user that upload mxm uses a simple rule

this is my idea about:

example:
(mxmname)_(1st three characters of user)_(kind of map).xxx

or in other words....
material name: Frosty ham
mxm filename: Frosty ham_LUC.mxm
diffuse-map filename: Frosty ham_LUC_diffuse.jpg
rough-map filename: Frosty ham_LUC_rough.jpg
preview1 filename: Frosty ham_LUC_pr1.jpg
preview2 filename: Frosty ham_LUC_pr2.jpg

...and so on for all elements of mxm..

and our libraries will be more ordered and every map has unique files linked.

ciao
Luca

I totally agree. But is this not to late now? Or can someone write an app that renames all linked files by these rules...?

yes, may be too late.

or it requires some efforts from users to update own materials in mxm gallery site.
or, as you said, an app.. but i'm really really not good in programming.

...and in next year campaing "1=5000" we will se some results


EDIT: (or a "resource-collector/pack-and-upload" in next MXED version? )

KurtS wrote:I totally agree. But is this not to late now? Or can someone write an app that renames all linked files by these rules...?

+1

or it requires some efforts from users to update own materials in mxm gallery site.

I agree, this would be highly apprechiated.

I agree totally, its hard enough keeping your 3d files organised
Also I have used quite a few materials without the texture maps included, which really defeats the purpose, perhaps the rules for uploading a material can be changed to accommodate these simple procedures, saves everybody a lot of work.

Cheers

Brett

Lots of materials have their maps on different drives and locations.
There must be a standard for adding a "map library path" and all materials would be looking to those paths first before looking to the paths embedded on the mxm files.

A good solution could be that by default the render will look on the material's own folder before go searching on for example "k:\maps" thus, if we keep each material on its own folder or folder group with its own maps it will always find the maps.

any suggestions?