Dota-2-Vulkan icon indicating copy to clipboard operation
Dota-2-Vulkan copied to clipboard

UI flicker on Nvidia mobile cards

Open ReactorofR opened this issue 9 years ago • 37 comments

PC SPECS: i7 3630QM @2.4GHz GTX 650M (Driver version : 368.22)

Running dota with -vulkan enabled and vulkan DLC downloaded. There are no problems before loading into a game but once I do the UI starts flickering.

Pick screen - https://u.pomf.is/xnfavz.webm

Opening the dashboard while ingame - https://u.pomf.is/lotkgu.webm

Also the HUD (just the bottom half) would do it as well but it's much less frequent and I couldn't record it.

The may 27 patch has not fixed this. DxDiag.txt

ReactorofR avatar May 27 '16 20:05 ReactorofR

I have the same issues with my laptop with a GTX 750M.

But I wonder if it's only exclusively mobile Kepler Nvidia chips that are having problems unless someone else can confirm with a mobile Maxwell chip.

simonlui avatar May 27 '16 20:05 simonlui

A user with a 960M reported the same issue in the dev forum thread.

ReactorofR avatar May 27 '16 20:05 ReactorofR

Duplicate of #1.

Tele42 avatar May 27 '16 20:05 Tele42

I don't believe it is, as the UI seems to be working fine in those examples. Where as here everything else is fine.

ReactorofR avatar May 27 '16 20:05 ReactorofR

A user with a 960M reported the same issue in the dev forum thread.

Seems to be before the patch though. It would be nice if someone could comment about this after the patch.

I'm also inclined to think it's also partially driver-related because I didn't have any problems with the 365.19 drivers.

simonlui avatar May 27 '16 21:05 simonlui

I'll try rolling back to 365.19

ReactorofR avatar May 27 '16 21:05 ReactorofR

Even after the Dota 2 update, 368.22 still doesn't seem to work on my GT 750M.

Rolling back fixed the flickering, but it still felt slower than normal.

andenrx avatar May 27 '16 21:05 andenrx

I can confirm reverting to 365.19 seems to fix the issue.

ReactorofR avatar May 27 '16 21:05 ReactorofR

I updated my drivers from a quite old version to the newest 368.22. I have a GTX 770M and it still flickers after recent update. I didn't test with 365.19, though.

Edit: I'm on Windows 7, 64 bit.

bxkx avatar May 27 '16 22:05 bxkx

even with the latest d2 patch,still didnt fix for me,365.19 driver was running fine with vulkan,however 368.22 nvidia driver had many problems Windows 10 64bit

man6231 avatar May 28 '16 02:05 man6231

Is this still happening since the 5/31 update on 368.22? If it is still happening, is this only happening for users at 368.22? So far I haven't been able to reproduce this issue. We did fix a bug on the 5/31 update with Kepler GPUs that could maybe be this although it had very different artifacts in my repro cases. It is also not something that should have been impacted by being at 365.19 vs 368.22.

danginsburg avatar Jun 01 '16 23:06 danginsburg

I did a quick retest on the 368.22 drivers. It seems that although flickering happens to a lesser extent, it is still present on my 750M. I could reproduce both issues listed in the original post of the issue but not consistently. The only thing I could consistently do to get the flickering to happen intermittently was watching a pub game and then opening the dashboard ingame.

simonlui avatar Jun 02 '16 01:06 simonlui

Yeah, still same issues like simonlui described for me too. It flickers less in-game now though (mostly the scan button, the fps and ping notification in the upper right corner and the quest progress stuff in the upper left corner - they flicker very constantly fast.)

bxkx avatar Jun 02 '16 07:06 bxkx

Flickering persists today. Microstutters, slideshow games even though fps is holding steady at 40+. Vulkan was ok with 365.19 .

650M, Windows 10 x64

DoulosTrieste avatar Jun 02 '16 16:06 DoulosTrieste

