[umdrehung]

Hello there,

I just want to report, that Mxed and Studio crash when I try to export an mxm file.
This happens since I upgraded from 10.6.8 to 10.7.

Can anybody reproduce this problem?

Best regards
Umdrehung

Maxwell 2.5.1
Mac OS X 10.7
2.4 GHz Intel Core 2 Duo
8 GB Ram

[el.mustafa]

Same here
Mxed running on 10.7

I get a memory allocation error EXC_BAD_ACCESS (SISGEV)
I suppose that means there is little that can be done until the programmers
iron out the bad pointers.

However mxm materials exported fine via Maya plugin.

Regards
El

[umdrehung]

Thank you el.mustafa. So let's wait. Maybe someone is reading our conversation.

I'm using the sketchup plugin and can not avoid the problem:
older mxm files are greyed out in the dialog box of the plugin, when I want to choose them.
When I want them to be eligible in the plugin, I have to open the older mxm Files in Mxed oder Studio and export them once.
And then boom - Mxed or Studio are crashing.

Best regards
Umdrehung

[JamesColeman]

10.7.1 has been released (http://9to5mac.com/2011/08/16/mac-os-10 ... wnloading/) any news if the problem's gone? (I haven't updated to Lion yet).

[umdrehung]

Updated to 10.7.1 - no change.

Studio and Mxed are still crashing when I try to save or export an mxm-file.

Umdrehung

[Peder]

Is there any ETA on a fix for this? I need to consider the painful return to Snow Leopard otherwise...

[umdrehung]

@Peder

Good question - I hope nextlimit has already tracked the bug.

Umdrehung

[nachob]

Hi all,

We are actively working on finding a solution for this bug, we should have a solution soon.

nachob

[umdrehung]

Good news - thank you very much nachob.

[nachob]

Hi all,

This problem is solved now:

Maxwell Render bug fix for OSX Lion (version 10.7) users
http://maxwellrender.com/forum/viewtopi ... 94&start=0

[messire]

hi
Upgraded both Lion and MR
Still got bug crashes when saving mxm's in maxwell editor...
Happens when i try to fix paths for mxm's that have a problem when used in sketchup ... every time the save as command is used, it crashes the Mxed..
any clue?
Nils


short extract from the bug report:

"Process: Mxed [1112]
Path: /Applications/Maxwell 2/Mxed.app/Contents/MacOS/Mxed
Identifier: com.nextlimit.Mxed
Version: ??? (2.5.1)
Code Type: X86-64 (Native)
Parent Process: launchd [124]

Date/Time: 2011-09-28 11:14:57.838 +0200
OS Version: Mac OS X 10.7.1 (11B26)
Report Version: 9

Interval Since Last Report: 69674 sec
Crashes Since Last Report: 2
Per-App Interval Since Last Report: 1142 sec
Per-App Crashes Since Last Report: 1
Anonymous UUID: 268A5384-7AE1-4A67-98DB-708449485A62

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: 0x000000000000000d, 0x0000000000000000

VM Regions Near 0:
-->
__TEXT 0000000100000000-00000001002cf000 [ 2876K] r-x/rwx SM=COW /Applications/Maxwell 2/Mxed.app/Contents/MacOS/Mxed