Open SeanRamey opened 4 years ago
Hello @SeanRamey, you could give fsync a try and see if that has a significant effect on performance for this game.
Unlikely to be Proton/Steam specific. This game gets very CPU intensive and does this on Windows as well.
@Ttimo I don't have these same slowdowns in Windows 10 on the same PC. The only variables are Linux/Proton. @kisak-valve I've never done a kernel swap before, but I'll give it a try.
I had these slowdown problems as well, they seem to have disappeared (or at least drastically improved) in the last few days. But I can't tell if it's due to Arch kernel updates, Noita update or something else .. (still using Proton 4.11).
Noita (881100)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3221. @TehCorwiz posted on 2019-11-14T23:43:18:
There are two other reports for the game:
Game does not launch. No window, No sound. Crash occurs within 2 seconds of starting.
Looks like the game hits fixme:process:GetNumaHighestNodeNumber (0x32eed0): semi-stub
and immediately segfaults with an access violation (c0000005) after that.
I leave this here - maybe it helps somebody
I was able to get this game running on wine without much trouble.
The only special thing I needed to do was add an override for msvcr120.dll to use the native .dll instead of the built in one, otherwise you'll get a crash right after the title screen
https://steamcommunity.com/app/881100/discussions/0/1630790506927916240/#c1608274347716189260
@Underknowledge That should be fixed in 4.11-8 already.
Hello @SeanRamey, you could give fsync a try and see if that has a significant effect on performance for this game.
@kisak-valve I tried to use the fsync kernel, but it wouldn't boot. Or at least, it seemed to get stuck while booting. Basically, it just took an abnormally long time, and I got tired of waiting over 10 minutes for it to boot, so I just reverted.
I had these slowdown problems as well, they seem to have disappeared (or at least drastically improved) in the last few days. But I can't tell if it's due to Arch kernel updates, Noita update or something else .. (still using Proton 4.11).
@TTimo I'm using the latest proton and the issue is still there. I have noticed that the issue isn't general performance issues, and is actually somehow linked to mouse movement. I've updated the report to reflect that.
Does anyone have made a performance comparison with Windows? To confirm that it's not an issue from the game itself.
Playing this on proton 5.13-1
with an fsync patched kernel 5.9.6-95-tkg-upds
and nvidia 455.38-5
.
This game plays mostly without any issues on my system. Had to add PULSE_LATENCY_MSEC=10
to the game's command in order to fix crackling sound.
A problem with this game is that you can't switch from it and back - at least on some window managers, as seen reported on protondb.com.
On i3, as soon as I do that, this happens in console:
OnFocusWindowChanged to window type: k_nGameIDControllerConfigs_Desktop, AppID 413080
Loaded Config for Local Override Path for App ID 413080, Controller 0: /home/volca/.local/share/Steam//controller_base/empty.vdf
wine: Unhandled stack overflow at address 7E70053E (thread 00d8), starting debugger...
And the game stops displaying anything and just freezes.
Edit: The problem with fullscreen freeze goes away when using Window mode: Windowed in game.
Tried running with various proton versions including experimental and GE. Does not start.
PROTON_LOG=1 gives me this error:
21270.303:0008:0009:err:ntdll:RtlLeaveCriticalSection section 0x3d0440 is not acquired
Happy that Noita works at least, but it too often grinds to be unplayable slow 😢
Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz
Zen kernel with fsync patches: 5.12.14-zen1-1-zen
Proton 6.3-5
Does anyone have made a performance comparison with Windows? To confirm that it's not an issue from the game itself.
Yes on my machine this game plays flawlessly on windows, on wine you get continuous slowdowns.
It seems to me that that Proton 4.2-9 is the most performant, versions since then are relatively worse performing but no version actually performs "well". I dont have a fsync enabled kernel to test that.
At least for me it seems I was affected by https://github.com/ValveSoftware/steam-runtime/issues/312#issuecomment-739441559 which resulted in the reduced performance of the game as I happened to have the vulkan drivers for intel and my igpu enabled. After removing the intel vulkan drivers the game performs as well as on windows.
I'd like to report a UI scaling issue. I have a 4k monitor on my laptop. I have Ubuntu set to 200% UI scaling in the system settings. When I run the game, the game window is tiny and hard to see. I can't find any UI scaling settings in the Proton runtime config options. When I run the game full-screen, it's very slow and proton does not appear to respect the games resolution settings in both of the full-screen modes that Noita provides.
I can't find anyway to do scaling of this application alone, or to have a resolution where I can actually see the game and also have it play at a reasonable frame rate.
Adding my PC specs:
Ubuntu 21.04 HP - Spectre x360 2-in-1 15.6" 4K Ultra HD Touch-Screen Laptop - Intel Core i7 - 16GB Memory - 512GB Solid State Drive - Dark Ash Silver NVIDIA GeForce MX150 graphics
To add, the game runs at a good speed when the game window is tiny, and it looks good at larger resolutions. I just happen to need both big and fast.
Noita doesn't start (881100)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/5889. @arouene posted on 2022-06-06T15:04:28:
I have found an issue for Noita (#3176) but it's about performance.
Game doesn't start at all. I tried various Proton options and various Proton versions (GE, experimental, 6.3) without a change.
I have an AMD ThreadRipper, tried gamemode and multithreading disabled without amelioration.
Noita not starting
Issue transferred from https://github.com/ValveSoftware/Proton/issues/6541. @Brulijam posted on 2023-02-16T04:01:37:
Game not launching.
I don't know. Tried reinstalling Game, Steam, OS, home dir (in that order).
Hello @Brulijam, looking at your system information, it looks like your NVIDIA driver install is missing the driver's 32 bit userspace libraries and Steam is forced to fallback to llvmpipe (mesa's faster CPU renderer) to run at all.
I would check if the lib32-nvidia-utils
system package is installed.
I would check if the
lib32-nvidia-utils
system package is installed.
Yup, that did the trick. Thanks for your quick help :)
Noita also won't launch for me (on both a system with an intel iGPU and dedicated AMD graphics)
I remember playing Noita a while ago, so it's a regression with a game update (since older versions of proton don't work)
Turns out it was because I had SDL_VIDEODRIVER=wayland
set for Factorio, and it causes Noita to crash
Game: Noita AppID: 881100
Graphics Card: GeForce GT 730 Driver: Nvidia 390.157 Kernal: Linux 5.19.0-38-generic x86_64
System Information Proton Version: Proton Experimental, Proton 7.0-6
Here yee LOGS steam-881100.log
Game does not launch.
New install of ubuntu 22.04. switch to Nividia driver supported for my graphics card ie 390. already downloaded noita. configure noita to force install with proton. click play not a fun day.
Hello @Vaxeral, the Vulkan implementation provided by the NVIDIA 390 series is unserviceable and the driver in general is older than the support cutoff for Proton.
Looking at your system information https://gist.github.com/Vaxeral/35eaf155ce84c45a37fd0d690186ce8a#file-system_information-L347-L358 is curious. There's 3 variants of the NVIDIA GT 730. Some of them are Fermi generation, and some of them are Kepler generation. There was no vendor support for running Vulkan on Fermi, so that section of your system information hints that you have a Kepler generation video card. Can you check lspci | grep VGA
and on the NVIDIA card's line, check if there's something like GK208
(the K in that would indicate Kepler)?
If you have a Kepler variant of the GT 730, then you should be able to try to update to the NVIDIA 470 series video driver, which is the last series to support that generation, along with Proton 7.0 (and older).
Hey thanks for reaching out. 01:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 730] (rev a1)
A google search says that should be the kepler arch
Replying to https://github.com/ValveSoftware/Proton/issues/3176#issuecomment-1501287400
Hey Thanks so much you are a wizard :D
Cursor moves erratically to side of screen since latest game update.
You didnt provide much system information, but if you are using wayland you may have configured your monitors to be placed in -x or -y coordinates which are not supported in xwayland/x11 that most games run in. Check your monitor configuration to ensure all coordinates are positive.
Thanks! I had recently gotten a new monitor and didn't realize I had moved it to negative space rather than moving everything around! This resolves my cursor issue. Is there any way to make the game render at higher resolution than 1920x1080? Or to have the pixels stretch out to my bigger display? EDIT: I've found this ultrawide mod that resolves this issue!
Noita not launching
Issue transferred from https://github.com/ValveSoftware/Proton/issues/6743. @flan7 posted on 2023-05-04T22:27:19:
Game does not launch, I click play and it immediately crashes.
This happened on nvidia-dkms, I switched to a new AMD gpu and am still facing this issue.
@flan7 Is Noita launching on any Proton version? Could you also try 7.0-6 and 8.0-2?
it looks like your NVIDIA driver install is missing the driver's 32 bit userspace libraries and Steam is forced to fallback to llvmpipe (mesa's faster CPU renderer) to run at all.
I would check if the lib32-nvidia->utils system package is installed.
Thank you!!
Noita on Wayland crashes one second after window is created.
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7205. @Blazing-Blast posted on 2023-10-26T18:23:08:
The game crashes just after the window opens.
Install Arch with Hyprland. Launch the game. Crash!
Crashing on wayland also happens on gamescope-3.3.19 with Xwayland-23.2.3.
Noita does not launch on my system as well.
Compatibility Report Name of the game with compatibility issues: Noita Steam AppID of the game: 881100 System Information GPU: AMD Radeon RX 6500 XT Video driver version: 4.6 (Compatibility Profile) Mesa 23.0.3 Kernel version: 6.5.5-100.fc37.x86_64 Link to full system information report as Gist: https://gist.github.com/reportingsjr/2e9901199da99c8e63e65531f3ad31b6 Proton version: I tried 8 and Experimental
Symptoms The game crashes just after the window opens. Full proton/steam log here: https://gist.github.com/reportingsjr/5d32678c5e9c816112425424030d3cb9
Reproduction Launch the game. Nothing happens Crash!
EDIT: I saw someone mention that running Noita from command line with proton directly works. I tried that and lo and behold, it does work! Not sure what steam is adding to the launch command that it is failing.
If you are under wayland, setting env --unset=SDL_VIDEODRIVER %command%
launch option works for me
Launching without forcing SDL to use Wayland does fix, but causes scaling problems on HiDPI displays (nobody is surprised). It also can't seem to change the resolution in the game, no matter what the option says, it won't use any 16:10 resolutions.
I have a strange issue where keyboard input seems to have latency issues. Mouse tracking is normal, and the game seems to be running at full performance, but I sometimes have delayed inputs, or dropped inputs entirely. Anyone know what'd cause this? (Using an AMD GPU on X11)
Hey there! Noita itself runs fine, but I can't upload workshop mods on Proton 9.0-2. If I try, the resulting workshop item appears to be empty (0.000 B).
Proton 8.0-5 and 7.0-6 works fine.
Two other people in the Noita Discord confirmed that switching to Proton 7/8 fixed this same issue for them.
Here are two test uploads.
Proton Experimental also doesn't work, same as Proton 9.
The upload appears to succeed but the resulting workshop entry is empty and unusable.
Run noita_dev -workshop_upload "Test Mod"
Thanks! I actually just figured out the issue myself. It turns out the latest version of ibus (1.5.30) was the culprit, so I've downgraded it for the time being.
@dextercd Thank you for the report! I tried to look into this, but I've never modded Noita before so I wasn't able to get this working on 8.0 either ... I'm assuming this is some failure on my part, so I'm hoping you can give me some more instructions to help me out :)
I tried just copying the daily_practice mod files that come with the game in the mods folder, and then renaming the folder, adding a workshop.xml file that I think I wrote correctly, and then putting many combinations of "noita_dev -workshop_upload" in the launch options for the game with Proton 8 selected. I had my mod in the common/Noita/mods folder. It would also be super great if you could upload your test mod folder or tell me where to find it (so I can use it instead of daily_practice) - I looked in compatdata/881100/pfx/drive_c/users/steamuser/AppData/LocalLow/Nolla_Games_Noita which I got from the Noita wiki, but I couldn't find your workshop data (even though the workshop is showing up in the mods area in-game after I subscribed to it).
Hey @alasky17,
My reproduction steps could've been more complete, sorry about that!
Here's the test mod I made: https://github.com/dextercd/Test-Mod I have it located at /home/dexter/.local/share/Steam/steamapps/common/Noita/mods/Test Mod
but the exact mod folder name doesn't really matter from what I could tell, so test_mod or Test-Mod will work the same. (Just remember to adjust the upload command)
noita_dev is actually a separate executable you need to launch. There are a couple ways to do this that I know of:
The Proton 9 issue happens with all three methods, so I don't think it matters much which you pick. Note that after uploading a mod, it creates these three files: workshop_id.txt
, mod_id.txt
, and compatibility.xml
. You need to remove them to create a fresh workshop entry, otherwise it'll try to update a previous upload.
Oh also, workshop mods are located in /home/dexter/.local/share/Steam/steamapps/workshop/content/881100/<mod_id>
, but you shouldn't need this with the GitHub repo linked above.
Let me know if you need anything else! It'd be great if this issue can be resolved :slightly_smiling_face:
@dextercd Thank you! These new steps were very clear, and I immediately see where I went wrong. I'm glad now that I didn't waste too much time before asking for some help :)
I see the regression between Proton 8 and 9 and will investigate further now. Again, thank you for the instructions!!
Compatibility Report
System Information
I confirm:
Symptoms
steam-881100.log
Game just has very poor performance when you move the mouse.
Reproduction
Just play the game. I'm sure performance will probably be better with a faster system, but it would be nice if we could get close to native performance.
EDIT: I have attempted to install the linux-fsync kernel, but couldn't get it to boot. I have also noticed that the performance hits only happen when you move the mouse in game, so I changed the symptoms to reflect that. If you leave the mouse still, it has perfect performance. Not sure if it's a game bug, or due to proton.
PS: Found another compatibility report for Noita, but it was closed and not for this issue. Wasn't sure if I should comment my issue there or not.