| Bug ID | 99923 |
|---|---|
| Summary | HITMAN (2016) having lighting and artefacting, and overly lig= ht room. |
| 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 | thedribbleondo@gmail.com |
| QA Contact | dri-devel@lists.freedesktop.org |
Created attachment 129874 [details] All the screenshots shown on imgur in case imgur goes down or something. When Running Mesa 17.1 git, upon entering any level, the game will start ha= ving black splotches and lighting missing/ not rendered correctly. This can be seen in this album here: http://imgur.com/a/k54kc This appears to be a problem with git only, as mesa 13.0.4 isn't affected by this bug...
| What | Removed | Added |
|---|---|---|
| Hardware | Other | x86-64 (AMD64) |
| OS | All | Linux (All) |
| Severity | normal | major |
Thanks for reporting this. Hitman used to work very nicely rec= ently. I will have a look.
Can you provide the following information, please. - Which mesa-git version? - Which LLVM version? - Which graphics settings in Hitman? After a quick try I can't reproduce right now.
(In reply to Samuel Pitoiset from comment #2) > Can you provide the following information, pleas= e. >=20 > - Which mesa-git version? > - Which LLVM version? > - Which graphics settings in Hitman? >=20 > After a quick try I can't reproduce right now. All screenshots were taken with Mesa Git 17.1~git170218133300.ad019bf (obta= ined via the Padoka PPA) or Mesa Git 17.1~git1702230730.6ca434 (from the oibaf P= PA). Mesa is built against LLVM 5 git, according to Paulo Dias Everything has been set to the lowest setting possible (No FXAA, trilinear, SSAO Disabled etc.) If it helps, Phoronix had problems of this nature too with certain graphics cards, one he name-checked was the R9 270X: http://www.phoronix.com/scan.php?page=3Darticl= e&item=3Dradeon-nvidia-hitman&num=3D1 (though the screenshots provided in the article are corruption-free), so it could be a problem with specific GCN cards. I have a GCN 1.1 card, an R7 250, so it may be an issue with Sea Islands Graphics Cards.
Okay, that makes more sense. I only have a RX480, so I definit= ely can't help here. If you get a chance, can you try recording an apitrace which reproduces? Th= at might other devs. Thanks.
(In reply to Samuel Pitoiset from comment #4) > Okay, that makes more sense. I only have a RX480= , so I definitely can't help > here. >=20 > If you get a chance, can you try recording an apitrace which reproduce= s? > That might other devs. >=20 > Thanks. Okie dokie.
(In reply to Samuel Pitoiset from comment #4) > Okay, that makes more sense. I only have a RX480= , so I definitely can't help > here. >=20 > If you get a chance, can you try recording an apitrace which reproduce= s? > That might other devs. >=20 > Thanks. Ok, I did a trace of Hitman, and I've included the insanely huge 1.4GB file= . Go nuts, to whomever can read it (It's compressed into a bzip2 to keep the filesize down): https://drive.google.com/open?id=3D0B4VxtGqhacqZSGl5OTV2WX= Yyams
FWIW, I get same artifacts as well. My setup: - R9 280 TAHITI GCN1.0 (1002:679a) - Mesa 17.1~git1702240730.ccb70d~gd~z (Oibaf PPA) - LLVM 4.0~+rc2-1
(In reply to Ernst Sj=C3=B6strand from comment #8) > R600_DEBUG=3Dsisched? One of the first things I tried. It makes no difference.
I have the same issue. My GPU is a 7950. I am using Debian pac= kages. I see the issue with Mesa 17.0.1/LLVM 4. With Mesa 13.0.5/LLVM 3.9 the issue is not present. This is also at the lowest settings possible, but it happens at "medium" settings too. One thing that changed between Mesa 13 and 17 for radeonsi is the OpenGL version, it was 4.3 now at 4.5. I used the GLSL override to put version 430 with Mesa 17 but the issue still persists. Unrelated last point: while searching on Bugzilla for this issue, there was another one (100061), I think the Hitman issue it refers to in the descript= ion is this issue?
(In reply to Ernst Sj=C3=B6strand from comment #8) > R600_DEBUG=3Dsisched? Also, I tried using the R600_debug command upon Steam startup, and Siched d= id make a positive performance impact after all.
With bug 100061 being fixed, I tried me= sa git 72fa447d45 which contains the fix, but did not see any change with regard to this bug. Would a new apitrace be needed for further debugging?
| What | Removed | Added |
|---|---|---|
| Blocks | 77449 |
I'm having the same problem, at least the black block artifact=
s.
It doesn't matter if I set the shadows to low or medium quality and window =
or
fullscreen also doesn't make any difference.
I'm using Mesa 17.0.2 (Debian, experimental), LLVM is 4.0 from Debian (1:4.=
0-1)
and have and AMD R9 280 (see below).
# lspci -vvvvv -s 01:00.0
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] (prog-if 00 [VGA controller])
Subsystem: PC Partner Limited / Sapphire Technology Radeon R9 280
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dfast >TAbort-=
<TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 36
NUMA node: 0
Region 0: Memory at c0000000 (64-bit, prefetchable) [size=3D256M]
Region 2: Memory at fea00000 (64-bit, non-prefetchable) [size=3D256=
K]
Region 4: I/O ports at e000 [size=3D256]
Expansion ROM at 000c0000 [disabled] [size=3D128K]
Capabilities: <access denied>
Kernel driver in use: radeon
Kernel modules: radeon
Kernels I tested are 4.7 and 4.10 (both from Debian).
TLDR: The issue is with LLVM >3.9. I started bisecting between the two versions I knew had differences (13.0.5= and 17.0.1). I started with 17.0.1 and was using LLVM 4.0, but then to compile 13.0.5 I had to use to LLVM 3.9. This gave me an idea to test the latest version with LLVM 3.9 and surprise, no more glitches! So I tested 17.0.1 and a recent git version (060a6434) with LLVM 3.9 (the o= ne from Debian) and the glitches are gone. So for now I have a workaround that= is ok for me.
The issue is still present using mesa 17.1.0-1 (Debian/experim= ental) and llvm 4.0.1~+rc1 (also Debian/experimental). I also have llvm 5.0 (5.0~svn301421; Debian/experimental) installed.
I can confirm that if I recompile the Debian sources with LLVM= 4.0 it's not working (the lighting bug is present) but if I set LLVM to 3.9 it's working correctly (lighting bug is NOT present). I was using LLVM 4.0.1 (1:4.0.1~+rc3-1) from the Debian archives to build M= esa (17.1.2-2) with the bug and LLVM 3.9.1 (3.9.1-10) from the Debian archives = to build Mesa without the bug.
Fo what it's worth, the issue is still present in mesa 17.2.0~= rc3-1 and llvm 1:4.0.1-1 (Debian/experimental).
Unfortunately still the same...
# glxinfo | grep Mesa
client glx vendor string: Mesa Project and SGI
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.4
OpenGL version string: 3.0 Mesa 17.2.4
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.2.4
# glxinfo | grep -i llvm
Device: AMD TAHITI (DRM 2.50.0 / 4.13.0-1-amd64, LLVM 5.0.0) (0x679a)
OpenGL renderer string: AMD TAHITI (DRM 2.50.0 / 4.13.0-1-amd64, LLVM 5.0.0=
)
Still the same with Mesa 17.2.5
# glxinfo | grep Mesa
client glx vendor string: Mesa Project and SGI
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.5
OpenGL version string: 3.0 Mesa 17.2.5
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.2.5
# glxinfo | grep -i llvm
Device: AMD TAHITI (DRM 2.50.0 / 4.13.0-1-amd64, LLVM 5.0.0) (0x679a)
OpenGL renderer string: AMD TAHITI (DRM 2.50.0 / 4.13.0-1-amd64, LLVM 5.0.0)
And also with 17.3.0 rc5.
# glxinfo | grep Mesa
client glx vendor string: Mesa Project and SGI
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.0-rc5
OpenGL version string: 3.0 Mesa 17.3.0-rc5
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.3.0-rc5
# glxinfo | grep -i llvm
Device: AMD TAHITI (DRM 2.50.0 / 4.13.0-1-amd64, LLVM 5.0.0) (0x679a)
OpenGL renderer string: AMD TAHITI (DRM 2.50.0 / 4.13.0-1-amd64, LLVM 5.0.0=
)
I recompiled Mesa with LLVM 6.0 but that didn't change anythin=
g.
# glxinfo | grep -i llvm
Device: AMD TAHITI (DRM 2.50.0 / 4.13.0-1-amd64, LLVM 6.0.0) (0x679a)
OpenGL renderer string: AMD TAHITI (DRM 2.50.0 / 4.13.0-1-amd64, LLVM 6.0.0=
)