Location address changed - component vanished.

About Truespace Archives

These pages are a copy of the official truespace forums prior to their removal somewhere around 2011.

They are retained here for archive purposes only.

Location address changed - component vanished. // Work in Progress

1  |  

Post by bobgreen // Nov 27, 2008, 6:44pm

bobgreen
Total Posts: 4
Hi All:


I am working on a new model and have run into a really strange problem that I am hoping someone here might have an answer for. Several components of my model have simply vanished from the screen, although they are still showing up in the Scene Editor. Upon closer inspection I noticed that the location information in the object info box showed the following strange numbers - 1.#Q0 - for the x,y and z locations. Anyone have any idea? Thanks!


Bob Green

Post by spacekdet // Nov 27, 2008, 6:55pm

spacekdet
Total Posts: 1360
pic
I don't know where ' 1.#Q0 ' is located, but if all else fails try selecting them via the scene editor or object info box and clicking the 'normalize location' icon. They'll return from wherever '1.#Q0' is and return to the center of the grid. You'll have to put them back in place on the model but at least they won't be in limbo.

You might want to 'normalize location' the whole model first, then select just the missing components and normalize them. Won't have as far to move them to get them back in place.

Definitely an odd one!

Post by bobgreen // Nov 27, 2008, 7:04pm

bobgreen
Total Posts: 4
Thanks for the tip. I normalized all and then selected components with bad addresses and normalized them. I did this from the scene editor and object info box and the weird address is not changing and components are still not visible.

Post by spacekdet // Nov 27, 2008, 8:01pm

spacekdet
Total Posts: 1360
pic
What happens if you type in 0 /Enter in each of the X, Y, Z boxes in the Object info box?
Do they return from Limbo?

Post by bobgreen // Nov 28, 2008, 3:48am

bobgreen
Total Posts: 4
Tried that, but it won't let me change any letters. Just pops back to 1.#Q0

Post by TomG // Dec 1, 2008, 2:11am

TomG
Total Posts: 3397
Are you using the latest 7.6? I recall earlier versions had a bug that could result in that appearing.


Note that the value you mention means "invalid value", they have data in there that is not a number and is meaningless. Happens when something gets corrupted.


Can you show the scene, perhaps share what you were doing that lead up to this? And confirm that this isn't 7.51 or earlier too, since I've not seen this occur since those times.


HTH!

Tom

Post by Norm // Dec 1, 2008, 7:23am

Norm
Total Posts: 862
pic
It should be possible to save one of the offending objects.
Upload the offending object here and folks can take a look at the scenario.
Awportals.com is a privately held community resource website dedicated to Active Worlds.
Copyright (c) Mark Randall 2006 - 2024. All Rights Reserved.
Awportals.com   ·   ProLibraries Live   ·   Twitter   ·   LinkedIn