marco.schulz Posted April 18, 2025 Posted April 18, 2025 Hi all, I’ve been trying to continue development on my Unigine project while on the go using my ASUS ROG Ally (Ryzen Z1 Extreme). However, the engine fails to recognize the GPU during startup, and I’m unable to get the project to run properly, it crashes right after initialization. Here's the relevant section from the Log: Quote 12:48:44 ---- OS ---- 12:48:44 Windows 11 (build 26100) 12:48:44 12:48:44 ---- CPU ---- 12:48:44 AMD Ryzen Z1 Extreme 12:48:44 Extensions: MMX+ SSE SSE2 SSE3 SSSE3 SSE41 SSE42 SSE4A AVX AVX2 HTT 12:48:44 Frequency: 3293MHz 12:48:44 Cores: 8 Threads : 16 12:48:44 RAM: 11.7GB 12:48:44 12:48:44 ---- GPU ---- 12:48:44 GPU 0 Active : Null Memory: 0MB Type:Other Vendor:Unknown CommonHeaps:false Priority: 0 LUID:0000000000000000 DeviceID:00000000 Driver:Null 12:48:44 GAPI: NULL 12:48:44 12:48:44 Is there any chance to run it on the Z1?
silent Posted April 18, 2025 Posted April 18, 2025 Hi Marco, Are you able to run other DirectX 12 applications successfully? There have been known driver-related issues with ROG Ally devices in the past, which might be contributing to the problem. You can check this reddit post: https://www.reddit.com/r/ROGAlly/comments/18radxj/rog_ally_software_and_directx12_issues/ Maybe also installing latest GPU driver from AMD will fix this behavior? Here is the short guide how to do this: You can also check current DX version in dxdiag and share dxdiag log with us. Thanks! How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN
silent Posted April 18, 2025 Posted April 18, 2025 Actually, looks like you have enabled NULL graphics API somehow. This mode is specifically designed to run on environments without GPUs (servers, for example): Quote 12:48:44 GAPI: NULL Could you please check if you are not passing -video_api null by accident when launching your application? The same can be done via code. You need to change it something like -video_app dx12 in order to run on DirectX12. You can also try to delete <Project>/data/configs/default.boot config to make sure that you are running engine without any custom modifications. Thanks! How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN
marco.schulz Posted April 19, 2025 Author Posted April 19, 2025 Hi, thanks for the help! I followed the steps from the video, and now the GPU is correctly detected in the log — so that part seems to be working. However, unfortunately, it didn’t really change the behavior. To narrow things down, I created a fresh project using the example world and also made a standalone build of my own project. The build works perfectly on three different machines I’ve tested it on, but on the ROG Ally, it still crashes both when launching the build and when running directly from the editor. Crash Details (Windows Event Log): Quote Fehlerhafter Anwendungsname: Project_Rom_x64.exe, Version: 0.0.0.0, Zeitstempel: 0x67ac0000 Fehlerhafter Modulname: Unigine_double_x64.dll, Version: 2.19.0.3, Zeitstempel: 0x679a8250 Ausnahmecode: 0xc000041d Fehleroffset: 0x000000000047cf9d Fehlerhafte Prozess-ID: 0x5E74 Fehlerhafte Anwendungsstartzeit: 0x1DBB10E64EBBAF2 Fehlerhafter Anwendungspfad: C:\Users\SosaS\Desktop\Unigine\romAlpha\Project_Rom\bin\Project_Rom_x64.exe Fehlerhafter Modulpfad: C:\Users\SosaS\Desktop\Unigine\romAlpha\Project_Rom\bin\Unigine_double_x64.dll Berichts-ID: 69f72ae7-f9ec-4902-96f7-31bdd8632689 Vollständiger Name des fehlerhaften Pakets: Fehlerhafte paketbezogene Anwendungs-ID: Visual Studio Debugger Output: Quote Exception thrown at 0x00007FF8FA8E3A6C (Unigine_double_x64d.dll) in Project_Rom_x64d.exe: 0xC0000005: Access violation reading location 0x0000000000000180.
silent Posted April 21, 2025 Posted April 21, 2025 Could you also please send us the engine log files from the ROG device after updating the drivers to the latest version? The log is usually located in the <Project>/bin directory (log_*.txt files). Additionally, we recommend updating the Visual Studio C++ Redistributable Runtimes, as outdated versions can sometimes cause unexpected issues. https://aka.ms/vs/17/release/vc_redist.x64.exe Also you can try to launch engine with differnt API (for example DX11 or Vulkan) to test the behavior: Also you can try to reduce memory consumption a bit by turning off the Microprofile tool: Thanks! How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN
marco.schulz Posted May 7, 2025 Author Posted May 7, 2025 Hi, none of the suggested solutions worked for me, but I did some testing with older versions of Unigine. Version 2.16 runs fine on the ROG Ally, but every version after that crashes consistently. log.txt log_0.txt log_1.txt
Recommended Posts