Maxwell Render | Official public forum

I use UNC paths for all textures, and I'm exporting to Studio from Max 2011 and it's losing the textures everytime. I can render fine via the plugin, so the paths are good, but if I export the scene and open in Studio directly I have to manually point to all the textures again. If I save the .mxs and re-open in Studio I have to do it again.

Is this is a bug or something I may be doing?

b

I have gone back to Max and re-exported the scene and had the same problem. Re-set the textures in Studio, save the .mxs, and if I re-open it the paths are gone again. They do render fine from the plug-in and also in Studio once I have re-set the paths.

Noticed an error in the log window when exporting from Max again that said:
Warning: Invalid path extension (in method setPath)

Could this be the culprit?

Also: when the .mxs is opened in Studio the paths set for render output are also gone (they are also UNC paths to a network location, same as all the textures).

/b

simmsimaging wrote: If I save the .mxs and re-open in Studio I have to do it again.

There is something strange here, perhaps in the SDK/mxs format. I tried specifying a UNC path for a texture, on reopening the scene, Studio says it can't find the texture and asks to find a replacement. I choose no, and the texture actually loads fine. You don't get the missing textures pop-up?

Mihai wrote:

simmsimaging wrote: If I save the .mxs and re-open in Studio I have to do it again.

There is something strange here, perhaps in the SDK/mxs format. I tried specifying a UNC path for a texture, on reopening the scene, Studio says it can't find the texture and asks to find a replacement. I choose no, and the texture actually loads fine. You don't get the missing textures pop-up?

Sorry - I had given up on getting a reply to this post as well so wasn't checking in often.

I tried what you said and this time when I got the missing textures popup I chose 'no to all' and the the file does open and loads the textures fine. Odd.

Is this a bug?

b

Yes, it was a bug It's fixed for the next release, including for the Max plugin.

Thanks Mihai. I had a few other issues as well so I will chk back again on the next release. Hopefully the october pricing will be in effect again.

B

Mihai wrote:Yes, it was a bug It's fixed for the next release, including for the Max plugin.

I was considering Maxwell for an upcoming project but wondered if this bug had been fixed for the currently available release?

I'm not sure I will upgrade now - I missed the better deal in October while some questions were hanging on on the forum, so I may wait till some nodes are included again, but would like to know if the problem is resolved in any case.

Thanks!
b