Third-Party Scene Managers (e.g., Eneroth, Curic)
Extensions that modify native scene properties (such as Eneroth Scene Visibility or Curic Scene Manager) can conflict with active visibility states if they attempt to override layout data simultaneously.
Liserok handles these external overrides based on your active synchronization mode:
- Auto Mode (Recommended): The Liserok engine constantly monitors the model database. If an external plugin disrupts the layout, Liserok will automatically re-establish and restore your correct Marker visibility matrix in real time.
- Manual Mode: To maintain absolute visual consistency and prevent unpredictable layout resets, avoid running secondary scene managers concurrently while in Manual Mode.
ℹ️ Note: Data synchronization conflicts will never result in geometry loss or object deletion. Concurrent third-party overriding can only cause temporary visibility desynchronization in the active viewport.
Model Optimization Utilities (e.g., CleanUp³)
When running third-party geometry optimization tools like CleanUp³ with the ‘Erase Hidden Geometry’ option enabled, the utility scans the entire database for hidden states.
To safely protect your layered project data, always execute Liserok Unhide All – Show All Markers before running any global purging scripts. This ensures that elements temporarily filtered out by your current production view are not misidentified as redundant geometry.