Maxwell Render | Official public forum

This may be an OS X issue, but I can't be sure.

In 2.5.1 when I wanted to resume an MXI, I used to open Maxwell, click the resume MXI icon, select the MXI to resume, and Maxwell would ask the target SL and resume rendering.

Now when I enter the target SL (which is definitely higher than the SL it is rendered to) and click OK, I get the message "Resume MXI File Error:
[file location] is not a resumable MXI File."

When I click OK, I get the console message: "ERROR: - Resume MXI File Error [file location] is not a resumable MXI File. cannot be resumed."

If I open the MXI straight from Finder click "Render" and select "resume", Console tells me the CPU ID used to render the image and then Maxwell does nothing.

If I want the MXI to resume I have to open it in Maxwell from Finder, then select resume MXI in the menu bar, find the MXI in the dialog box and then it works.

It's worth saying that when I open the the MXI straight from Finder, the Time parameter is 10, whatever the original setting.

OSX 10.6.8

That happened to me too (windows7 64). In my experience:

-hit resume button and select mxi > mxi not resumable
-load mxs, hit render > asks if I want to render, resume or cancel > hit resume > it works.

Please can a mod to move this to Bug Reports > Maxwell Render, thanks.

Seriously guys I can't even pause and resume a render without a roundabout way of resuming now, and I can't find a way to pause, adjust settings e.g. threads (something I often change to give me some CPU for other applications) and then resume. Even changing the settings, saving the MXI and then resuming gives the same results.
You were kind enough to move the thread, can you take the time to confirm/deny this behaviour?

slightly off topic... but you don't need to stop a render to adjust the core count. just remove (or add) some cores in windows task manager from the "maxwell.exe" while it it rendering.

numerobis wrote:slightly off topic... but you don't need to stop a render to adjust the core count. just remove (or add) some cores in windows task manager from the "maxwell.exe" while it it rendering.

JamesColeman wrote:OSX 10.6.8

I also confirm the same behavior here, on both win and osx. Like Fernando said, you might just want to use Open MXS (pretty convenient, if your MXS is in the File > Recent MXS list), instead.

JamesColeman wrote:

numerobis wrote:slightly off topic... but you don't need to stop a render to adjust the core count. just remove (or add) some cores in windows task manager from the "maxwell.exe" while it it rendering.

JamesColeman wrote:OSX 10.6.8

Bizarrely, I tried pausing and resuming today (forgetting the bug) and it worked. Don't think I did anything differently, will report if it happens again.

Haven't come across this yet in 2.6.10, will let you know if I do, but for the moment it looks fixed.

Just a quick note to say that I think this bug is only rearing its ugly head when an mxm is imported to use in the scene, even if it is embedded in the scene and not referenced. Also worth saying that I think I'm seeing this bug more on my desktop than my laptop. Exactly the same software versions so I can't explain that discrepancy yet.