2 Years Ago
Code review: properly fix SetVisible not working on MeshCull components. Added a force optional paramter to SetVisible. MeshCull components were remembering their state when they were disabled, when entering the HLOD bounds LODComponents are told to become visible and then adjust based on LOD however MeshCull components would ignore this as their saved state wouldn't have changed. Once in this state the MeshCUll component would think it was disabled, but it's mesh was actually visible. This likely wouldn't have been problematic if the player came into range via a CullingVolume as the player would be closer to the renderer as opposed to hundreds of metres away in the case of a HLOD component, however I've applied the same fix in that case.