MAXScript Callback script Exception: -- Unknown property: "modifiers" in undefined

[Anonymous]

ok so every time i click on an object in my scene these error pops up .. Idk what caused it.. max crashed the other day and it's been happening ever since then ..

I'm also having an issue rendering it says mental ray has encountered a fatal error and must close.

This is rather frustration especially since i don't know what caused it

[Steve_Curley]

What version of Max?

This is (probably) an installation issue, tied up with windows permissions. Either the Installation forum or the specific one for your version of Max would be far better places than this Maxscript forum.

Post back and let me know where you would prefer the thread moved to - please don't create duplicate posts as I'll have to run around deleting them (duplicates break the forum rules).

[Anonymous]

I also have this problem, max 2011 it's a Nvidia physx plugin issue although I don't know what the cause of it.

[stigatle]

same as above.

[Anonymous]

I've just started getting this error since upgrading to MAX 2011 with the nVidia PhysX driver... no rendering problems though just this error on file open.

[PiXeL_MoNKeY]

The problem is caused by groups and the Physx callbacks. There are 3 solutions:
1) Don't use groups.
2) Uninstall Physx.
3) Edit the px_globals.ms file.

For the last one this may fix it, but hasn't been extensively tested.

WARNING: Alter at your own risk!!!

1. Save a backup of px_global.ms (located in C:\Program Files\Autodesk\3ds Max 2011\Scripts\nvpx\) as I won't be responsible for any issues it may cause
2. Open px_global.ms in theMaxscript Editor.
3. Change line 545 (of the 2011 AP version) from:

if isgrouphead(node) then modRB = node.children.modifiers

To:

if (isgrouphead(node) AND isValidNode(node.children)) then modRB = node.children.modifiers

4. Execute the script.

So far I have seen no adverse effects, but have done only limited testing.
-Eric

[jeff]

The advice about not using Groups is probably good even without PhysX !
I've had fewer headaches using hierarchies and/or containers instead of groups.

-jeff

[Anonymous]

bah.. same thing is happening again.. unfortunately not using groups isn't an option for me as there are alot of groups in the project i'll see about editing the physx code.. good to know i'm not the only one with this issue


however i modified the script and now all seems well so far however you have an extra )in there

[Anonymous]

I've just started getting this error since upgrading to MAX 2011 with the nVidia PhysX driver... no rendering problems though just this error on file open.

Me too. Luckily this didn't affected my 3ds Max & Vray performance. Not a big problem but i hope that can find a solution to fix this issue.