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, but
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 wrote:
> Create an annotation and write a ID into that - we used that in our asset
> system, worked fine for u
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 kn
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 wrote:
> At work I use a topology hash which I base off a string composed of either
> boundingbox
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 strings.
It's persistent between sessions and is preserved when models are exported.
Works like a charm.
The only problem is that it's possibl
No, i haven't, but this is what I was looking for, thanks a lot!
On 4 June 2013 16:52, Ciaran Moloney 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 strings.
> It's persi
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 wrote:
> Hi,
> did you try XSIUtils.DataRepository.GetIdentifier() passing the
> siObjectGUID argument?
> I've used this to keep
-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 o
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 wrote:
> How about with refmodels? I know ObjectID som
ave a
> new ID.
>
> ** **
>
> 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
ne 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 a scene. However, I would not dismiss the object GUID, which appears
to persists between sessions despite the cha
ran 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 a scene. However, I would not dismiss t
*
>>
>> ** **
>>
>> ** **
>>
>> ** **
>>
>> ** **
>>
>> ** **
>>
>> *From:* softimage-boun...@listproc.autodesk.com [mailto:
>> softimage-boun...@listproc.autodesk.com] *On Behalf Of *Ciaran Moloney
>> *Sent:* Tuesday, Ju
t; ** **
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> *From:* softimage-boun...@listproc.autodesk.com [mailto:
>>> softimage-boun...@listproc.autodesk.com] *On Behalf Of *Ciaran Moloney
>>> *Sent:* Tuesday, June 04,
goes for CLSID.***
>>>> *
>>>>
>>>> ** **
>>>>
>>>> Matt
>>>>
>>>> ** **
>>>>
>>>> ** **
>>>>
>>>> ** **
>>>>
>>>> ** **
>>>&g
>>>>
>>>>> Object GUID is persistent, but not granular enough. I’ve run into
>>>>> cases where multiple items get the same GUID. Same goes for CLSID.**
>>>>> **
>>>>>
>>>>> ** **
>>>>>
>>>>> Matt***
16 matches
Mail list logo