Seleucids Posted Tuesday at 23:19 Report Share Posted Tuesday at 23:19 I'm using RC-3 and WIndows 11. The archers in Atlas editor look like this by default. I am not using any mods to change the graphics. Give that I am a total cosmic noob at Windows, I probably messed up something simple. Here are the logs and my user.cfg user.cfgcrashlog.txtcrashlog.dmpuserreport_hwdetect.txtsystem_info.txtmainlog.html Quote Link to comment Share on other sites More sharing options...
Seleucids Posted Wednesday at 13:28 Author Report Share Posted Wednesday at 13:28 This seems to happen outside of atlas as well: Quote Link to comment Share on other sites More sharing options...
feneur Posted Wednesday at 15:55 Report Share Posted Wednesday at 15:55 I'm sure someone else has got a more informed solution, but just to rule out the obvious/easy ones: have you tried reinstalling the game? Have you checked that the drivers for your graphics card are updated? Quote Link to comment Share on other sites More sharing options...
ffm2 Posted Wednesday at 17:28 Report Share Posted Wednesday at 17:28 Your user.cfg has not set gpuskinning. The default value is true. When I activate it I get nightmare fuel as well. I use arch on my laptop with AMD Ryzen 7 5700U and a AMD gpu. Does it help to set it off? headless.mp4 Quote Link to comment Share on other sites More sharing options...
Seleucids Posted Wednesday at 18:32 Author Report Share Posted Wednesday at 18:32 1 hour ago, feneur said: have you tried reinstalling the game? I have installed and re-installed both release candidates RC1 and RC3. It happens on both versions. Regarding graphics driver, I installed AMD Radeon driver for my specific card from the AMD website. Maybe I misconfigured something... This problem only occurred on Windows and I was able to see perfect graphics with Linux on the exact same hardware and in-game settings. 2 minutes ago, ffm2 said: Does it help to set it off? No. The funny thing persists, although in a slightly different form: Some additional observations: All buildings are rendered correctly, but any organic unit is completely messed up Unit skin look darker than they should be All GUI elements work perfectly fine Quote Link to comment Share on other sites More sharing options...
Stan` Posted Wednesday at 19:38 Report Share Posted Wednesday at 19:38 GPU skinning requires restart IIRC. And that's definitely the symptoms for it. 1 Quote Link to comment Share on other sites More sharing options...
Seleucids Posted Wednesday at 22:33 Author Report Share Posted Wednesday at 22:33 (edited) I managed to solve this problem, without restarting. Steps: 1. Uninstall game completely, delete all 0ad config, cache, log and replays. 2. Re-install game but in a different location. I did it to my C:\ 3. Instead of using the start menu, go into where you installed 0ad and click on pyrogenesis.exe to launch the game. Now the graphics are fine. Installing to the same location will persist the problem (reason is beyond me) Not deleting configs, and most importantly cache, will persist the problem (probably broken render artifacts are in there) Starting menu on windows sometimes randomly fails to run the correct .exe file (reason is also beyond me) Edited Wednesday at 22:36 by Seleucids Quote Link to comment Share on other sites More sharing options...
little Guest Posted 15 hours ago Report Share Posted 15 hours ago (edited) Here is a Win10 system with a Vega iGPU. If I use the old driver (Adrenalin 22.6.1): OpenGL with GPU skinning disabled: works fine OpenGL with GPU skinning enabled: same issue occurs 14 hours ago, Seleucids said: I managed to solve this problem, without restarting. Steps: 1. Uninstall game completely, delete all 0ad config, cache, log and replays. 2. Re-install game but in a different location. I did it to my C:\ 3. Instead of using the start menu, go into where you installed 0ad and click on pyrogenesis.exe to launch the game. Now the graphics are fine. I followed your steps, and the issue is not fixed. (22.6.1OpenGL)system_info.txt (22.6.1OpenGL)userreport_hwdetect.txt Edited 15 hours ago by little Guest Quote Link to comment Share on other sites More sharing options...
Seleucids Posted 13 hours ago Author Report Share Posted 13 hours ago 1 hour ago, little Guest said: Here is a Win10 system with a Vega iGPU. If I use the old driver (Adrenalin 22.6.1): OpenGL with GPU skinning disabled: works fine OpenGL with GPU skinning enabled: same issue occurs I followed your steps, and the issue is not fixed. (22.6.1OpenGL)system_info.txt 12.42 kB · 0 downloads (22.6.1OpenGL)userreport_hwdetect.txt 12.06 kB · 0 downloads I was using vulkan all the time. Maybe try vulkan renderer instead? Quote Link to comment Share on other sites More sharing options...
little Guest Posted 12 hours ago Report Share Posted 12 hours ago 1 hour ago, Seleucids said: I was using vulkan all the time. Maybe try vulkan renderer instead? If I follow your steps with Vulkan and GPU skinning enabled, then there is a crash issue similar to the one I posted before. I guess your insane graphics issue might be caused by the driver. At least on my Vega iGPU, updating the driver solved it. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.