Notifications
Clear all

[Closed] editable poly is non-editable??

This is one of the more cryptic error messages. An editable poly that´s a non-editable poly?

Does anyone know what´s going on?

>> MAXScript MacroScript Error Exception: – Runtime error: EPoly operation on non-Editable Poly: #($Editable_Poly:Box04 @ [214.396729,-396.800507,131.264450]) <<

6 Replies
1 Reply
(@bobo)
Joined: 11 months ago

Posts: 0

Are you sure you are operating on the OBJECT and not an ARRAY of selected objects?
See the #() around your Editable_Poly? How have you acquired the selection and what is the code that causes the error?

I would guess that you used something like getCurrentSelection() to get the selected objects and then attempted to apply an operation to the resulting array instead of the objects inside …

But I have been wrong before, so who knows.

Hi Bobo… Thx a lot for your reply!!

convertToPoly kasse
   max modify mode
   subObjectLevel = 4
   Polyop.setFaceSelection kasse #(6,5,4,3)
   print kasse
    It must be me using the wrong syntax here. It´s the polyop. that suddenly turns kasse in to an array? Can you tell me what I´m doing wrong, it´s probably VERY basic....

hmmm… Using $ instead of “kasse” solves the problem.

kasse was originaly derived from

kasse = startObjectCreation box returnNewNodes:#first

maybe that causes the trouble??

Yep, this method always returns an array if returnNewNodes: is set to true or #first. It is NOT explicitly mentioned in the method description in the Help, but just calling it makes it obvious that the result is always an array of nodes, even when a single one is returned.

So you should use kasse[1] instead to get the first and only object from the array.

Hi Bobo

Thx loads

( One ) reason I was so confused is this: “print kasse” will not yield an array, but just “kasse” will ??

someArray = #(1,2,3)
print someArray –always prints the ELEMENTS of the array.
format “%
” someArray –will print the actual array.

So it is to be expected.

Thx again Bobo… This forum beats everything regarding “how to MaxScript”!

So it is to be expected

Yep… And now I know