Open simonvanderveldt opened 3 years ago
Fixed for me by using winehq staging 5.20. I'm not sure if Lutris has anything new enough without using System wine. But I didn't test others.
About all I can guess in that gforce now installs a latest version on installation and its incompatible with the older selected wine version of the script. Its either that or the script was pushed broken.
The fix here should be to change the selection wine version.
@tannisroot this would be resolved by pushing a release for wine-lutris 5.20
not sure, I managed to run the client but then I was unable to run any game as it refused to connect to the Now servers
The Web version runs great btw
not sure, I managed to run the client but then I was unable to run any game as it refused to connect to the Now servers
I didn't test any games, just made sure it didn't crash on start as according to the issue. Suppose, the new wine versions might have regressions if that's what happened there but have seen connection like issues with another application when using anything but winehq staging [recently]. Wine builds seem to be a bit to finicky at times.
Thanks for the info/feedback so far! Unfortunately I have an issue with wine versions > 5.10 so I can't currently test with 5.20/5.21.
The web based installer worked fine but the input lag in the web based version is horrendous, around a second I think, so it's unusable. This is the case in both Chrome as well as in Lutris's web runner.
The Web version runs great btw
Runs absolutely horrible for me, i could have times where i would have to wait 6 seconds to see any of my input register at all, whereas in the client version latency was barely even noticeable.
Weird, I tried a game of Fortnite and it was really playable, even on Wi-fi. Had no connectivity issue compared to a few months ago.
Fixed for me by using winehq staging 5.20. I'm not sure if Lutris has anything new enough without using System wine. But I didn't test others.
@byte1024 Did you change anything else? I managed to fix my issues with wine > 5.10 and tested running with wine-staging 5.20 as well as 5.21 but in both cases Lutris still crashes for me. I still need to compare if it's a different crash than with the old 5.6 version provided by Lutris. And are you using 5.20 from your distro or a Lutris build?
Fixed for me by using winehq staging 5.20. I'm not sure if Lutris has anything new enough without using System wine. But I didn't test others.
@byte1024 Did you change anything else? I managed to fix my issues with wine > 5.10 and tested running with wine-staging 5.20 as well as 5.21 but in both cases Lutris still crashes for me. I still need to compare if it's a different crash than with the old 5.6 version provided by Lutris. And are you using 5.20 from your distro or a Lutris build?
No, just installed per the link in the issue, started to crash, changed to wine staging, started without crash.
Using winehq-staging right now which cannot be installed at the same time as distro wine. This is direct install from wine devs: https://wiki.winehq.org/Fedora However, I do install various distro wine provided packages that can be installed at the same time and are required for various games such as wine-mono and all the wine fonts packages, etc.
Just to give you more to work with: I had the same problem (crash on startup with a black window). Per the advice in this thread I installed Wine 5.20 which fixed the problem. I can run the client now, but whenever I try to open a game a get a network error - so it's still unusable for me.
I tested this further.
Yes, latest version fails to connect to the network for Steam, games, etc with recent Wine versions even though it works fine for searching / browsing.
Older Geforce Now application verisons also run into this. However they still work fine with lutris gfn wine as long as they don't update.
That's a bit of a problem. I don't think its a great idea but one might be workaround it for the moment by obtaining an older version and installing it manually. I only tested one restart after it said it would update after that and it didn't but that doesn't mean it won't.
The only good way is to patch Wine I would think. That could mean patching the older Wine or the newer Wine. Not sure if its possible to edit Geforce Now files, could be, but its possibly the worst option.
The only good way is to patch Wine I would think. That could mean patching the older Wine or the newer Wine. Not sure if its possible to edit Geforce Now files, could be, but its possibly the worst option.
If all else fails, the specific patch(s) pertaining to whatever wine code is responsible for breaking gfn compatibility could be reverted to wine 5.20 but still have the networking code of an older version that previously worked with it, and have that as a geforce now specific wine fork, assuming these two things are fairly agnostic to each other and wouldn't require too much rewriting.
For the end user my recommendation would be to not use geforce now altogether and instead opt to use a service like shadow PC cloud streaming or the upcoming amazon luna that looks promising, obviously this is a wine issue but it's also pretty obvious that nvidia does not care for linux users in this space, if you're paying and struggling to run their service while they are doing nothing to support you the customer, quite frankly they don't deserve your money or attention.
I'm not entirely sure this is the correct repo, but I couldn't find a repo with the script anywhere, so I figured it must be this one.
Geforce NOW as installed by the install script from here https://lutris.net/games/geforce-now/ (or here https://lutris.net/games/install/18981/view, I don't know if this is a version pinned view of the script) no longer works, it crashes on startup whilst showing a black window.
Steps to reproduce
Complete log
I did copy
msmpeg2vdec.dll
next to theGeForceNOW.exe
executable which solved theERROR:dxva_video_decode_accelerator_win.cc(1431)] DXVAVDA fatal error: could not LoadLibrary: msmpeg2vdec.dll: Module not found. (0x7E)
error but didn't make a difference, the application still crashes the same way, no relevant changes in the log output.