Performance & Crashes

I approve the translation for troubleshooting/crash-issues.mdx

Troubleshooting for performance and stability issues such as “app crashes,” “screen stutters,” or “camera moves slowly.” Whether the symptom is “crashes” or “sluggish,” the root causes and solutions are common.

⚠️ Priority Check: Power & GPU

Regardless of symptoms, always check the following two points first. If you overlook these, any subsequent setting changes will be ineffective.

1. Laptop PC Power Connection

2. Warning Message Presence

Does a window like this appear at startup?

WARNING: Known issues with graphics driver The installed version of the Intel graphics driver has known issues…

What this warning means:

• For dGPU-equipped machines: The app is likely starting with iGPU while graphics quality settings remain at “High” or above (configuration error).
• For iGPU-only PCs: Lowering graphics quality to “Low” or “Medium” will enable normal operation.

👉 If this warning appears on a dGPU-equipped machine, GPU settings need verification.

Step 0: Problem Isolation (Important)

Before suspecting PC settings, check “is only a specific room heavy/crashes” or “does it happen with all rooms?”

1. Start R.Design and download/open an official sample room (e.g., Japanese Apartment).
   • If it runs smoothly: Your project data contains too-heavy objects or corrupted data.
   • If still heavy/crashes: There’s an issue with PC settings (GPU/VRAM) or specs. Proceed to diagnostic flow below.

Diagnostic Flowchart

Diagnostic routes differ depending on your PC environment.

Common Causes & Solutions

1. Integrated GPU Being Used (dGPU-equipped machines with High quality settings)

Windows assigns “integrated GPU (Intel/AMD)” for power saving, despite having GeForce etc. iGPU itself is not a problem, but keeping dGPU-oriented quality settings (High/Epic) causes “stutters” and “heavy” performance.

• Solution A (Recommended): Force R.Design to use high-performance GPU (dGPU) in NVIDIA Control Panel and Windows settings.

  • 👉 Procedure: GPU Configuration & Verification

• Solution B (Temporary): Lower quality settings to Low or Medium. This enables comfortable operation even with iGPU.

2. VRAM Shortage (dGPU-equipped machines)

GPU settings are correct, but quality settings too high, exceeding GPU memory capacity (VRAM). Especially Epic settings can consume 10GB+ VRAM, which standard PCs (VRAM 6GB~8GB) cannot handle.

• Solution: Lower quality settings (Graphics Settings) to High or Medium.

3. Quality Settings Too High for iGPU (iGPU-only PCs)

On PCs with only integrated graphics like Intel Iris Xe, setting quality to “High” or above makes Unreal Engine 5’s latest features (Lumen/Nanite) too heavy, causing crashes or freezes.

• Solution A: Lower quality settings to Low or Medium. This ensures comfortable operation in most cases.
• Solution B: If still unstable, switch to DirectX 11 (DX11) mode. Latest features are limited but provides even more stable operation.
  • 👉 Details: Graphics API Settings

4. Asset (Data) Issues

If only a specific room is heavy/crashes, the furniture or material data placed in that room may be too heavy (abnormally high polygon count, etc.).

• Solution:
  • Delete recently added furniture.
  • Create a new room and place furniture bit by bit to see if it reproduces.

Frequently Asked Questions (FAQ)

Q. Lowered settings, got FPS, but screen is grainy (noisy)

This is because resolution scale (Screen Percentage) is lowered or upscaler (DLSS/FSR) is in “Performance” mode. It’s a result of prioritizing smoothness (FPS), an unavoidable trade-off for low-VRAM PCs.

Q. Only specific rooms like “ST55 Sample” are very heavy

Some sample rooms experimentally use very high-load assets. If concerned about PC specs, test with lightweight rooms like “Japanese Apartment” or “Japandi Apartment.”

Q. Screen goes black when pressing render button / TDR error occurs

TDR (Timeout Detection and Recovery) error may be occurring during high-quality Path Tracing rendering, where GPU becomes unresponsive.

Main causes:

• Spatial Samples set too high (e.g., 2048)
• GPU load instantaneously too high, Windows judges as timeout

Solution:

1. Lower Spatial Samples to 64 or below
2. Raise Temporal Samples to 16 or above (maintain Total Samples)
3. Details → Samples Settings Deep Dive