Is this Code saving performance ? It is kind of a Occlusion Culling

Question

I wanted to do Occlusion Culling on my Scene but I just get a bunch of Errors like "Couldn't load geometry..." etc. I tried to do like another way but the same thing, the Occlusion Culling just disables the Objects the Camera dont see. I tried it with OnTriggerEnter and Exit.

I have 2 Areas one is on the left and one on the right, when the Player is walking in the first Area the Box Collider checks it and disables the Objects in Area2 but when Player is walking into Area2, Objects in Area1 disables and Different. Got the Script on both Areas that it disables a list of arrays as GameObjects.

My Question is, does this save performance ?

---

public GameObject[] deactivatingModels;
bool playerEntered = false;

void OnTriggerEnter (Collider other) 
{

    foreach(GameObject envis in deactivatingModels)
    {
        if(other.gameObject.tag == "OcclusionCuller")
        {
            envis.SetActive(false);
            Debug.Log ("Player has entered Occuling Zone");
        }
    }
}

void OnTriggerExit(Collider other)
{
    foreach(GameObject envis in deactivatingModels)
    {
        if(other.gameObject.tag == "OcclusionCuller")
        {
            envis.SetActive(true);
            Debug.Log ("Player has left Occuling Zone");
        }
    }
}

Answer 1

An inactive object isn't not just not rendered anymore. All other components on the game object are deactivated as well. Inactive objects aren't rendered, don't get checked for collisions and aren't updated anymore. So this should save even more performance than "normal" occlusion culling.

But you can even go a step further: Destroy the game objects in the inactive areas of your game world and re-Instantiate them at their initial positions when the player comes back. That way they don't just stop using CPU and GPU resources, but stop consuming memory as well. The drawback is that you lose the state of left areas. When world persistence is important for your game, you might want to write any information worth persisting to a file.

Keep in mind that destroying and instantiating objects are expensive operations. So you should avoid doing it every frame. You might want to place the trigger areas which cause some areas to unload and other areas to load in passageways where not much action is going to happen. If you still have visible stutter from it, you might want to do the deleting and instancing in packets in a coroutine.