Re: Persistent objects ids

2013-06-05 Thread Michal Doniec
: softimage-boun...@listproc.autodesk.com] *On Behalf Of *Ciaran Moloney *Sent:* Tuesday, June 04, 2013 3:55 PM *To:* softimage@listproc.autodesk.com *Subject:* Re: Persistent objects ids ** ** Yes, you're right...I can reproduce a change of ID when deleting an object and re-opening

Persistent objects ids

2013-06-04 Thread Michal Doniec
Hi, Is there any obvious way I am missing which would allow me to identify objects in the scene, but not by name? Something like ObjectID, but persistent between scene saves and loads. I can generate UUID or something similar using ObjectAdded event and store custom property but I'd rather avoid

Re: Persistent objects ids

2013-06-04 Thread Sandy Sutherland
Create an annotation and write a ID into that - we used that in our asset system, worked fine for us. S. On 2013/06/04 12:49 PM, Michal Doniec wrote: Hi, Is there any obvious way I am missing which would allow me to identify objects in the scene, but not by name? Something like ObjectID,

Re: Persistent objects ids

2013-06-04 Thread Michal Doniec
That's what I've been doing (I use properties instead of annotation but the principle is the same), maybe there is no need to change after all :) On 4 June 2013 12:52, Sandy Sutherland sandy.mailli...@gmail.com wrote: Create an annotation and write a ID into that - we used that in our asset

Re: Persistent objects ids

2013-06-04 Thread Alan Fregtman
At work I use a topology hash which I base off a string composed of either boundingbox and component counts, or if there's collisions from similar objects, the whole position array in local space. I use SHA1 for the hashing as it's a teensy bit faster to compute than MD5, but both of those have

Re: Persistent objects ids

2013-06-04 Thread Michal Doniec
Interesting idea Alan - thanks for this. Can't apply it to this particular thing I am doing now (topo, or anything can change), but I'll save it for the future. On 4 June 2013 15:25, Alan Fregtman alan.fregt...@gmail.com wrote: At work I use a topology hash which I base off a string composed

Re: Persistent objects ids

2013-06-04 Thread Michal Doniec
No, i haven't, but this is what I was looking for, thanks a lot! On 4 June 2013 16:52, Ciaran Moloney moloney.cia...@gmail.com wrote: Hi, did you try XSIUtils.DataRepository.GetIdentifier() passing the siObjectGUID argument? I've used this to keep track of ICE nodes without relying on name

Re: Persistent objects ids

2013-06-04 Thread Alan Fregtman
How about with refmodels? I know ObjectID sometimes changes with refmodels. Does this ObjectGUID suffer the same fate? On Tue, Jun 4, 2013 at 11:52 AM, Ciaran Moloney moloney.cia...@gmail.comwrote: Hi, did you try XSIUtils.DataRepository.GetIdentifier() passing the siObjectGUID argument?

RE: Persistent objects ids

2013-06-04 Thread Matt Lind
-boun...@listproc.autodesk.com] On Behalf Of Ciaran Moloney Sent: Tuesday, June 04, 2013 8:52 AM To: softimage@listproc.autodesk.com Subject: Re: Persistent objects ids Hi, did you try XSIUtils.DataRepository.GetIdentifier() passing the siObjectGUID argument? I've used this to keep track of ICE

Re: Persistent objects ids

2013-06-04 Thread Ciaran Moloney
Looks like it'll keep the same GUID as when exported as long as it's unique in the scene. If you have two references of a refmodel in a scene, the contents of the second model will get new GUIDs. On Tue, Jun 4, 2013 at 5:41 PM, Alan Fregtman alan.fregt...@gmail.comwrote: How about with

Re: Persistent objects ids

2013-06-04 Thread Ciaran Moloney
. ** ** Matt ** ** ** ** ** ** *From:* softimage-boun...@listproc.autodesk.com [mailto: softimage-boun...@listproc.autodesk.com] *On Behalf Of *Ciaran Moloney *Sent:* Tuesday, June 04, 2013 8:52 AM *To:* softimage@listproc.autodesk.com *Subject:* Re: Persistent objects ids

RE: Persistent objects ids

2013-06-04 Thread Matt Lind
, 2013 3:55 PM To: softimage@listproc.autodesk.com Subject: Re: Persistent objects ids Yes, you're right...I can reproduce a change of ID when deleting an object and re-opening a scene. However, I would not dismiss the object GUID, which appears to persists between sessions despite the change

Re: Persistent objects ids

2013-06-04 Thread Ciaran Moloney
@listproc.autodesk.com *Subject:* Re: Persistent objects ids ** ** Yes, you're right...I can reproduce a change of ID when deleting an object and re-opening a scene. However, I would not dismiss the object GUID, which appears to persists between sessions despite the change in the object ID value

Re: Persistent objects ids

2013-06-04 Thread Raffaele Fragapane
...@listproc.autodesk.com [mailto: softimage-boun...@listproc.autodesk.com] *On Behalf Of *Ciaran Moloney *Sent:* Tuesday, June 04, 2013 3:55 PM *To:* softimage@listproc.autodesk.com *Subject:* Re: Persistent objects ids ** ** Yes, you're right...I can reproduce a change of ID when

Re: Persistent objects ids

2013-06-04 Thread Ciaran Moloney
:* Re: Persistent objects ids ** ** Yes, you're right...I can reproduce a change of ID when deleting an object and re-opening a scene. However, I would not dismiss the object GUID, which appears to persists between sessions despite the change in the object ID value. In the below snippet

Re: Persistent objects ids

2013-06-04 Thread Raffaele Fragapane
: Persistent objects ids ** ** Yes, you're right...I can reproduce a change of ID when deleting an object and re-opening a scene. However, I would not dismiss the object GUID, which appears to persists between sessions despite the change in the object ID value. In the below snippet the sphere