Proton: The Elder Scrolls V: Skyrim (72850)

Created on 25 Aug 2018  ·  74Comments  ·  Source: ValveSoftware/Proton

Arch Linux
Kernel 4.18.3
Proton 3.7
bspwm 0.9.5
CPU Intel Core i3-2350m @ 4x 2.3GHz
RAM 4gb
GPU Intel(R) HD Graphics 3000

Working OK, the game already work slowly in my windows cuz my slow notebook hardware, but still working in linux.

https://store.steampowered.com/app/72850/The_Elder_Scrolls_V_Skyrim/

Game compatibility - Unofficial Regression XAudio2

Most helpful comment

Some bugs on my box (Debian Stretch / NVIDIA 390.77 / KDE) :

  • Crackling sound
  • Force to run kill -9 instead of simply quitting the game, otherwise it creates a zombie process.

All 74 comments

I dont have Music and some sound effects and voices seem to be missing
Same on Skirim Special Edition.

My system:
https://gist.github.com/Zero86Sk/d629f657c1ae861c36657cdf238a7765

Download xact if you are having trouble with sound.

See: https://github.com/ValveSoftware/Proton/issues/54

For me the non-special-edition of Skyrim has crackling sound issues and the game locks-up when I exit it. The game itself runs fine on ultra settings.

System is the following:

Processor Information:
CPU Brand: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz

Operating System Version:
Arch Linux
Kernel Name: Linux
Kernel Version: 4.18.4-arch1-1-ARCH
X Window Manager: KWin

Video Card:
Driver: X.Org AMD Radeon(TM) HD 8800 Series (PITCAIRN, DRM 3.26.0, 4.18.4-arch1-1-ARCH, LLVM 6.0.1)
Driver Version: 3.1 Mesa 18.1.7

Works for me on SteamOS, intel i7, Nvidia GTX 1080, but after hitting Play on the splash screen, I do not have proper mouse movement

Work on Linux Mint 19, i5, gtx660m, but i can't change my keycontrols.

Is working for me.

Información del equipo:
Fabricante: Unknown
Modelo: Unknown
Factor de forma: Portátil
Entrada táctil no detectada

Información sobre el procesador:
Fabricante de la CPU: GenuineIntel
Marca de la CPU: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Familia de la CPU: 0x6
Modelo de la CPU: 0x9e
Stepping de la CPU: 0x9
Tipo de CPU: 0x0
Velocidad: 3800 MHz
Procesadores lógicos: 8
Procesadores físicos: 4
HyperThreading: Compatible
FCMOV: Compatible
SSE2: Compatible
SSE3: Compatible
SSSE3: Compatible
SSE4a: No compatible
SSE41: Compatible
SSE42: Compatible
AES: Compatible
AVX: Compatible
CMPXCHG16B: Compatible
LAHF/SAHF: Compatible
PrefetchW: No compatible

Versión del sistema operativo:
Ubuntu 18.04.1 LTS (64 bits)
Nombre de kernel: Linux
Versión de kernel: 4.15.0-32-generic
Editor de X Server: The X.Org Foundation
Versión de X Server: 11906000
Gestor X Window: Compiz
Versión del runtime de Steam: steam-runtime-beta-release_2018-06-14

Tarjeta de vídeo:
Controlador: Intel Open Source Technology Center Mesa DRI Intel(R) HD Graphics 630 (Kaby Lake GT2) x86/MMX/SSE2
Versión del controlador: 3.0 Mesa 18.0.5
Versión de OpenGL: 3.0
Densidad de color del escritorio: 24 bits por píxel
Frecuencia de actualización del monitor: 60 Hz
Identificador del fabricante: 0x8086
Identificador del dispositivo: 0x591b
Revisión no detectada
Número de monitores: 1
Número de tarjetas de vídeo lógicas: 1
Resolución de pantalla principal: 1920 x 1080
Resolución de escritorio: 1920 x 1080
Tamaño de la pantalla principal: 73.70" x 41.46" (84.53" diag)
187.2cm x 105.3cm (214.7cm diag)
No se ha detectado la memoria VRAM principal

Tarjeta de sonido:
Dispositivo de sonido: Realtek ALC233

Memoria:
RAM: 15925 MB

Varios:
Idioma de la IU: Español
IDIOMA: es_ES.UTF-8
Espacio total en disco disponible: 452317 MB
Bloque libre más grande en el disco: 141990 MB
HMD de RV: Ninguno detectado

Informes de fallos recientes:

Skyrim not running on SteamPlay in Manjaro KDE

Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/5689.
@lil5 posted on 2018-08-27T15:54:30:

Your system information

  • Steam client version (build number or date): API v018, 1535062307
  • Distribution (e.g. Ubuntu): Manjaro KDE Linux 4.14.65
  • Opted into Steam client beta?: Yes
  • Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

Game launched via compatibility tool Steam Play

  • Clicked play
  • Didn't start game

The err.log file is from the terminal that I started steam from (same issue if I start steam normally).

File: err.log

Steps for reproducing this issue:

  1. run manjaro https://manjaro.org/get-manjaro/
  2. install steam
  3. download skyrim
  4. run
  5. fail on load

The game works fine for me on this Debian system, with two caveats :

  • I had already tried it in vanilla Wine, and possibly applied some system-wide fixes that I forgot about (maybe missing packages). I seem to recall sound issues at some point and graphical glitches several years ago.
  • I had some issues while trying to rebind keys, with a mysterious 0x45 key that was detected as constantly pressed by the game. It may have been linked to this issue. I fiddled with some settings, tried xset r off and the bug is gone for now ; I'm not sure if it's an actual fix or just a coincidence.

Other than that, the game runs perfectly for me, with no bugs, hiccups or crashes so far.

System Information

I confirm:

  • [x] that pressing the Play button in the Steam client is sufficient.
  • [ ] that runtime config options
    are necessary to run the game.
  • [x] that no workarounds other than the mentioned ones are necessary.

Issues

  • [x] I haven't experienced any issues.
  • [ ] There are no issues left open for this game.
  • [ ] Although I consider the gaming experience equal to Windows there are
    remaining issues:

Skyrim not running on SteamPlay in O

Your system information
Steam client version (build number or date): 1.0.0.56-1 (i think)
Distribution (e.g. Ubuntu): I3 Arch
Opted into Steam client beta?: Yes
Have you checked for system updates?: Yes
Please describe your issue in as much detail as possible:
Game launched via compatibility tool Steam Play

I am using bumblebee on an laptop with an 860m and an i7 from some time ago.

when i add optirun to the launch options or (if i dont) the progress bar on downloading DX11 doesn't seem to advance and then it switches to launch.

When i select my options and select run i just get a black schreen.

File: err.log

Steps for reproducing this issue:
install arch
install i3
install bumblebee
install nvidia driver
config bumblebee
install steam
download skyrim
add optirun to launch options
run
config run
BLACKCHREEN

Some bugs on my box (Debian Stretch / NVIDIA 390.77 / KDE) :

  • Crackling sound
  • Force to run kill -9 instead of simply quitting the game, otherwise it creates a zombie process.

Running the latest SteamOS, Skyrim (non SE) mostly works - 3 issues:

1) I cannot run any mods from the Steam Workshop - If I do, I get the error "failed to extract plugin file from ckm!" - If I click "ok", the game then runs, but the mods from Steam Workshop are not loaded.

