By JDHill
#321924
May I assume you are using the 2.0.6 plugin? That message simply means that the Maxwell SDK function used by the plugin to read MXI files was not able to read the file. So it might mean that the MXI is corrupted, or that the MXI is from a newer version of Maxwell than the plugin being used to read it.
User avatar
By osuire
#321931
This is not on my computer which has the latest versions of both Maxwell and plug-in.
On my config, it seems to work OK indeed.

My colleague has :
-Maxwell : 2.0.2
-Rhino Plug-in : 2.0.5

The MXI can be opened in Maxwell , so I suppose it is not corrupt.

I think that those compatibility issues between Maxwell and it's plug-ins should be advertized somehow/ somewhere...

Cheers,

--
Olivier
By JDHill
#321934
It is a simple question of backward compatibility; an older plugin uses an older SDK, and therefore cannot read MXIs written with a newer version of Maxwell. I am planning on getting the plugin versioning aligned with that of Maxwell, but there are technical issues that require me to wait until Maxwell reaches 2.1.x for me to do so.
By JDHill
#321948
So, it appears in the Rhino viewport, but not when Maxwell is rendering the image? I would first check to see whether the plugin is writing the file correctly or not by looking at the MXS in Studio.
Sketchup 2025 Released

Thank you Fernando!!!!!!!!!!!!!!!!!!!!!!!!!!! hwol[…]

I've noticed that "export all" creates l[…]

hmmm can you elaborate a bit about the the use of […]

render engines and Maxwell

Funny, I think, that when I check CG sites they ar[…]