Max 7 - slow undo?

Rick Stirling

Has anypne else here had a problem of slow undos in Max 7? Everything else is fast, but the undo is taking ages. Its affecting a few of us here.

In the UV editor it can be up to 20 seconds for an undo to complete.

Megaphobema

Interesting....neither of the Maxes I use on two different computers does that to me.

Are you sharing a license on a network by chance?

Mojo2k

reset xforms?

Jay Evans

ya I've had that problem and have yet to figure it out.

MoP

Mine does that sometimes, but it seems to be only when I have DirectX shaders in the viewport.
At least, that's the only thing I can find in common with the few files that get a slow undo - most of the time it's perfectly fine.

Rick Stirling

It is the direct X, but you don't need to be using Direct X materials to get the slow down. Switching to open GL fixes it, but then when I do add spec and bump maps I can't see them. Great.

Steve Green

I've just had this as well - at first I thought it was a bug in the recent service pack, but I guess not.

Not sure if it's the DX shader itself or the emulation of DX shaders for standard materials.

- Steve

Steve Green

It seems to be related to the 'Show DX in viewports' flag for standard materials. If this is ticked in the MatEd then it slows down undo to varying degrees, even if the material isn't assigned to any object in the scene.

The DX9 Shader doesn't seem to have this problem, so a possible workaround is to save out the FX file while in the standard material, turn off the flag, and then do a new proper DX9 Material using that FX file.

- Steve

MoP

I have a theory that it might be something to do with Max creating "Shell materials" or backing up existing materials when using render-to-texture... but it's far more likely that it's just the viewport shader, as Steve says.

Steve Green

It could be an nvidia only problem - I'll try it on an ATI based machine tonight, see what happens.

Cheers

Steve

MoP

Nah, I have an ATI card, and I've got this problem from time to time. Again though, only when working with DirectX shaders and render to texture.

Steve Green

Cool, thanks for the info - I'll fill out a bug report, see if anything comes back.

Cheers

Steve