Summary: | Game Crashlands crashes on startup | ||
---|---|---|---|
Product: | Mesa | Reporter: | ratatosk.yggdrasil |
Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | normal | ||
Priority: | medium | CC: | lockert.fredrick, ratatosk.yggdrasil |
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | 105797 | ||
Bug Blocks: | |||
Attachments: |
gdb output when running crashlands
gdb output when running crashlands Output with R600_DEBUG="ps,vs,tcs,tes,cs,gs" |
Description
ratatosk.yggdrasil
2017-09-08 13:27:43 UTC
Created attachment 134086 [details]
gdb output when running crashlands
Apologies, please ignore the previous gdb output. The error printed there was transient which was gone after a reboot. I have updated the attached gdb output which should be more helpful now. I bet if you launch the game with R600_DEBUG="ps,vs,tcs,tes,cs,gs" it will work. It's similar to the "Peace, Death!" issue because they both use the same engine. Created attachment 134101 [details]
Output with R600_DEBUG="ps,vs,tcs,tes,cs,gs"
Radeon RX 560
Arch Linux, mesa 17.1.8, xf86-video-amdgpu 1.3.0
R600_DEBUG="ps,vs,tcs,tes,cs,gs" LD_LIBRARY_PATH=~/.steam/bin32/ ./run.sh
With xf86-video-amdgpu 1.4.0 and mesa 17.2.0 the game starts for me. Seems this bug has already been fixed. In this particular situation it would be good to know what fixed the issue and whether there is a workaround available. Any ideas? As far as I know there was an update of the game engine included. Reopening as the game engine version is the same in both logs. Can you confirm if its working or was it just working when you ran with R600_DEBUG="ps,vs,tcs,tes,cs,gs" ? -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1281. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.