[Daniel Hruby]

Just had a Studio crash while I was sitting motionless looking at the screen, doing nothing at all

This happened to me once. It turned out I just needed to comb my hair.

All kidding aside, I also had a couple crashes yesterday, with no apparent REPEATABLE cause, except that I was refreshing material previews when it happened.

[J. Israelsson]

I have searched my computer for said framework but haven't been able to find it. I have SketchUp Pro installed on my Mac. So unfortunately I cannot test this possible connection.

Regards,

Johan I

[xenophya]

Still having massive problems with studio crashing, also now getting MXCL crashing as well

I've got console crash reports if it helps you to solve this . . just ask and I'll email them to you.

using MXWR 1.6.1 on OS X 10.5.2. on new mac pro 2.8Ghz x 8 cores, 10gb Ram. Don't know wether this makes any difference - but using a software RAID volume as storage?

Studio is totally unstable, touching anything to do with output paths kills it 90% of the time. This is hugely frustrating and getting in the way of work now. Please fix this soon !!!!!

thanks, any guidance or thoughts on this appreciated.

david

p.s. not using sketchup - do not have that xerces framework to my knowledge.

[Mattia Sullini]

xenophia, i am running maxwell on an identical machine with less RAM and no RAID disks, i do all my setup in studio and in the past week i worked on it for at least 6h per day, but i had no crashes at all....

[xenophya]

want to swap machines???

*sigh* mxcl just quit on me 20 mins into a render. oh well time to restart it

thx for reply

d

[superbad]

I know this doesn't help you any xenophya, but I have never had an MXCL crash that I can remember. With Studio, of course, the crashes are impossible to forget.

[J. Israelsson]

Now I've almost had it. It is almost half past two (am) and I'm getting angrier by the minute. The Studio crashes are serious and occurring all the time.

Since NextLimit refuses to release the updated SketchUp plug-in which supports instances I have to manually add a lot of exported high-poly trees but I can't add as many as I want because of Studio crashing when trying to save the MXS and Studio having decided I have added too many.

But I have come to accept that but then I stumbled into another problem. I have added an HDRI sky (which I always have to enter the URL manually since the browsing also always (99%) causes a crash. I then accidentally switched to Physical sky and happened to save the MXS with that setting and when I reopened the file to change that back it had lost all the URLs to my HDRI-file but now I can't add them back at all probably because now I have all the trees already imported taking up memory. CRASH CRASH CRASH remove all trees, add URL CRASH. So I have to start all over to reassemble the file.

But the most irritating in all this is the complete silence from NextLimit. It is really irresponsible of NextLimit to be this ignorant in regards to support issues.

Sincerely,

Johan Israelsson

[jespi]

Hello Israelsson,
How many polys have your scene? And also which is your hardware?.

[J. Israelsson]

I'm on an iMac 2.8 with 4GB of RAM and Mac OS X 10.5.2. MXCL reports the following scene statistics:

Geometry:
- Num Meshes: 139
- Num Triangles: 5306096
- Num Vertexes: 5167724
- Num Normals: 4294731

Which to me doesn't sound that much. But I am sure that most of my problems is memory related since when I run Terminal and top while working in MXST and see the memory requirements go up for every added group of trees an also it temporarily goes up a lot when saving the MXS-file. I KNOW that instances will solve some of my problems but I have not access to the new plug-in for SketchUp for Windows yet. (My SketchUp-model is on an Windows machine and I haven't had the time to migrate it to my Mac since it would take a lot of time to just find all the material links in SketchUp since you don't have a list of any kind but have to go through your entire model and search for Maxwell materials applied).

The other main issues I'm having have been covered in this thread. Its the fatal instability of MXST that adds to my problems since I have the workflow I have. When I have access to instances I hope that I wont need to use Maxwell Studio that much.

As it is now I can just open up MXST, load an MXS-file and do no more. After some time the MXST may crash all by itself. One theory I have is that the NextLimit programmers have added a bunch of really stupid design ideas like having a constant listener connected to the HDRI URL input field that constantly tries to detect if a complete URL has been added. When I write the URL manually, as soon as i enter the final letter in the URL MXST freezes for a while and loads the HDRI. I dont have to klick a button or even exit the input field så there must be a listener that constantly check to see if there is a file present in the constantly evolving URL. Really, really stupid design decision and should be removed. Firstly no file input field usually work like this and the amount of processing would have to be too great compared with the benefits and lastly it is uneccesary in the first place since most people (I guess) uses the browse button and file dialog anyway (wich I cant due to contant crashes).

Phew that was long. I would hope that a representative of NextLimit would read this and comment and let us know what they are doing in order to alleviate the problems.

Regards,

Johan Israelsson

[superbad]

Oddly enough, I am using Studio today for the first time in a few weeks and it is eerily stable. I am able to change the tile value multiple times in MXED without crashes. Did an OSX update fix something?