FetusZero
Published
Game works fine windowed, required config INI modification for fullscreen
Editted the following ini config file of the game to enable fullscreen:
/steamapps/compatdata/283840/pfx/drive_c/users/steamuser/Application Data/SITER SKAIN/ALLTYNEX Second/AlltynexSecond.ini
Changed the following:
SCREEN_WIDTH=1920
SCREEN_HEIGHT=1080
FULL_SCREEN=1
WAIT_TYPE=0
The "WAIT_TYPE" changes to 1 when using the config.exe through the "Controller Layout Tool" of the game in Steam, which made it boot on a white screen. Setting it back to 0 launches the game in fullscreen without issues.
Outside of the AlltynexSecond.ini modifications for fullscreen, the game works without further issues. Controls are good, game runs fine, and I'm still as bad at it as I was back in the days.
Works out of the box, including in Tate mode (vertical screen)
Game worked flawlessly on launch in both regular horizontal view as well as Tate mode (vertical screen).
Works out of the box
Game worked out of the box without any issues for my full playthrough. I did not try subsequent playthroughs or custom stories.
Works out of the box
Works flawlessly right out of the box and the Steam Cloud save carries over nicely from a previous Win10 installation. Played through to the final chapter using a DS4 without issues.
Disabling the sound driver via protontricks prevented the crash at the final boss (sound still played regardless):
- In a terminal, enter:
protontricks 1065180 --gui - Select "Select the default wineprefix".
- Select "Change settings".
- Select "sound=disabled".
- Press "OK" and close any additional winetricks GUI that opens after a while.
Crash at final boss if the protontricks changes listed are not applied.
The game worked fine out of the box up until the final boss, at which point I needed to disable the sound drivers via protontricks to avoid crashing. Once done, I was able too complete the game without issues. My DS4 was recognized and its mapping was accurate using the regular Steam configuration for it.
Works out of the box, both solo and in local multi
The game worked flawlessly out of the box in both horizontal and vertical (Tate) modes. Played through the various levels with a DS4, both solo and with a guest player on a second DS4. The save data was initially created on Win10 and was carried over through Steam Cloud without any issues.
Works out of the box
Game works flawlessly out of the box both in solo and local multiplayer with 2 controllers (DS4). The config utility on launch also works properly.
Works out of the box
No issues running the game for it's entirety up to my escape, which is about 10-15 minutes. Runs flawlessly.
Works flawlessly out of the box.
There was stuttering in the tunnels leading from one area to the other.
Played through the entire game without issues outside of the stuttering in the "loading" tunnels. Towards the end of the game, I had 3 instances of the display freezing for a few seconds. It was unfortunate and caused me to die, but they never occurred more than once.
Proton-6.13-GE-1 GloriousEggroll
- Used Proton-6.13-GE-1
- Installed the Lutris' community installer for Proton.
Here what I did, kudos to the previous user who pointed out Lutris:
- Launch Lutris.
- Search "Concluse" in community installers.
- Install from Lutris on Proton.
- Click to launch the game, which will start the Steam install.
- In the games properties on Steam, force compatibility to Proton GE.
- Launch the game through Steam.
With those steps, I played the game entirely from beginning to end, cutscenes included. I also tried with regular Proton (6.3-5 at the time of writing), but the cutscenes were displayed as placeholder videos. Without the Lutris install, the cutscenes simply did not play, and the game would just softlock for the time of the cutscene.
Works out of the box
Game worked flawlessly out of the box both in single player and local multiplayer, using either keyboard or DS4 controllers.
Works out of the box
Game worked flawlessly out of the box in both windowed and fullscreen, using either a controller or the keyboard. Local multiplayer worked as well with 2 DS4 controllers. As a side note, achievements are awarded once the game is closed, as it was before in Windows as well, though it feels unusual since not many games do so.
Outside of the dual screen mode, game runs flawlessly
Dual screen does not work as intended, squishing the display onto my 2nd display instead.
The game works fine and the saves were carried over nicely from a previous Win10 installation via Steam Cloud. DUALSHOCK 4 worked without issues in the game (for 2 Players and up, make sure to select the additional controllers in the OPTIONS of the game).
Works without issues out of the box
Played with a dualshock 4 connected through bluetooth, game runs perfectly. The launch itself seems long though, but outside of that, nothing wrong that I noticed.
Overall the game works fine, with minor inconveniences
Menu inputs are performed twice, making it difficult to navigate the menus with my DS4. The keyboard can be used in its stead for the menus while keeping the controller connected.
Gameplay works fine however. I mapped the buttons through Steam configuration to reflect the keyboard keys used in the game.
I get minor stutters every 3-5 seconds regardless of resolution and window mode. While annoying, it does not prevent from playing the game.
The game can be played for the most part and behaves as it would under Windows. The controller and stutter issues are both present under Windows if I'm not mistaken, as they can both be found in the Steam forums.
Works perfectly out of the box, needed to map controller through Steam
I had to map my DUALSHOCK4 manually through Steam configuration to match the keyboard controls, otherwise my controller was not recognized properly. Works flawlessly after this.
The game worked flawlessly out of the box with the regular keyboard controls. Unlike the 2nd game, I don't experience any stutter and the gameplay is super smooth.
Most of the game played fine, but certain areas crashed or stuttered heavily
Game exhibits heavy stuttering at certain occasions, often leading to crashes.
The game crashed on a few occasions.
I was on the fence about thumbing this one up or down, because most of my experience was fine, but I did encounter a crash early on when fetching the first rig, as well as towards the end shortly before the final boss. Both of those crashed my system and occurred consistently, I had to boot the game into Windows to bypass them. On a side note the save transfers well between Windows and Proton.
Stutters were fine most of the time, but when they happen, boy are they there and they severly degrade the experience. Stuttering doesn't seem specific to Linux though, as I encountered a lot of them on Windows as well in more or less the same areas where I crashed under Linux.
All in all, outside of specific areas, the game ran fine for the most part and played well, but were it not for the fact that I have a Windows SSD, I'd have been stuck early in the game.
Works out of the box
Game worked flawlessly right out of the box, played with a pair of DUALSHOCK 4, using Valve's default selected Proton 4.2-9.
Works flawlessly out of the box
I've completed the game on Normal difficulty with a Dualshock 4, and played a bit on Hard with the keyboard, both configs working flawlessly out of the box.
Works out of the box
Game worked flawlessly both solo and in local multi with two DUALSHOCK 4.
Game works flawlessly after dismissing the debug DirectX error.
DirectX error is prompted on boot, however dismissing it allows playing the game as though nothing happened. The error in question is "Debug version has been selected for DirectX run time. Application may not run on intended performance."
All modes worked flawlessly in the game, played with a DUALSHOCK 4.
Proton-6.19-GE-2 GloriousEggroll
Proton-6.18-GE-2 GloriousEggroll
The developer splash screen is a video that doesn't play with regular proton, but displays fine on GE. Otherwise the game works just fine, though I didn't get very far.
Works flawlessly out of the box
Absolutely no issues running F.E.A.R. on Proton on my end, I don't even need to worry about the HID fix needed on Windows to avoid massive drops, it just ran perfectly from start to end without issues.
Crashes on "New Game", if you can even view the main menu.
I've tried a few regular Proton versions, everytime the main menu is just a white, blank screen. You can hear sound and selections but can't see anything.
With the latest Proton GE (20), the game simply crashed on the main menu.
Finally, with Proton Experimental I was able to view the main menu, change settings and all that, but the game crashes as soon as it enters the loading to a new game.
I kept getting black screens with regular Proton, but had no issues at all from beginning to end while using Proton GE 7-55. Played through the entire game using a DUALSENSE controller.
Proton-6.18-GE-2 GloriousEggroll
Proton-6.18-GE-2 GloriousEggroll
Sometimes had some slight performance issues when starting a level, fixes itself after a couple seconds.
Played from start to finish on the default difficulty with mouse keyboard without issues.
No issues completing the game in DX12
Played through the entire game without issues on DX12, using mouse and keyboard. Did not try controllers.
Works out of the box
Games works flawlessly. To switch to fullscreen, press the F11 key. Also note there are no sound effects and no music in the menus, which is also the case in Windows and is not caused by running the game in Proton, that's just how the game was developed.
As noted by a previous user, my game started in fullscreen (possibly due to Steam cloud and previous Windows installation), displaying only about 1/4 of the game in a smaller square. Thanks for his fix:
- Editing "./steamapps/common/GundeadliGne/gundead.ini" with "Resize=-1", plus the "Width" and "Height" to my native resolution fixes the issue.
Controller was detected as both players at the same time.
- Unplugging the keyboard allowed for the controller to be used as P1 on its own.
- Unplugging the keyboard allowed playing locally with 2 controllers, however controller 2 is detected as P1, and controller 1 is detected as P2.
- Disabling Steam input in the game's properties allowed the controller to be used as P2 on its own.
As stated by a previous user, the game when initially started in fullscreen will display only about 1/4 of the game in the top left corner. Thanks for his solution:
- Proceed to ./steamapps/common/Gundemonium Recollection/" and open "gundrec.ini" in a text editor. Modify to "Resize=-1", along with "Width" and "Height" to your native resolution.
Played through a bit using a DUALSHOCK 4 without any issues.
gamemoderun %command%
Had some minor FPS issues with the game. Fixed by installing gamemod and running with the "gamemoderun %command%" as per various other posts.
The game is fully playable out of the box without any launch command, however on my system I had ever so slight FPS issues, with the game running slightly lower than 60 FPS (around 57-58 FPS). It's nothing that impedes actual gameplay, it was more of an eyesore.
Following the recommendation of other players, I installed gamemode and launch with the command "gamemoderun %command%", this eliminated my FPS problem.
Played for hours using a DualShock 4 connected wirelessly via bluetooth on my system, controller setup through Steam and I've had no issues. I've also played a bit with the keyboard, which works, but isn't my thing.
Note I've not tried any mods.
Game freezes in tutorial and fullscreen does not scale properly on dual-monitor setups.
The game scales as if my dual monitor setup was a single width, resulting in the game quadrupling the resolution. This results in only 1/4 of the game screen showing up on my main display. I have yet to find a solution, I assume disabling my second monitor would work but I haven't tried it. Running the game in Windowed mode works.
The game consistently freezes in the tutorial on a fresh save (or via Practice mode), it seems to occur mostly when using a "Discharge", though I've seen it happen just by going left and right. If the game saves and allows skipping tutorial on the next boot, then it can be played, just steer clear of the practice mode.
If you boot in Windowed mode, and have a previous save, or manage to make the game save after the initial boot (so it takes you to the main menu on second boot), the game seems mostly playable. I was able to clear the first stage's boss and move on the next level from that point, though I can't confirm if you can progress further (due to my lack of skills in this game).
When starting the game for the first time in fullscreen, only 1/4 of the game will be displayed. Changing the resolution in the game's .ini fixes this:
- Proceed to ./steamapps/common/Hitogata Happa/“ and open “happa.ini” in a text editor. Modify to “Resize=-1”, along with “Width” and “Height” to your native resolution.
Works out of the box
Did a quick run through of this short game from start to end and it ran as it did under Windows without issues. Note the game just closes at the end, though if I recall correctly, the itchio version on Windows did the same.
Works flawlessly out of the box
The game works without issues, both windowed and fullscreen. Played locally with 2 DUALSHOCK 4's. To note, the first controller was identified as "Gamepad2" and the second as "Gamepad1", but they are still assigned as first and second player properly regardless.
Works mostly fine, slight performance issues.
I did experience heavy stutters when loading into the game initially and occasionally throughout the game. Not sure if it is due to Proton since I've read similar issues from Windows users in the Steam forums. While they occur occasionally, it generally ran fine.
Outside of the occasional perf issues listed prior, I had no other problems playing the game from beginning to end. Once or twice I had a full system lock up but I think it was due to OBS running alongside the game since it never occurred if OBS wasn't running.
Game crashes consistently when reaching Chapter 7 (Book World). Whether from continuing the game or through chapter select. Chapter works fine when booting the game under Windows, so I ended up having to continue playing on Windows instead.
The game works fine for the most part without issues. My Dualshock 4 was recognized and worked perfectly fine as well, but you do have to change "Settings > Gameplay > Input" to "Gamepad" for it to work. Unfortunately I was unable to complete the game since it crashes for me upon reaching Chapter 7. I also tried clearing the first part of it under Windows and coming back to Linux, but it still crashes regardless.
Note that Proton 7.0-1 worked exactly the same as GE 7-10, but the cutscenes were placeholder screens. They play back fine with GE.
Works out of the box
Both games in this small bundle run flawlessly without issues.
Works out of the box
No issues playing the game. Press F1 for the options for fullscreen and such.
Works perfectly outside of the random crashes.
Encountered frequent Unreal crashes anywhere between 5 mins to 1 hour of playing, also present under Windows. Many players reported these and it was just never fixed. Offered solutions didn't work for me.
Outside of the UE crashes, the game ran absolutely wonderfully. Perfect as though native. Despite the crashes I did manage to fully complete a playthrough using a PS5 controller. I used a mod for PS5 button prompts which worked without any tinkering, just dropped the file in the appropriate folder.
Not everyone gets the crashes, so it's fair to assume most people will be fine.
Works perfectly fine out of the box
Had no issues running and completing the game, with only 4 endings that I did not go back to get. Everything worked without issues.
Game works out of the box
The initial loading of the game seems to softlock for a few seconds on launch, though it's only the animation that lags during loading. After 2+ hours, I haven't encountered any issues, whether with my DUALSHOCK 4 or keyboard, and all CG's encountered during gameplay worked flawlessly.
Impossible to play due to controls and audio.
The audio constantly cuts and stutters.
Inputs are performed without pressing anything, constantly scrolling left, whether by controller or mouse and keyboard.
With the audio and inputs issue, the game suffers greatly and is pretty much impossible to play since pieces will constantly fly to the left of the screen during gameplay, or up in the menus (which can be navigated with the mouse despite the issue). I've tried disconnecting each peripheral just in case, but the issue persists even with only one of them connected.
No longer have audio issues with pipewire, however inputs still are borked in my case
Inputs are performed without pressing anything, constantly scrolling left and up, whether by controller or mouse and keyboard.
Following another recent report, I decided to go and replace pulseaudio with pipewire on my desktop. I can say this has definitely fixed the audio issues I was experiencing.
Sadly, the inputs are still stuck on left/up for me, making the game unplayable since the menus can hardly be navigated and the blocks will stay stuck on the left of the screen. I've again tried disconnecting each peripheral and using community configs on Steam for this, but the issue persists.
Worked out of the box from beginning to end
Played through the entire story with a dualshock 4, also tried a dualsense for a while to see if it worked and it did without issues.
The mouse cursor does stay over the game in menus, though that's also an issue in windows.
Game works windowed without issues
I was unable to activate fullscreen. It's possible to force it with gamescope, but since gamescope is bugged I had force reboot my PC after using it if I wanted to launch the game again.
Absolutely no issues on my end other than the fullscreen not working, played through the game with a dualsense.
Note that after saving, you need to open up the emulator's menu (L1+R1, or E+M on keyboard) for the save to register (you will see the exclamation mark top right), after that you can Alt+F4 if you want, or quit normally. If you don't open up that menu after saving and you Alt+F4, the saves will not sync with the emulator and will be lost on next reboot.
Works out of the box
Game ran flawlessly, completed the first couple stages and it runs just as it did back then on Windows.
Mostly worked flawlessly from start to end
Had no issues running the game from start to end on Proton 7.0-2 other than rare, occasional hitches, which only occurred one at a time, usually early in new areas, and so did not prevent playing. For all I know those hitches are probably in Windows as well. I did not check controller support however, I only played using mouse and keyboard.
Works flawlessly
Played through and completed all games, as well as a few challenges without any issues using the default Proton selected by Valve testing (3.16-9). All games were played with a DUALSHOCK 4.
Proton-6.16-GE-1 GloriousEggroll
6.16-GE-1 GloriousEggroll
The game works flawlessly with Proton GE, including the cutscenes in MM8. Had no issues playing through every game in the collection.
MMX4 videos have audio with Experimental, WINED3D launch argument gives smoother performance.
PROTON_USE_WINED3D=1 %command%
Game seems to run slower than intended out of the box. Launching with "PROTON_USE_WINED3D=1 %command%" gives me better and smooth frame rates.
Overall the game works relatively well out of the box. When using Proton Experimental, the animated cutscenes in MMX4 will have proper audio playback. When using Proton 7 instead, the cutscenes will play back but will not have any audio. In both instances however, the game seems to run at a lower speed than it should. As per another post, running with "PROTON_USE_WINED3D=1 %command%" fixed it and makes my game as smooth as butter.
No issues out of the box
Played the entire game without any issues and without any modifications needed.
Worked out of the box
The game launches and works flawlessly with the default selected Proton by Valve testing (3.16-9). The DLC v1.5 works flawlessly as well. Played with both keyboard controls and a DUALSHOCK 4 without issues.
Works out of the box
Played without issues with both keyboard controls and a DUALSHOCK 4.
6.10-GE-1 GloriousEggroll
Proton 6.10-GE-1 https://github.com/GloriousEggroll/proton-ge-custom/releases
Once Proton 6.10-GE-1 is installed, the game no longer crashes when a movie cutscene is played. As a result, the game plays flawlessly now. My playthrough was started from a Windows installation and was resumed without issues through Steam Cloud on Linux.
Works out of the box
The game works without issues, just make sure it is fully updated and that Proton 7.0-1 and above is used.
Doesn't launch
Steam shows the game running but it never actually launches. I tried with both regular proton and proton GE.
Wanted to try ϟϟ Illusion's way but I do not have the game on GOG and their links no longer work.
Worked out of the box with slight performance issues.
Slight stuttering here and there
Had no issues playing the game from start to end on my setup, though I did encounter slight stutters and performance issues every now and then, mostly noticeable when entering a new area. It did not prevent me from playing and enjoying the game.
Works out of the box
Couldn't select any text replies on the native version, but running it under proton worked out of the box and without issues.
-vulkan
Played through the multiplayer chambers with a friend without issues. If you have multiple monitors, make sure to use the -vulkan command, otherwise the game sees both monitors as a single resolution, making it weird and which offsets the activation area of all menu buttons.
I don't believe this is needed if you only have one monitor.
-vulkan
Played through the multiplayer chambers with a friend without issues. If you have multiple monitors, make sure to use the -vulkan launch command, otherwise the game sees both monitors as a single resolution, making it weird and which offsets the activation area of all menu buttons, making the game pretty much unplayable.
I don't believe this is needed if you only have one monitor.
Works out of the box
Played from start to finish without any issues encountered. I did not play Mooncrash however.
Works out of the box
No issues in the game, played a bit with both a dualsense and moused/keyboard. I did not complete the game however, ended up not my type, but it worked oob for how far I got.
Works out of the box
Game works flawlessly without any issues out of the box.
Game works out of the box
On the first boot the game seemed to softlock on the "press any button" screen, but after a few seconds it loaded. This only happened on the very first boot and not subsequent ones and did not affect its playability.
- Had to set my DUALSHOCK 4 via Steam's "Controller Configuration" to reflect keyboard inputs.
- For 2 Players local coop with controllers, I needed to start the config tool of the game and set "Keyboard 1P" and "Keyboard 2P" to different keys, then set each controller to reflect their respective keyboard keys in Steam's controller configuration. Without doing this, all peripherals were seen as Player 1 and both controllers were seen as the same in the game's own config key mapping. I assume this is the game's fault more than Proton.
The game kept crashing when starting a new game with any Proton more recent than 4.2-9. Forcing compatibility via the game's properties to 4.2-9 made it work without issues.
Game works out of the box
No issues running the game with 2 DUALSHOCK 4 controllers, both solo and with a friend locally.
Game crashes after a Visual Runtime error window
A visual runtime error window is displayed on boot about the file "libGLESv2.dll" in the game directories, along with a message saying to verify Visual C++ documentation. Ignoring the error message only leads to a crash on boot.
Screen remains black
The game launches, you can hear the audio and can even hear yourself navigating the menus, but the screen remains entirely black, making it impossible to do anything.
Cutscenes remain entirely black, otherwise the game works fine.
Screen remains black on cutscenes, including on boot. It can be skipped with ESC or "X" on my DS4.
The games work pretty much flawlessly for me outside of the cutscenes that remain entirely black (audio can be heard). This includes on boot, the game seemingly boots to a black screen, however it can be skipped with the ESC key or the shot button on a controller.
Works flawlessly with default settings.
Carrying a previous save from Windows, the game crashes to Desktop if the Window DisplaySize is set to higher than 640x480. Changing the Window size to 640x480 (which is normally the default) in config.txt makes the transition to fullscreen smooth and without issues.
The configuration tool seems to launch fine with Proton 6.3-5, however all text are placeholder characters. Outside of that, game runs flawlessly.
Works flawlessly witth Proton 7.0-1
Game starts minimized, I have to manually restore the window (it restores to fullscreen without issues).
I've ran the game both vanilla and with the Sky Reclamation Project without issues on Proton 7.0-1. I remember before you had to force Proton 3.16-9 for it to work without issues, so I'm not sure what changed, but I can now launch it without issues on the latest. If you do get issues booting on the latest, do try 3.16-9 instead.
Game works without issues, mods can be installed manually or through Wine for installers.
Haven't had any issues with the default selected Proton, 3.16-9. I've tried latest releases but the game would crash on boot, so just use the one selected by default by Valve.
I had no issues installing mods either by manually transferring gamedata files, or by running installers through Wine.
Any crashes or issues I've seen are issues that have plagued the S.T.A.L.K.E.R. series since its beginning on Windows as well, so don't worry too much about those and do make multiple save copies in the game, as you should under Windows.
Works out of the box
The game worked out of the box, played with ZRP installed. I couldn't get other mods to work though, the game would crash on boot whenever I tried booting with one. Could be the mod, could be proton, I can't say, but I remember being able to play with mods without issues back in the 3.16-9 days.
Runs flawlessly through Proton
I couldn't get the native version to boot past the Nyu Media logo with freezing. Running it with Proton allowed me to boot it and it works flawlessly.
Runs out of the box
Had absolutely no issues playing the game from beginning to end. Used a Dualsense for controller but also played a bit with mouse keyboard.
Game runs without issues, including the setup tool by following some fixes provided by Captain Cool in an older report.
- To get the game working:
protontricks 200940 d3dcompiler_43 d3dx9_43
- Then, to get the setup tool working (/Steam/steamapps/common/Sonic CD/setup.exe), one after the other:
protontricks 200940 dotnet40
protontricks 200940 mdx
Works flawlessly out of the box, including local coop.
The game worked flawlessly from beginning to end, including special stages. I've played through entirely with my daughter using a pair of DUALSHOCK 4 controllers connected via Bluetooth and with a cable when out of charge, both of which worked flawlessly with the game.
6.16-GE-1 GloriousEggroll
Proton-6.16-GE-1
Only played the third game from start to finish with a DUALSHOCK 4, which was recognized and worked out of the box through Steam (proper button prompt images too). Other 2 games I had already completed on a Windows install.
Works out of the box, flawless with 2 player couch coop
Have been playing with my daughter in splitscreen and the game plays flawlessly using a pair of DUALSHOCK 4 controllers, both in Team and standard races. We've played around a bit with each modes without any issues together. I haven't tried with 3 or 4 players however, so I can't speak for that.
Game worked out of the box, with performance problems
Heavy suttering when arriving in new areas or in cutscenes. Dropping all settings to Medium helped, but didn't get rid of the problem entirely.
Outside of the heavy stuttering and frame drops when loading new areas (the initial cutscene was especially awful), the game worked fine out of the box. No issues with the controls or anything else. The loadings felt overly long despite being installed on an SSD. If I'm not mistaken though, all of these are issues on Windows as well and are fairly frequent based on the forums.
Worked out of the box
No issues, had a single UE crash, worked otherwise without issues with latest proton.
Works perfect out of the box.
Had absolutely no issues running this game out of the box. The only issues were the same ones as on Windows, where the initial version had some perf issues, and even then I barely had any (running the game on Medium however, with RT off). Played from start to finish with a dualsense controller. To note I do get the new shader caching UI on every single boot, I don't know if that is the case on Windows however.
Worked out of the box
Absolutely no issues encountered specific to Proton, I ran the game at 60 FPS from start to end without issues. I did have to swap to 30 FPS for some of the chase scenes due to bugs, but those are also a thing on Windows.
Worked out of the box
Had no issues with the game, got to the exit twice and found all anomalies in it.
Game crashes on boot out of the box, black screen with WINED3D
Running the game with the WINED3D launch command allows booting it, however it stays on a black screen. Sounds and menus seem functional, but since it remains entirely black you can't play it. The launch command I used is the following:
PROTON_USE_WINED3D=1 %command%
Without the launch command, the game simply crashes on boot for me.
Proton-6.14-GE-2 GloriousEggroll
Proton-6.14-GE-2 GloriousEggroll
The game works flawlessly out of the box with Steam Play and regular proton, however a single scene will display a test placeholder video. Running with ProtonGE plays back that video properly.
Works out of the box
Performance seems to degrade over time when playing for a stretch, leading to lower fps and overall performance.
Game launches and works flawlessly for the most part. I've had occasional screen tearing, obviously fixed with v-sync but then, as v-sync often does, mouse movement becomes sluggish if enabled. Otherwise, game works perfectly fine.
Assertion failed on boot
I was unable to launch the game with Experimental, 8.0-5, or the latest GE. Game crashes automatically with an Assertion failed pop up. I tried some older Proton versions and they crashed as well but without any pop up. Didn't try any workarounds (my knowledge is limited in this regard anyway).
Some light FPS issues, coupled with screen tearing.
I previously wrote a report where the game just crashes on my AMD setup (7900 XTX), as well as on my laptop (also AMD-powered graphics), but for some reason runs on Steam Decks. I tried several distros from scratch, several mesa drivers, several protons, all with the same crash.
I got a chance to setup my old Nvidia (RTX 2070) powered PC recently, fresh install, and the game boots and runs fine outside of the FPS issues. I'm not sure what's up, but in my case the game can be run just fine on Nvidia and crashes on AMD-powered computers. All the setups mentioned are running AMD CPUs.
Game works flawlessly outside of video playback
Video playback does not work
Had no issues running the game from beginning to end as far as gameplay goes.
The videos however do not play back, this affects the intro cutscene, the small tutorial videos, and the end credits. There's about 2 or 3 additional videos similar to the intro cutscene that will display a white screen as well. The subtitles will still display however, and the small pop-up windows for the tutorials all have text detailing the tutorial, so they won't prevent you from knowing what's happening nor will it prevent understanding the game and how to play. The in-game cutscenes all work perfectly fine (which is how the majority of the story points are shown).
Game works out of the box
No issues playing either with keyboard and DUALSHOCK 4. Do note that the game has an extremely weird key mapping compared to pretty much every single shmup out there, but this is in no way caused or altered by Proton.
Works the same as native
I checked Proton just by curiosity. While I didn't play this game for a long time, it ran exactly the same both native or with proton, which is pretty much flawlessly on both.
Proton-6.20-GE-1 GloriousEggroll
Proton-6.20-GE-1 GloriousEggroll
On my first launch, freshly installed, the game spanned and scaled to both monitors while displaying on the primary monitor only. This caused only the top left corner of the game to be displayed. Reaching the main menu and rebooting the game fixed it, no special manipulation needed.
Didn't have any issues in the game other than the initial launch being displayed strangely. I played through 2 chapters with mouse/keyboard before moving on.
Game doesn't boot
I couldn't get this game to boot. Initially received a message stating that dot net 3.5 sp1 will need to be installed manually, then the game stopped running. Tried installing 3.5 sp1 via protontricks with no luck, possibly due to the package being broken currently in wine. Tried forcing regardless and it didn't work, resulting in the game still not launching.
Using the latest proton (currently 6.3-5), the screen remains black, with only the audio and inputs working.
However, if you force Proton 3.16-9 in the game's compatibility settings, it runs pretty much flawlessly and doesn't have any performance issues. The dialog in the game displays messy characters, though, as it is on Windows, this is due to the local of the system not properly supporting Japanese characters.
Proton 3.16-9 needs to be forced in the compatibility options within the properties of the game. Once done, the game runs flawlessly. If ran with the latest (6.3-5), the screen remains black, although audio and inputs still work.
Proton 3.16-9 needs to be forced in the compatibility options within the properties of the game. Once done, the game runs flawlessly. If ran with the latest (6.3-5), the screen remains black, although audio and inputs still work.
