Aside from maybe two instances of textures popping in from a relative distance, everything ran great. Had the game at medium preset and locked at 60 while streaming on Vencord and it was all fine.
gamemoderun %command% -dx12
-dx12
Missing textures on vending machine
Cannot create a new game without the launch option: -dx12
-dx12
画質設定を全て最低設定にし、フレームレートキャップを30に設定した。
起動オプションに-dx12を入れないとゲームができなかった。ただ、それさえしてしまえばそれで終わりである。一部グラフィックのバグに遭遇したが、進行不能やクラッシュなどはなかった為、さほど気にしなければ良いと思える。protonのバージョンがexperimentalだとゲームを始めれなかったため、9.0-2に変更した。以上。
Works perfectly after said tweaks. -dx12 is musthave, cause it wouldn't load new game without it.
gamemoderun %command% -dx12
gamemoderun is optional for "better stability" (maybe)?
Running with DirectX 12 causes memory leak and causes the game to run at very low framerates
%command% -dx12
The audio sometimes crackles randomly, but not very often.
The textures look blurry at the beginning of the game when using VKD3D (-dx12). It happens only there, the textures look fine later.
You have to either use -dx12 in launch options or switch to Proton 6.3-8 to make the game work. Without it, you will see а white screen in the introduction video аnd skipping will result in crashing your game. I was able to finish the game with minor issues, but it was playable.
%command% -dx12
As others note, on first area, it's got some heinously low res textures in the start. It's a theme park though so you don't miss anything, the same banners that were a bit too blurry to read outside are nice and sharp a minute or two later when you're in the park.
Defaulted to Epic settings -- FPS dipped down to like 15-20FPS, but I'm walking around an abandoned park, not running and gunning so I didn't find this an issue. If you DO turn down the graphics setitngs you'll want to turn the lighting quality back up -- the park has a lot of burned out light bulbs, the ones that DO work seem to cast less light the lower the lighting quality is set.
gamemoderun mangohud %command% -d3d12
During the mollie chase sequence, you would freeze and inevitably die but after that it was fine.
I would also advise not to use lumen as it ruins the atmosphere of the game a lot (making the environment way brighter than it should). I used SSR and it was more enjoyable for me.
gamemoderun %command%
Runs at my framerate cap of 144hz if I turn off Lumen. TSR looks fugly as all get out on the bright screens, causing tons of ghosting on Rambley.
Disable Lumen and TSR for the best visual clarity, enable them if you prefer the shadowing effects despite the ghosting artifacts.
removed gyro
game ran choppy, couldn't find graphics so I played like that
-DX9
Game refused to go above "medium" graphics preset
Frequent, somewhat random lagging
Freezes upon dying to Mollie (I used Ctrl+Alt+Bkspace to restart PC)
I was using the free driver, video-linux, and was getting either a frozen loading screen or just a black screen. Once I switched to video-nvidia, though, everything works just fine with GE-Proton (I haven't tried other versions, yet)! There's a bit of a lag, but not enough to be frustrating.
The first area still fills my 6 GB of vram, but the textures mostly load correctly now. If the textures didn't load correctly, fiddling with the settings generally fixed it. (eg: turning texture quality down, then back up to where it was. This is mostly applicable to the first area.)
If you don't want to install GE-Proton, you can play using the launch option -d3d12 with regular old Proton 9.0-2. The textures don't load fully in the first area, but otherwise it plays fine.
changed shift key from left stick click to x button to be more comfortable
medium graphics locked to 30
some subtitles go of screen
low textures not protons fault games dev says all platuforms are affected
runs at 20fps on default go to m3dium for 30fps
doesnt run without custom ge
Indigo park is an enjoyable and charming indie horror game that runs great on the deck at medium graphics settings
Added a shift backpad
The cutscenes work using this Proton : GE-Proton9-10
Changed shift
This version allows the cutscenes to be played!
Game finally gets through the intro screen without a command in launch. Playable with some minor artifacts here and there with the latest GE-proton.
%command% -d3d12
Played through the game twice, the first level seems to load low quaility textures. After the first level it is fixed.
Without the launch args the game only launches with 1/4 of the screen being visible
Ew Lloyd
gamemoderun %command% -d3d12
Installed and got to menu ok, would get a whitescreen and no audio when attempting to start the game. Forced DX12, and experianced no issues afterwords.
Game crashes upon loading. Also fullscreen and borderless don't work at all and if you set your Windowed mode too high.
Doesn't work on Linux.
Game only loads on Proton 9 for commands to work ( does not work on Proton Experimental). Slow performance with unrendered graphics.
%command% -d3d12
Intro Crashed everytime
I do not recommend playing till everything is fixed.
Will not launch unless in dx12, which leads to instability and awful texture quality. Gameplay not achievable without it, though.
Borked. You need to put up with obscenely bad texture quality even if the game is set to Epic by forcing the game into dx12, or not be able to play it at all.
If you're willing to put up with degraded texture quality even if the game is set to Epic texture quality, sure.
Texture streaming seems to be bugged or are incredibly slow. Game critical textures appear to load just fine.
Alt-Tabbing leads to a game crash.
ProtonGE and -d3d12 as a launch parameter are REQUIRED. Will not launch with one or the other alone.
gamemoderun %command% -d3d12
Proton 8 caused all textures to be EXTREMELY low resolution
The first area is really choppy, but all further areas ran smoothly
First jumpscare had a harsh few seconds of the game being frozen; further deaths did not freeze.
Running without d3d12 EXACTLY causes all videos to show as white with no audio.
WASD on D-pad
Rarely, subtitles would be wider than the screen.
Def not ready for stock Proton 8+
%command% -d3d12
Occasional choppiness in certain busy areas, presumably due to engine
Presumably at fault of UE, however once the game is forced to run under Direct 12, it runs fine, albeit with frame drops in busy areas.
mangohud %command% -dx12
Textures look blurry. Assuming this is because of setting all graphic options to the lowest values.
Inconsistent FPS, ranging from 88 to 37. Had to run the game on 720p or else it'll close due to VRAM running out. Locked the FPS to 30 to hopefully reduce the chances of it crashing.
Will sometimes close due to running out of VRAM. Sometimes will run just fine despite VRAM already being full and have offloaded a few GB's on system RAM.
The introduction video will not play unless ran with "-dx12" or "-d3d12" launch option. Adjusting the "Resolution Scale" option will freeze the game, throw an "Assertion failed" error and make it unlaunchable because it will throw up the same error next time it's launched. To fix, validate game files to reset in-game settings.
After hours of tinkering around, I've finally made it to playable FPS! Sadly this game needs a GPU with > 4 GB of VRAM for it to be stable. I'm assuming because this is a UE5 game. Still inconsistent with the game complaining that its exhausted the VRAM and closing but when it works, it works. I've yet to finish the starting scene.
white screen after the head menu. after skipping it, black screen and thats over. tryed to check in game settings, doesent work eather
%command% -d3d12
Degraded graphics when ran with "-d3d12" launch option
Low FPS
Inconsistent freezing when ran with "-d3d12" launch option.
Intro video is white when the game isn't running on DX12 (VKD3D)
From the looks of it, it fills up the VRAM. Then it goes on to fill a portion of RAM once the VRAM is full. Even when adjusting the graphics options to lowest, it still manages to fill up the VRAM.
only 1 - 2 FPS
Out of VRAM when ran with "-d3d12" launch option.
Sometimes the introduction video will play. Sometimes it's white.
From the looks of it, it fills up the VRAM. Then it goes on to fill a portion of my RAM once the VRAM is full. The lack of graphics quality adjustments such as shadow quality, postprocess, etc. makes things complicated.
Softlocks after loading when clicking "New Game"
Game gets stuck after loading, does not play initial cutscene. Skipping the cutscene by holding E gets you stuck on a black screen afterwards
WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%
need to set launch options or video cutscenes ether hang the game or dont play.
gamemoderun %command% -d3d12
Once you get to Jetstream Junction the graphics are completely unrendered, does not fix after restart, check for my post on GE to see if problem is solved
The game IS great, but due to the loading freeze, I am unable to play it. Maybe with some low-level tinkering it could work.
Disconnecting audio +bluetooth devices (quite common on my machine, could also be a problem on my part frfr.)
shading appearing too strong
Forced fullscreen, could ony switch to a different VirtualDesktop.
My mouse would stop "clicking on buttons" when I changed my proton versions (Both standard/steam and GE)
When changing video settings, the game always freezed and sometimes even crashed, but it kept the changed setttings (maybe intended, but the freezing looks like a byproduct regardless)
The game would not load both the initial and ending sequence, the intro/outro is always sutck at 0% loading, I will be running further tests regarding this issue . . . On my 2nd try I somehow maneged to bypass it. Allowing me to finally play this masterpieceof a game! But.. Sadly, not anymore.
My steam log + tinkering when loading >>>
https://docs.google.com/document/d/195AsveHZEOjEM2BW1TRdr_Nah4hZ6IzO_qkw2fmdBzc/edit
gamemoderun %command% -d3d12
Setting graphics to medium helped
Was only able to get the intro video to play with the launch commands shown. If the intro isn't playing, it can be skipped by holding E
[Intel Iris Xe] Works fine and with okay framerates (50~60 FPS) at Medium, 720p. See below for notes on running on this hardware.
Very low texture quality in the first area and later on near the ending. All other areas are fine.
The memory leak issue could sometimes cause Linux to start swapping memory and introducing stutters, they were very brief though (see my previous reports).
Cutscenes do not work in D3D11 with Proton, TKG-Proton or GE-Proton (it does work in Bottles with Soda 9.0 though). I cannot test -d3d12 because VKD3D does not support SM6.6 on Intel Iris Xe.
I needed to upgrade to 16 GB of RAM to finally be able to play this game on my Intel Iris Xe GPU, otherwise a memory leak would cause the game to crash as it tries to allocate too much VRAM. D3D12 mode is not possible on this GPU.
MANGOHUD_CONFIG=vram mangohud %command% -d3d12
Only a little bit though.
Some low quality textures in the first area (Minimum LOD, less than normal low settings.)
At some point in my testing, it put me at the ending cutscene? It hasn't happened since.
It crashed once when starting a new game at high settings. (I think it filled my ram? It killed all my programs.) I haven't done any long-term testing though.
It plays fine at Epic settings with no Lumen. It only worked when I turned up the settings after getting past the first area. In the first area, it completely filled my vram at minimum settings. In the second area at nearly max settings, it's only using 4.5 gigs of vram.
game closes on startup with error
Assertion failed: IsValidIndex(Index) [File:D:\build++UE5\Sync\Engine\Source\Runtime\Core\Public\Containers\UnrealString.h] [Line: 217] String index out of bounds: Index 0 from a string with a length of 0
Game runs a little slowly. Had to use Proton-6.21-GE-2, wouldn't work otherwise. Froze up nearly every time I died. Cutscenes do not play.
Game seemed to freeze at the splash screen, but worked fine in Desktop Mode.
Textures were very low quality, had to set the texture quality to Epic, even High was worse than what Low should be
Game froze up every time I died, except the first time
Cutscenes do not play and just show a test pattern, then moves on
Runs well enough if you mess with custom Proton versions and graphics settings.