Game Development Community

1.5.1 LOD (?) system broken

by Christian Rousselle · in Torque Game Builder · 08/02/2007 (3:57 pm) · 8 replies

I reported this behavior in the beta already. When I work with the editor TGB often hides elements. I think this is some kind of LOD system that tries to hide elements based on their size (or whatever). The problem is that it does not work. In fact it keeps me from working at all. Please take a look at the following screenshots. The marked (but invisible) objects are path objects and mounted objects.

www.codecoach.de/TGB/1.png
When I zoom in very close some of the mounted objects become visible but still not the paths. Even if I click on "Edit this Path" the path nodes do not become visible.

www.codecoach.de/TGB/2.png
When I zoom in even closer the path nodes become visible again.

www.codecoach.de/TGB/3.png
But if I move the viewport a bit (without changing the zoom level the become invisible again.

Can I somehow disable this? Help :-(
NextNext Thread
PrevPrevious Thread
More from Torque Game Builder


Torque 3D Owner Marc Dreamora Schaerer
Gayasoft
#1
08/02/2007 (5:23 pm)
What graphic card do you have.
The last time I've seen something that bad was on an integrated intel with outdated drivers ...

Torque Owner Christian Rousselle
Default Studio Name
#2
08/02/2007 (5:34 pm)
6600GT, happens with D3D and OpenGL.

Torque Owner Stephen Howe
#3
08/02/2007 (10:14 pm)
I've seen this in doom 3 based games when using paths/nurbes too. Strange. No clue how to fix except just remember where things are.

Torque Owner Christian Rousselle
Default Studio Name
#4
08/03/2007 (1:27 am)
It does not only happen with paths it happens with all other objects too but not that severe. So I am the only one seeing this? Then I think it is a problem on my side....

Torque 3D Owner Marc Dreamora Schaerer
Gayasoft
#5
08/03/2007 (2:49 am)
Tried it.

Do not get that problem.

Perhaps you overload your VRAM?
If you have 128MB and no apperture memory you can get quite fast up there with many and large images.


But I struggled over a different issue. Don't know if it is my code or something within TGB that goes wrong (incorrect object scaling with script .setSize with other scaled objects in scene)

Torque Owner Christian Rousselle
Default Studio Name
#6
08/03/2007 (7:38 am)
Card has 256 MB. I installed new drivers - no change. I tested on a different machine (GeForce Go 7400) exact same behavior. I created a minimal project with only 2 graphcs - same problem. I do not belief that is has to do with a card but with TGB or some settings in TGB. I uploaded the project (just 161 kb). I hope it is reproducable on other machines tpp. Someone from GG please? The paths are in the bottom left corner (As I mentioned it does not only happen with paths but with other sprites too but not that severe). One is visible directly. You can take a look in the projects tab to see what is in the scene

Project: http://www.codecoach.de/TGB/testproj.rar

First shot shows only one path and nothing else

www.codecoach.de/TGB/4.png
When I move the scene (top works good) I can see

www.codecoach.de/TGB/5.png

Torque 3D Owner Stephen Zepp
#7
08/03/2007 (11:50 am)
Doesn't address the root problem, but if you name your path, and use the "project" tab (as in the last screenshot above), you should be able to at least select the path itself, which should bring it to front (and therefore make it visible).

If this doesn't work consistently, it does point to a sorting issue (although not an LoD issue--there is no LoD of that nature within the editor as far as I am aware).

Torque Owner Christian Rousselle
Default Studio Name
#8
08/03/2007 (12:14 pm)
Clicking on the path in the project tab does only mark it. This is not really the problem. The problem is that I am not able to change the nodes of the path. But the sorting tip did help. When I use the Back/Forward buttons I am able to focus on one path and work with them one by one. Thank you!