| Bug ID | 108919 |
|---|---|
| Summary | Parkitect (Unity Game) dispalys artifacts and black screens w= ith Vega hardware |
| Product | Mesa |
| Version | 18.2 |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/radeonsi |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | yovejuyas@moruzza.com |
| QA Contact | dri-devel@lists.freedesktop.org |
Created attachment 142689 [details] Screenshot of one of the possible outcomes of starting the game Issue: Vega hardware not working with Parkitect. The game is based on Unity. Lots of artifacts, particularly with ambient occlusion turned up in game's settings=20 Steps to reproduce: Start a game in parkitect with Vega hardware. Turn the graphics settings to max and you will experience issues. Sometimes it's playable, but always with artifacts Happy to provide logs and feedback. Some notes:=20 https://www.reddit.com/r/ThemeParkitect/com= ments/a0oboe/black_screen_on_linux_with_rx_vega_56/ Tested this with Mesa 18.2.4 and 18.3 in Fedora 29 (also had issues in Fedo= ra 28). Happy to donate a copy of the game to a known dev.
Created attachment 1426=
90 [details]
Another artifact example
I am the creator of the reddit post mentioned in the opening c= omment of the issue. The 3 images (1 on the reddit post, and the 2 attachments posted) sh= ow exactly what I get when I start the game, depending on what settings are us= ed. I cannot get it to any playable state though. I'm running Arch Linux 4.19.4, mesa 18.2.5-1 (along with the same lib32 version), and running on i3 (Xorg) with xf86-video-amdgpu 18.1.0-1. Here are also some logs from when I started the game: https://paste.ubuntu.com= /p/fRt54ftVD4/
Similar issue with black flickering reported here on an RX480 = with Mesa 18.2.2 and ambient occlusion turned on: https://old.reddit.com/r/Theme= Parkitect/comments/a1mt60/graphics_issue_black_flickering_all_over_the_plac= e/
I am using an RX580 and also have this issue. Forcing OpenGL 4=
.2(4.3 and above
causes the issue) with the mesa environment variable allows the game to run
without artifacts but some shaders do not work, such as ambient occlusion.<=
/pre>
| What | Removed | Added |
|---|---|---|
| CC | t_arceri@yahoo.com.au |
Can somebody try to get an apitrace of the issue [1]? Thanks. [1] https://git= hub.com/apitrace/apitrace/wiki/Steam
(In reply to Timothy Arceri from comment #5) > Can somebody try to get an apitrace of the issue= [1]? Thanks. >=20 > [1] https:= //github.com/apitrace/apitrace/wiki/Steam Never used that tool before but I uploaded a trace that shows it immediately visible on the main menu. Lots of these in the console if they're relevant: apitrace: warning: _gl_param_size: unknown GLenum 0x8267 apitrace: warning: _gl_param_size: unknown GLenum 0x92F5
(In reply to Alexander Walker from comment #7) > (In reply to Timothy Arceri from comment #5) > > Can somebody try to get an apitrace of the issue [1]? Thanks. > >=20 > > [1] h= ttps://github.com/apitrace/apitrace/wiki/Steam >=20 > Never used that tool before but I uploaded a trace that shows it immed= iately > visible on the main menu. >=20 > Lots of these in the console if they're relevant: > apitrace: warning: _gl_param_size: unknown GLenum 0x8267 > apitrace: warning: _gl_param_size: unknown GLenum 0x92F5 I'm not sure, I don't see these when replying the trace. Aside from some ca= lls to unsupported debug functions I don't see any obvious issues in the trace. Do you think you could try grabbing a capture in renderdoc [1]? Once you un= zip it somewhere you can add the following to the launch options for the game in steam: LD_PRELOAD=3D/your path to renderdoc here/renderdoc_1.2/lib/librenderdoc.so %command% When you lanuch the game you should see some text overlayed at the top of t= he screen saying you can create a capture by pressing F12. Once you have a cap= ture you can find it in a folder in the /tmp/ directory.=20 [1] https://renderdoc.org/
Created attachment 142775 =
[details]
renderdoc capture
(In reply to Timothy Arceri from comment #8) > Do you think you could try grabbing a capture in= renderdoc [1]? Once you > unzip it somewhere you can add the following to the launch options for= the > game in steam: >=20 > LD_PRELOAD=3D/your path to renderdoc here/renderdoc_1.2/lib/librenderd= oc.so > %command% >=20 > When you lanuch the game you should see some text overlayed at the top= of > the screen saying you can create a capture by pressing F12. Once you h= ave a > capture you can find it in a folder in the /tmp/ directory.=20 >=20 > [1] https://renderdoc.org/ I've attached a capture. It's a flickering issue so hopefully it was captur= ed in that 1 frame.
Created attachment 142776 [details]=
renderdoc black screen from toggling vsync
Just adding this same bug affects Tonga based GPUs as well.
I thought I'd try this one out as I always loved Bullfrog's Th= eme Park back on my AMIGA 500+ -- Parkitect 1.3 -- I've captured a more up-to-date trace: (1.8GB) https://drive.google.com/open?id=3D1DaekuBy9fBdQr4ceqskx_5w2m5BDt_CV<= /a> > Debian Testing > Linux-drm-fixes-5.1 > Mesa 19.1.0 (4e802089) http= s://tinyurl.com/mesacommit > Device: AMD Radeon R9 200 Series (TONGA, DRM 3.30.0, 5.1.0-rc1+, LLVM = 8.0.0) The game appears to be quite playable now.=20 Ambient occlusion appears to be the main cause of some heavy graphical glit= ches - which I've shown in my trace by lowering the slider. Alien Isolation is another game that suffers from glitches with HDAO enabled but otherwise works fine with it turned off.