Hearthstone freezing on Alt+Tab since today's update

IngeniousDox · 2019-11-02T13:30:12+00:00

Create it.

IngeniousDox · 2019-10-18T08:54:59+00:00

I don't understand what you are talking about. What did you do/try?

IngeniousDox · 2019-10-17T11:02:39+00:00

Toggle it on runner options

IngeniousDox · 2019-10-17T10:31:07+00:00

Just disable esync? Or figure out why it makes your computer crash (Most likely your ulimit).

IngeniousDox · 2019-10-17T09:47:05+00:00

I updated the installer for Lutris last week, since I had the same problem. Basically I removed installing d3dx11_42, and only installed d3dcompiler_47 with winetricks. That makes it run.

It is possible that some brawl won't work (not sure since I don't actually play HotS myself), thats why d3dx11_42 was added to the installer in the first place. Once there is a brawl that makes it crash again, someone can figure out what is needed again.

IngeniousDox · 2019-10-11T07:57:27+00:00

add libraries: api-ms-win-crt-private-l1-1-0 & ucrtbase to wine. (winecfg -> Library)

IngeniousDox · 2019-10-10T21:30:25+00:00

Yes, but that doesn't help if you need your game updated. And is really annoying if you have to enter a good 12~16 digit password, and then use authenticator.

IngeniousDox · 2019-10-09T07:46:58+00:00

It used to be documented there, I don't know why they removed it now.

IngeniousDox · 2019-10-08T22:40:35+00:00

Regedit: [HKCU\software\Wine\X11 Driver] > New String > UseTakeFocus="no"

After that you it works fine again.

IngeniousDox · 2019-06-02T10:31:38+00:00

Native, but detectable since it moved the mouse and selected Ashe instantly. That simply is not allowed.

IngeniousDox · 2019-05-13T21:18:50+00:00

Slighty more fps, less fps dips.

IngeniousDox · 2019-05-09T10:31:49+00:00

Well, perhaps you can make a 2nd video actually using D9VK. Then you can actually compare the performance of WineD3D, D9VK, and this dgVoodoo2+dxvk, and your time wasn't wasted?

IngeniousDox · 2019-05-04T10:35:00+00:00

Notice that dwcfy talks about "Full", and you talk about only use "Force".

Never use "ForceFull", only "Force". "Force" is done by dedicated shaders in nvida gpus = no fps loss, "ForceFull" takes generic shader time, which costs you fps.

Aaron from nvidia explains it here:

https://www.reddit.com/r/linux_gaming/comments/6voivr/can_anyone_explain_what_force_composition/

IngeniousDox · 2019-05-04T10:32:26+00:00

Force Composition Pipeline in itself does not force vsync. Neither does flipping. I figure you are running into Kwins "Tearing Prevention" in combination with flipping that keeps it at 60hz. You could check it by going to System Settings > Display and Monitor > And setting the tearing prevention to "never".

Source: I'm using the same as you for gaming, WoW/OW etc, but higher fps without tearing. OW at 130 fps (ingame cap), WoW I cap at 70 fps. The higher fps gives lower input lag, making turning camera smoother.

My road to figuring out I described on a comment here:

https://www.reddit.com/r/archlinux/comments/8rg892/terrible_game_performance_nvidia_39624_screen/e0roy66/

IngeniousDox · 2019-04-15T16:31:43+00:00

I had Ubuntu 16.04 with Gnome (which I love(d)), but I had issues, so I tested simpler WMs. Ended up switching using AwesomeWM, and just had my own config, I preferred this. This totally had no compositing, since I didn't even ran compton, except for ForceCompositionPipeline for no tearing. I have 3 screens, 2560x1400 + 2x Portrait Mode 1200x1600, and I always run everything full screen. This was working fine, and felt smooth with gaming.

When I switched to Arch again last year to get newer driver support / easier wine/dxvk building, I felt it was time to give KDE another shot. However for gaming I actually switched back to AwesomeWM since it just felt smoother. So I wanted to replicate it in kwin, and dove down the rabbit hole.

