Page 1 of 1

Here's my list - mainly MAX material editor related

Posted: Thu Sep 07, 2006 5:17 pm
by Peter Shupe
Here's my list:

1. a way to drag materials from MXED to MAX material editor.
1a. When you choose a material in the MAX material editor it would open the MXED and see 1.

2. in the MAX material editor you could see the path, scroll feature?, to the mxm file. So that when the path cannot be found you at least know which material it is.

3. that the name of the material (mxm file) would automatically appear in the MAX material editor

4. that when you render from MAX it would direct it, somehow, to the correct path for the maps, or at least ask you to find the directory, like it does in studio.

5. I wish that when you applied a material (mxm) to an object it would notify you that there was a bitmap missing a path and/or map.
a. so thta you could just adjust the path, see wich 4.
b. so that you could use a different one if that map was missing.

Thanks - that's it for now.

Regards Peter.

Posted: Mon Sep 11, 2006 4:52 pm
by Fernando Tella
I'll add:

-capability to see in viewport the tiling of a texture tiled in maxwell picker.

Here's some more - frustration!!!!

Posted: Tue Sep 12, 2006 3:28 pm
by Peter Shupe
These material editor issues in MAX are absolutely brutal. I also crash 90% of the time when I open up and go straight to the material editor. Even if I only have 6 slots open.

I have 2 computers that I switch back and forth between. One has XP 64 bit the other XP 32. I have the materials on the C:/ of each in the same directories and I still need to tell the app where some of the bitmaps are even though the path it shows is correct. It asks me when I open the file and search the path. When I go to render it either just craps out or asks me again. If I go to modify the material it asks me again. I find this almost unuseable.

Please fix this issue! This should not be a wish but a bug fix!!!

Regards Peter.

Posted: Tue Sep 12, 2006 3:57 pm
by Fernando Tella
I'm experiencing those crashes too and are really frustating. I don't have that problem with the paths though. Remember to resave the material after you specify the path. It also sometimes looks for an old preview map (to show in max viewport) if you haven't updated it, check that too in the eye icon and resave after.

Posted: Tue Sep 12, 2006 4:32 pm
by Peter Shupe
I'll check that but the paths aren't as annoying as the constant crashing!! I have yet found a way to avoid the crashing. Sometimes I can make a plane or a box and rotate around add a UVW modifier and then erase them all or move them below the ground plane and other times it will still crash after doing all this ridiculous work! I might just consider going back to Vray to add any materials! Pretty expensive greyscale renderer!!!

Regards Peter.

Posted: Tue Sep 12, 2006 6:12 pm
by kraemerJK
Peter, I do not have that many path issues, but I got used to not saving the material after changing, but exporting it again overwriting the old version. I don“t know if this really helps, it sure "feels" like it does .... :roll:

Posted: Tue Sep 12, 2006 7:37 pm
by Peter Shupe
kraemer JK- I usually export and call it something different and then re-assign the new material in Max. I still have issues.

Thanks

Regards Peter.