> Why do projections show up as 'locked' when I open my MXS in Maxwell Studio?

The MXS format does not hold data about 'projectors', UV mapping is saved on the objects themselves in the form of UV data attached to each mesh triangle. So in short, it is not projectors which are written into an MXS, it is the UV coordinates that they create.

> I've pressed 'Render' button but the render doesn't seem to start.

It's probably that you have to do an extra step once the scene file has been exported, and press 'Done' button afterwards.

This happens if the plug-in issued some warning during the export process.

>There are some scenes that you can open and render in LW but cannot export to Maxwell.

The exported scene is built entirely in memory and only written to disk after it's complete. This means that if your scene is already using more than half the available memory space, it won't export. It's a limitation of the Maxwell SDK so it affects all the plug-ins and Studio.

> By enabling Motion Blur I don't get instances but copies. 

Motion Blur and instances cannot currently run together in Maxwell. So if Motion Blur is enabled in Maxwell Render Options, the plugin will automatically treat layout clones as standard geometry, allowing the render to show the desired motion blur (but not having the memory benefit from instances).

> Textures look bad when importing an MXM.

Mapping differs a bit in Maxwell and Lightwave, so the user has to bear this in mind when texturing.
MXS stores a reference number by UV map ([0],[1], etc...) and Lighwave gives a name to each one of them. They are related by the creation order.
This is especially important when importing textured MXM into Lightwave, as due to this limitation the textures have to be manually re-set after importing (otherwise the mapping is reset to planar).

> What does 'There is no MAXWELL_ROOT environment variable on this machine' mean?

 If you encounter this error when attempting to load the plugin, it means that either:

A System Environment Variable is a value that is available to every application on your machine. As such, the MAXWELL_ROOT variable points to Maxwell's home directory, and provides the ability for any application that wishes to locate Maxwell to be able to do so. So, it is very important that it is correctly set when you install Maxwell. Usually this is no problem, but there are always cases where installation is not completely successful, and it is possible that you may need to manually create the variable. Note that you should proceed with caution when accessing Environment Variables. If you alter Environment Variables without having very specific reasons, you may encounter problems with the applications that rely on them.

To view your System's Environment Variables, go to: Start > right-click My Computer > Properties > Advanced > Environment variables:

> Why aren't my Emitters working?

Maxwell Emitters behave according to real-world parameters. Therefore, it is necessary to: