Last night my Undo command suddenly stopped working. I rebooted computer. Tested on the small file populated with standard primitives only - doesn’t work. Reloaded original Default.UI. Doesn’t work.
The only thing I can think of - I used Hold/Fetch command that I almost never use.
Is there any setting that could have been deactivated by mistake?
Thanks,

Ewa

Customise > Preferences > General (tab) > Undo Levels. That’s the only one I can think of offhand.

Only other thread I can find specifically on this issue is this one.

Max 4.2 through 2013.
XP-64 (SP2)
NVidia 9800GTX-512 (Driver 266.58).
Core 2 Quad Q6600 2.4GHz, 8Gb Ram, DX9.0c.

Thank you. It is set to 20 all the time. Since my posting, I found some other threads of users complaining about some commands coming and going as they please (Undo - one of them).
I just restarted Max for the n-th time and the command works in this session.
Is it a bug then?

Difficult to say - I’ve not had it happen to me. There are a fair few things which will clear the undo stack, though not just creating a few primitives which some have reported.
If we (anyone) could find a reproducible sequence of events we could report it.

Max 4.2 through 2013.
XP-64 (SP2)
NVidia 9800GTX-512 (Driver 266.58).
Core 2 Quad Q6600 2.4GHz, 8Gb Ram, DX9.0c.

Does anyone out there know how to restore the undo command or return the undo stack recording?

My workaround:
cltrl-alt-h to HOLD a scene
ctrl-alt-f to FETCH the previous scene

Disadvantage: you have to remember to HOLD something that you might want to return to.

Thanks for the input. That particular time I would have had to do it after every command.
It happened again but it didn’t last that long.
I need to add, that both times I was animating Biped using Auto Key. The moment I changed any position - I couldn’t undo if that wasn’t working. My painful workaround was saving at each good step and exit without saving at the bad one. (You may guess: I am not an animator...)

same problem to me. I think it happens when animate is on. I meet that bug in my first max2009 animation and never before when working for still render.

One reproducible way to lose the undo command is to start creating a box, and just before you place the final click to set the height, right-click (which should simply cancel the creation).  This often works--but not always.  This particular action is definitely NOT what is causing my recent undo problems, but there could be some other innocent keystroke that is causing it.

--3ds Max Design 2009 64bit, Direct3D 9, Win Vista Premium 64, 3ghz quadcore Xeon, Quadro FX1700--

I still have the problem with loosing undo command and can’t find the pattern. I continue to work in the files with biped animations.

I have been having the same problem. It is extremely frustrating. Undo will work for a time - 10 min, an hour, 3 hours - but it tends to dissapear on me. Like finding something in the last place that you look for it - of course I only notice that it is gone when I need it and it’s not there. I have had it return after going to a perspective view and moving around. But that only works sometimes. Sometimes it returns with as little known reason as its leaving. Sometimes there seems to be nothing short of a restart of the software that will fix it, and then I may have to do the same thing again in a few minutes. This is not so bad sometimes - but other times after a complex bunch of sub-object modeling - it is quite a pain in the a$$. However you look at it - it is a big waste of time and mental energy in my work day. The main thing that sucks is not knowing what is causing it - so that it may at least be avoided.

I have been doing 3D for 20 years now and have used many packages (including Maya since it began) so I am fairly experienced, though I have only been using Max for about 9 months. This is a very annoying little bug.

I am using a Dell Precision M90 / Centrino Duo / nVidia Quadro FX 2500M w/ 512 megs VRAM / 4 gigs RAM / XP Pro 64 / Max Design 2009

- Michael Pond / Applied Software, Atlanta