Maxwell Render | Official public forum

Hi there.
After an export of 1.14 mins maxwell fire doesn't start running. Is there a way to know why?
Is the scene too complex?

It's impossible to say, without more information. Please go to Scene Manager > Options > Diagnostics and enable Ruby Echo, then perform the export again, to see if any errors are printed in the Ruby Console. Otherwise, I would need you to upload the model, so I can try to reproduce and diagnose the issue here.

MX: unloading Fire data
MX: found 'resina industriale.mxm' @ '/Users/mattiamoretto/Documents/CRC/materiali/MARMI/Resina industriale'
MX: texture export warnings:
- TextureWriter::write_all failed
MX: Exported in 1m 12s.
MX: update check succeeded [installed: 2.7.0.0, available: 2.6.10.0]

could be that texture?
What should i do?

The mention of the MXM file is normal and is not a problem, it just means that the MXM was not found at the path specified, but was found using search paths.

Regarding the TextureWriter, in general, the main effect of the TextureWriter failing to write all textures will be a slowdown of the export, since the plugin must then ask SketchUp to write each texture individually. A valid question is why it failed: it could be due to a specific problematic texture in the model, but it is hard to say; this failure is a common one on the OSX side, and I've never seen a real reason for it in that case.

One thing you might do is to update to version 2.7.10 of the plugin, available for download here. There are not huge changes, but it would not be a bad idea to update. Lastly, you might try to isolate the problem by hiding half of the model, trying to render, and if it still fails, hiding half of the remaining model -- and so on. One can usually narrow down a problem pretty quickly using this method.

I've updated to 2.7.1 but nothing has changed. I'm gonna try to remove some materials even though it's shouldn't be the right way to solve the problem

You can do that, but I'd greatly appreciate it if you could upload the model somewhere (dropbox or some other file sharing site) first, so that I can take a look and find what is the real source of the problem. If it is on the plugin's side, I want to fix it.