CHEATFAN14
Published
Not being able to use the trigger for blocking is a huge problem, as it forces you to use mouse and keyboard.
Proton-6.5-GE-1 GloriousEggroll
The left and right triggers would not work. I tested this on the current version of Proton and with GloriousEggroll. I have also tested this on Windows 10 to make sure it wasn't just the game.
Sometimes, the camera seemed to "stick" on one of the axes. For example, sometimes the camera would get stuck straight up for a small amount of time, but moving left and right was fine. This seemed to only happen when using the mouse.
The initial loading screen does not load using normal proton (just a black screen until the game loads). It does show up with GloriousEggroll.
Twice my controller was not recognized/didn't work when I started up the game. I made sure it was plugged in before loading the game, as the game will not detect a controller if you plug it in while the game is open (that is normal for Neptunia games).
Using a mouse and Keyboard for this game is a terrible experience, even with rebinding. It's just as bad on Windows 10.
Works perfectly even using swap space. I got a mostly stable 60 FPS on missions. I did not test multiplayer.
I did have a crash on startup once or twice, but that's all.
Multiplayer works as expected.
I use Proton Experimental, so the crashing might have been from that. Game works perfectly fine aside from that. I have not tested the game on other versions.
The game likes to minimize itself if you alt-tab or otherwise unfocus the game.
The game is extremely dark and color/brightness settings aren't saved on some Proton versions. I only had success with GE versions.
Proton-6.8-GE-2 GloriousEggroll
https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/6.8-GE-2
I had an issue where if you're moving with the keyboard and you Alt + Tab while moving, the controls kinda get stuck, so you keep moving the way you were before you Alt-Tab'd. This is fixed by spamming the movement keys (basically you smash keys) or doing Alt + Tab to switch out of the game, then switching back in. This isn't super likely to happen to people, but it happens to me because I keep some bindings on Alt + [Key] and I use Tab to target.
To make it easier to understand:
- Move with WASD
- Alt+Tab while moving
- Alt-Tab back
- Stuck moving (still can control, but constantly moving in a direction)
- Smash keys or Alt+Tab out and back in
- Should be able to fully control your character again.
It might be because I play using Borderless Fullscreen, but when I use my keyboard's audio controls, it causes a very short lived stutter. I also go down to ~30 FPS (I'm normally Between 70-100 FPS) if I adjust the volume or when I get a visual alert from programs. This lasts for as long as the alert is shown. I'm guessing this happens when something is "drawn" on top of the window.
Please test if you can play without tweaks before making modifications. When I was last on Solus (about 3 weeks before this report), I was able to run it with just Proton Experimental, no tweaks or anything.
To make the game work on Pop!_OS I had to modify the FFXIV_BOOT.cfg file found at ~/.steam/debian-installation/steamapps/compatdata/39210/pfx/drive_c/users/steamuser/My Documents/My Games/FINAL FANTASY XIV - A Realm Reborn
The line I changed was Browser 2 to Browser 1.
If that modification doesn't work for you, check other reports below to find other solutions that have worked for others.
If you don't use Experimental, the game works fine.
Online play works perfectly (aside from game bugs)
I used to use Proton Experimental, but recently I had major performance issues with it. Using non-experimental versions fixed that issue.
If you're looking to play Halo's campaign solo, the game works fine. If you want to do anything related to multiplayer, you're out of luck.
Game audio seems very quiet for me if I set audio to the remastered settings (AKA not "Original")
Co-op would not work properly. The game would desync constantly and consistently in Halo CE and would disconnect frequently during Halo Reach. This happened no matter what version of Proton I used (Experimental, GE, Default, older versions).
The game should work fine with any recent version of proton, including GE and Experimental.
If you want to play with a non-Xbox 360 controller (yes, that includes Xbox One), you'll want to configure JadeEmpire.ini in the game's installation directory and use these settings (taken from pcgamingwiki.com):
Movement L/R=Left StickX
Movement U/D=Left StickY
Look L/R=Right StickX
Look U/D=Right StickY
Menu=Button 8
Combat Pause=Button 7
Fight Style 1=Hat 1
Fight Style 2=Hat 1
Fight Style 3=Hat 1
Fight Style 4=Hat 1
Attack=Button 1
Block=Button 2
Strong Attack=Button 3
Focus=Button 4
Chi Strike=Button 6
Chi Heal=Button 5
Target Left=Left StickZ
Target Right=Right StickZ
No Target=-
Free Look=Button 10
It's not perfect, and there will be issues, but its far better than default. If you have a Steam Controller, you can configure it like a 360 controller and you won't have any issues with the controls at all (not sure if you still need to make the above changes though).
During some cutscenes, some audio was way too loud, and some audio was nearly impossible to hear.
I had the launcher crash once when opening the configuration tool.
Cutscenes play in half of the screen (meaning it looks half cut off). This isn't much of an issue as you're easily able to understand what's happening regardless of that issue.
This game is a notoriously bad port, so its very difficult to tell what's a Proton issue and what's just the game. You can use mods, which is nice.
It runs fine with Proton Experimental. No issues at all while playing in the normal windowed mode.
Downside is you can't use the 18+ patch as far as I know.
The game works well on v1.0.2 and e1.9.0 (Beta version), as long as modding isn't important to you.
I noticed some minor crackling at times. Its pretty subtle most of the time.
I haven't had any issues with the current version of the game nor with the beta version I play on. So far my performance is better than on Windows, but not by much. Some mods do work, but I would like to stress that it's only some mods. It seems like, from my experience, anything that changes parts of the game have a good chance to just not work and crash the game on startup or freeze during the initial load screen (it can also infinitely load). I have only been successful getting 2 mods to work.
I have not used any Proton versions other than Experimental.
I had an issue once where the game went back to having the resolution set to 1920x1080 instead of 3840x2160.
WINEDLLOVERRIDES="wsock32=n,b" MANGOHUD=1 %command% -skip_intro
Online works perfectly.
Be aware that if you switch from native to Proton, you will need to rename your save if you want to keep your progress, as Overkill decided that Linux and Windows saves won't be synched anymore.
I had to switch to the Proton version after a Vulkan/Mesa update broke my game a few months back. I wish I did this earlier. SuperBLT and BeardLib work perfectly on Proton as long as you use WINEDLLOVERRIDES="wsock32=n,b". If you don't add that launch option, they will not work.
The game will crash from time to time, but that's not a Proton issue. It's normally due to stuff like the cop AI trying to index null (that's my most common crash). I've only had 2 crashes since I switched.
I had some noticeable stutters after combat in one of the Palaces, but that's all.
On day 5/27, during the phone call for the counselor rank 3 hangout event, my game completely froze. While I was trying to troubleshoot what was happening, the game unfroze and played like normal again after about 3 minutes. This issue never happened again
I'm not sure if newer Proton versions fixed the save issues that plagued the game at release, so I went with the GE version that added the fix.
Set your graphic/video settings to low if you have slowdown issues or weird framerates
Any graphics/video settings above "low" have inconsistent framerates and high is horribly slow.
Steam Overlay does not work in the game (at least for me). I cannot see my FPS nor does Shift + Tab work.
The game works almost perfectly, just not Voice Recognition. Even the beta versions work.
Voice Recognition does not work. This is because it uses some Windows 10 specific features.
My mouse was extremely sensitive. Roughly 2-3 times the normal sensitivity. This is easily fixed though by turning the sensitivity down in the game.
I did try this both with the live version and the beta versions. I did not experience any issues I wouldn't experience on Windows (other than the mouse issue). I was also playing with max settings during all sessions.
Multiplayer still works perfectly.
I have not used any Proton versions other than Experimental.
Game works perfectly after the game's last major update which seems to have fixed the issue with the game not being able to use your microphone.
protontricks 21690 -q wmp11
Inside the game's installation directory, I edited the file BH5AE_install.vdf using NotepadQQ (though I'm sure any editor will work). I deleted the section regarding GFWL (Games For Windows Live) before launching the game for the first time.
Game likes to minimize if you alt-tab.
I was able to play with my friends in co-op without issue.
DO NOT LAUNCH THE GAME FOR THE FIRST TIME WITHOUT FIXING THE ISSUE WITH GFWL OR YOU'LL HAVE TO DELETE YOUR PREFIX AND START OVER
I honestly have no idea how, exactly, I got the game working. I tried doing the methods other people have reported but nothing was working. I installed this mod here, deleted the section of code I mentioned above, and used the protontricks command also listed above, and the game still didn't want to launch. I eventually let it try to start for about 2 minutes and it eventually opened and I've never had issues launching the game since.
If you don't want to bother with getting the game to run at modern resolutions, I highly suggest you enable windowed mode by changing the following in swkotor.ini:
[Graphics Options]
FullScreen=0
AllowWindowedMode=1
There's also an issue with being unable to move after combat that can be mostly avoided by enabling V-Sync and setting your system's Refresh Rate to the same as the game's.
Cutscene after defeating the final boss had no audio. Some of Bastila's lines had some crackle that was quite loud (this was rare).
There was at least 1 instance of the dome around mines having a bit of "RGB blooming".
When playing in fullscreen, if a cutscene were to play, it would act like it was reopening the game in fullscreen (this never happened in Windowed).
The game sometimes failed to load areas, leaving you stuck in a load screen. I had to close the game through steam to fix it.
The credits for the game played in a small window on the bottom left of the game window, surrounded by dark pink.
If you play the game with V-Sync on, but your refresh rate is higher than the game's refresh rate (its listed right next to the resolution), you can get stuck after combat. The simple way to get around it is to quick save then quick load. If it happens all the time, you'll want to change your system's refesh rate like I had mentioned.
I got some mods to work (I played with and without mods). If you install mods, I would suggest testing each mod you add to make sure you don't break your game.
The game has been working perfectly fine for me with default Proton.
The video that plays at the start doesn't work properly (looks like the "technical difficulties" thing you see on TV). This isn't an issue as it skips itself after about 2 seconds and it doesn't prevent you from getting to the main menu.
This game uses the Unity Engine and you'll see performance tank when you get more students and buildings. I've had the game crash once or twice but I don't think it was due to proton. There have been reports of input lag but I myself haven't experienced it unless I was playing another game in the background.
This game runs well enough IF you don't play it for a long time in 1 session and have a good amount of RAM. (Please read extra notes)
Recently I've been getting stutters when I try to play cards or place a building, but it only seems to happen 50% of the time and usually when I have a few students/buildings.
Recently I noticed the game started to take up an alarming amount of RAM which some times lead to a crash, and other times locked up my system when I ran out of swap space. I have 16GB of RAM and 4.3GB of swap.
The problems I mentioned I have only very recently discovered. I've done testing on Windows 10 as well but can't get conclusive evidence that the memory issue I've been having is a game issue or not.
I play with "Marathon" game length so this might explain as to WHY I see this issue. At times I saw that the game was taking over 12GB of RAM.
I tested this over the past few days with the default version of Proton and noticed that you gain a bit of RAM usage when you draw cards, but the RAM usage never goes back down, so it begins to snowball when you start drawing lots of cards. This results in the game using about 6-8GB of RAM by the end of a round with marathon game length (can take upwards of an hour depending on difficulty settings). I also tested this with GloriousEggroll 6.15-GE-1 (Proton-6.15-GE-1) and found that the RAM gets used up far FAR quicker (often times hitting 10GB used in 10 minutes).
Native version does not work on Solus, but it works with Proton as long as you roll back the game version to 2.8.1
Version 3.0 of Stellaris doesn't work at all with Proton. It works perfectly fine as long as you roll back the game by right clicking the game in your Steam library -> Properties -> Betas -> Under "Select the beta you would like to opt into", select "2.8.1 - Butler Version" from the drop down menu.
The game may ask you to install a launcher when you first start up (only happened once) and then crash after, but it works fine if you relaunch the game. This may only happen if you use a version of Proton older than 6.3-2 (I accidentally used 5.13-2 when trying to get the game to launch)
You won't be able to see almost anything.
Textures were stretched or "runny"? Don't exactly know how to describe it. Point is, the main menu looked terrible and the text was near impossible to read. It wasn't any better after starting a new game.
I did also try other Proton versions, but the result was the exact same.
Game works normally with Proton, even the patched version.
If you have Windows, you can play the patched (18+) version by installing the game on Linux and copying the patched version files from Windows into the game's Linux directory.
Install Linux version on Steam -> Install on Windows -> Patch windows game -> Copy Windows files into the Linux version's directory. Mine was located at: ~/.local/share/Steam/steamapps/common/Terrible Laboratory
I had dropped mouse inputs in combat before leaving the sewers. This problem hasn't happened since.
Frame dips in the areas before the end of the sewer (at the start of the game). I would go from 60 FPS to 30 - 40 FPS for about 2 seconds, then back to 60 FPS. This happened most frequently after leaving the prison cell.
Game was working fine with some frame dips on Proton 5.0-9. I changed my graphic settings (in game) and I started getting constant CTD in the main menu after restarting. Switching to Proton 4.11-13 fixed the CTD issue. No other issues other than a normal Bethesda game crash and other bugs.
Game minimizes itself if you alt-tab. You can fix it by setting the game to fullscreen.
Once, I could not see settlement names and other parts of the game were missing. I fixed the issue by deleting the prefix.
Multiplayer seems to work fine.
I highly recommend playing on Proton over native if you care to play the game for longer than 20 turns or want to play multiplayer. Native has a very notorious bug, that I have yet to run into on Proton, that will basically brick your save as you'll get the segment fault almost no matter what you do. The game has also not crashed yet due to running out of RAM which happens to me frequently with the native version.
The game would not launch after installation.
I tried using all available proton version, including G.E., with no success.