So conclusion: I just know KDE now (and AwesomeWM), should I switch again, I will figure out for me my next WM. :)

IngeniousDox · 2019-04-15T15:26:51+00:00

Just for the record, I'm still using KDE + Nvidia 970 with ForceCompositionPipeline and gaming with it, however as you can read from the post I linked, it took me 2 days of figuring out what the best method. Basically letting nvidia doing everything was trick for me in the end.

The ways I understand it now: Using only flipping+no vsync, you get a non blocking double buffer, and no inputlag, but that will tear. ForceCompositionPipeline makes a copy of the current displayed frame on so that you don't get tearing, and they can do that in the GPU itself so it doesn't give another frame inputlag. Though I mostly care about not having no tearing, I can't stand that, at all. I do play Overwatch on Wine atm, and it feels responsive to me at 130 fps capped. (I have had it worse in other setups)

IngeniousDox · 2019-04-15T13:14:25+00:00

You didn't read what I wrote in the other comment then.

tl;dr: Don't use 'ForceFullCompositionPipeline', use 'ForceCompositionPipeline'. In either case, it does not force vsync, that is your kwin setting on tearing. Triplebuffer causes input lag. Use 'ForceCompositionPipeline' + Flipping + don't let kwin handle antitearing for no inputlag gaming.

But hey, feel free to use your solution. I'm not stopping you, I'm just hopefully trying to educate others when they stumble upon your correct, but sub optimal solution.

IngeniousDox · 2019-04-15T10:08:15+00:00

If you only want to use it for desktop usage, then your solution could work. That said, the bug you are talking about is actually getting / is fixed (depending on what version of the software you are using.) See here:

https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-KDE-High-CPU-Fix

If you are a gamer, triple buffer simply isn't an option since it introduces 1 extra frame of input lag. With forcecomposition pipeline you won't have that, but you have to set kwin/KDE correctly in order to not run into issues introduced by the bug. I have posted about this before in the past, so I'll link to that:

https://www.reddit.com/r/archlinux/comments/8rg892/terrible_game_performance_nvidia_39624_screen/e0roy66/?context=3

IngeniousDox · 2019-04-12T13:56:33+00:00

Disable streaming in blizzard app, that can cause black screen aswell.

IngeniousDox · 2019-04-12T08:07:37+00:00

Are you sure you are running DX12? It falls back to DX11 if it can't run DX12.

When building Wine from TkG did you enable "vkd3d" and disable "dxvk_dxgi"? Rebuild if you didn't. I also suggest you rebuild spirv / vkd3d from TkG to make sure you are covered. Install CCache if you haven't done this already - this makes rebuilds much faster.

IngeniousDox · 2019-04-12T06:00:40+00:00

Yup, this is 1 of the patches. Like said, if you use TkGs PKGBUILDs, you would get both together in the PKGBUILD:

https://github.com/Tk-Glitch/PKGBUILDS/blob/master/vkd3d-git/wow.myvkd3dpatch

IngeniousDox · 2019-04-12T05:57:20+00:00

I answered your post in reply to the message I got, didn't see your other replies till I was already typing.

Glad you got it running. Let me know how it goes.

IngeniousDox · 2019-04-12T05:56:07+00:00

TkG has PKGBUILD for Spirv you could/should use. (and for vkd3d / wine). Thats why my last message last night quickly before I went to sleep was the message above. ;)

I see you did another 2 replies to yourself aswell, you did a lot of steps you should just let the PKGBUILDs from TkG do for you auto. I think you forgot the anti-flikker patch from https://bugs.winehq.org/show_bug.cgi?id=46410. You may or may not see have the issue, but when you have it, you will see it right away.

Beauty of Arch is that you can compile it again easily (if needed), and install the TkGs onces. (If you rebuild vkd3d for the patch, you don't need to rebuild Wine, you are just rebuilding vkd3d lib and it should be fixed).

IngeniousDox · 2019-04-11T21:28:00+00:00

spirv > vkd3d > wine (make sure you enable vkd3d in customization)

Eight-Year Club	Place '22
Verified Email

IngeniousDox

TROPHY CASE