[austerlitz]

Has anyone figured out how to fix this problem? I haven't seen any posts resolving this issue in Max, anytime I want to use the mxm files with textures that come with maxwell I get an error in maxwell saying that the path to the texture maps cannot be verified.

[Peter Shupe]

I would like to know this as well! ANYONE?? ANYONE??

I cannot render straight from MAX because it doesn't find the paths and you cannot change them. So I have to render and then open studio and find the mxs file and render that. And even that doesn't work very well as it doesn't allow you to have different directories to store you textures. It asks you for every single one if they differ?? What's up with that??

Regards Peter.

[Peter Shupe]

NOBODY??? Is there any way to change the paths for this plugin? Is there any way to add more than one path in Studio so you don't have to have all the textures in one directory??

THANKS!

Regards Peter.

[Frances]

Peter, what do you mean when you say that you can't change the paths? Have you tried opening the materials in mxed.exe and changing the path in the bitmap loader?

[ludi]

I solved this issue by creating this path

[Peter Shupe]

Fran - I have no problem applying my materials from the MAX material editor, which shows the correct paths, and also the correct bitmap in the preview. If I want to "edit material" it says texture not found and shows, what I assume to be the default path, and has a YES option button. I hit this button to direct it to the correct path and it launches the MXED and has the correct path in the browser. If I close it and save and then go to the same material, or any other, to edit it gives me the same texture not found error and I have to navigate to the directory again.

Once I get all my materials applied I hit render and it writes the mxs file, reads it succesfully, and gives me an "Error: Bitmap File not found (C: "default directory") Render Failed

I assume it is crashing because it cannot find the bitmaps and do not know how to change that default path, as it is correct in the MAX material editor, where you think it would be getting the material from as that is where it was applied.

I can however open up the mxs file with the mxst, and after redirecting to the correct path it opens the file and renders without asking again, or just crashing. But I want to know why it doesn't render right out of MAX?? It is especially a pain if I want to change something because if I change it in studio it doesn't keep it when I go back and update my MAX file.

Ludi - What path??? English is my only language, unfortunately, but that link looks like it is just to a Maxwell forum in a different language.

Any other suggestions are greatly appreciated. Thanks for the input.

Regards Peter.

[ludi]

No that's just my signature...

If you type exactly this path in your explorer:
C:\Program Files\Next Limit\Maxwell\materials database\textures\arroway
Do you find this location?

If no, creat it (in my case the Program Files folder had have an other translation, because of my OS language), so copy the texture to that location.

If yes, is this problem only in a complex scene or anyway in all little one-object test scenes?

[Frances]

Fran - I have no problem applying my materials from the MAX material editor, which shows the correct paths, and also the correct bitmap in the preview. If I want to "edit material" it says texture not found and shows, what I assume to be the default path, and has a YES option button.

That error box that shows up when you edit a material that is missing a bitmap path is worthless. I've posted about it in the bugs section and I hope NL paid attention. What should happen when you dismiss the worthless dialog, is you should then have a Folder dialog come up so that you can navigate to the correct path for the bitmap. This has changed from V1.0, where only the Folder dialog would pop up with the full path of the missing bitmap noted at the top for easy reference. Next Limit please fix this! The V1.0 way was better and followed standard practise.

So, once you click OK on the stupid dialog, find the smart dialog and navigate to your bitmap folder (where the Arroway textures are). You should know that preview images of materials are saved with the mxm and don't necessarily reflect the current settings of the material. They will show a bitmap that can't be found because it is a "dumb" picture that isn't really connected to the material in any "realtime" way.

I should add that it is a good idea to enable Show info window in the Max Maxwell plug-in System rollout. It will tell you when it can't find materials or has a problem with objects.

[Peter Shupe]

Ludi - No I don't have that path because I am using Win XP Pro 64 bit so I have a similar path but with "Program Files(x86)".

I don't want to have to make that directory. That is the point of the post! How do I change the default path to render??

Fran - As I said I have no problem getting the correct bitmaps and changing the paths, and editing materials, even exporting new materials etc. But I cannot get it to render out of MAX. I guess I will try making a directory for my files as Ludi suggests, but that just seems silly!

Do you have to have all of your textures in the same directory? Can't have different folders for different types of bitmaps?? eg. arroway/wood
I'll test to see if that works but seems silly, as I have said previously.

Thanks for the help. Your images really look great Fran! Are you using all the renders currently or are you searching for the best. I know your Vray renders are top notch as well. Thanks again everyone.

Regards Peter.

[Peter Shupe]

Well that worked but I am not completely happy with that work around! Funny thing is that I "moved" my textures to the default "Program Files" path and then I had a couple of bitmaps thta were looking for the old "Program Files (x86)" path??? So I guess it does somehow re-assign the path?? Not sure how or in what instance that happens. But atleast I can render from Max now without taking to Studio.

Thanks for the help it is just unfortunate we have to stumble through this stuff without any help or confirmation of correct procedure from NL !!!!! HELLO!!

Regards Peter.