Stability in 7.5?

[Kaostick]

I haven't had the chance to use 7.5, but I have had simiar problems (freezing, loosing undos) ever since I've been working with ClothFX in 7.. Kinda makes ya wonder.

[Ninjas]

I'm using 7.5 and I haven't had any extra problems with it over older versions

[Blue]

I've been using 7.5 for a bit and have not had any noticable difference in stability, or with the undo function failing.

[naik]

In my view

i had unstability in every Version of Max ( the Max 5 one was horrible!)

And in every Version, i got failures with the undo function.
I think thats a running gag brought over from Max 1... very strange that they didnt killed that.

Also i think, it really depends on your projects.
I know people, they say that max hasnt crashed ever - but when you look what they are doing with their max, than its obvious that doing
simple and basic stuff and never had "stressed" their max in order to see if its stable or unstable anyway.

regards

NAIK

[mummey]

Just out of curiousity, does anyone else save their files over a network while using max? For example, their autobackup is set to a drive that is on the network.

[naik]

Hmm, not really but i can tell you some "storys" about the autoback function.

During my time at a local 3D Firm, i recognized that sometimes the autoback function crashed max or freezed it due the saving process while i was heavily working on a mesh.

That was really annoying, i can tell ya...

Perhaps that and the fact that you use a network drive as saving source will append or even amplify this...

my two cents...

NAIK

[mahmoudcg]

sometimes i discover that there are no recent autoback files and the most recent is more than 3 hours ago or something
this happened to me more than once after a crash, although i saw it auto saving down in the status bar

about max 7.5, i beleive it does randomly change the texture tiling of materials and it also changes the material to faceted. but i haven't met stability problems

[artisanfx]

Hmm, not really but i can tell you some "storys" about the autoback function.

During my time at a local 3D Firm, i recognized that sometimes the autoback function crashed max or freezed it due the saving process while i was heavily working on a mesh.

That was really annoying, i can tell ya...

Perhaps that and the fact that you use a network drive as saving source will append or even amplify this...

my two cents...

NAIK

the best think is switch autsave off and just save after some peroid always you seq with increment number to your hhd
that will always save you better if somethimes max crashed
somethimes max also corrupted your last saved seq and you have then always a chace to jump back on the seq before

:)

[robinb]

In my experience autoback gets confused by manual saving and loading. The count seems to start the instant you start loading a file, so if it's a big one and takes say five minutes to load, and Max is set to autoback every five minutes, it'll reach its limit as the file finishes loading and immediately saves an autoback. Quite annoying.

Conversely the autoback counter seems to get reset by a manual save, so if you've got the autoback set to every 30 minutes and save manually after every 25, then it'll never get to 30 and won't save anything. I've had scenes I've crashed and found the last autoback was several days ago because I'd been saving more frequently than autoback was set to.

I've certainly had occasions where I've been forced to turn off autoback as it gets in the way, but never forget you've done that and remember it'll still be turned off when you work on another file. There's nothing worse than turning it off while working on a big file, remembering you've done that, then starting a new small scene, suffering a crash and wondering where all your autobacks have gone.
As for the original question about undo being purged. Yes it's always done that. There's a list of functions that are known to purge the undo somewhere or other. I don't think they always do. Things like assigning materials seem to do it occasionally. Here's one: take a multi-sub material, drag one of the sub-materials to the top level (where it says Standard). Look at the undo queue- nothing there. I can't remember any other specific examples I've seen, but it does happen from time to time. Quite inconvenient I must say.

[BradT]

>about max 7.5, i beleive it does randomly change the texture tiling of materials and it also >changes the material to faceted. but i haven't met stability problems

There was a hotfix for this. It has to do with using an outdated version of cebas.dlu. You can download it directly from autodesk. As for crashing during saves and autosaves, we managed to track that issue down and eliminate it studio-wide by changing video card drivers.

[Maven]

About a month ago I had very bad undo problems in which either it didn't work at all or it would work once but if I tried again I would get a crash. But for some reason it has gone away (knocks on wood). I didn't do anything except put SP2 on Winxp, but I think they are unrelated.

[mummey]

>about max 7.5, i beleive it does randomly change the texture tiling of materials and it also >changes the material to faceted. but i haven't met stability problems

There was a hotfix for this. It has to do with using an outdated version of cebas.dlu. You can download it directly from autodesk. As for crashing during saves and autosaves, we managed to track that issue down and eliminate it studio-wide by changing video card drivers.

What was the video card brand?

[abyjoe]

hi

my max 8 freezes while using cloth (garment maker ) and happens very frequently.

[BradT]

The video card brand was Nvidia. All of our machines had quadro based cards, ranging from 980xgl's at the low end and FX3400's at the high. It was a newer driver that caused us all the problems. We are now using the older 6.7.2.2 (as listed in the device manager) and the problem is gone. When we had the problem, it seemed to be related mostly to direct3D mode and using a scene with heavy geometry or viewport textures. The crashes would happen randomly whenever some action would force a viewport redraw, like saving.

[mummey]

Ok, good to know. We had issues with Direct3D as well, but it was nothing that serious. Switching to OpenGL fixed our issues, but not the crashing. :(

[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.