1### Before submitting your bug report: 2- Check if a new version of Mesa is available which might have fixed the problem. 3- If you can, check if the latest development version (git main) works better. 4- Check if your bug has already been reported here. 5- For any logs, backtraces, etc - use [code blocks](https://docs.gitlab.com/ee/user/markdown.html#code-spans-and-blocks) 6- As examples of good bug reports you may review one of these - #2598, #2615, #2608 7 8 9Otherwise, fill the requested information below. 10And please remove anything that doesn't apply to keep things readable :) 11 12 13### Description 14 15Describe what you are doing, what you expect and what you're 16seeing instead. How frequent is the issue? Is it a one time occurrence? Does it appear multiple times but randomly? Can you easily reproduce it? 17 18"It doesn't work" usually is not a helpful description of an issue. 19The more detail about how things are going wrong, the better. 20 21### Screenshots/video files 22 23For rendering errors, attach screenshots of the problem and (if possible) of how it should look. For freezes, it may be useful to provide a screenshot of the affected game scene. Prefer screenshots over videos. 24 25### Log files (for system lockups / game freezes / crashes) 26 27- Backtrace (for crashes) 28- Output of `dmesg` 29- Hang reports: Run with `RADV_DEBUG=hang` and attach the files created in `$HOME/radv_dumps_*/` 30 31### Steps to reproduce 32 33How can Mesa developers reproduce the issue? When reporting a game issue, start explaining from a fresh save file and don't assume prior knowledge of the game's story. 34 35Example: 36 371. `Start new game and enter second mission (takes about 10 minutes)` 382. `Talk to the NPC called "Frank"` 393. `Observe flickering on Frank's body` 40 41### System information 42 43Please post `inxi -GSC -xx` output ([fenced with triple backticks](https://docs.gitlab.com/ee/user/markdown.html#code-spans-and-blocks)) OR fill information below manually 44 45 46- OS: (`cat /etc/os-release | grep "NAME"`) 47- GPU: (`lspci -nn | grep VGA` or `lshw -C display -numeric`) 48- Kernel version: (`uname -a`) 49- Mesa version: (`glxinfo -B | grep "OpenGL version string"`) 50- Desktop environment: (`env | grep XDG_CURRENT_DESKTOP`) 51 52#### If applicable 53- Xserver version: (`sudo X -version`) 54- DXVK version: 55- Wine/Proton version: 56 57 58### Regression 59 60Did it used to work in a previous Mesa version? It can greatly help to know when the issue started. 61 62 63### API captures (if applicable, optional) 64 65Consider recording a [GFXReconstruct](https://github.com/LunarG/gfxreconstruct/blob/dev/USAGE_desktop.md) (preferred), [RenderDoc](https://renderdoc.org/), or [apitrace](https://github.com/apitrace/apitrace/blob/master/docs/USAGE.markdown) capture of the issue with the RADV driver active. This can tremendously help when debugging issues, but you're still encouraged to report issues if you can't provide a capture file. 66 67### Further information (optional) 68 69Does the issue reproduce with the LLVM backend (`RADV_DEBUG=llvm`) or on the AMDGPU-PRO drivers? 70 71Does your environment set any of the variables `ACO_DEBUG`, `RADV_DEBUG`, and `RADV_PERFTEST`? 72