3DS Max 2009 - Isolate Script Woes

Ace-Angel

Hey to all, how is everyone doing today?

Anyone knows what up with this error in here?

---

MAXScript Rollout Handler Exception

---

-- Unknown property: "IsInstance" in undefined

---

OK

---

It then highlights the whole part here:

adtStyleIfc = styleMgr.IsInstance n
if (atStyleIfc != undefined )then
(
result = (adtStyleIfc.GetCompositeStyle() == adtStyleIfc)
)
)
result

Last thing I did to Max was use 3DS Clean by Perna and crew, but I'm not sure if that is case. Any helpies here?

Also, Win 7, Admin rights, blah blah blah, yeah, I did all the routine checkups.

renderhjs

I had that very same error a year or 2 ago, didn't happen again so I never looked into it futher. I assume that the garbage collector of maxscript chucked that variable to dispose when it was idle for a long time or not in use anymore. Or another script used the same variable in the same root space overwriting it and causing the GC to sweep it.
Either way check if it still persists after the next time you start max

Ace-Angel

Yep, it still there, and it doesn't allow me to isolate my mesh even, just throws up the listener with error and calls it a day.

Also, when the Isolate Box is open, it will keep on throwing at me errors till I close the Box.

So yeah, double jeopardy as they.

leechdemon

I've had this happen in Max2010 a lot lately. I've been playing around with scripts more, and assumed some sort of conflict. It, itself, doesn't seem to crash anything, but if I just ignore I get crashed soon after. Usually I just save and relaunch, and it works again when I'm back.

Ace-Angel

This perplexes me even more, the only tools I have installed for Max 2009 is ShaderFX and Viewport Grab 2.0 alongside the batcher 3DS Clean.

Restarting doesn't fix it, and I can't even find any tools which Max loads which are even remotely close to the issue I need to fix.

Oh well, I'll live.

leechdemon

ShaderFX? Hmm. I changed to the DX from OGL for my viewport renderer, and recently started playing with "Show Hardware Map in Viewport". Maybe it's something to do with fancy shaders?

Ace-Angel

Hmm, that could be, I'm not home now, so I'll drop and check tonight...I mean it shouldn't be, but you know, Autodesk *insert 80's audience laughing*.

Ace-Angel

Note: Solved issues by restoring ADTObjects and AcadBlocks to stdplugins. Cheers.

Minos

!Bump!

Ace-Angel wrote: »

Note: Solved issues by restoring ADTObjects and AcadBlocks to stdplugins. Cheers.

This is so funny. I was having the problem so I googled for the max script line highlighted on the error message and found this thread.

I had removed the very same plugins from the stdplugs folder to see if max loaded faster. Guess there's a reason Max doesn't allow you to unload plugins via the plugin manager tool

Anyway, just wanted to thank you for posting the solution.
Cheers

Ace-Angel

Cheers, and yeah, Max can be weird like that

Bruno Afonseca

Oh nice! I'm having the same problem as well. Reinstalled max + 3ds clean and that kept happening. I owe you two a beer!