Problem with a mapping app on Windows 10 and Nvidia graphics card
Problem with a mapping app on Windows 10 and Nvidia graphics card
Hello, I wasn’t expecting to seek assistance on general forums, especially since this involves a more complex OS and GPU setup. The challenge here centers around the operating system and graphics card rather than just the software itself. To be honest, I’m not a complete novice, but also not an expert-level one. I possess solid understanding of operating systems and graphics hardware, as well as general troubleshooting for most issues I’ve encountered so far—though this one is quite unique.
To clarify: I’m a modder and artist who works with several 3D/level design programs, including some from around 2006-2009. My main system is Windows 10, which has some strange behavior when running a particular application. My specs include a GTX 1060, 16GB RAM, an SSD, and an i5 processor with 3450 MHz.
Regarding the problem: it involves a program called Unreal Level Editor (or UE2004). The main concern is that viewports are rendered using D3D8, D3D9, or OpenGL, and whenever I interact with the mouse—like selecting objects or using context menus—the software freezes for 5 to 15 seconds. This happens even when no map is loaded in the viewport (just an empty project).
Some useful insights from my research: I previously encountered this issue in 2017 on a 64 Home Desktop version of Windows 10, but it resolved itself. Later, on a 64-bit Win8 Pro laptop with only 4GB RAM and an older i3 CPU, the software ran perfectly without GPU usage. In 2019, after system updates, the problem persisted. I tried various fixes—updated drivers, disabled GameDVR, changed GPU settings—but nothing worked. Eventually, I suspected a Windows 10-specific issue.
After extensive attempts, including basic steps like switching GPUs or reinstalling, the problem remains. I reached out to a friend who uses the same program on a newer system with an Nvidia GPU and got no issues. This led me to believe the root cause lies in D3D drivers or OpenGL itself, not the GPU.
This is where I need expert guidance: pinpointing whether the freeze is due to D3D/OpenGL handling or something else would help narrow it down. I’m hoping someone can provide more targeted advice and possibly point out a workaround.
If you need further details, I’ll keep checking this thread throughout the day to respond quickly. Thank you for your time, and please keep an eye on this thread—this could be crucial!
PS: If there’s any way to disable GPU usage entirely or find a workaround that prevents these freezes, that would make things much easier.
Have you attempted to run it in compatibility mode? If this is essential and you frequently use older software (beyond this project), consider a dedicated machine with an older operating system or a virtual machine running an older OS.
I've tried it too; it seems like the dedicated PC setup isn't currently an option for quick fixes. It might be necessary to replace the machine entirely since resolving this would require a new device. My main goal is to grasp how the GPU and Windows 10 handle the viewport process, hoping this insight will help me fix it permanently. I'm not alone in facing this problem, but because the software is outdated, few people are raising concerns. Even moving just one file from a folder works for me. What file exactly am I dealing with?