Any features you'd like to see implemented into Maxwell?
#324775
Maybe there's something out there that I just don't know about, if so I'd love to know.

The problem I'm having is that when I run a rendering through 3ds Max on a car model I've been working on, the render fails and Maxwell let's me know the name of the .jpg file that it can't find. However, it doesn't let me know which material that image file belongs to. So how am I supposed to find out what the problem material is without going through every material?

Shouldn't Maxwell give me both the name of the image file AND the maxwell material that houses it?

-Brodie
#326031
I'll have to go back and check that box I suppose. The problem with that box, as was mentioned, is that so often the "errors" posted there are worthless that you just get used to not looking at it at all. Besides, I use SU a lot as well which doesn't have that box. The logical place for such information to be would be in the maxwell render box though, right after it tells me it can't find a texture it should tell me which texture that is.

-Brodie
#326040
If you could point me to some useless errors that window displays, I'll be happy to correct, improve or remove them.
The logical place for such information to be would be in the maxwell render box though, right after it tells me it can't find a texture it should tell me which texture that is.
The reason I've asked you if the Max Translation Window displays some errors about bad texture paths it's because the plugin, when it exports the scene to the renderer, it fixes the paths so that Maxwell can find them. If it manages to fix them, there are no errors displayed in the Max window. Of course, if it can't, it will display errors.
Also your suggestion with more precise information in Maxwell related to missing/wrong texture paths is valid and I'm sure the guys working on Maxwell are aware of it.

So, is this a known issue?

Thanks a lot for your response, I will update and […]

did you tried luxCore?