​
Physics Engine

​
Debug Rendering

​
Ray Tracing

When enabled, the system performs a Raycast from the player’s head in the aiming direction, extending 1000 meters to detect obstacles. The result is visually displayed with a line segment connecting the starting point, hit point, and target point.

​
Static Models

When enabled, renders static model objects loaded in the physics engine.

​
Dynamic Models

When enabled, renders dynamic model objects loaded in the physics engine.

​
Terrain

When enabled, renders terrain data loaded in the physics engine.

​
Render Distance

Sets the maximum display distance for debug rendering. Keep this value low to reduce system load and avoid lag, frame drops, or crashes.
The above features are intended for testing and debugging only. Do not enable during normal use, as they will significantly impact visual rendering frame rates.

​
General Settings

​
Static Model Loading Radius

Sets the loading range for static models (radius centered on the player). Adjust based on device performance. High values may cause performance degradation, lag, or crashes; low values may affect the experience.

​
Dynamic Model Loading Radius

Sets the loading range for dynamic models. Adjust according to hardware performance.

​
Physics Model Types

  • Description:
    Loads pre-baked model data directly after detecting scene information, requiring no additional parsing.
  • Advantages:
    Extremely fast loading with low resource usage.
    Low performance requirements for the secondary PC, suitable for resource-limited devices.
  • Disadvantages:
    Does not support interactive objects (e.g., doors, certain metal fences).
    Does not support scene destruction (e.g., collapsing buildings, destructible objects).
    Cannot update in real-time for destroyed scenes, potentially causing physics misjudgments.
  • Description:
    Loads pre-baked models and supports real-time reading, baking, and loading of uncached model data.
  • Advantages:
    Good performance and compatibility.
    Supports interactive objects (e.g., doors, metal fences).
    Higher ray-tracing accuracy compared to static models.
  • Disadvantages:
    Requires adequate secondary PC processing power and high DMA transfer rates.
    Real-time loading may cause slight lag on low-performance devices.
  • Description:
    Combines static and dynamic model approaches. Prioritizes pre-baked models, with missing parts loaded in real-time; performs data comparison and updates after scene loading.
  • Advantages:
    Supports dynamic destruction in maps like Karakin and Sanhok.
    Compatible with randomly generated building structures in Paramo.
  • Disadvantages:
    High performance consumption, less efficient than other methods.
    Demands high secondary PC performance and DMA bandwidth.
    May cause crashes, loading failures, or model inconsistencies in certain scenarios.
All model loading methods do not support terrain destruction.
If model anomalies or scene errors occur, try the following steps to resolve:
  1. Open the Physics Engine page in the menu.
  2. Click the Clear Cache Files button.
  3. Press F8 (default hotkey) to rebuild the physics scene.
  4. If the issue persists, switch to Static Model or Dynamic Model mode for troubleshooting.

​
Clear Cache Files

When model behavior is abnormal (e.g., Raycast consistently hits incorrect positions or the console outputs unknown mesh errors), click this button to clear related cache files and restore normal model display.

​
Reload Scene

Click to rebuild the current physics scene, useful for resolving some model loading issues. If the model cache is corrupted, click “Clear Cache Files” first, then use this function to ensure the reload takes effect.