Terrain Occlusion Issues?

#1 If the cost of iterating all possible occlusion candidates is higher than the cost of rendering all occlusion candidates then it stands to reason you'd get higher framerates if you didn't check for occlusion.

If this is the case, something is probably wrong with the occlusion test. Have to benchmark it somehow, but it smells like a bug.

#2 these are 2 posts i saw on it before, but they are older

https://www.garagegames.com/community/resource/view/3751/2#comments

http://www.garagegames.com/community/forums/viewthread/119067

and this isnt a small 'un-used' level that im doing this on.

#3 We saw the same thing in dhmc.

#4 If I recall we had a conversation concerning the terrain occlusion issues back in the early Steering Committee days. I know it was never working 100% correct.

Ron

#5 how it can be switched off in script? like the editor does.

#6 im not finding it in the script yet

what I found was in code:

sceneCullingState.cpp


bool SceneCullingState::smDisableTerrainOcclusion = false;

im guessing make it true

#7 $Scene::disableTerrainOcclusion

#8 Thanks!