skyrim error screenshot

2) there is occasional sound crackling

3) The opening screen (with 'play, options, data files, tech support, exit') does not scale properly when using Steam Link (SteamOS shows it fine, but TV with SteamLink shows the top left corner of the screen only).

I have the exact same issues as @jaubin My box is running Linux Mint 19, i5 and a 1060 6gb with the 396.54 drivers

Arch Linux
Kernel 4.18.9
Proton 3.7 beta
RX460
Mesa 18.2.1 (OpenGL4.4)
Proton 3.7-6 Beta

Prelauncher settings do net get saved/applied. Cannot get the game to run fullscreen. Therefore the performance is skewed (Runs ok, but a 400x600 window is not saying much)

Also getting the "Fail to extract plugin from ckm!" message as @briangular
Some modes do load. The one that don't, usually are in some kind of "legacy.bin" file format in the "./steamapps/workshop/content///" folder
Any way to like extract or unpack a .bin file?

My prelauncher problems got resolved yesterday due to a Skyrim update via steam. Runs flawlessly now

Fedora 28, Mesa 18.0.5, AMD RX 580.

I have tested the game with latest Proton 3.7-7 Beta and Dawnguard DLC disabled to workaround Wine bug that causes the game to hang on exit. Steam Workshop mods do not work (errors about ckm archive extraction and bad size) and there is a slightly crackling sound in the game sometimes, but it is not that bad and the game seems to be fully playable with good framerate on ultra details and no other issues.

Running Kubuntu 18.04 with an i5-2430M (sandybridge mobile graphics). Works fine other than crackling audio and not being able to load mods (unable to extract plugin from ckm archive).

Antergos with R9 390 on AMDGPU driver.

Game launches but sits on a black screen with no audio.

Launching with Wine's implementation of DirectX11 gets it to run, however as is the case with most people there's no audio. Additionally, the framerate is extremely chopping on relatively decent hardware, with it hovering around 20 - 25 FPS at fullscreen 1080p.

