LODs and LODs of confusion
by Fabio Luis Stange · in Technical Issues · 12/17/2006 (8:30 pm) · 0 replies
I was unable to see LOD changes inside the game, so I run ShowTool Pro and loaded the StoneChurch from the FPS env. pack.
Running at 1600x1200, the LOD never kicked in, no matter how far. So I lower close to 640x480, it kicks in at about 210 meters, pixel size showing is about 53, but the pixel width of the image was almost 100. So I raise the TST window to about 800x600, and the LOD only kicks in at 363 meters, pixel size showing is still 53, but now the pixel width of the church is at 70!
So what's happening here is that whenever I increment my resolution, the ABSOLUTE pixel size for a given "Pixel Size" as used by TST (not sure what that really means, since it doesn't equate to what I would expect) actually decreases, and the effect is that LODs take longer and longer to kick in higher resolutions.
BEFORE someone answers that it is expected to take longer, I already know that, but it should take longer RELATIVE to the current resolution, but the pixel width of the image when LODed should not change, at least that's how I see it. But here the ABSOLUTE values are also taking longer, so much as to never kick in at higher resolutions.
Running at 1600x1200, the LOD never kicked in, no matter how far. So I lower close to 640x480, it kicks in at about 210 meters, pixel size showing is about 53, but the pixel width of the image was almost 100. So I raise the TST window to about 800x600, and the LOD only kicks in at 363 meters, pixel size showing is still 53, but now the pixel width of the church is at 70!
So what's happening here is that whenever I increment my resolution, the ABSOLUTE pixel size for a given "Pixel Size" as used by TST (not sure what that really means, since it doesn't equate to what I would expect) actually decreases, and the effect is that LODs take longer and longer to kick in higher resolutions.
BEFORE someone answers that it is expected to take longer, I already know that, but it should take longer RELATIVE to the current resolution, but the pixel width of the image when LODed should not change, at least that's how I see it. But here the ABSOLUTE values are also taking longer, so much as to never kick in at higher resolutions.
