[mashium123]

When you specify a "working folder" in the "file options" tab, the bitmap and the mxs-file are named as your "Scene name" and saved in the specified working folder.

But the mxi-file is saved in the application folder (...\Next Limit\Maxwell\) and is named default.mxi.

To grant that all three elements are named (also the mxi file) and saved in the previously specified "Working folder" one has got to click the "Command Line" tab and type in the wished working folder.
Like this:

-d -p:low -mxi:"Drive:\folder1\...\YourSceneName.mxi"

(The quotation marks are for the case, that there is a space in the folder names)

Is this wanted behaviour?

[Becco_UK]

mashium123: I hadn't noticed this but just checked and you are correct. The mxi file gets written as 'default' in the main Maxwell folder.

With Maxwell 1.1, using the Cinema plugin, the mxi got automatically saved at the image location adopting the image name. I prefer that method to keep all project files in the same location.

At first glance it looks like a small problem but then you realise that this has the potential to overwrite important work causing hours of re rendering.

[Tyrone Marshall]

Hello Mesut,

Its not proper and should save all in the same working path. Thanks for bringing this one to foreground.

[stu.dio]

Would this have anything to do with rendering any cinema4d file straight from cinema to maxwell. then crashing cinema?
I mean - The process at the moment - I'm doing is to see if we don't have to re-texture everything within cinema (placing maxwell tags every where) - so I open "a file' add a maxwell settings object - write in the image file name - choose the working folder - hit render AV - it works for a second or too - then boom - cinema drops out. I have a feeling it's texture related as a few procedurals/texture maps get written but never the scene file.
The same thing happens with write mxs. Or am I doing something quite wrong here?
It works fine with a scene and no textures. - very fast - very pleased - well done BTW
I thought it may be some old 3rd party tags they may be causing the problem (as they have crept in from old scenes such as jenna tags left over after making an object editable - but no - after deleting them - the same problem) - I am now in the process of deleting texture by texture until it works - as I know it works without textures.

I have my working folder within my jobs folder away from Maxwell (currently in apps folder) - all my textures ie library is in a collective 3D library then in sub catagorised folders ie wood / metal / hdri etc

SYSTEM - Mac 10.4.9 - 2 x 2.66 Dual-Care Intel Xeon
SOFT - Cinema4D 10.1 - Maxwell 1.5 + cinemaxwell_1.5g7ub

[Becco_UK]

stu.dio: Instant Cinema crashes with the new Maxwell plugin are very often caused by using two or materials on one object. There are plenty of recent threads to describe the problem. That, together with the inability to use new custom Maxwell materials directly from the Cinema plugin make it very unuseable at present.