@Drunkenpanda2000 Oof, bumblebee/optirun has A LOT of issues on linux, most of them can be circumvented by using nvidia-xrun (run X11 with nvidia's gpu as the main one instead of the integrated one) so you may want to try that.

Otherwise, have you tried primusrun? It's way better than optirun. Just set the launch setting to "primusrun %command%" (without quotation marks) it should work better.

The game does not use DirectX11, it uses DirectX9. Only Special Edition uses DirectX11, it also works mostly fine thanks to dxvk, but skse does not work without a wine patch, and it requires a specific sound library enabled.

Perhaps the papropriate setting would be "PROTON_NO_D3D11=1 %command%" to disable d3d11 support altogether.

Some bugs on my box (Debian Stretch / NVIDIA 390.77 / KDE) :

* Crackling sound

* Force to run kill -9 instead of simply quitting the game, otherwise it creates a zombie process.

I have exactly the same setup, Debian Stretch with backported kernel (4.18.0) and backported nVidia driver 390 and I have crackling sound and force kill problems. The graphical problems with shadows seem to be gone for now, haven't tested the water problem I used to have when running the game on Play on Linux yet (all visibility was lost), I'm thinking that may have been a result of the workaround i used to implement to deal with shadow problems. Going to test out SKSE and mods soon.

@Luticus crackling sound is probably not game specific, it's pulseaudio being shitty, as always.

Set this in pulseaudio default.pa:

load-module module-udev-detect use_ucm=0 tsched=0

(The above is a commonly touted fix for crackling audio in pulse)

And for good measure to eliminate a bunch of other problems and further reduce crackling, in pulseaudio daemon.conf trey setting the following:

# Start as daemon 
daemonize = yes
allow-module-loading = yes

# Realtime optimization
high-priority = yes
realtime-scheduling = yes
realtime-priority = 9

# Scales the device-volume with the volume of the "loudest" application
flat-volumes = no

# Script file management
load-default-script-file = yes
default-script-file = /etc/pulse/default.pa

# Sample rate
resample-method = speex-float-9
default-sample-format = s24-32le
default-sample-rate = 192000
alternate-sample-rate = 176000
exit-idle-time = -1

# Optimized fragements for steam
default-fragments = 5
default-fragment-size-msec = 2

# Volume
deferred-volume-safety-margin-usec = 1

(source )

The changes require a restart to take effect, this should severely reduce the crackling sound issues in various applications. Sampling rate may need to be set lower (96000 preferably, don't go below 48000) on some cards.

If you use a something like an equalizer with pulseaudio, these tend to add to these kinds of issues.

@Rabcor I'll give those values a shot and see if it helps, I tweaked some stuff already and it seemed to help some but hasn't made it perfect yet.

@Everyone Also I can confirm that the green water issue is still a thing. When when under water the entire screen will turn green and you can't see anything. It's like that on normal wine (Play on Linux) too for me. The really great news is that the shadow glitch is fully resolved! So, no more flickering shadows!

I also managed to get SKSE, SkyUI, and HDT, among other mods fully working! That was something I was rather worried about. The key to SKSE for anyone who doesn't know: Get it from the nexus, don't use the one you can get from steam, as far as I know. Install it by dragging files into data and rename your skyrimlauncher.exe to something else (skyrimlauncher.exe.orig) and then rename the skyui launcher to skyrimlauncher.exe. Once you launch the game it should work. Test it by hitting the ~ (tilde) key to bring up the console and typing GetSKSEVersion. If it returns a version number, you're good to go.

The green water issue is not a Linux bug.
Workaround here : https://steamcommunity.com/app/72869/discussions/0/540744936022804105/
File to edit is :
/steamapps/common/Skyrim/Skyrim/SkyrimPrefs.ini

Le lundi 15 octobre 2018 à 18:34:57 UTC+2, Joe <[email protected]> a écrit :

I'll give those values a shot and see if it helps, I tweaked some stuff already and it seemed to help some but hasn't made it perfect yet.

Also I can confirm that the green water issue is still a thing. When when under water the entire screen will turn green and you can't see anything. It's like that on normal wine (Play on Linux) too for me. The really great news is that the shadow glitch is fully resolved! So, no more flickering shadows!

I also managed to get SKSE, SkyUI, and HDT, among other mods fully working! That was something I was rather worried about. The key to SKSE for anyone who doesn't know: Get it from the nexus, don't use the one you can get from steam, as far as I know. Install it by dragging files into data and rename your skyrimlauncher.exe to something else (skyrimlauncher.exe.orig) and then rename the skyui launcher to skyrimlauncher.exe. Once you launch the game it should work. Test it by hitting the ~ (tilde) key to bring up the console and typing GetSKSEVersion. If it returns a version number, you're good to go.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I also managed to get SKSE, SkyUI, and HDT, among other mods fully working! That was something I was rather worried about. The key to SKSE for anyone who doesn't know: Get it from the nexus, don't use the one you can get from steam, as far as I know. Install it by dragging files into data and rename your skyrimlauncher.exe to something else (skyrimlauncher.exe.orig) and then rename the skyui launcher to skyrimlauncher.exe. Once you launch the game it should work. Test it by hitting the ~ (tilde) key to bring up the console and typing GetSKSEVersion. If it returns a version number, you're good to go.

@Luticus Can you please be more specific about this? I've tried this, but SKSE still doesn't work for me.
Moreover, I've compared SKSE files installed by Steam and they're exactly the same as downloaded from official SKSE website (http://skse.silverlock.org/ - which isn't nexus, btw, so it's unclear what exactly you recommend to download from nexus), only difference is Steam version also contain extra file skse_steam_boot.exe and, probably, has no files in Data/Scripts/.

@powerman So for me I just downloaded a copy manually, from the official skse page, (got the link from nexus, probably why I said it that way). Then you extract the files to the folder ( ~/.steam/steam/steamapps/common/Skyrim/ ). You don't actually need the txt files or the src files (unless you make mods). Now you'll have an skse_loader.exe in your skyrim folder as well as the SkyrimLauncher.exe. What you want to do effectively is replace SkyrimLauncher with the skse_loader.exe, but you'll want to keep SkyrimLauncher around in case you need to swap resolutions or change mod load orders, etc. So rename the original SkyrimLauncher to something else and rename skse_loader to SkyrimLauncher.exe. Now when you hit the play button in steam it will load skse. Once you're at the title screen and can tell it to continue or load or whatever, hit the tilde ( ~ ) key and bring up a console. Here type GetSKSEVersion and it will return a version number. If you get the version number then you're set. Remember to regularly back up the data file in case you screw everything up trying to manually install a big mod or something.

@jaubin Thanks, I'll look into that

@jaubin and anyone else who suffers green water, the path to SkyrimPrefs.ini in linux with steam play is: ~/.steam/steam/steamapps/compatdata/72850/pfx/drive_c/users/steamuser/My Documents/my games/skyrim/SkyrimPrefs.ini Or at the very least that should point people in, hopefully, the right direction. Not sure if some of that may vary from system to system, but the "locate" command is your friend :)

Well, it's a bit unexpected, but I've solved issue with SKSE… by changing Linux kernel from 4.9.74-unofficial+grsec (latest available hardened kernel with GrSecurity and PaX support from https://github.com/minipli/linux-unofficial_grsec) to 4.14.65-gentoo (current "stable" Gentoo Linux kernel without GrSecurity/PaX).

I've got an idea hardened kernel may be the reason of this issue when I've tried to run Overlord game. It's steamos/linux version and it fail to run because it tried to access some files under /sys which was protected by GrSecurity. For Overlord I was able to fix the issue by disabling CONFIG_GRKERNSEC_SYSFS_RESTRICT, which doesn't helps Skyrim/SKSE, but I've tried to boot non-hardened kernel just in case - and it fixed the issue with SKSE! So, looks like SKSE does something not-really-nice from GrSecurity's point of view, and this breaks SKSE - or it's an issue with too old 4.9.74 kernel (like kernel bug fixed in 4.12 which breaks Witcher 2). :disappointed:

SKSE installed from Steam works just fine after cp skse_loader.exe SkyrimLauncher.exe.

@kisak-valve Requesting an XAudio2 label for this game...

Anyone else having issues changing hotkeys in Skyrim? When I try to change a hotkey, any hotkey, it sets the hotkey to 0x45 whatever I press. (using latest Proton, 3.16-3). Not tested with earlier.
@kisak-valve or if you've heard of similar issues in other games?

I had issue with changing hotkeys, IIRC no matter what I press I get "Num" or something like that. Worked around by switching NumLock off.

@powerman Yuup! That did it. the 0x45 I got was the numlock key.. for some reason it thinks it is continuously pressed when numlock is on.
Not sure if a local fault, I know I enable numlock by default in my .profile if that does something strange.. Or if this is a wine issue that should be reported upstream.

With 3.16-4:

  • Mods are now installed and loaded from Steamworks
  • Numlock issue no longer present making it impossible to change hotkeys

Proton 3.16-4 Work Great SE Editon too but for SE Edition no sound for npc !
For Skyrim all work great but no close correctly !

In my case the problem was, a ubuntu 18.10 problem with missing libraries when using dual graphics card in my laptop, i had to manually install this lib to launch the game, my problem was just steam not loading.

sudo apt-get install libnvidia-gl-390:i386

I comment it just inc se somebody having same problem with ubuntu 18.10 in a laptop.

Some bugs on my box (Debian Stretch / NVIDIA 390.77 / KDE) :

* Crackling sound

* Force to run kill -9 instead of simply quitting the game, otherwise it creates a zombie process.

I have exactly the same setup, Debian Stretch with backported kernel (4.18.0) and backported nVidia driver 390 and I have crackling sound and force kill problems. The graphical problems with shadows seem to be gone for now, haven't tested the water problem I used to have when running the game on Play on Linux yet (all visibility was lost), I'm thinking that may have been a result of the workaround i used to implement to deal with shadow problems. Going to test out SKSE and mods soon.

Same issue here. Have to force kill.

The water bug is also present in Windows. Not a Proton bug.
Le lundi 3 décembre 2018 à 17:50:05 UTC+1, Cxpher notifications@github.com a écrit :

Some bugs on my box (Debian Stretch / NVIDIA 390.77 / KDE) :

  • Crackling sound
  • Force to run kill -9 instead of simply quitting the game, otherwise it creates a zombie process.

I have exactly the same setup, Debian Stretch with backported kernel (4.18.0) and backported nVidia driver 390 and I have crackling sound and force kill problems. The graphical problems with shadows seem to be gone for now, haven't tested the water problem I used to have when running the game on Play on Linux yet (all visibility was lost), I'm thinking that may have been a result of the workaround i used to implement to deal with shadow problems. Going to test out SKSE and mods soon.

Same issue here. Have to force kill.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Since 3.16-5, the Game crashes in the Main Menu, someone could confirm me it is happening for him to since the update.
The Game is accessible if a fast double Enter Press is performed.

Hello @Alexmitter, most likely the same as here: https://github.com/ValveSoftware/Proton/issues/4#issuecomment-446368793

@kisak-valve sorry if i am wrong, but should this not be included as Faudio is included in 3.16-5?

Edit: Sorry i was reading wrong. Got it.

Hi,
Works fine for me but I have FFMPEG installed (Debian Stable)
Le mardi 11 décembre 2018 à 22:53:18 UTC+1, Alexmitter notifications@github.com a écrit :

@kisak-valve sorry if i am wrong, but should this not be included as Faudio is included in 3.16-5?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Having trouble when switching windows here, everytime I use alt + tab the game window becomes ultra small and i need to restart the computer to play again.
Resolution : 1920x1080
GPU : R9 380
Kernel driver in use: amdgpu
Kernel modules: amdgpu
Operating System Version:
Ubuntu 16.04 (LTS) with Unity
Kernel Name: Linux
Kernel Version: 4.15.0-42-generic

You must kill -9 tesv.exe to do this.
This is the reason why I always play in window mode : games tend not to survive to alt-tab in full screen while in window mode it is not a problem.
Le dimanche 16 décembre 2018 à 05:33:21 UTC+1, tsouza0 notifications@github.com a écrit :

Having trouble when switching windows here, everytime I use alt + tab the game window becomes ultra small and i need to restart the computer to play again.
Resolution : 1920x1080
Operating System Version:
Ubuntu 16.04 (LTS) with Unity
Kernel Name: Linux
Kernel Version: 4.15.0-42-generic


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

The Elder Scrolls V: Skyrim freezes for a few seconds on every mouse movement

Issue transferred from https://github.com/ValveSoftware/Proton/issues/2348.
@o-alquimista posted on 2019-02-19T11:36:36:

Proton version affected: 3.16-x Beta and Stable (does not affect 3.7-x Beta or Stable)
OS: elementary OS 5 Juno
_Specs:
i3-8100 w/ UHD Graphics 630
8 GB of DDR4-2400 Mhz RAM
Kingston SATA SSD A400_

The problem
The Elder Scrolls V: Skyrim freezes for a few seconds on every mouse movement. If I don't move the cursor and just press the arrow keys to walk around, it won't freeze and the game runs smooth.

@kisak-valve I have the exact same issue.

The Elder Scrolls V: Skyrim freezes for a few seconds on every mouse movement

Issue transferred from #2348.
@o-alquimista posted on 2019-02-19T11:36:36:

Proton version affected: 3.16-x Beta and Stable (does not affect 3.7-x Beta or Stable)
OS: elementary OS 5 Juno
_Specs: i3-8100 w/ UHD Graphics 630 8 GB of DDR4-2400 Mhz RAM Kingston SATA SSD A400_

The problem
The Elder Scrolls V: Skyrim freezes for a few seconds on every mouse movement. If I don't move the cursor and just press the arrow keys to walk around, it won't freeze and the game runs smooth.

A correction, this issue only happens on elementary OS's Pantheon DE, so far. I'm on Ubuntu 18.04 LTS w/ GNOME now and none of these freezes happen. I should report it to them, instead.

Hi, 
With NVidia driver 410.104 and Proton 3.16-8 dragons become invisible. This is extremely annoying for the game. :-(
Le lundi 25 février 2019 à 22:37:24 UTC+1, Douglas S. notifications@github.com a écrit :

The Elder Scrolls V: Skyrim freezes for a few seconds on every mouse movement

Issue transferred from #2348.
@o-alquimista posted on 2019-02-19T11:36:36:

Proton version affected: 3.16-x Beta and Stable (does not affect 3.7-x Beta or Stable)
OS: elementary OS 5 Juno
Specs: i3-8100 w/ UHD Graphics 630 8 GB of DDR4-2400 Mhz RAM Kingston SATA SSD A400

The problem
The Elder Scrolls V: Skyrim freezes for a few seconds on every mouse movement. If I don't move the cursor and just press the arrow keys to walk around, it won't freeze and the game runs smooth.

A correction, this issue only happens on elementary OS's Pantheon DE, so far. I'm on Ubuntu 18.04 LTS w/ GNOME now and none of these freezes happen. I should report it to them, instead.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Okay it only targets one specific dragon, Viinturuth, and it is a known bug of the game.
Le dimanche 24 mars 2019 à 14:17:19 UTC+1, Julien Aubin julien_aubin_lm@yahoo.fr a écrit :

Hi, 
With NVidia driver 410.104 and Proton 3.16-8 dragons become invisible. This is extremely annoying for the game. :-(
Le lundi 25 février 2019 à 22:37:24 UTC+1, Douglas S. notifications@github.com a écrit :

The Elder Scrolls V: Skyrim freezes for a few seconds on every mouse movement

Issue transferred from #2348.
@o-alquimista posted on 2019-02-19T11:36:36:

Proton version affected: 3.16-x Beta and Stable (does not affect 3.7-x Beta or Stable)
OS: elementary OS 5 Juno
Specs: i3-8100 w/ UHD Graphics 630 8 GB of DDR4-2400 Mhz RAM Kingston SATA SSD A400

The problem
The Elder Scrolls V: Skyrim freezes for a few seconds on every mouse movement. If I don't move the cursor and just press the arrow keys to walk around, it won't freeze and the game runs smooth.

A correction, this issue only happens on elementary OS's Pantheon DE, so far. I'm on Ubuntu 18.04 LTS w/ GNOME now and none of these freezes happen. I should report it to them, instead.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

  • GTX 960
  • Blob 418.56
  • Ubuntu 18.10
  • Proton 4.2.1

Game runs okay-ish but FPS could be higher, on all low settings.

Game crashes when trying to quit and many forked processes stay running, hard to kill them all.

The Elder Scrolls V: Skyrim vertical map scrolling issue w/Proton 4.2-1

Issue transferred from https://github.com/ValveSoftware/Proton/issues/2487.
@Noskid23 posted on 2019-04-01T23:45:44:

Compatibility Report

  • The Elder Scrolls V: Skyrim
  • Steam AppID of the game: 72850

System Information

I confirm:

  • [x ] that I haven't found an existing compatibility report for this game.
  • [x] that I have checked whether there are updates for my system available.

Symptoms

Since upgrading to Proton 4.2-1 (from 3.16-8 Beta), map scrolling no longer works as it should (it did on every earlier version I tried). Horizontal map scrolling still works, but vertical is non-functional. I have tried older game save files to make sure it was not related to corruption in a saved game file. I then reloaded 3.16-8 Beta and can confirm that map scrolling again works as it should; changed back to 4.2 and it's broken again. As this seems to be a regression in 4.2, I wanted to report it. In case it helps, I've uploaded logs for 4.2.1 and for 3.16-8 - in each case I loaded the same save game file and attempted to scroll from top to bottom on the map.

I have over 400 hours on this title and the only other issue I have with it is that quitting to desktop locks up the system so I quit to menu and then kill tesv.exe process, this is with all versions of Proton.

I have tested this with Skyrim Special Edition (489830) also, and the effect is not present there, i.e. map scrolling works normally with 4.2-1 in this title.

Reproduction

Change start options to use Proton 4.2-1 and issue recurs.

Posting here since it looks like all unofficial game issues are put into the same place. Any mouse movement in Skyrim causes the game to stutter a lot. Controller movement is fine though.

https://pastebin.com/BXESQZrW

EDIT: Switching my cpu governor to performance mode seems to help alleviate the issue significantly.

The Elder Scrolls V: Skyrim vertical map scrolling issue w/Proton 4.2-1

Issue transferred from #2487.
@Noskid23 posted on 2019-04-01T23:45:44:

Compatibility Report

* The Elder Scrolls V: Skyrim

* Steam AppID of the game: 72850

System Information

* GPU: RX 470

* Driver/LLVM version: 4.5 (Compatibility Profile) Mesa 19.0.1 - padoka PPA

* Kernel version: 4.15.0-46-generic

* Link to full system information report as [Gist]:
  https://gist.github.com/Noskid23/647724c620b55ceb5205628ba5e1ad55

* Proton version: 4.2-1

I confirm:

* [x ] that I haven't found an existing compatibility report for this game.

* [x]  that I have checked whether there are updates for my system available.

Symptoms

Since upgrading to Proton 4.2-1 (from 3.16-8 Beta), map scrolling no longer works as it should (it did on every earlier version I tried). Horizontal map scrolling still works, but vertical is non-functional. I have tried older game save files to make sure it was not related to corruption in a saved game file. I then reloaded 3.16-8 Beta and can confirm that map scrolling again works as it should; changed back to 4.2 and it's broken again. As this seems to be a regression in 4.2, I wanted to report it. In case it helps, I've uploaded logs for 4.2.1 and for 3.16-8 - in each case I loaded the same save game file and attempted to scroll from top to bottom on the map.

I have over 400 hours on this title and the only other issue I have with it is that quitting to desktop locks up the system so I quit to menu and then kill tesv.exe process, this is with all versions of Proton.

I have tested this with Skyrim Special Edition (489830) also, and the effect is not present there, i.e. map scrolling works normally with 4.2-1 in this title.

Reproduction

Change start options to use Proton 4.2-1 and issue recurs.

I can reproduce this vertical map scrolling bug and also the hang when you exit the game.
Reverting to 3.16-9 Beta solves both problems in this system. No performance loss. Running great.

AMD RX 560
i3-8100 processor
Fedora Workstation 30 (GNOME on Wayland) and Kubuntu 18.04 (Xorg)

EDIT: Tested Proton 4.2-6. Still can't scroll vertically on the map. However, the game did not hang on exit. Further tests needed.

EDIT 2: Proton 4.2-6: Game hangs on exit most of the time, and you have to kill it manually.
About the vertical scrolling bug on the map:
You can still navigate the map view using the WASD keys. It's just the mouse that won't let you do it.

OS: Ubuntu 19.04 disco
Kernel: x86_64 Linux 5.0.0-20-generic
CPU: Intel Core i5-2320 @ 4x 3.3GHz
GPU: GeForce GT 710
Driver: nvidia 418
RAM: 8 Gb
Proton: 4.2-9

Steam correctly identifies my video card, but when I enter the skyrim settings, it displays nvidia 470 for me. Fps keeps at the level of 13-17, but most likely this is due to problems with incorrect identification of the video card. Help me fix the error, please.

Hello @indrih17, Proton/wine seeing your video card as a GTX 470 is the same as https://github.com/ValveSoftware/wine/issues/42. Wine hasn't been taught to identify your video card, so it falls back to a generically picked DirectX 11 capable nVidia card. There's a good chance that part is just cosmetic and your performance issue is with maxing out vram on the card.

@kisak-valve On Windows, I could get 40 fps, here above 17 does not work. How to increase fps?

Issue with map scrolling as well with gamepad. It works from time to time. Before it worked all the time.
Pad : XBOX 360
Environment :Debian Buster AMD64KDENVidia GTX 1070 w/ blob 418.74Proton : 4.2.9Windowed mode : on
Le lundi 15 juillet 2019 à 23:55:16 UTC+2, indrih17 notifications@github.com a écrit :

@kisak-valve On Windows, I could get 40 fps, here above 17 does not work. How to increase fps?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I found the game worked fine in Wine 4.6 but if I recalled there was some issues with the Creation kit which is a tool that can be download in Steam to make mods for Skyrim.

One of the issues is that when you edit an objects position, the integer will become a high value instead of going up a single integer.

For me, the game does not even launch. A few seconds after clicking the "Play game" button I see the launcher menu for a split second, then it vanishes and the process goes away.

I'm running the game with the following command:

%command% 2>&1 | tee /home/user/skyrim.log

And I get the following output:

ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
esync: up and running.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
pid 6015 != 6014, skipping destruction (fork without exec?)
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
esync: up and running.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
pid 6050 != 6049, skipping destruction (fork without exec?)
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
esync: up and running.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Setting breakpad minidump AppID = 72850
Steam_SetMinidumpSteamID:  Caching Steam ID:  <redacted> [API loaded no]
ERROR: ld.so: object '/home/user/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
er.exe: malloc.c:2385: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
wine: Assertion failed at address 0xeed25929 (thread 0029), starting debugger...
er.exe: malloc.c:2385: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
pid 6086 != 6085, skipping destruction (fork without exec?)

The main error is the following (at the bottom):

er.exe: malloc.c:2385: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
wine: Assertion failed at address 0xeed25929 (thread 0029), starting debugger...
er.exe: malloc.c:2385: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long)

I was unable to find anything useful on the internet with that error message, as it suggests that the program is doing bad stuff with its memory management.

System information:

OS: Arch Linux
Kernel: 5.2.9.a-1-hardened #1 SMP PREEMPT
CPU: Intel i7-4790K
GPU: AMD Radeon VII
Driver: 4.5 (Compatibility Profile) Mesa 19.1.2
RAM: 32GB
Proton: 4.11-2 and 4.2.9
Running Steam inside a flatpak (however, I have a very similar issue with Skyrim when running steam natively)
Steam Runtime Version:  steam-runtime_0.20190711.3

Edit: Here is the (relevant) output when run with PROTON_LOG=1:

[...]
1678.939:0027:0028:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\opengl32.dll" at 0x7ccf0000: builtin
1678.939:0027:0028:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\wined3d.dll" at 0x7ce40000: builtin
1678.939:0027:0028:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\d3d9.dll" at 0x7cfa0000: builtin
er.exe: malloc.c:2385: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
1678.973:0027:0028:trace:seh:raise_exception code=80000101 flags=1 addr=0xea653929 ip=ea653929 tid=0028
1678.973:0027:0028:trace:seh:raise_exception  eax=00000000 ebx=00000002 ecx=0032db0c edx=00000000 esi=00000008 edi=00000000
1678.973:0027:0028:trace:seh:raise_exception  ebp=0032db0c esp=0032daf0 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00200282
1678.973:0027:0028:trace:seh:call_stack_handlers calling handler at 0x41d005 code=80000101 flags=1
1678.973:0027:0028:trace:seh:call_stack_handlers handler at 0x41d005 returned 1
1678.973:0027:0028:trace:seh:call_stack_handlers calling handler at 0x407fad code=80000101 flags=1
1678.973:0027:0028:trace:seh:_except_handler4_common exception 80000101 flags=1 at 0xea653929 handler=0x407fad 0x32d7cc 0x32d76c cookie=42f831d9 scope table=0x424bc8 cookies=-2/0,-120/0
1678.973:0027:0028:trace:seh:_except_handler4_common level 1 prev -2 filter 0x407ce9
1678.973:0027:0028:trace:seh:_XcptFilter (80000101,0x32d688)
1678.973:0027:0028:trace:seh:_except_handler4_common filter returned CONTINUE_SEARCH
1678.973:0027:0028:trace:seh:_except_handler4_common reached -2, returning ExceptionContinueSearch
1678.973:0027:0028:trace:seh:call_stack_handlers handler at 0x407fad returned 1
1678.973:0027:0028:trace:seh:call_stack_handlers calling handler at 0x7b4aa4c0 code=80000101 flags=1
wine: Assertion failed at address 0xea653929 (thread 0028), starting debugger...
1678.974:0027:0028:trace:seh:start_debugger Starting debugger "winedbg --auto 39 100"
er.exe: malloc.c:2385: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
1678.974:0027:0028:trace:seh:raise_exception code=80000101 flags=1 addr=0xea653929 ip=ea653929 tid=0028
1678.974:0027:0028:trace:seh:raise_exception  eax=00000000 ebx=00000002 ecx=0032b98c edx=00000000 esi=00000008 edi=00000000
1678.974:0027:0028:trace:seh:raise_exception  ebp=0032b98c esp=0032b970 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00200282
1678.974:0027:0028:trace:seh:call_stack_handlers calling handler at 0x7bcaa0d0 code=80000101 flags=1
1678.974:0027:0028:trace:seh:call_stack_handlers handler at 0x7bcaa0d0 returned 2
1678.974:0027:0028:trace:seh:call_stack_handlers calling handler at 0x41d005 code=80000101 flags=11
1678.974:0027:0028:trace:seh:call_stack_handlers handler at 0x41d005 returned 1
1678.974:0027:0028:trace:seh:call_stack_handlers calling handler at 0x407fad code=80000101 flags=11
1678.974:0027:0028:trace:seh:_except_handler4_common exception 80000101 flags=11 at 0xea653929 handler=0x407fad 0x32b64c 0x32b5ec cookie=42f831d9 scope table=0x424bc8 cookies=-2/0,-120/0
1678.974:0027:0028:trace:seh:_except_handler4_common level 1 prev -2 filter 0x407ce9
1678.974:0027:0028:trace:seh:_XcptFilter (80000101,0x32b508)
1678.974:0027:0028:trace:seh:_except_handler4_common filter returned CONTINUE_SEARCH
1678.974:0027:0028:trace:seh:_except_handler4_common reached -2, returning ExceptionContinueSearch
1678.974:0027:0028:trace:seh:call_stack_handlers handler at 0x407fad returned 1
1678.974:0027:0028:trace:seh:call_stack_handlers calling handler at 0x7b4aa4c0 code=80000101 flags=11
1678.974:0027:0028:trace:seh:call_stack_handlers handler at 0x7b4aa4c0 returned 1
1678.974:0027:0028:err:seh:raise_exception Unhandled exception code 80000101 flags 1 addr 0xea653929
1679.998:0016:001a:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\winebus.sys" : builtin
1679.998:0016:001a:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\setupapi.dll" : builtin
pid 1094 != 1093, skipping destruction (fork without exec?)

Update to my lengthy comment from above:

Skyrim works with the normal Arch kernel (in my case tested with 5.2.11.arch1-1) but not with the hardened kernel.

Ubuntu 19.04, Linux 5.0.0-29-generic, Mesa 19.0.8, Proton 4.11-6, Intel HD Graphics 620. Skyrim is installed on a Windows NTFS partition, with the compatdata folder on there symlinked to compatdata on my Linux partition. I’ve created Skyrim’s stuff in the Windows user folder. The launcher starts and works just fine. When I click ‘Play’, the launcher closes, but comes right back; the game doesn’t start.

Running the game with PROTON_LOG=1 produces this: steam-72850.log.

Edit: works fine now with Proton 4.11-7, apart from hanging on exit. Not sure if it’s the update or something else …

Ubuntu 19.04, Proton 4.11.
I identified a problem that on Linux Skyrim does not start with the Russian language. On Windows this was not. The problem is reproduced on another pc.

Compatibility Report

System Information

LOG:
steam-72850.log

Symptoms

Game runs, but loading screen was at a super low 3-4 FPS, resulting in the game taking almost 10 minutes to start the beginning game sequence.

Got the following error with Proton 5.0.1 when launching the game :"Failed to create the renderer. Unable to create the renderer".The game works perfectly fine w/ Proton 4.11-12.
Playing in windowed mode.

System info :

  • GPU : RTX 2070 SUPER
  • Driver : NVIDIA 440.59
  • Distro : Debian Buster
  • Desktop environment : KDE
  • Locale : fr_FR.UTF-8

UPDATE : the issue does affect all 5.0.x versions of Proton at least until 5.0.5 but no 4.11.x (and older) versions.

Hello @jaubin, your mail chain has created a fair bit of spam on the issue report. If you're using this method, please try to trim the old content out of the email.

@indrih17 You can start Skyrim with the Russian language if you back up the "SkyrimLauncher.exe" and rename "TESV.exe" to "SkyrimLauncher.exe".
I have experienced the same error as you.

Issue description:

  1. Switch the language of the game in Steam to Russian
  2. Start the game
  3. Launcher appears showing only a background image with no text on it
  4. Launcher crashes with no errors in ~/steam-72850.log
    (*) Issue only reproduces with the Russian language of the game

    What I've tried:

  • Installing allfonts with protontricks intro skyrim's WINEPREFIX .local/share/Steam/steamapps/compatdata/72850/pfx/
  • Running the game with ru_RU.UTF-8 locale as follows LC_ALL=ru_RU.UTF-8 %command%
    (I've uncommented ru_RU.UTF-8 locale in /etc/locale.gen and generated it with sudo locale-gen)

System Information

  • GPU: RTX 2070
  • Driver/LLVM version: NVIDIA 440.64, llvm 9.0.1
  • Kernel version: 5.5.8-1-MANJARO
  • sysinfo
  • Proton version: 5.0-5

Game won't start with Proton 5.0-5

EDIT:
Problem solved by installing the package mesa-vulkan-drivers:i386.

  1. Press Play and keep watching the loading animations in the Steam client.
  2. The loading animation is gone, the 'running' indicators are gone and the game window did not show up.
  3. Try again, same results

It works with Proton 4.11-13

System information

GPU: AMD RX 560 4GB
Kernel: 5.3.0-42-generic
OS: Ubuntu 19.10 Eoan (x86_64)
Proton: 5.0-5
System information and Proton log: https://gist.github.com/o-alquimista/ec41121e8cebb20bf43da28114e37d4b

Hello @o-alquimista, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. Also, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

Hi,

Actually the windowed bug comes from DXVK. If you use PROTON_USE_WINED3D=1 for Proton 5.0.x Skyrim just starts fine and works fine, albeit a bit sluggish compared to DXVK.

UPDATE : DXVK update with Proton 5.0.6 does not solve the issue. Using the WINED3D workaround solves it. The sluggishness issue was not related to Skyrim nor Proton but something else on my host (Folding at home running in the background...)

@o-alquimista, your system is missing 32 bit vulkan support for your video card. Please run sudo apt install mesa-vulkan-drivers:i386 and retest.

@o-alquimista, your system is missing 32 bit vulkan support for your video card. Please run sudo apt install mesa-vulkan-drivers:i386 and retest.

Thank you. It's working now.

Performance decreased considerably with v5, compared to the latest v4, but that's probably due to some new feature. With v4 I could play smoothly in Ultra High, but with v5 I can only play in High (with occasional stutters during intense movement).

No idea if this has been brought up yet, and yes I know there's not really a point to it, but the title for the game and this issue should be:

The Elder Scrolls V: Skyrim
not
The Elders Scrolls V: Skyrim

@GloriousEggroll it's not related, but The Elders Scrolls: Skyrim SE audio does not work for me with Proton GE 5.8, except Bethesda intro logo. It works with official proton 5.0.7 and xaudio. Is there a way to fix that?

Sound issues with Skyrim and Skyrim SE (Possible Solution)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/3974.
@Xeroderma posted on 2020-06-12T06:01:51:

Game

  • Name of the game: The Elder Scrolls V: Skyrim (Special Edition)
  • Steam AppID of the game: 72850, 489830

System Information

  • GPU: NVIDIA GeForce GTX 1080ti
  • Driver/LLVM version: nvidia 418.113
  • Kernel version: 4.19.0-9-amd64
  • Proton version: 5.0

Symptoms

Sound stops playing after some minutes of play.
This is a known Engine-Bug of both Skyrim versions. To fix this the game needs to be installed on drive C.
Proton seems to use the Z-drive to load the game, what may lead to this issue.
Reports of players having this issue in windows can be found all across the internet.

Possible solution

Instead of using the Z-drive to access the game files, a symbolic link could be made pointing into the prefix, so the game could be launched from the c-drive.
The registry would need to be changed accordingly.

Hi,

Actually the windowed bug comes from DXVK. If you use PROTON_USE_WINED3D=1 for Proton 5.0.x Skyrim just starts fine and works fine, albeit a bit sluggish compared to DXVK.

UPDATE : DXVK update with Proton 5.0.6 does not solve the issue. Using the WINED3D workaround solves it. The sluggishness issue was not related to Skyrim nor Proton but something else on my host (Folding at home running in the background...)

Hi,

I tested again with Proton 5.13-1 and the issue is still there. The same workaround applies.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

BLaDZer picture BLaDZer  ·  3Comments

raikirii picture raikirii  ·  3Comments

lucifertdark picture lucifertdark  ·  3Comments

juppso picture juppso  ·  3Comments

shanefagan picture shanefagan  ·  3Comments