Jump to content

0.a.d Alpha 27, Vulkan crashes starting game.


Shafe
 Share

Recommended Posts

Reinstalled the game twice, and no luck, Vulkan crashes every time when starting a game, OpenGL works fine. Before installing Alpha 27, I had the pre-release of Alpha 27(0.0.27-rc-27645) and Vulkan worked just fine, to confirm, I uninstalled Alpha 27 and reinstalled the pre-release and Vulkan works fine. If it helpful, game was installed on a Acer laptop with a 5700u.

 

This is the message that pops up when the game crashes.

Much to our regret we must report the program has encountered an error.

Please let us know at https://gitea.wildfiregames.com/0ad/0ad/issues/ and attach the crashlog.txt and crashlog.dmp files.

You may find paths to these files at https://gitea.wildfiregames.com/0ad/0ad/wiki/GameDataPaths

Details: unhandled exception (Integer divide by zero)

Location: unknown:0 (?)

Call stack:

(error while dumping stack: No stack frames found)

errno = 0 (No error reported here)

OS error = 0 (no error code was set)

  • Like 1
Link to comment
Share on other sites

How does it work with GPU skinning disabled?
I guess it might be the same issue as point 2 in this post, except for the driver version — I only know it's older than Adrenalin 24.9.1.

By the way, could you test whether you’re experiencing the issue mentioned in point 1 of that post and reply there?
Vega GPU users seem to be pretty rare. Thanks!

Link to comment
Share on other sites

Disabling GPU skinning does nothing. What happens, when starting a game, it starts to load, then goes to windowed mode with the error message popping up to continue or exit,(clicking continue the game just closes after a few seconds). Just tried running the game in windowed mode, and it does finally work, but units have artifacts, which I found goes away if I disable gpu skinning and restart the game.

Link to comment
Share on other sites

Current driver version is 31.0.14076.3. Checked Acer's website and it's the most recent driver available. Will try downloading a newer driver from AMD,

 

Yes the game works normally in windowed mode with GPU skinning off. Game works in windowed mode with GPU skinning enabled, but units contain artifacts as if there glitching with the horse unit, the guy has no head. Weirdly, if I enable GPU skinning during a game, all the unit's glitch out to like they are infinitely stretched in a straight line and any units produced after enabling GPU skinning are fine(tho they are glitchy with artifacts).

Restarted the game multiple times in windowed mode with GPU skinning disabled no issues. Will see how the game runs after updating the graphics drivers.

Link to comment
Share on other sites

7 minutes ago, Shafe said:

Updated graphics drivers and so far the crashing issue seems to be gone but GPU skimming issue is not. GPU skimming being disable I can live with for now.

Yeah it will be fixed in the point release. Sorry about the inconvenience

Link to comment
Share on other sites

9 hours ago, Shafe said:

Updated graphics drivers and so far the crashing issue seems to be gone but GPU skimming issue is not. GPU skimming being disable I can live with for now.

So you mean that after updating the driver:

  • Vulkan + GPU skinning disabled works fine in both fullscreen and windowed mode,
  • Vulkan + GPU skinning enabled in both fullscreen and windowed mode runs, but the units look broken,

is that correct?
 

Besides, after changing the GPU skinning setting and saving it, did you restart 0 A.D.?
Because on my side, if I change from Vulkan + GPU skinning disabled to Vulkan + GPU skinning enabled, save the setting and start a new game right away, the game runs without crashing — but I suspect GPU skinning isn’t actually active.

Link to comment
Share on other sites

12 hours ago, little Guest said:

So you mean that after updating the driver:

  • Vulkan + GPU skinning disabled works fine in both fullscreen and windowed mode,
  • Vulkan + GPU skinning enabled in both fullscreen and windowed mode runs, but the units look broken,

is that correct?
 

Besides, after changing the GPU skinning setting and saving it, did you restart 0 A.D.?
Because on my side, if I change from Vulkan + GPU skinning disabled to Vulkan + GPU skinning enabled, save the setting and start a new game right away, the game runs without crashing — but I suspect GPU skinning isn’t actually active.

Yes, correct for both. 

Units are only broken when enabling GPU skinning during a game and it seems to only effect current units, and when their broken, they don't even look like units, they look like never ending lines of color

I re-enabled GPU skinning during a game to get a screen shot of broken units looking like never ending lines. Tried getting a screen shot of the units after restarting the game with GPU skinning enabled, but weirdly, instead of getting with units with artifacts(different from the image, more the units not rendering correctly) the game closes with no error message as if I opened task manager and closed the game. Tried restarting the game multiple times with GPU skinning enabled not toughing any setting, and game starts to load then closes with no error message. I opened the game, disabled GPU skinning, exited the game and reopened and it back to working normally. So diffidently an issue going with the game and my hardware not liking each other as the game works flawlessly on my desktop.

Screen Shot.jpg

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...