Unsolved FPS impact of invisible nulldetail1 objects

Discussion in 'World Editor' started by Murokmakto, May 7, 2025 at 11:18 AM.

  1. Murokmakto

    Murokmakto
    Expand Collapse

    Joined:
    Dec 24, 2023
    Messages:
    252
    Hello everybody,

    while working on my custom map I just noticed the following:

    When I set objects to hidden (eye symbol in the scene tree) I get some FPS gain even though the said object is so far away that it is not visible anyways (due to the nulldetail1 node turning it invisible).


    I thought that the nulldetail node simply turns "off" any object thus making it invisible and not using any more performance. But apparently that is not the case since only making it hidden in the scene tree does any effect on the performance, not it turning invisible by the nulldetail node.


    This is a bit of a concern for me since on this map I have certain areas that are rather high detail but far away from each other. I thought I could keep my FPS despite having some high detail areas simply by having these areas so far away from each other that all objects in one place are not visible in the other place (distance is far enough to turning them invisible by the nulldetail node).


    Does anyone have an idea why there is a performance difference between turning objects to hidden in the scene tree and turning invisible by the nulldetail node? And if there is some possible solution to this?




     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice