Rivals of Aether (383980)

[unmellow]

Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 55 Model name: Intel(R) Celeron(R) CPU N2840 @ 2.16GHz Stepping: 8 CPU MHz: 2582.300 CPU max MHz: 2582.3000 CPU min MHz: 499.8000 BogoMIPS: 4333.08 Virtualization: VT-x L1d cache: 24K L1i cache: 32K L2 cache: 1024K NUMA node0 CPU(s): 0,1 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat

rivals of aether works except that my controller controls multiple players at the same time and some crashing with no log boring man online tactical shooter has the same problem with crashing

[TiZ-HugLife]

rivals of aether works except that my controller controls multiple players at the same time

Tekken 7 actually has this issue in Vanilla Wine, but in triplicate: XInput controller, DInput controller for event device, and DInput controller for JS device. Proton doesn't. Is there some sort of predefined workaround used in Tekken 7 to get around this issue, like disabling dinput8.dll or a custom dinput8.dll that ignores controllers? The same thing could be used here. When I get an opportunity I'll poke around my Tekken 7 prefix to see if there are any DLL overrides in the prefix.

[aeikum]

The duplicate input bug for Rivals of Aether should be fixed in Proton 4.2-1. Please retest.

[unmellow]

the controller I found this bug on is missing... but it was a ps4 controller I'll see if i can borrow one to check

[unmellow]

cannot test with the ps4 controller anymore as I don't own one anymore but I haven't found the bug when using Hori switch controller so i think it's safe to assume the bug is fixed

[unmellow]

also, the games haven't crashed on me since I've been playing them recently lovers of aether also works well thought I'd mention it here and not make another issue

[Veedrac]

This game lags significantly, ~45Hz, even less in menus, in Proton 4.2-4 and 3.16-4, which is a regression from 3.7-8 which the console claims runs at >240Hz.

Proton 4.2 does fix the multiple controller issues that are present on 3.7-8, though the lag leaves it unplayable regardless.

System report: https://gist.github.com/Veedrac/b98a948ef4787263b074cf9ae4bf0770

Update: 5.0-5 has the same performance issue.

---

For people who found this issue on Google and want a working configuration:

Switch to Proton 3.7-8, this runs fast but has issues with the controller. Then follow the advice from one of the comments on https://www.protondb.com/app/383980, copied below:

Runs as intended after a tweak to stop the game from reading double inputs from 1 controller To stop that you need to run the following command just a heads up this is with default proton, if you are using other proton versions please replace the path to proton with the appropriate one

UBUNTU AND DERIVATIVES

export WINEPREFIX="$HOME/.steam/steam/steamapps/compatdata/383980/pfx/" && "$HOME/.steam/ubuntu12_32/steam-runtime/run.sh" "$HOME/.steam/steam/steamapps/common/Proton 3.7/dist/bin/wine64" control

OTHER DISTROS WITH STEAM RUNTIME DISABLED (Solus, arch, wine manually installed...)

export WINEPREFIX="$HOME/.steam/steam/steamapps/compatdata/383980/pfx/" && "$HOME/.steam/steam/steamapps/common/Proton 3.7/dist/bin/wine64" control

click the Game Controllers icon and disable the controllers that you want to use, click OK and do it again if more controllers popped out After that you can play the game as intended! PS: If you dont want to disable DXVK make sure you have your 32 vulkan libs and icd loader are installed, i can't really tell any difference but it feels like it loads faster on vulkan.

[kisak-valve]

Hello @Veedrac, 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.

[Veedrac]

steam-383980.log

[unmellow]

for no perceptible reason rivals of aether closes with no error's on clear linux btw i installed steam from flathub

i can open a new issue if need be i have a new rig now so none of the old info apply's now

[kisak-valve]

Hello @unmellow, we're using one issue per unofficially supported game title, so this is the right place to discuss this game. 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.

[unmellow]

