| Bug ID | 111060 |
|---|---|
| Summary | Dying Light does start but doesnt render properly. |
| Product | Mesa |
| Version | git |
| Hardware | Other |
| OS | All |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/radeonsi |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | haxk612@gmail.com |
| QA Contact | dri-devel@lists.freedesktop.org |
I have installed Dying Light few days ago. I know there were s= ome issues with mesa and dying light but now i heard that most of them are fixed. So i started it and it crashed. So i used the dying light shim provided in other bug report and the game launched bug not even the video was rendered properly. It wasnt rendered to entire screen but only to one quarter in down right of the screen. And the entire quarter was displaying only one color a= s if it was showing only one pixel. Im using AMD_DEBUG=3Dnir variable so i was thinking that may be the issue. Disabling it didnt help and the same issue happened. Launching the game from pure executable showed that i was missing one libra= ry. Installing that library didnt help and same issue and trying again the executable it shows FATAL ERROR cannot initialize renderer. Its weird as i have not seen this issue anywhere else. Hardware: CPU Ryzen 5 2500U GPU Radeon RX560X Using LLVM from git and mesa built from git too. If you need any logs or anything of that matter im happy to provide it all.=
Ohhh and when using Proton the game works perfectly fine witho= ut any issue just with much lower FPS.
Which exact driver and driver version is used on which distrib= ution and distribution version?
Driver is ofcourse MESA built from git. Latest commit. And dis= tribution is Arch linux.
| What | Removed | Added |
|---|---|---|
| Resolution | --- | NOTOURBUG |
| Status | NEW | RESOLVED |
The crash on Arch Linux is due to a game bug not a Mesa bug wh= ich is bought to light by Arch using libglvnd, basically the game doesn't check for features= it uses correctly. Recent patches have landed in git that implement the functions Dying Light tries to use and users have reported that this fixes the start-up crash. I suggest you make sure your system is correctly picking up the version of Me= sa you have built from git and is not continuing to use your system copy of Me= sa. Either way this in not actually a Mesa bug so I'm going to close this bug report. If you really are correctly using the copy of Mesa you built from g= it and it is still crashing I suggest waiting a little longer until full suppo= rt for the EXT_direct_state_access extension lands in Mesa.
I dont care about the damn crash. Thats not even why i opened = the bug report. The bug report is for not correctly rendering stuff. It renders to one quat= er of the screen in down right corner and shows only one color as if it was shoring only 1 pixel.
(In reply to Timothy Arceri from comment #4) > The crash on Arch Linux is due to a game bug not= a Mesa bug which is bought > to light by Arch using libglvnd, basically the game doesn't check for > features it uses correctly. >=20 > Recent patches have landed in git that implement the functions Dying L= ight > tries to use and users have reported that this fixes the start-up cras= h. I > suggest you make sure your system is correctly picking up the version = of > Mesa you have built from git and is not continuing to use your system = copy > of Mesa. >=20 > Either way this in not actually a Mesa bug so I'm going to close this = bug > report. If you really are correctly using the copy of Mesa you built f= rom > git and it is still crashing I suggest waiting a little longer until f= ull > support for the EXT_direct_state_access extension lands in Mesa. I just opened the 00-mesa file and set the variables manually for dying lig= ht and the game launches just OK and works as expected. How can i check which file is overwritting the variables ?
Issue fixed. For some reason i had all the variables that work= around bugs set in .drirc as false. Its fixed now.