Hi everyone,
I’m facing a critical, project-breaking issue where a specific file (****) completely shuts down without any error message exactly when the loading bar hits 41%.
To rule out a single-system hardware limitation, I tested opening this exact same file on three completely different computer builds, and the exact same 41% shutdown behavior occurs on all of them. On my primary machine, I monitored the Task Manager and saw massive, immediate memory spikes right before the crash.
Here are the details of the machines tested and the performance behavior:
Tested Systems & Hardware:
- PC 1 (Primary): Intel i7-10700F | 48 GB RAM | RTX 3070 (8GB VRAM)
- PC 2: AMD/Intel Build | 32 GB RAM | RTX 4070 (12GB VRAM)
- PC 3 (High-End): AMD/Intel Build | 64 GB RAM | RTX 5070 (Next-Gen VRAM)
The Problem Behavior (Captured on Primary PC):
- System Memory (RAM): Spikes completely to 100% utilization (using 47.8 GB out of 47.9 GB). The committed memory flies up to 86.6 / 93.9 GB, showing that the system is aggressively dumping data into the pagefile because physical memory is exhausted.
- GPU Memory (VRAM): Dedicated VRAM maxes out entirely at 7.6 GB out of 8.0 GB.
- Storage: The C:/D: SSD storage drives instantly spike to 100% active time trying to process the massive pagefile overflow.
- The Loop: Even on PC 3 with 64GB RAM and an RTX 5070, the file still immediately force-closes at 41%. This suggests an optimization bug, asset conflict, or memory leak triggered at that exact percentage mark in the loading sequence.
What I need help with: Because the software completely closes, I cannot get into the file to optimize materials, reduce texture maps, or hide heavy geometry/scattering layers.
- Is there a known bug in the current D5 version causing a memory loop at the 41% mark?
- Is there any way to force-open a file in a “safe mode,” with disabled assets, or with a lower display resolution preset?
- Can I manually delete or isolate a specific cache folder (like temporary asset packages) within the project directory to stop this memory spike so the file can finish loading?
I have attached screenshots of my Task Manager performance tabs showing the 100% RAM/VRAM cap and the loading screen for reference.
Any insights, workarounds, or help from the D5 team would be deeply appreciated. I am currently completely locked out of this client project.
Thank you!