The Elder Scrolls V: Skyrim (72850) #460
Comments
|
I dont have Music and some sound effects and voices seem to be missing My system: |
kisak-valve
added
the
Game compatibility - Unofficial
kisak-valve
changed the title
|
Download xact if you are having trouble with sound. See: #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: Operating System Version: Video Card: |
|
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: Información sobre el procesador: Versión del sistema operativo: Tarjeta de vídeo: Tarjeta de sonido: Memoria: Varios: Informes de fallos recientes: |
|
Skyrim not running on SteamPlay in Manjaro KDE Issue transferred from ValveSoftware/steam-for-linux#5689. Your system information
Please describe your issue in as much detail as possible:Game launched via compatibility tool Steam Play
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:
|
|
The game works fine for me on this Debian system, with two caveats :
Other than that, the game runs perfectly for me, with no bugs, hiccups or crashes so far. |
System Information
I confirm:
Issues
|
|
Skyrim not running on SteamPlay in O Your system information 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: |
|
Some bugs on my box (Debian Stretch / NVIDIA 390.77 / KDE) :
|
|
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 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 |
|
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. |
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:
(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: (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 :
<YOUR_STEAM_APPS_PATH>/steamapps/common/Skyrim/Skyrim/SkyrimPrefs.ini
Le lundi 15 octobre 2018 à 18:34:57 UTC+2, Joe <notifications@github.com> 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.
|
@Luticus Can you please be more specific about this? I've tried this, but SKSE still doesn't work for me. |
|
Hello @indrih17, Proton/wine seeing your video card as a GTX 470 is the same as ValveSoftware/wine#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:
And I get the following output: The main error is the following (at the bottom): 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: Edit: Here is the (relevant) output when run with |
|
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 Running the game with 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. |
Compatibility Report
System Information
LOG: SymptomsGame 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". Issue description:
What I've tried:
System Information
|
|
Game won't start with Proton 5.0-5 EDIT:
It works with Proton 4.11-13 System informationGPU: AMD RX 560 4GB |
|
Hello @o-alquimista, please copy your system information from Steam ( |
|
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 |
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). |
This comment has been minimized.
This comment has been minimized.
|
@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? |
kisak-valve
changed the title
|
Sound issues with Skyrim and Skyrim SE (Possible Solution) Issue transferred from #3974. Game
System Information
SymptomsSound stops playing after some minutes of play. Possible solutionInstead 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. |
Hi, I tested again with Proton 5.13-1 and the issue is still there. The same workaround applies. |
|
Skyrim "Failed to initialize renderer" on Wayland Issue transferred from #4900. Compatibility Report
System Informationhttps://gist.github.com/RavenOchlich/ab89e8b570c8a8540084b300fa1b2e3d I confirm:
##Log File SymptomsThe Launcher starts fine, but when i hit Play a messagebox opens with "Failed to initialize renderer". Changing the resolution or enable windowed mode doesn't changes the error. The game was running under Xorg (Awesome vm) fine. Now on Wayland(Sway) the error occurs. Reproductionstart Skyrim |
|
Hello @RavenOchlich, your log includes |
I enabled Proton Experimental and the problem is gone. The game now seems to run fine. Thanks! |
|
Replying to #460 (comment)
Hi,
You can run as well the game with environment variable WINE_USE_D3D=1 - I do
this otherwise the game won't start in windowed mode (and this has been the
case since Proton 5.x).
|
and others
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/
The text was updated successfully, but these errors were encountered: