| Bug ID | 108340 |
|---|---|
| Summary | Ambient Occlusion in Two Point Hospital shows black spot arti= facts |
| 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 | christos.kotsaris@gmail.com |
| QA Contact | dri-devel@lists.freedesktop.org |
Two point hospital works pretty well on my Archlinux system us= ing Mesa 18.2.2, LLVM 7.0, kernel 4.18.12 with max graphical settings. The only setting that= has an issue is Ambient Occlusion. With that enabled, when you move the camera around it produces a lot of black spots around the edges of walls and items. With that setting disabled everything displays fine.=20 >>From what little search i did, i saw other people reporting this issue on t= he steam forums of the game but it is not reported here and i think it is an i= ssue with Mesa. For the record i am using an R9 380 card and i saw people report= ing the same problem on Polaris cards.
| What | Removed | Added |
|---|---|---|
| Status | NEW | NEEDINFO |
Getting an apitrace [1] of the problem would be useful. [1] https://git= hub.com/apitrace/apitrace/wiki/Steam
I am noticing the same issue, also running on max graphical se= ttings. Ubuntu 18.10 Kernel 4.18.0-13-generic AMD RX 480 OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.2 Steps followed: 1. Installed apitrace (sudo apt-get install apitrace) 2. Looked up the ID of Two Point Hospital (535930) 3. Ran the following command in terminal (DEBUGGER=3D"apitrace trace&q= uot; steam steam://rungameid/535930) 4. Once ingame with the Ambient Occlusion option active, I zoomed in and out and moved the camera around as this seems to exacerbate the black spots. 5. The trace file is stored next to the game executable (/home/username/.local/share/Steam/steamapps/common/TPH/TPH.x86_64.trace) 6. I compressed the trace file with 7z https://mega.nz/#!y3IzRY6A!ksUZcYGjgeHnBk9XtZb3J7pnIb5meZV8TxB-T27X= mPs The file is hosted on MEGA, and I used 7z compression to make the uploaded = file somewhat smaller.
Created attachment 142915 [=
details]
Recurring error in trace file replay in qapitrace
I've now installed qapitrace (sudo apt-get install apitrace-gui) and can now
look into what errors are being listed after I replay the trace therein.=20
Then I tried delving deeper into the error messages and think I may have at
least found something relevant. But I'm quite out of my element here.
In the attached screenshot, you can see it lists 4 errors regarding "a=
rray
index must be a scalar". These errors seem to refer to a glShaderSourc=
e call
for a GL_FRAGMENT_SHADER, shader string 0, at lines 65,98,99 and 100.
What these four lines have in common is that they all use the same value to
address a certain index in an array:=20
ivec4(u_xlati12)
For line 65 it's unity_Builtins0Array and for 98,99 and 100 it's
unity_Builtins0Array.
So now the question is, what is the value of ivec4(u_xlati12) and what
generates it, to find out what is causing it.
The error is repeated quite often, and it's always that index.
The fact that I can also see variables named _OcclusionStrength and
_OcclusionMap at least makes me think I'm looking in the right direction.
Parkitect has the same issue, it seems to be a general Unity t= hing.
| What | Removed | Added |
|---|---|---|
| Status | NEEDINFO | RESOLVED |
| Resolution | --- | MOVED |
-- 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/1336.