8089
8089 > General > Topic Details
 This topic has been pinned, so it's probably important
phr00t  [developer] Aug 16, 2021 @ 2:01pm
Troubleshooting? Questions? Check here first!
8089 crashes (and it isn't an OpenXR error)
Make sure your GPU drivers are up to date! FPS Infinite uses Vulkan exclusively, and the best support comes from your latest drivers.

If you have anti-malware preventing this game from writing files, try disabling it for this application (it may try writing crash files to your Documents folder).

If a certain resolution or fullscreen setting is causing issues, you can edit (or create) a DefaultResolution.txt file in the same local folder as the running executable. For example, try this in DefaultResolution.txt:

1280
720
window

... which will make the game attempt to start as a window with a resolution of 1280 by 720.

If you still have issues, please post Event Viewer details on the crash!

1) Start -> "Event Viewer"
2) Windows Logs -> Application
3) Find "Errors" that describe 8089 around the time of the crash. Usually two errors get created.
4) Either paste the contents here for each error found (contents of the "General" tab should do).

8089 crashes when trying to play VR with some OpenXR error!
SteamVR is the only OpenXR runtime that is supported -- make sure it is running! Windows Mixed Reality's OpenXR implementation doesn't support Vulkan, and Oculus's OpenXR doesn't appear to play nice with Silk.NET.OpenXR currently (validation errors). SteamVR works great, though! To set SteamVR as your OpenXR runtime:

SteamVR Settings > Show Advanced Options > Developer > Set SteamVR as your OpenXR Runtime

This will NOT mess with the vast majority of other games that use OpenVR or the Oculus SDK. It will make OpenXR games run in SteamVR, which is how Valve tests all OpenXR games that hit the Steam store & isn't a bad thing! If you want to switch it back, here are the instructions to do so for Oculus:

https://steamcommunity.com/app/250820/discussions/8/2448217320134491995/#c2448217763555888424

The registry key is a post or two above. I wish Oculus had a simple button like WMR and SteamVR!

What happened to Mac support?
OSX doesn't support Vulkan, and 8089 uses Vulkan. OSX has a proprietary "Metal" graphics API, and a compatibility layer called MoltenVK does exist that tries to bridge the gap. The problem is, working through these two complications is very difficult to maintain. Mac support did work about 2 years ago for FPS Infinite, but now even that game's Mac support has faltered after changes to both MoltenVK and OSX. After seeing wishlist numbers compared to Linux and Windows, Mac support was not worth the time pursuing. If you want to read more about this, see the discussion starting here: https://steamcommunity.com/app/1256380/discussions/0/1744520688775831493/?ctp=6#c3114795024914161106
Last edited by phr00t; Oct 26, 2021 @ 10:28am
< >
Showing 1-7 of 7 comments
Tip for people having issues with the game not running that have a laptop with both dedicated and integrated graphics. On my Asus ROG G14 Windows 10 has a habit of "updating" the AMD graphics driver to an older version that causes issues with some games, 8089 included. Going to device manager and rolling back the driver actually put it back on a newer version that I had updated to and that fixed the issue.

I had the same issue with X4 and it was the same fix. My Nvidia drivers were up to date.
Playing in non-VR I can't get the FOV to change at all, DefaultResolution.txt is not created upon running the game and when I created the file it still doesn't work, my file reads;
1920
1080
window
90

Any idea what I'm doing wrong? Many thanks.
phr00t  [developer] Jan 14 @ 6:38am 
Originally posted by FiveSixtyEight:
Playing in non-VR I can't get the FOV to change at all, DefaultResolution.txt is not created upon running the game and when I created the file it still doesn't work, my file reads;
1920
1080
window
90

Any idea what I'm doing wrong? Many thanks.

You won't see the change in the main menu. Did you try starting a game to see if the fov was different? Also try changing resolution numbers to make sure the file is being picked up.
Hi there Phr00t! Yes I'm loading my save each time I try it and I've set the fov to 150 so that it will be obvious if it works lol
phr00t  [developer] Jan 14 @ 9:36am 
Originally posted by FiveSixtyEight:
Hi there Phr00t! Yes I'm loading my save each time I try it and I've set the fov to 150 so that it will be obvious if it works lol

Have you tried changing resolution numbers to see if those get picked up?
Originally posted by phr00t:
Originally posted by FiveSixtyEight:
Hi there Phr00t! Yes I'm loading my save each time I try it and I've set the fov to 150 so that it will be obvious if it works lol

Have you tried changing resolution numbers to see if those get picked up?

ok I changed the DefaultResolution.txt file to 1368x720 and it worked, the FOV still won't change though.
Update
For some strange reason the fov works if I set the resolution to 1600x900. I'm happy though :)
Last edited by FiveSixtyEight; Jan 14 @ 1:08pm
phr00t  [developer] Jan 14 @ 4:22pm 
Originally posted by FiveSixtyEight:
Originally posted by phr00t:

Have you tried changing resolution numbers to see if those get picked up?

ok I changed the DefaultResolution.txt file to 1368x720 and it worked, the FOV still won't change though.
Update
For some strange reason the fov works if I set the resolution to 1600x900. I'm happy though :)

Hmmmm you may have just tipped me off to a bug... I will look into this!
< >
Showing 1-7 of 7 comments
Per page: 15 30 50

8089 > General > Topic Details