[JesperW]

The plugins memory management is not very smart, unfortunatly it seems to need a lot of ram...

Here's what I usually try: First of all, disable "Start Render", and press the render button as the first and only thing you do in a new Max session (after loading the model of course). Then open the generated .MXS file from the MXCL app.

If there is still not enough memory, you will need to break your scene down to parts and merge them in Studio afterwards.

[Mihai]

DPI doesn't mean anything when you're looking at a texture on screen, or want to find out how much memory it will use. It's the size in pixels that matters. You can have a 3000000dpi texture which is only 25x25 pixels. DPI only relates to printing.

[JesperW]

Texture size has nothing to do with it. It's all about the number of polygons.

The textures are not stored in the .MXS file, only a reference to the file location. (Actually, the Material is stored in the .MXS, as a copy of the MXM if you wish, but the textures are not stored in the MXM's)