Object Scene ID?

Object Scene ID?

theoG7GJE
Participant Participant
12,181 Views
9 Replies
Message 1 of 10

Object Scene ID?

theoG7GJE
Participant
Participant

When using some plugins - Datasmith for example, when exporting your scene the status bar at the bottom left will show a % and a number like 18% 282/1562. is there a way to find out what has been assigned as the 282th object to be processed?

 

Do all Max items have a scene number assigned to them?

 

I'm having issues with exporting for Datasmith and this 282th object is crashing Max every time without warning and no error messages. It was working fine and suddenly it doesn't work at all.

0 Likes
12,182 Views
9 Replies
Replies (9)
Message 2 of 10

CAMedeck
Advisor
Advisor

Well, I can't answer your question about knowing which object is number 282.  But you could always try the old method of eliminating some objects from your export until you narrow it down to the culprit.  

 

My method, when having export issues, is to Export Selected after selecting the first half of the objects in the Select Objects list.  If that works, do the second half.  If they both work, then try selecting all and export selected.  If either half fails, then start reducing the number of objects selected and work your way through the list until you find the offending object.

Chris Medeck
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature

0 Likes
Message 3 of 10

wernienst
Collaborator
Collaborator

Here is something else you could try (success not guaranteed 😏 )

Open the Scene Explorer and select Display/Configure Advanced Filter. Select Property: Handle, Condition: Equal To, enter 282 as Reference Value. Click Add and then OK. Now a node with handle 282 is selected, if existing.

wernienst_0-1718644589546.png

This is NOT the consecutive number!

0 Likes
Message 4 of 10

theoG7GJE
Participant
Participant
This is what I ended up doing to try and find the objects, its just a pain to have to do. Especially when Max closes every time it crashes! I was hoping that knowing the export crashed at 282 there might have been a way to find that reference some how.
0 Likes
Message 5 of 10

theoG7GJE
Participant
Participant
I tried, unfortunately no results show up. Thanks for the suggestion though!
0 Likes
Message 6 of 10

wernienst
Collaborator
Collaborator

Ok, scripting is next. Try this:

clearSelection
objNr = 282 -- object nr in question
q = 0
for i in objects do (
    q = q + 1
    if q == objNr then (
        select i
        print i.name
    )
)

If existing, the object is selected and its name is shown in the Scripting Listener.

Message 7 of 10

theoG7GJE
Participant
Participant

Hi I tried to do this but ended up with a syntax error

-- Syntax error: at ), expected <factor>
-- In line: )


I think this might have been my mistake. pasted it into the listener and not into scripting editor! it is indeed now selecting objects! only its selecting hidden ones that arent being used in the export process so im going to delete all hidden and see what i can find after.

0 Likes
Message 8 of 10

theoG7GJE
Participant
Participant
unfortunately this isnt selecting the same object datasmith is selecting. it looks like datasmith breaks it up. theres about 500 objects selected for export this time and it begins by exporting 176 of something. materials? textures? object? i dont know. zero luck getting a response from EPIC forums about what its processing in Max.
0 Likes
Message 9 of 10

wernienst
Collaborator
Collaborator

Sorry to hear that. I could modify the script so that it is counting visible objects only, but I'm afraid this won't work either.

0 Likes
Message 10 of 10

theoG7GJE
Participant
Participant
I found out its because there might be 500 objects but because of instances, it ignores some. so of the 500 only 178 needed to be exported. this throws off the selection but i narrowed it down manually to 10 objects. then I used this script and it actually did select the one that was causing issue! 6th object of the 10.
0 Likes