Maxwell Render | Official public forum

ok, so I d/l the new version yesterday, and for the first time in a year really get frustrated with MWR.
lots of things go wrong here.
I removed all previous versions, trashed and emptied, only have 1.1 (and an archived 1.0 just in case). I rebooted. I set the license files correct, both in studio and in CL. I installed the new FormZ plugin.

what goes wrong?
- clicking the Render button in studio does nothing. (although doubleclicking a newly made mxs in the finder does launch CL).

- sometimes the top toolbar and the part above (with the minimize/close/maximize buttons) disappears, or it seems to have shifted under the menu bar. see item (1) in screendump below. this might explain following error in console:
QLayout::addChildWidget: QFrame "ooo" in wrong parent; moved to correct parent
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap

- I also get following console msg when opening any file, even one with just 1 object set at color middle grey:
QColor::setRgb: RGB parameter(s) out of range

- the preview refresh button in the material editor mostly is cut off partly, it is still clickable but hard to target. (see item (2))

- can't get normal emitter values anymore. the ball in the box has 1000 watt value, but renders very dark grey, with nominal camera settings, shutter 100, iso 100, fstop 8. (ok, this should probably be posted in the render forum, dunno)

- occasionally, MWR studio crashes, never did that since I installed rc5 in january.
QColor::setRgb: RGB parameter(s) out of range
QLayout::addChildWidget: QFrame "ooo" in wrong parent; moved to correct parent
QColor::setRgb: RGB parameter(s) out of range
QLayout::addChildWidget: QFrame "ooo" in wrong parent; moved to correct parent
QLayout::addChildWidget: QFrame "ooo" in wrong parent; moved to correct parent
Jul 6 12:42:45 G5HD80 crashdump[387]: fitisnais crashed
Jul 6 12:42:45 G5HD80 crashdump[387]: crash report written to: /Users/wimver/Library/Logs/CrashReporter/fitisnais.crash.log

excerpt from the crash log:
Host Name: G5HD80
Date/Time: 2006-07-06 12:42:44.439 +0200
OS Version: 10.4.6 (Build 8I127)
Report Version: 4

Command: fitisnais
Path: /Applications/Maxwell 1.1/mxstudio.app/Contents/MacOS/fitisnais
Parent: WindowServer [60]

Version: Maxwell Studio (???)
PID: 374
Thread: 4
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

- on other occasions, quitting studio fails, need to force quit the program (not responding). I think I can reproduce that:
I save my job (mxs)
I press cmd Q for quit
then this stupid (allow me) dialog box appears, asking if I want to save my job, it is stupid and totally non-mac since it should remember I just saved the job, like any other self-respecting app does.
so naturally I click the discard button, and not 'save' or 'cancel'.
and Dang, the program hangs.

if I can't find the answers to the above soon, I will have to reinstall 1.0 I am afraid... the announcement looked too good to be true.

thanks for your input

wim

wimver wrote:ok, so I d/l the new version yesterday, and for the first time in a year really get frustrated with MWR.
lots of things go wrong here.
I removed all previous versions, trashed and emptied, only have 1.1 (and an archived 1.0 just in case).

Hi Wim

sounds awful. 1.1 runs well here on G5 and OSX 10.4.7.
Did you delete the preference files as well? (user/library/preferences/fitisnais.plist; mxcl.plist; mxed.plist; com.maxwell-render.Recent Files.plist; com.maxwell-render.Recent Mxms.plist; com.next-limit-technologies.Maxwell Render.plist)

I do get some unruly console output too, but no crashes or odd behaviour so far.

QLayout::addChildWidget: QFrame "ooo" in wrong parent; moved to correct parent
prompted by selecting a material from within mxstudio.

QLayout::addChildWidget: MaterialEditor "MaterialEditor" in wrong parent; moved to correct parent
QLayout::addChildWidget: TinyMaterialBrowser "MaterialBrowser" in wrong parent; moved to correct parent
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
prompted by opening mxed.

I dont speak console. Is this maybe a permission issue?
Please NL have a look.

Thanks
Sebastian

Hi Dexel,

thanks for suggesting, I did all this, did it again to make shure, no good.

studio also crashes when I want to load a light object from library.
the rgb params out of range occur when loading the studio_m environment.

QColor::setRgb: RGB parameter(s) out of range
QColor::setRgb: RGB parameter(s) out of range
QColor::setRgb: RGB parameter(s) out of range
QColor::setRgb: RGB parameter(s) out of range
Jul 6 15:58:42 G5HD80 crashdump[680]: fitisnais crashed
Jul 6 15:58:42 G5HD80 crashdump[680]: crash report written to: /Users/wimver/Library/Logs/CrashReporter/fitisnais.crash.log

dunno, if it runs fine on your machine, it must be local here, but I usually am very proud to have a real clean machine, I only put (as little as possible) productive software on it, no junk.
I never had any crash issues with any program. I have been using macs since '84...

G5 1.8 Ghz DP - OSX 10.4.6

wim

Wim,
no consolation for you, but I get the
QColor::setRgb: RGB parameter(s) out of range
with studio_m environment too. Rendering works nonetheless without further console output.
And I also crash when loading lamp from library. Didn't check that before.
Not entirely your local trouble I assume. Definitely something for NL Mac dept.
S

I can also confirm a crash on adding a light from the library. And the undo commands dont seem to work after one inadvertantly misplaces a texture onto the wrong object.