Haunted Adventurer
Published
Manually set game window to full screen (two clicks on game window in bottom panel), no screen issues during play; Xbox 360 controller works after setting up controller in Options --> Configure controller within the game
Runs, but numerical values such as number of units or $ values appear as ##0; unable to get multiplayer to function or connect; online replays functioned; adding an anti-aliasing value in the video settings causes the screen to displace in a horizontal bar pattern. (Unknown values and no multiplayer prevent a Silver rating).
Runs but numerical values such as number of units or $ values appear as ##0; unable to get multiplayer to function or connect; online replays functioned; adding an anti-aliasing value in the video settings causes the screen to displace in a horizontal bar pattern. Occasional temporary screen freezes occur when Alt-Tabbing. (Unknown values and no multiplayer prevent a Silver rating).
Runs but numerical values such as number of units or $ values appear as ##0; unable to get multiplayer to function or connect; adding an anti-aliasing value in the video settings causes the screen to displace in a horizontal bar pattern. Almost a silver rating.
I was able to set graphics to my monitor (2560x1080) in Linux better than in Windows (only 1920x1080); no issues vs my Windows testing; 1st time playing the game froze on the menu while exiting but subsequent exits had no issues.
I was able to set graphics to my monitor (2560x1080) in Linux better than in Windows (only 1920x1080); no issues vs my Windows testing; 1st time playing the game froze on the menu while exiting but subsequent exits had no issues. Multiplayer co-op works fine.
Single and multiplayer work (I was able to join a Windows 10 session); game runs perfectly with no tweaks; bugs present in Windows also occur with Steam Proton; played in 1920 x 1080 resolution.
Online play does not work & account lock on 1 PC OS
After the airship update cannot play online. Also, your Among Us account is locked to the PC that the game is initially installed on, so no chat on other PC's that you may have your steam account on with the game, including dual-boot Windows on the same PC and same Steam account (as of today).
Keyboard, mouse, and XBox 360 wired controller all work.
Runs perfectly with forced Proton Experimental no other changes needed. Did not try multiplayer.
Worked the same as when running in Windows 10, including bugs found in Windows due to the game's Early Access state.
Game is currently Early Access. I found one show stopping bug in the tutorial that is also present while running in Windows 10, so it is not a Proton issue.
Initially, some pop up boxes with error messages occurred but did not effect gameplay. I did not try multiplayer for the demo.
Works perfectly as of Proton 3.16-6 with Nvidia 415.25 drivers; did not test VR mode
After (or during) the opening cut-scene (which goes black and does not continue after playing), activate the console by pressing the ` key (on US keyboards), then type "open MAP_Space" without the quotes and then press the [enter] key to continue the game. Works very well with Steam Proton 4.11-3 on my system.
Works running bubble.exe with W.I.N.E. 4.13; does not work properly using Steam Proton 4.11-3.
To run in English, set Launch Options to: "LANGUAGE=en_GB.UTF-8 %command%" Make sure that English United Kingdom UTF-8 is fully installed in your system's Language Settings (initially I did not and it corrupted my game install). Game runs fine on my system with high graphics settings. Play tested free driving for an hour.
Manually set multiplayer zone; everything else works. Experienced a crash in a private multiplayer game; still Early Access so YMMV.
After adjusting in-game graphics settings to ultra/high, game runs perfectly; tested campaign mode.
Gives Steam Error "Application load error 5:0000065434" then exits.
After validating game files, it works perfectly out of the box.
Gives Steam Error "Application load error 5:0000065434" then exits.
A save file must be created in Windows and transferred to Linux in order to play as of Proton Beta 3.16-6: Dual boot to Windows, install game and create a save file, files directory located within %USERPROFILE%\Documents\My Games\EDF4.1\SAVE_DATA Then boot to Linux, copy save files directory to /steamapps/compatdata/410320/pfx/ Some text is missing in game menus, but game is playable; completed first mission for testing
Works running executable with W.I.N.E. 4.13; does not currently work with Steam Proton.
Initial tests indicate it works with Steam Remote Play Together
Runs perfectly out of the box; however, changing the anti-aliasing settings to highest caused the game to crash repeated at start; had to reinstall to get it working again.
Game runs and could set up a private server with password. Was not able to find any games online (possible due to early access state).
Not able to use in the game system to link and create a new IL-2 account.
After the tinkering, the game ran perfectly with an XBox 360 controller; I was not able to test multiplayer.
- Downloaded mf-install-master from https://github.com/z0z0z/mf-install
- Unzipped the 6 items to /home/[your user name]/.steam/steam/steamapps/compatdata/342620/pfx
- In the Terminal, run WINEPREFIX="/home/[your user name]/.steam/steam/steamapps/compatdata/342620/pfx" ./mf-install.sh
Configuration utility starts up, then crashes after any selection.
Use experimental Vulkan-based Direct3D 9 renderer in Launch Options -
PROTON_USE_D9VK=1 %command%
- Fixes graphics glitches using Steam Proton 4.11-3 on my system.
After ignoring "Assertion failed!" Microsoft Visual C++ Runtime Library error 3 times, game starts with no video. All 3 tweaks attempted.
Changed graphics settings to 1920x1080 to fit my 2560x1080 screen, otherwise ran fine on my system; suspect slow downs occur in Windows also according to reviews; completed one play through successfully; did not test local coop.
Set graphics to 1920x1080 to fit my widescreen; runs perfectly after changing graphics resolution; slow down in games occur in Windows also. Tested with Xbox 360 controller.
Game now runs and starts properly. A quick test reveals that everything appears to be working; more play time testing is needed.
Runs using default graphics settings at 1024x768; played with Xbox 360 wired controller & keyboard; did not play online missions.
Game played well through the tutorial.
Had to press buttons to advance black screens pre-game. Everything else worked. Demo hung on exit; had to force quit.
Worked perfectly out of the box; configured X-Box 360 controllers in settings
Played with Xbox 360 wired controller; in galleries, control scrolls automatically to the last item, videos don't play, otherwise game is completely playable.
Runs perfectly out of the box! Played the tutorial and some free-play.
Did not test VR in Linux (Wireless HTC Vive has no drivers for Linux).
Played with XBox 360 wired controller on my system. After initial resizing of video to full screen, game seemed to play well. Did not try coop features.
Text now works within the game; set to Ultra in Unity menu; left game in windowed mode 1920x1080; I have not tested multiplayer extensively.
Works better than native except for minor slowdowns in menu initially connecting online and when selecting to connect to an online game, otherwise perfect.
Game now runs fine from startup for several minutes until the mouse stops working with all in game pop up messages. I got around this issue by using an Xbox 360 gamepad to navigate the messages without tabbing out, and then continued to use the mouse/keyboard setup. If I tabbed out and back into the game, the mouse would spin uncontrollably. The game could be continued with a gamepad but the mouse remained uncontrollable.
Game now appears to run perfectly again; mouse errors no longer occur as of Proton 4.11-4; Xbox 360 controller interchanges seamlessly with mouse/keyboard setup.
Now runs with no mouse or controller issues as of Proton 4.11-4. If ship navigation control issues occur, saving and restoring the game eliminate the problem.
Scopophobia (Patch 10.0.0 BETA II) does not work with Steam Proton
Error is: Can't obtain system code integrity info (C0000003)!
The game worked for me by adding Proton-5.9-GE-1-MF to the steam compatibilitytools.d folder.
Scopophobia 10.0 beta V works with GloriousEggroll Proton-5.9-GE-1-NR as of 2010-06-02 https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.9-GE-1-NR
I believe anticheat softrware is implemented. Did not attempt online multiplayer but appears to work as I could see servers and create my own.
I created a local server with the client and it worked; I did not change menu or graphical settings as other players indicated having issues doing so; latest version of game is still in beta as of this review.
As of Version 10.0.0 Scopophobia Beta VII , the game no longer runs with Proton or GloriousEggroll.
Linux support has been dropped for the next public update. Currently I cannot get the beta to run using any methods, including GloriousEggroll.
Tutorial/single player was excellent connected with the server. Do not expect any online multiplayer issues but haven't tested yet.
Set Launch Options: PROTON_NO_ESYNC=1 PROTON_USE_WINED3D11=1 %command% -popupwindow Screen will occasionally freeze when press Esc; pressing Win key will fix; screen spinning with mouse control fixed by pressing Win key.
Played both demo and retail; seems to run perfectly, no apparent issues; have not tried on Windows
Works running Windows 7/8 executable with W.I.N.E. 4.13; I found the Xbox 360 controller working on my system. The Windows 10 executable did not work with W.I.N.E. Does not currently work with Steam Proton.
Using GloriousEggroll Proton-5.9-GE-3-ST, the game plays perfectly using a wired Xbox 360 controller.
Loaded GloriousEggroll Proton-5.9-GE-3-ST into home/.steam/compatibilitytools.d directory
In game text now fixed; game functionality and mods work fine.
