NotteScura
Published
Works great OOB, no tweaks, using Xbox360 controller with xboxdrv and default config.
Updating entry (2022) - Ran well with wireless Xbox360 controller, no tweaks, default latest proton version.
Played flawlessly OOB using Xbox 360 controller with xboxdrv and default config
Runs well after following the tweak for installing directmusic/dsound with winetricks (protontricks), and using a slightly custom config for xboxdrv with Xbox360 controller to prevent camera spinning. I used the "default.xboxdrv" config file from the examples with changes: trigger-as-button=true / remap RZ axis to Y2
Direct command should be something like: xboxdrv --detach-kernel-driver --silent --trigger-as-button --axismap TL=BTN_THUMBL,TR=BTN_THUMBR --ui-axismap Y2=ABS_RZ,RT=ABS_RY
Game works, but no audio of any kind
I attempted to install directmusic/dsound as I had previously done on my original system 4 years ago and even that didn't work. Tried various versions and that also failed. I also tried to use Glorious Eggroll versions of Proton, but the game won't even launch using any of those.
Tried both distro package and flatpak, made zero difference. Frustrating to say the least.
I'm not sure what changed, but running this game with the latest Proton 8 (as of this entry) allowed everything including sound to work. The only non-working part is fullscreen mode. The game starts, and background music can be heard, but nothing appears on screen. Windowed mode is fine.
Latest version of proton does not work. Previous version 4.2-9 works flawlessly following the winetricks install of d3dx9
Played through a normal 4vs4 local battle against CPU, no issues. Frame rates at 1080p and high graphics were 60fps+.
Played through a normal 4vs4 local battle against CPU, no issues. Frame rates at 1080p and high graphics were 60fps+.
Tried a multitude of different settings with no success. Game throws an exception as it's starting, but the message is vague and generalized so it is unclear what the source/cause is. Pressing the OK on that leads to the game exe running in the background, but nothing happening. SIGKILL required to kill off the process, standard SIGTERM doesn't cut it.
