- Thu Feb 03, 2011 4:30 pm
#337149
Good morning friends,
Yesterday we ran our first rendering and although we are excited about the results we saw that Maxwell did not render several objects with the mxm materials that we had assigned to them. We approached Jeremy about this and his explanation follows below. This is pretty heavy and obscure stuff. We wonder if someone could elaborate:
“The way that it happens is usually that you download an MXM from the MXM Gallery, and this MXM contains texture paths which were created on a different machine. When you clicked on that folder icon, you were importing the state of that MXM file into the material you were currently editing in the material editor. If bad paths are contained inside of that MXM file, then you will see them being reported there in the material editor once it has been imported.
You can alter your strategy to let the plugin help you out a bit here; if you access the MXM Gallery from the plugin (right-click in the Scene Manager > Materials window),”
Let’s stop here. We're not sure what Jeremy's saying here. What are we trying to do here? When you rc on the Materials window are you trying to go out to the Maxwell Resources website and download directly from there?
“… then when your chosen MXM is downloaded, the plugin attempts to fix up any bad paths it contains. After doing so, it saves the MXM to one of two places: (a) if the document has been saved, then the MXM is saved in an 'mxmgallery' folder next to the document, and its textures are saved in a 'textures' folder inside that. If the document has not been saved (and therefore has no location on your disk), then the MXM is saved to an 'mxmgallery' folder in your documents folder; you can also find this folder pre-populated in the drop-down.”
What does Jeremy mean by this?
“In practice, there is a choice to be made on the plugin's part: export an MXS with bad texture paths and let Maxwell tell you about it, or disable the textures preemptively. The plugin chooses to do the latter, and as a middle road, provides the 'Bad Paths' report in the material editor, as well as optionally, at export time (see the plugin Option 'Disable Path Check'). Usually this takes care of any issues, but in looking at your scene I did notice that while I am doing this for textures, I am not doing it for emitter MXI/HDRIs and IES files. So Maxwell can still refuse to render. I'll tweak this for the next plugin build, but until then, you'll have to make sure the paths you use are valid.”
How do we check and see if any of our mxm’s have bad paths before we render? Do we double-click on each and every one and look for the “bad paths” warning? If so, again – how exactly do we fix it?
Thank you.
Cosmas Demetriou
Yesterday we ran our first rendering and although we are excited about the results we saw that Maxwell did not render several objects with the mxm materials that we had assigned to them. We approached Jeremy about this and his explanation follows below. This is pretty heavy and obscure stuff. We wonder if someone could elaborate:
“The way that it happens is usually that you download an MXM from the MXM Gallery, and this MXM contains texture paths which were created on a different machine. When you clicked on that folder icon, you were importing the state of that MXM file into the material you were currently editing in the material editor. If bad paths are contained inside of that MXM file, then you will see them being reported there in the material editor once it has been imported.
You can alter your strategy to let the plugin help you out a bit here; if you access the MXM Gallery from the plugin (right-click in the Scene Manager > Materials window),”
Let’s stop here. We're not sure what Jeremy's saying here. What are we trying to do here? When you rc on the Materials window are you trying to go out to the Maxwell Resources website and download directly from there?
“… then when your chosen MXM is downloaded, the plugin attempts to fix up any bad paths it contains. After doing so, it saves the MXM to one of two places: (a) if the document has been saved, then the MXM is saved in an 'mxmgallery' folder next to the document, and its textures are saved in a 'textures' folder inside that. If the document has not been saved (and therefore has no location on your disk), then the MXM is saved to an 'mxmgallery' folder in your documents folder; you can also find this folder pre-populated in the drop-down.”
What does Jeremy mean by this?
“In practice, there is a choice to be made on the plugin's part: export an MXS with bad texture paths and let Maxwell tell you about it, or disable the textures preemptively. The plugin chooses to do the latter, and as a middle road, provides the 'Bad Paths' report in the material editor, as well as optionally, at export time (see the plugin Option 'Disable Path Check'). Usually this takes care of any issues, but in looking at your scene I did notice that while I am doing this for textures, I am not doing it for emitter MXI/HDRIs and IES files. So Maxwell can still refuse to render. I'll tweak this for the next plugin build, but until then, you'll have to make sure the paths you use are valid.”
How do we check and see if any of our mxm’s have bad paths before we render? Do we double-click on each and every one and look for the “bad paths” warning? If so, again – how exactly do we fix it?
Thank you.
Cosmas Demetriou