T3D 1.1 final - Rendering of final LOD level is incorrect - NOT A BUG
by Guy Allard · in Torque 3D Professional · 10/03/2011 (7:22 am) · 8 replies
Build: T3D 1.1 final
Platform: Windows
Target: game, shape editor
Issues: The final LOD level for imported models continues to render below its specified LOD threshold.
Steps to repeat:
1) launch the FPS example, hit F11, choose a level, then go to the shape editor.
2) Load the cheetah body shape
3) Look at the detail levels and the model while you zoom out. The cheetah has a LOD level of 100, but will continue to render when its size falls below 100.
4) Try another model - art/shapes/rocks/half_rock_1
5) zoom out, watch it go through detail levels 400, 200, 100 but then continue displaying the 100 mesh when the pixel size is less than 100.
more info
The official documentation states "Once the estimated size is less than the smallest positive detail size, no geometry will be rendered for the shape. You can force a shape to always render something by making the smallest positive detail level have size=0".
This is not the way its behaving.
Platform: Windows
Target: game, shape editor
Issues: The final LOD level for imported models continues to render below its specified LOD threshold.
Steps to repeat:
1) launch the FPS example, hit F11, choose a level, then go to the shape editor.
2) Load the cheetah body shape
3) Look at the detail levels and the model while you zoom out. The cheetah has a LOD level of 100, but will continue to render when its size falls below 100.
4) Try another model - art/shapes/rocks/half_rock_1
5) zoom out, watch it go through detail levels 400, 200, 100 but then continue displaying the 100 mesh when the pixel size is less than 100.
more info
The official documentation states "Once the estimated size is less than the smallest positive detail size, no geometry will be rendered for the shape. You can force a shape to always render something by making the smallest positive detail level have size=0".
This is not the way its behaving.
About the author
Recent Threads
#2
10/03/2011 (8:24 am)
No, the cheetah isn't set up for billboards. I'm trying the stock shapes in the stock unmodified engine. 
#3
10/03/2011 (8:34 am)
ah true... i just woke up.. ill take a look to see how its behaving on our stuff too 
#4
Memory is fuzzy but i seem to remember it working just like this in at least one of the engines i actually tested this in, maybe its a bad memory issue :)
10/03/2011 (9:54 am)
We talked about this in IRC for a while before i had to disappear for something else. It was always mu understanding that the detail size was the size at which that model was enabled, so a detail400 was displayed when the model is less than 400 pixels and stayed that model until it becomes 200 pixels high at which point detail200 is displayed.Memory is fuzzy but i seem to remember it working just like this in at least one of the engines i actually tested this in, maybe its a bad memory issue :)
#5
..you need to add a "nulldetail" node to [edit] each model [/edit] to have objects no longer render below their lowest LOD #.
10/03/2011 (10:04 am)
The Docs are wrong for 1.1 as Tom added the "Nulldetail" detail level...you need to add a "nulldetail" node to [edit] each model [/edit] to have objects no longer render below their lowest LOD #.
#6
It's definately the other way round. Detail400 is displayed at size 400px and larger. detail200 is then displayed from 200px to 399px.
@E.B.,
cool, I had no idea that was changed. I guess there's a well hidden one-liner in a change log somewhere that covers the use of this?
10/03/2011 (10:53 am)
@Bloodknight,It's definately the other way round. Detail400 is displayed at size 400px and larger. detail200 is then displayed from 200px to 399px.
@E.B.,
cool, I had no idea that was changed. I guess there's a well hidden one-liner in a change log somewhere that covers the use of this?
#7
when you make your model, add a nulldetail node in the same manner as a detail node(hierarchy wise) and the model will no longer render when pixel size is lower than the lowest detail level.
detail200
detail100
nulldetail (now <100 pixels is removed from render)
(I have no clue where I read it, I think perhaps I took it as a global change after learning about it from within the change to breakable shapes from 1.0 to 1.1)
k ?
10/03/2011 (1:52 pm)
[I made a small edit above.]when you make your model, add a nulldetail node in the same manner as a detail node(hierarchy wise) and the model will no longer render when pixel size is lower than the lowest detail level.
detail200
detail100
nulldetail (now <100 pixels is removed from render)
(I have no clue where I read it, I think perhaps I took it as a global change after learning about it from within the change to breakable shapes from 1.0 to 1.1)
k ?
#8
10/03/2011 (3:11 pm)
Thats good to know EB thx :) 
Torque 3D Owner Andy Wright
BrokeAss Games