GT750M, Win7 64bit, 368.22 Same issue with the flickering, EXACTLY the same as the .webms as shown in the first post. Although it mostly only affects the scan, ping/fps display, and quest window, the flickering occurs once every 10 seconds or so on the main UI, which can be very distracting.

Here are the settings I used: https://files.catbox.moe/anefq7.png

Rolling back to 365.19 completely fixed most of the problem.

nisbahmumtaz avatar Jun 05 '16 14:06 nisbahmumtaz

i tried 368.22 as well, still getting the microstuttering bug so i rolled back to 365.19

costa58 avatar Jun 06 '16 22:06 costa58

Nvidia's 368.39 driver has released, and it still seems to exhibit the same issues.

simonlui avatar Jun 07 '16 19:06 simonlui

tested with latest 368.39 driver,issues still exists

man6231 avatar Jun 08 '16 06:06 man6231

http://prntscr.com/be4c28 740m 365.19

ShizoHere avatar Jun 09 '16 02:06 ShizoHere

Tested with driver version 368.69. Issue still exists.

realmofchaos avatar Jul 07 '16 15:07 realmofchaos

same issue

840M 368.69

StEaLtHmAn avatar Jul 19 '16 14:07 StEaLtHmAn

tested with driver 368.81 with 740M,win1064bit problem still exists

man6231 avatar Jul 19 '16 14:07 man6231

Newest driver, Win 10 x64, 760m, still same issues. Win 8 worked okay (on older driver, ofc).

Mayurifag avatar Aug 04 '16 03:08 Mayurifag

New Driver 372.54. Win 8.1 64bit, Graphics Driver GT 740M. Issue still exists.

realmofchaos avatar Aug 17 '16 11:08 realmofchaos

I appreciate you for reporting this every time a new update comes out.

But it seems like it's not worth Nvidia's effort to patch out an issue within a small niche of their mobile graphic card customer base, playing one single game, on a supposedly beta-only API. It's sad, but realistic on their part.

nisbahmumtaz avatar Aug 17 '16 18:08 nisbahmumtaz

I'm pretty sure at this point, this is a driver side issue because none of this has been seen so far on AMD cards. It can always be a bug in Source 2 but no one from Valve has marked it one way or another. Nvidia has not started, up to this point in time, doing much of anything with Vulkan besides occasionally putting in the appropriate LunarG SDK updated components and updating its Vulkan driver. Fixing any issues that may come up since this bug was created didn't happen, really. But that might be starting to change.

If you look over the 372.54 driver release notes, Nvidia did put out a fix Vulkan-related that allows full-screen exclusive mode to work now. They also added a Windows cross-API interop between Vulkan and DirectX 11. So I am sure they might at some point be able to fix this. The International is also over so Valve should be able to look into this more now.

simonlui avatar Aug 17 '16 20:08 simonlui

I've switched to Arch Linux recently and to my surprise Vulkan works just fine with the same hardware configuration and the latest Nvidia linux drivers (367.35).

I understand this driver is quite a bit older than the current windows one, but it works remarkably well.

ReactorofR avatar Aug 17 '16 23:08 ReactorofR

So, seems like there's a trend here that all affected systems are windows variants of the nvidia driver.

Tele42 avatar Aug 17 '16 23:08 Tele42

So, seems like there's a trend here that all affected systems are windows variants of the nvidia driver.

Not only that but it seems like everything is happening with x86-64 only. It also seems like it only affects Windows 7 and onwards too. Although I do doubt these two factors have any additional impact on the bug itself.

simonlui avatar Aug 17 '16 23:08 simonlui

I also experience flickering on a mobile NVIDIA GPU with Dota 2 and Vulkan.

Windows 10 x64 (14393) GeForce 945M (Optimus, 372.54) Vulkan Libraries 1.0.11.1

Espionage724 avatar Aug 18 '16 15:08 Espionage724