[claus]

It seems to me that after the v2 upgrade it is almost impossible to work in studio if more than one render instance is working. Navigating and selecting objects is painfully slow and if you try to pan a scene some strange behaviour make the view "run away". I render 900x600 pixel images in "low priority" using all cores on

MacOSX 10.6.2
2x3 GHz Quad-core Intel Xeon
4 GB 667 MHz DDR2 FB-DIMM
Lots of HD space

Is there a setting I'm missing?

Claus

[jvanmetre]

Agree...the silence on this issue is hard to understand given the numerous times this has been raised. Apparently, those responsible for addressing this cannot be bothered...don't know what else to say. This only effects, as far as I can tell, Studio in OSX.

[Mihai]

Perhaps you're running out of memory? Can you try with a very simple scene, low resolution?

[jvanmetre]

Mihai-

I know you are trying to be helpful, but Claus' isn't alone on this issue. I have similar issues with scenes...not particularly large files. As I've stated in other posts, I've got 18 gigs of ram and experience maddening delays with studio...slection is painfully slow, scrolling windows even more painful. When I use the same scene in Vista on a 6 year old dell with 2 gigs of ram, Studio shows none of those problems. Studio, in OSX cannot be be counted on for productive workflow!

My apologies for hijacking Claus' thread, but many would like this issue addressed without having to hit someone over the head to acknowledge it.

[claus]

Mihai,

did a simple test on a very simple scene, 200x150 pixels, no multilight.

First of all the scene renders 20% faster using only 7 rather than 8 cores - I think this has been brought up before.

Then, launching 4 identical renders at the same time (by clicking 4 times on the render button) using anything from 2 to 8 cores will hit the performance of Studio making it impossible to work with during renders.

However, launching 4 identical renders at the same time using only 1 core will NOT hit the performance of Studio.

Tried launching in 32 bit mode, no change.

[claus]

I upgraded from 4 to 12 mb ram today, no difference.

Claus

[jvanmetre]

It's definitely not a ram issue from my perspective...probably path related.

[Fabius]

After having worked with 4 core Windows XP Pcs we now have bought new 4core iMacs.
But what a delusion after we have installed Maxwell and launch Studio: it is impossible to use, every command have a "pause" of many seconds, changing the views it's a suicide...
And now we have to return to our three years old Pcs to get some productivity... naaaa!!

What is the problem with OSX??

[claus]

Just read that a "competing product" is coming to the mac in a few months. Maybe it's a good time to fix the mac version of Maxwell?

[fv]

I have the same problem with a run away scene when panning or zooming. It seems the geometry dissapairs into space when you try to zoom in. But it happens sometimes, not all the time. When I focus regularly on the zoomed in geometry things get better.

Studio for me runs ok with a render in the background. I have a 8 core mac with 4Gb ram. But I am not expecting great performance. But its workable. No seconds delay though, but its a bit slower. Rendering material previews causes a crash most often.

Francois