[gtalarico]

I was able to solve it, but I am not sure how I did it.

I did a fresh install of the plugin, deleted all temps, and copy and pasted geometry into a new .skp

Unfortunately, I am not being able to reproduce it now... I will post it right away if it happens again.

However as I tried to reproduce it, I had a file that kept crashing fire and render. Once I disabled Instances, it worked... I guess there is another potential bug there.

[gtalarico]

Got some more MXM mode link failure!

Here is a bunch of logs for you:
http://db.tt/2LFrcGFF

Log6 is the recent failure.

This time the failure is in Fire only. MXS in studio looks ok.
I also notice the "textures" folder from the Pack & Go is missing tons of textures....
texture folder shows about 10 textures, the model has many many more...


Not sure which MXMs are failing, but WhiteWall.mxm is for sure

Update: Weird, just notice temp.mxs has the right materials... Isn't this the file fire uses?
I opened temp.mxs in studio and it looks good too... temp.jpg shows the wrong materials
Fire Cache is disabled.

[gtalarico]

Started getting Full MXM failures (alll materials).
Does this log says anything about it?
https://www.dropbox.com/s/ilkym9szea2gi ... 772481.txt

[JDHill]

Well, there are a ton of MXM-read failures, most likely due to the use of an 2.5.1.0 exporter (see the top of the log). Are you using that on purpose? If not, you should delete Skp2Mxs.dll from your SketchUp Exporters directory and run repair from the 2.6.0 installer. If so, then you have to make sure to use MXM files which were written with a compatible version of Maxwell.

[gtalarico]

I think I now why... I am at work, and there is a script or something that "restores" certain folders at every restart (for some weird reason, it keeps resurrecting old plugin exporters...)

A while ago I had this problem because it kept restoring the old Maxwell exporter (you might remember it, I was getting two renderings everytime I tried rendering).
I asked them to clean up the "image" and update to the new exporter, but that was before I updated to the 2.6

Let me take care of that, and I will let you know if it solves the problem.

PS: I have seen this issue coming up a lot.... What do you think if the plugin "checked" the version of the exporter and gave a warning if there is an issue... (ie. 2.6 plugin with 2.0 exporter).
Maybe not, but it would definitely help users quickly troubleshoot...

Thanks JD.

[JDHill]

I'll see -- I know that seems easy to do, but it is actually not so simple as it sounds. And it should be a pretty rare case that parts of the plugin would randomly get replaced after they had been put in place by the installer, so the payoff, in terms of the added complexity, is not so good.

[gtalarico]

I agree, it probably doesn't happen to a lot of people... I guess I just have had bad luck with it... ; )

Ok, I fixed the exporter, still mxm link failure... This is driving me crazy.
Here is the log
https://www.dropbox.com/s/gfsv96xee0ri4xh/log.txt

Not sure if it's all mxms, but Painted White Wall is one of them...

[JDHill]

I do not see any obvious issues in the log. It looks like you have two materials, _Painted-Wall and _GWB, which link to an MXM named WhiteWall.mxm, located in your [...]/SU/mxm directory. As far as the plugin knows, this MXM exists, and it should be putting it into the MXS for those two materials. If I understand correctly, what you mean by mxm link failure, is that the link is showing up correctly in the UI, but in the produced MXS, the material is one auto-generated by the plugin, as though the material were in Embedded mode. Is that correct?

[gtalarico]

Yes correct.
I often give metals a different SU color so I can tell them appart, but when rendered it is replaced by the linked MXM.

Since 2.6, I have had this issue where sometimes a material (sometimes all) don't get replaced by the MXM at render time.
It happens more often in Fire than in maxwell.

[JDHill]

Do you only see this happen with a particular scene or scenes, or using a particular set of MXMs, or a particular MXM location? In other words: do you think you would be able to reproduce it at will, using a fresh, simple scene? If not, is it reliably reproducible once it has occurred in a particular file? Meaning, does closing and re-opening SketchUp affect the behavior in any way?

[gtalarico]

I think it's only this scene... and only sometimes...
(I know, there is not much you can do if you can't reproduce....)

I just realized though that one of the problems was caused by a texture color adjustment in the SU Material Edit.
Once I set a new texture, reset color and resized, Fire was rendering it correctly.
It shouldn't affect it because it was in MXM mode, but....