ZaptorZap
Published
A truly beautiful game.
My DS4 controller, which Steam indicated was supported by the developer, simply wasn't picked up. I just used by Xbox controller, which was correctly detected and worked like a charm.
In fact, one certain easter egg involving moving the window itself while in windowed mode is preserved.
One very specific, extremely endgame secret involving physical printing appeared inoperable, but to be honest, I'm not sure the developer expected everyone playing this game to have a functioning printer in the first place.
For the most part, this lightweight 2D game is one that demands performance from its tight controls and gameplay. Proton suits this need.
PROTON_USE_WINED3D11=1 %command%
Without D3D11 enabled, you'll end up running into a vague "Win32 function failed: HRESULT: 0x887a0002" fatal quit immediately upon booting. This game won't be the first you need to use it on, and it won't be the last, so always keep that launch option in your back pocket!
Running LUMINES is a simple task---although based on Unity, Proton has zero issue completing that task.
Similar to some other reports here, I've also received the locally generated crash reports when exiting the game. They're pretty rare, though, and are easily dismissed by clicking that OK button.
I tried porting a save over from a friend's Windows computer---it flatly didn't work but there wasn't much progress anyways. Of course, saving/loading on the device works fine.
I had to switch to Medium effects/foliage but it's been a pretty comfortable/great looking experience. Intro videos simply take a while so I would maybe recommend deleting them, but they didn't actually stop the game from launching. Initial launch took forever, but it was the first time I launched a game with my new graphics card.
While the native release works just fine for me, issues launching without tinkering on a Steam Deck may render Proton the only solution.
PROTON_USE_WINED3D=1 %command%
From PC→Steam Deck(thanks lindtobias!), the crossplay here worked perfectly, even while I was using the native release. Unfortunately though, my testing was done at a pretty odd hour of the day, so considering the servers are only based in the US, I wasn't able to play with random people(they just weren't on).
If launched with Proton forced on, you'll be greeted with the following error:
D3D error Could not create a Direct3D9 context. This usually means you need to update your GPU drivers.
This is what prompts usage of the advanced launch option above. Generally, the game runs fine natively for me, although that's an experience Steam Deck users aren't treated to, hence the "unsupported" rating from Valve. So long as you're behind Proton though, it runs just fine.
Under Proton, this game runs very competently with little-tinkering on my end. Considering the minimum *req*, I'd recommend the experience!
PROTON_USE_WINED3D11=1 %command%
If you try running the game without that aforementioned launch option, you'll be greeted face to face with the following error:
Failed to initialize Direct3D. Make sure you have at least DirectX 9.0c installed, have drivers for your graphics card and have not disabled 3D acceleration in display settings. InitializeEngineGraphics failed
Direct3D problems are always in some form related to wineD3D missing, so the solution was straightforward.
Very minor issues here, you could almost mistake the title screen music for actually including this quirk originally. I believe starting this game with the PULSE_LATENCY_MSEC=60 %command% fixes this crackling for myself.
The ingame option titled "Borderless Windowed" has noticable letterboxing around the left, right, and top of the screen, as if the window title still existed. The ingame option titled "Fullscreen" cannot be Alt-Tabbed out of, nor does any other escape sequence i know of work.
This is likely an issue which occurs on Windows versions as well. This game appears to only support the Xbox 360 input format, so by default, my Xbox One controller did nothing(although the ingame displays for menu navigation did show the Xbox controller's face buttons). After remapping with Steam Input's configuration, using the "Gamepad" template for the Xbox 360 controller, the controller worked as expected.
Initially opening the application led me directly to an issue regarding DirectX 10 compatibility, error code 0x80004005. After acknowledging this error, the game would close instantly. Opening the game with the advanced launch option "PROTON_USE_WINED3D=1%command%" fixes this issue altogether.
Furthermore, the online portion of this game must've died out years ago, but I can easily hop into the matchmaker and wait around. Leaderboard submissions go nicely too!
Aside from some rare Z-fighting---which I presume is intentional given the subject---it was a seamless experience with my PS4 controller.
I have SOME license in my wallet
Just tried to install this. Steam just throws
An error occurred while installing Steam Deck: "No licenses"
at me. Was not able to open Steam Deck on my computer :(
Certainly one of my **most smooth** experiences on Proton, thanks to the popularity this game stouts.
Particularly during the intro outdoorsey area, which made me slightly worried for the rest of the game---but aside from some noticable streaming on the low-LOD building textures when viewing the entire walled city from the few vantage points, it was flawless.
I initially played this on my Windows laptop in anticipation of Discord streaming, but after noting the poor performance under Discord's Go Live feature, a friend of mine conviced me to switch over to my Linux desktop and try it out again. While I believe now the first area simply pushed me to switch, while the rest of the game would've ran fine; Discord's Go Live simply worked a ton better under my Linux desktop for some reason. (bar proper sound support—something Discord on Linux still doesn't have)
So far, pretty seamless
On initial startup, the game window rendered nothing for about 40 seconds. It kicked into action, and hasn't done this since. About 83 minutes in, just froze up. I was able to get back in and replicate what I was doing without issues, and the game autosaves frequently enough.
I haven't quite finished the game yet, but frankly I don't anticipate many issues based on my playthrough so far. I'm using a DS4 controller, and while the glyphs are for Xbox, Steam clearly communicates that they haven't implemented Playstation glyphs yet.
In addition, the system journal is complaining pretty often with the below logs:
kernel: umip: Zau.exe[2374168] ip:14784b2c6 sp:b96140: SGDT instruction cannot be used by applications.
kernel: umip: Zau.exe[2374168] ip:14784b2c6 sp:b96140: For now, expensive software emulation returns the result.
kernel: umip: Zau.exe[2374168] ip:21c1aa1 sp:b96108: SGDT instruction cannot be used by applications.
kernel: umip: Zau.exe[2374168] ip:21c1aa1 sp:b96108: For now, expensive software emulation returns the result.
kernel: umip: Zau.exe[2374168] ip:14a78bacd sp:b96140: SGDT instruction cannot be used by applications.
Not gonna comment on what this means, but as previously stated, the game ran A-OK without any configuration whatsoever.
The lens flares appeared corrupted on my Intel ARC A580 and ingame settings don't expose any fix for this. To remove them, I had to drop the below config lines into a file titled Engine.ini in the directory: ~/.steam/steam/steamapps/compatdata/2634950/pfx/drive_c/users/steamuser/AppData/Local/TokyoXtremeRacer/Saved/Config/Windows/.
[SystemSettings]
r.BloomQuality=0
After running unix2dos on the new file(just in case), the game should eat it(actually deleting the file) on your next boot. All lens flare will be gone. If you mess with the settings thereafter they may reappear. (I believe they're tied to post processing.)
(lens flare is broken and it cannot be disabled ingame. more details ↑ above ↑)
Upon first boot with my DS4 connected, the game would throw
Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000000000003a0
and refuse to boot. Opening the game without the controller connected fixed this issue. I was able to connect it afterwards and everything worked fine. It no longer does this even when the controller's connected on startup.
A Windows friend reported they had the same issue until they had uninstalled vjoy.
Besides these startup troubles, I haven't ran into any more concerning behavior from this game. I don't even think Proton Experimental is required, but it works now and I'm not changing it. I would wager much of this instability can be attributed to my relatively new Intel ARC A580.
