Could someone confirm that this causes an error (using max 2010 32 bit)?
- Create a sphere
- Add a turbosmooth and edit poly modifier onto the sphere (turbosmooth is on top)
- Execute this: addModifier $ (point_cache()) before:2
- This returns in the listener ** system exception **
The modifier panel is now messed up, and no matter what it won’t display any data. The only way to fix the modifier panel is the restart max.
Hey Jason… shakes fist …I tested it on my laptop for you, and I didn’t have an issue in (Vista) 2010 64 bit.
Edit: I don’t have 32 bit installed on this machine…
This starts looking like a Prime Focus channel…
Anyway, it does indeed cause system exception in 32 bit Max 2010.
Does NOT do that in 64 bit though.
Also, to “repair” the modifier panel, just call
resumeEditing()
as it has been suspended in the process.
^ Prime Focus For the Win!
…Jason, as a workaround you could maybe make instances of the top two modifiers in memory, remove them from the objects, add your pointcache, then reapply the top two modifiers…?
See ya tomorrow!
…Jason, as a workaround you could maybe make instances of the top two modifiers in memory, remove them from the objects, add your pointcache, then reapply the top two modifiers…?
… Farnsworth!! Was thinking the same thing. I’ll give that a try.
Also, to “repair” the modifier panel, just call
resumeEditing()
Thank you!! I restarted Max many many times today because of that.
Keep it real, PF folks.
Possible solutions:
oldState = $.modifiers[2].enabled
$.modifiers[2].enabled = off
addModifier $ (point_cache()) before:2
$.modifiers[2].enabled = oldState
select $
or
oldSel = $
clearSelection()
addModifier oldSel (point_cache()) before:2
select oldSel
or
max create mode
addModifier $ (point_cache()) before:2
max modify mode
Unfortunately each of those returns a system exception. So far I only got Ian’s approach working by rebuilding the stack (fun!).
Here’s something interesting though. It seems like it’s all in the ORDER of how the modifiers are added in. For example, if you add an edit_poly THEN the turbosmooth, there won’t be any system exceptions. However if you add a turbosmooth then an edit_poly, move the edit_poly below the turbosmooth, it’ll cause it to error.
I posted them because they worked for me, but it is possible that I created the modifiers in the wrong order as you mentioned above…
Oh well…
I’m thinking that’s what may have happened too. Sneaky sneaky!
Don’t they let you Prime Focus guys talk to one another at work? You need to sneak out to the internet to do it.
Well, I can talk to Bobo via jabber, but that Jason guy is nothing but trouble. They keep him locked up in the corner for a reason.