Proton
Proton copied to clipboard
Rain World (312520)
System: Steam System information report Kernel: 4.14.67-1-lts x86_64 Desktop Env: i3 4.15 Distro: Antergos Linux (Arch Linux based) Device: laptop System: CLEVO Mobo: P370EM CPU: Quad core Intel Core i7-3740QM (-MT-MCP-) 3700 MHz Graphics: GPU: NVIDIA GK104M [GeForce GTX 670MX] Display Server: X.Org 1.20.1 Resolution: 1920x1080 60.02hz Nvidia driver version: 4.6.0 NVIDIA 396.54 OpenGL: renderer: GeForce GTX 670MX/PCIe/SSE2 Memory: 16 GB
Two issues:
-
~~The main character (slugcat) is yellow, instead of white. Posted on Steam community forum here.~~ This is normal.
-
(Wired) Xbox 360 controller doesn't work, no input at all. Posted on Steam community forum here.
-
~~Arguments were needed to launch:
PROTON_USE_WINED3D11=1 PROTON_LOG=1 PROTON_DUMP_DEBUG_COMMANDS=1 %command%
~~
~~Without these arguments, the game fails to launch. Here is the Proton log when PROTON_USE_WINED3D11
is NOT being used (and doesn't launch).
Here is the log with PROTON_USE_WINED3D11=1
(which works).~~
Update: the yellow character is normal, I had selected "the monk" in the selection screen before the game started (which is yellow, so this is normal). Sorry about that.
Also, installing lib32-vulkan-icd-loader
fixed having to use the PROTON_USE_WINED3D11=1
option.
System: Steam System Information Report Kernel: 4.18.11-200.fc28.x86_64 Desktop Env: XFCE Distro: Fedora 28 Device: Desktop CPU: Intel i5 3570K @ 4400 MHz Graphics: GPU: NVIDIA Geforce GTX 1070 Nvidia driver version: 4.6.0 NVIDIA 396.54 OpenGL Renderer: GeForce GTX 1070/PCIe/SSE2 Memory: 16 GB
Main issue:
The game doesn't recognize my bog-standard wired Xbox 360 controller.
- [x] The controller itself works.
- [x] The game recognizes the controller on my Windows installation.
- [x] The controller works in Steam games running natively on Linux.
- [x] The controller works in other games running within Proton.
- [x] Wine itself recognizes the controller perfectly fine (
wine control
).
Rain World doesn't seem to care about those facts, though, and apparently decided to ignore my controller entirely.
with the latest beta 3.16-4 my controllers are recognized (xbox one s or emulated xbox360 through sc-controller) but the controls behave erratic. controller seems to be stuck in top left corner, trigger pads are interpreted as analog stick directions as well. control not possible.
that is over USB and I tried different drivers (xpad, improved xpad, xpadneo...) wine control panel and big picture both recognize the controller correct and show the right controlls being pressed. No difference if I turn xbox support on or off in steam.
Tried this with the latest Proton and controllers appear to work..sort of. Dead zones are really wacky and there's an incredible amount of input latency, even up to one second or more of input latency from the controller. I've tried all of the wine-related solutions I can think of but nothing seems to work.
Indeed, I can also confirm the controller is recognized with Proton 3.16 beta but the input is not right at all. Using xboxdrv driver.
@exezin @glubsy It's possible that what you're describing isn't a bug, I felt that way too until I tried the dpad. Slugcat's physicality means it takes a moment to get moving. The game controls completely horribly with analogue sticks, try the dpad and see if it's better. I came to like the controls a lot once I'd gotten used to them.
You are right that the input to slugcat is.. Sluggish, but there is noticable inconsistent and severe input delay with my wire 360 gamepad, and it works fine under windows.
On Fri, 19 Jul 2019, 11:12 mako yass, [email protected] wrote:
@exezin https://github.com/exezin @glubsy https://github.com/glubsy It's possible that what you're describing isn't a bug, I felt that way too until I tried the dpad. Slugcat's physicality means it takes a moment to get moving. The game controls completely horribly with analogue sticks, try the dpad and see if it's better. I came to like the controls a lot once I'd gotten used to them.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/1230?email_source=notifications&email_token=ABGXN4W26JRHCFJGLQREIR3QAGHRBA5CNFSM4FTEYAQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2LG5IQ#issuecomment-513175202, or mute the thread https://github.com/notifications/unsubscribe-auth/ABGXN4VI55XE72Z24EDE4CDQAGHRBANCNFSM4FTEYAQQ .
Input latency seems to be gone with the latest Proton release. (Moderator note: Proton 4.11-1?)
Sorry, yes Proton 4.11-1.
hello, i reinstalled steam as requested in .deb to benefit from the active mesa of ubuntu 22.04, but proton experimental and proton 7-0-3 encounters a problem on this game, the game goes black screen with some lightning, can start the game and then the game crash instantly. attached file are PROTON_LOG=1 %command% and crash files and dxlog from rain world folder i5 10400f rx6600 8go 16gb ram ubuntu mate 22.04.1 latest updated (COmpositor marco:picom-glx) kernel 5.19 tkg-pds OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.0.5
Gist for my full spec info : https://gist.github.com/SlugSleepy/0453e441b7d8fd8f811d2fa98614ea86
steam-312520.log
2022-08-15_164052.zip
thnaks
Hello @SlugSleepy, looking at your log, there might be an issue with the game parsing the #
in the path to your Steam library. It's uncommon for this symbol to be used on Windows as well, so this might be a cross-platform game bug.
From the log:
You are trying to load data from a www stream which had the following error when downloading.
Couldn't open file /Z:\mnt\bx300
(Filename: Line: 1075)
Map load request for: SU
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)
Checksum CORRECT!
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)
Followed by an access violation (c0000005).
Are you able to easily test this game with it installed into a Steam library that does not include that symbol?
Wow ! you are correct, installed it on my main SSD and works like a charm. interessing bug, I did not know that the name put on my disk would have an importance on the launching of these. thanks !
With the release of Downpour, the game now comes packaged with BepInEx as a way of loading modded content. This relies on winhttp.dll and requires WINEDLLOVERRIDES="winhttp=n,b" %command%
in the launch options for it to be loaded properly. Workshop content and Remix/Downpour DLC will still work fine without doing this, but usage of mods placed in the BepInEx/plugins folder will not work.
Logs will complain with Wine detected: fixing BepInEx next launch by setting DLL override for winhttp to 'native,builtin'
but the user will need to set the override themselves either through the launch options or by using winecfg with protontricks.
Workshop mods that use BepInEx such as SplitScreen Coop do not work without the dll override
Game not recognizing button inputs
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7177. @Such-Significance posted on 2023-10-17T12:56:08:
Compatibility Report
- rainworld doesn't recognize any steam deck button inputs:
- Steam AppID of the game:
System Information
- GPU:
- Video driver version:
- Kernel version:
- Link to full system information report as Gist:
- Proton version: 7 and experimental
I confirm:
- [ ×] that I haven't found an existing compatibility report for this game.
- [ ×] that I have checked whether there are updates for my system available.
Symptoms
when opening rainworld i cant press any buttons. I have tried deleting and re-downloading proton files and it works when i first open the game. But after i close the game the issue reapears. i have tried multiple proton updates.
Reproduction
@Such-Significance commented on 2023-10-17T12:57:00:
Sorry for not answering some of the questions i have no idea what they were asking