where does proton save the logs? edit: still don't know where to find the log but i think roa only crashes when my screen blanks tbc the power saving screen blank in gnome settings i'll see if it crashes without screen blank on

edit2: i left my pc and came back to find rivals closed again even with screen blank off

[unmellow]

https://steamcommunity.com/groups/SteamClientBeta/discussions/0/2727382174633287305/ someone else is having the same issue

[MOLLARDAmbre]

Hi, I am having the same problem as describbed (The game just doesn't launch, like it instantly crashes). I took the liberty to try the launch option command, here is the log file (since it was not provided i thought it could help you steam-383980.log

[kisak-valve]

Hello @SamuelleMollard, your log tells us that Vulkan failed to initialize. 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.

[MOLLARDAmbre]

Like that ? https://gist.github.com/SamuelleMollard/b6b272413e1ebd1e5e5c13200340ed4f

[kisak-valve]

Thanks, looks like you do not have any vulkan drivers installed. Please run sudo apt install mesa-vulkan-drivers mesa-vulkan-drivers:i386.

Note: You have an Intel Haswell chipset, and the drivers provide an incomplete Vulkan implementation. It's likely that you'll experience rendering quirks and other issues. Newer mesa drivers from a PPA like oibaf or kisak-mesa may help a bit, but it's still a partial implementation.

Alternatively, you could try adding PROTON_USE_WINED3D=1 %command% to the game's launch options to tell Proton to use wine's DirectX to OpenGL render path, but this is expected to come with a significant performance penalty and is not considered supported.

[MOLLARDAmbre]

Thanks a lot I had a lot of issues on my last OS when trying to install the dirvers (my computer would freeze, like very often), so i'm a bit reticent to the first solution, might try the ppas though. Do you know if i can just apt purge them if it turns out to freeze my computer often like for my last installation ? I will also try the command modification In any case, thanks

[kisak-valve]

apt purging mesa will make the package manager very upset, leave the system with no video drivers, and most likely remove hundreds of packages you want to keep. Instead of apt purging, ppa-purge does a good job of backing out all packages from a PPA and re-installing the previous drivers. This is documented in both PPAs, but you might need to add -d bionic to the command because you're running elementary OS instead of Ubuntu (unconfirmed).

[qwertyuiopleowo]

when I try to boot the game with proton 3.7-8 specifically it doesn't want to boot, I click the play button, it loads for a couple of seconds and then it returns to the play button(it doesn't boot) idk what's wrong but here's the log file: steam-383980.log

[kisak-valve]

Hello @qwertyuiopleowo, looks like Proton 3.7 is now too old for this game, specifically, err:steamclient:create_win_interface Don't recognize interface name: SteamClient018 was first added in Proton 3.16.

[qwertyuiopleowo]

Gotcha, is the latest Proton version the best version, then?

[coatlessali]

https://gist.github.com/CoatlessEskimo/ba9479bdfe20bf34f45408193aed30e6

(Proton 6.3-2) After extensive furiously wiggling the stick in the menu cursor movement and replay watching with mangohud enabled, the game maintains a completely stable 60 FPS regardless of vsync being on or off... On my 72hz monitor. Can anyone verify if the game outputting 60 FPS with vsync on with refresh rates other than 60hz is normal? I have a feeling it contributes to feeling like there's lag that isn't actually there, and I don't have a Windows install to test.

As a side note, is there anything we that can be done about the Mayflash GameCube Controller Adapter (- a dinput controller -) being detected as an Xinput controller by the game through Proton? It's easy to work around in game but the default button mappings are wrong, the GameCube Controller button icons don't show up, and certain bindings made to buttons that don't exist on the GC (i.e. frame advance toggle in training mode) won't function properly.

[coatlessali]

Update: Adding the necessary udev rules for the adapter and disabling Steam Input fixes the issues with the Mayflash GameCube Controller Adapter. Controller has to be calibrated with external software systemwide.