Modo freezes with high polycount models?

[seneca]

Are you running on mac or pc?
What video card/drivers?
Do you have autosave on? (how long does it take to save?)

[StephanD]

Disable autosave or give it a longer amount of time...

I once had this exact problem in another software.In fact,it was worse because I had set the autosave too short and it didn't even finish saving before re-attempting.That was with a massive 300K something mesh though.

[helicopterr]

Okay I will give that a try. I guess auto-save will have to go....

[Beamtracer]

Yeah, I've just started noticing this, but only with high-poly models. Modo pauses (on the Mac version you see the beachball), then it eventually comes good again. Despite this, OpenGL performance for high-poly models is really good, and I can rotate them smoothly compared to some other apps I've used.

I thought reducing the 'patch display level' might help, but any effect was just minor.

http://img134.imageshack.us/img134/8055/modoprefs2ex.gif

[MadMax]

I almost dread responding to problem posts after the last time I suggested that maybe drivers/hardware was at fault and got attacked and insulted for it, but..........

For me, 20k is a very tiny model. Most of my current projects are more like 350k or higher. 20k is NOT a high poly count model. Modo should eat that for breakfast.

what hardware are you running?

driver versions?

video card?

PC or mac?

You might also dowload an app called memtest86 if you are on a PC and test your ram. I had squirrelly results in LW with freezes once, it turned out to be a bad dimm. worked fine most of the time, occasional hard freeze, then go along like nothing happened.

memtest86 identified the bad ram that APPEARED to work just fine with everything else.

[seneca]

I almost dread responding to problem posts after the last time I suggested that maybe drivers/hardware was at fault and got attacked and insulted for it, but..........


Yep. I totally agree with you. I really don't like people pushing the blame on video card manufacturers. The only reason why *I* asked that was because if he's using a MAC, it's probably the terrible beachball problem. If he's using an nvidia card, it's probably because he's got new drivers. I personally had this absolutely terrible thing happen when I was using new nvidia drivers.. I'd get horrendous pauses for about 30 seconds to a minute every 4 minutes. There was also a 25% chance that modo would crash after the pause anyways. (of course, it had nothing to do with autosaves or big meshes or anything, and once I went back to the old drivers again, the problem went away. And I got that problem with *TWO* different nvidia drivers.)

So there are those two problems I know of, and if it's not those two, then my guess is that it's an autosave problem, where the mesh takes a really long time to save for some reason.....

[MadMax]

Yep. I totally agree with you. I really don't like people pushing the blame on video card manufacturers. The only reason why *I* asked that was because if he's using a MAC, it's probably the terrible beachball problem.


Generally I prefer to place the blame for problems accurately. Unfortunately you get people will say a program is buggy, they need to fix this or that, and the problem isn't the application being used at all.

In this case, there is definitely a technical problem afoot. But you have to step through the ropes to figure it out. My favorite was in techs upport people would call and say "I already checked that" and didn't want to listen to what they were being told, only to find out that what they had already dismissed was the answer.

[StephanD]

A few years ago I fried an Oxygen card and checked it throughly before with their techies and I was right.

Still got denial until the very return of the card,one of them kept expressing how he hated when users blamed the video card when it was probably a mobo or mobo driver problem at hand.

Took 3 months to get another back but I still trust their products,go figure.

Glad I shared that wih you guys. ;)

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.