Open MordragT opened 6 years ago
It does start now but there are no fonts displayed and the video scenes wont work
Runs without any issues for me with Proton 3.7 on Ubuntu 18.04
System Specs: Ubuntu 18.04 Core i7-4790K, 16GB Ram GeForce GTX 1060 (396.51)
OS: Fedora release 28 (Twenty Eight) x86_64 Kernel: 4.17.14-202.fc28.x86_64 Resolution: 1920x1080, 1280x1024 DE: GNOME 3.28.3 WM: GNOME Shell WM Theme: Adwaita Theme: Adwaita [GTK2/3] CPU: Intel Pentium G4620 (4) @ 3.700GHz GPU: NVIDIA GeForce GTX 1060 3GB Nivida Driver Version: 396.45 Memory: 4540MiB / 15492MiB
Works without any issues, no need to set anything up. This game can probably be whitelisted. +MordragT I would suggest loading winetricks, deleting all data in the prefix and then creating a new "fresh one". I did this for another game and got it working. But Witcher seems to work without any problems (NOTE: I have the Director's Cut DLC). *Of course someone else with AMD needs to confirm that this isn't an issue with the GPU, as the two working versions seem to have Nvidia GTX 1060's.
Also, I wish there was a way to no play the long video at the beginning.
EDITED (only after I commented I noticed that you are running a non-Nvidia GPU)
System: Host: blad-pc Kernel: 4.18.3-1-MANJARO x86_64 bits: 64 Desktop: Xfce 4.12.4
Distro: Manjaro Linux
CPU: Topology: 6-Core model: AMD FX-6100 bits: 64 type: MCP L2 cache: 2048 KiB
Speed: 1541 MHz min/max: 1400/3300 MHz Core speeds (MHz): 1: 1554 2: 1806 3: 1527 4: 1529
5: 1535 6: 1529
Graphics: Card-1: AMD Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.1 driver: amdgpu unloaded: modesetting
resolution: 1360x768~60Hz
OpenGL:
renderer: AMD Radeon HD 7800 Series (PITCAIRN DRM 3.26.0 4.18.3-1-MANJARO LLVM 6.0.1)
v: 4.5 Mesa 18.1.6
*Of course someone else with AMD needs to confirm that this isn't an issue with the GPU, as the two working versions seem to have Nvidia GTX 1060's.
There was some fps drops and missing mouse cursor in in-game menu(not main menu) which fixed with ALT+TAB(maybe cuz steam overlay or something else). Everything else was fine(but I'm only played prologue).
Installed the game and played the prologue. So far it has worked perfectly.
Works perfectly fine. Tested a few savegames. Performance is… not great. Works much better with gallium nine.
flatpak
OpenGL renderer string: AMD Radeon(TM) HD 8800 Series (PITCAIRN, DRM 3.26.0, 4.18.0, LLVM 6.0.1)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.1.6
@MordragT can you please test again with Proton 3.7-4 Beta?
This game runs near flawlessly for me using Proton 3.7-4 Beta. There is an issue when moving the mouse during the intro video causes it to lag, but there are no issues with the actual gameplay.
@swick for me it was working on 3.7-3 but now at 3.7-4 Beta it has some issues. mainly there's no skin :skull:
I'm runnig on:
Many thanks
The no skin bug can be solved by setting a registry key in wine: https://bugs.winehq.org/show_bug.cgi?id=34052
In my testing, the no skin bug appears randomly and will appear and disappear on game restart.
https://gist.github.com/grabmateusz/d8289ff0b86269092ce1139fd140d665
Game has known bug with missing people except eyeballs and teeth:
It is impossible to move and look around (mouse and keyboard seems not to work at the same time)
1) Run a new game and use mouse + keyboard control variant 2) Watch how it looks 3) Try to move Geralt and look around
I've played the game for about an hour. Worked out-of-the-box perfectly. Ubuntu 18.04 Linux 4.15.0-34-generic R7 1700 GTX 1080 Nvidia 396.54 Proton 3.7-3 and 3.7-6
@grabmateusz READ: Nvidia 396.54 is the MINIMUM driver necessary for Proton, and you should always test with the latest. Also, Ubuntu 17.10 has been end-of-life for a few months now. Upgrade to 18.04 LTS, it will be supported for 5 years.
Performance is good enough for me to consider it playable now. The visual problem has a workaround.
@MordragT can you try to test again?
I "tested" the game for around 40 hours in the last 2 weeks. Ubuntu 18.04, GTX 660, Nvidia 396.54, beta client. Default Proton versions (haven't changed any settings). I manually set the registry key using wine regedit on the wineprefix.
Performance is good with some slowdowns on medium graphics. I've been playing exclusively using a Steam Controller through a Steam Link. I encounter only one issue worth mentioning -
This is a particular bizarre one - when I input a left click using the Steam controller, the mouse cursor becomes visible and sort of suck on screen (it should be invisible in this mode). When I input a left click using the mouse, it doesn't happen.
After the mouse cursor appears, it will stay stuck on screen until some dialog comes up. When the dialog is closed, the mouse cursor will not be visible until the next time I input a left click using the controller.
For mouse/keyboard players, I'd certainly white-list this game.
Witcher 1 When set language as Chinese and save game will cause crash
Issue transferred from https://github.com/ValveSoftware/Proton/issues/2094. @spphinslove posted on 2018-12-15T12:35:53:
The game work fine unless you set the language as chinese.when save the game it will crash and wont save.
Crash
option->subtitles->chinese run game and save game or wait autosave.
When game set language as Chinese,and the map name also Chinese.save game will cause crash. if map name was English or other non-chinese,save game will work fine. You can see the picture below,the document name is based on map name.(when loading map,you can see the map name)
The Witcher: Enhanced Edition Director's Cut
Proton:Beta (3.16-5) Distro:Debian GNU/Linux 9.6 (stretch) (64 bits) Kernel:4.20.0-rc7 RAM:6 GB GPU Driver:NVIDIA 415.22.01 GPU:NVIDIA GeForce GTX 750 CPU:AMD Phenom II X6 1090T
the game work well for me but ,i need to disable steam overlay (in steam game property);otherwise i "loose" the mouse device: in the menu game go to steam overlay ("shift"+"tab") and leave it (again "shift"+"tab"),you will see you can't use keyboard or mouse to browse.
The Witcher: Enhanced Edition (20900)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/2118. @ItsDaFaz posted on 2018-12-22T10:28:02:
When I try to run the game which is installed in an ext4 partition, the game closes right after the DirectX install dialog pops up. There is no other message that pops up afterwards. I do have Python 2.7+ installed. I believe installing the game on a separate HDD formatted to ext4 is an issue
Just clicking play
The Witcher crashes on save just like https://github.com/ValveSoftware/Proton/issues/255#issuecomment-447584408 stated, with language set to russian (probably this would reproduce with any non-ASCII locale). This is likely a proton-specific bug, as on vanilla wine 4.0-rc5 the game saves and loads just fine.
The game crashes when I try to save with Proton 3.16-6 Beta. With Proton 3.7-8 it seems to be working fine. I tried PROTON_NO_ESYNC=1
to see if that causes the issue but it did not change anything.
Try saving the game once it allows you (right after the first fight).
Game regressed. It was working perfect on 3.16-4 but not on 3.16-7.
It crashes when you start a new game. I tried disabling esync , adding large adress aware variable and old gl strings variable but result was same every time.
Proton log:
Hi all. The problem with saving games in non-English languages should be fixed in 3.16-7.
@Leopard1907 Thank you for providing the log. Unfortunately we haven't been able to reproduce your failure. Are you using a non-English language for Witcher 1? Does Witcher 1 still work in 3.16-4 for you?
@aeikum
I'm using English language , on a Turkish client and OS.
Yes , Witcher 1 still works on 3.16-4. And i also didn't have any save issues on 3.16-4. Saving and loading works just fine.
I assume that is the fix you mentioned?
https://github.com/ValveSoftware/Proton/commit/2ae0d898eb1d6279cc705307a459f920bc7c921e
I had language related problems before on Steam Client but those are mostly fixed.
https://github.com/ValveSoftware/steam-for-linux/issues/5827
https://github.com/ValveSoftware/steam-for-linux/issues/4792
I still have a keyboard problem though , on some games.
https://bugs.winehq.org/show_bug.cgi?id=46102
So 3.16-7 broke things for me on Witcher 1 and also somehow Dirt 3 regressed on it. Both still works fine with 3.16-4. Games like Witcher 3, Quake Champions etc still works on 3.16-7.
@Leopard1907 Thanks for explaining. This seems to be a problem specific to using Wine with the Turkish locale. I will look into the problem. As a workaround in the meantime, I think you can set LC_ALL=en_US.UTF-8 %command%
in the game's Launch Options in Steam to get the game running again.
Hi @aeikum
I just tried with that launch option on 3.16-8.
Game still crashes when you start a new game.
3.16-4 still works flawless.
Hi again, @Leopard1907. Strange that the workaround didn't work. One of our developers found that this seems to be related to this glibc issue: https://sourceware.org/bugzilla/show_bug.cgi?id=23393 We are investigating a workaround for Proton/Wine.
@aeikum Thanks for the answer. Was it supposed to solve loading issue or keyboard issue?
Because with 3.16-8 i can't boot a new game ( probably loading a saved one will also end up with crash ) , so i didn't test keyboard related problem if that is the case workaround intends to solve.
Probably only the loading issue.
So i tested the right one :)
Strangely 3.16-8 and 7 caused regressions for me on various titles. They all seem to be related.
Skyrim SE infinite loading screen , Dirt 3 doesn't boot , Grid 1 crash after first Codemasters scene.
I already reported them and attached logs , if there are anymore tests i can do on my end i would gladly do it. They all seems to work fine on 3.16-4.
Yes, thank you for reporting. I'm surprised the LC_ALL thing didn't work. Maybe try with LC_CTYPE=C
or LC_CTYPE=en_US.UTF-8
or LC_ALL=C
?
@aeikum Sorry for late reply.
Both LC_CTYPE
workarounds worked on 3.16-8 , LC_ALL=C
didn't work.
Great, thanks. I guess I misunderstand some part of those variables (read locale(7) sometime, it's a bit complicated). Anyway, I will let you know when we have a real fix for this in Proton. In the meantime, using that workaround should be safe, I think.
Thanks for your interest. Have a good day.
@kisak-valve
Proton 4.2-2 fixed that regression for me on Witcher 1. Skyrim SE and Dirt 3 also seems fixed. However Grid 1 still keeps crashing on 4.2-2.
Fixed some games failing or crashing in certain locales like Turkish.
@aeikum Thanks for your interest. One more thing to ask ; do i have to open a seperate issue on Proton tracker for keyboard locale problem i mentioned and linked the Wine bug report or is it visible enough?
@Leopard1907 Great, glad it's working for you! I don't think opening another report for the keyboard problem is needed. Probably you'll get the best results by being active on the Wine bug. We'll take a quick look at Grid, it's likely it just needs a small correction to some other part of Wine (see Piotr's recent str* related patches on wine-devel if you're interested).
@aeikum I will , thanks again!
Despite game works very well ; there are two issues. I don't know if they are exist on Windows or not.
1-) Alt tabbing and getting back into game introduces graphical issues. Weirdly , fps counter of Steam overlay disappears too when that happened. Changing location or alt tabbing and getting back into game fixes that.
2-) Game crashes after alt tabbing and getting back in game at crowded places like Vizima streets.
Log of it:
I can confirm that this game exhibits the same issue I detailed regarding The Witcher 3 here. I've yet to find anything that differs, aside from that instead of merely going back to normal framerate after the brief freeze, Witcher 1 (sometimes?) plays the missed frames at fast-forward rather than skipping them. Can look a bit humorous.
Running this game with PROTON_USE_D9VK set to 1 causes visual artefacts. They are a bit hard to catch, but here's one:
nvidia 430.26 Linux 5.1.20 Fedora 30 GTX 970
Hi! First of all, thank you, Valve, for starting and developing the Proton project, it's awesome.
I have troubles with running The Witcher Enhanced Edition with Derictor's cut DLC. When I run the game, nothing happens, no window appears, however I can see the process witcher.exe in the list of processes (and the time while this process is running counts as "hours played" for this game)
Sometimes after a system update the game runs perfectly, with no bugs or any graphical problems (I have finished the prologue when it happened). But another system update returns me to the situation described above (in which I am now).
I do not see any clues in the logs of the game or in the console output of the Steam (both are attached). I have found an issue with quite similar symptoms for Witcher 3 here https://steamcommunity.com/app/221410/discussions/0/1640915206462889040/ However, turning off the shaders pre-caching hasn't worked out for me.
OS: ArchLinux, kernel 5.3.1 CPU: Intel Core i5-7200U CPU 2.50GHz GPU: Intel HD Graphics 620 GPU driver: mesa 19.1.7 vulkaninfo output is also attached
* I'm getting red spots around the lab at the beginning, don't know if they're supposed to be flying embers since I never played it before.
They are due to high toxicity. Intentional.
Intro movie is played at my ultrawide resolution but zoomed in.
It's a game bug.
Quest text is cutoff.
I don't experience this with 4.11-11.
@kisak-valve can this be converted to whitelist request?
Hello @soredake, you can grab the whitelist request template, copy it over to the comment box here and fill it out to request that a compatibility report get converted. We will have a holding period for anyone else to give feedback if they're seeing any issues that would block the game from being whitelisted.
Play
button in the Steam client is sufficient.Is anyone seeing any issues with this game and Proton 4.11 with PROTON_USE_D9VK=1 %command%
that would block it from being whitelisted?
@lavadrop, can you check if the cut off text is limited to ultrawide desktop resolutions?
Nothing changed.
Your screenshot is 2560x1080, the same as your previous report. Can you easily check 1920x1080?
Yeah, 16:9 ratio shows proper text.
Steam Play is enabled for all titles. My System: Manjaro 17.1.12 Mesa 18.1.6 with R9 270x Console Output: