Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Known Issues Sticky

A topic by ashtorak created Dec 14, 2021 Views: 1,262 Replies: 17
Viewing posts 1 to 7
(79 edits) (-1)

You can add issues / bugs that you find here in the replies or as a new thread. I will add them here to the list. If you report a bug please answer these questions:

  • When does it happen / how often?
  • Is it reproducible?
  • If so, how can I reproduce it?
  • Post a screen shot with FPS counter on or system specs.

Most reports are posted by people on Discord nowadays. I'll try to keep the issues list updated. Here is the link: https://discord.gg/Rnqsu5nxjf

Known Issues:

NEW

  • Initiating landing on Starship after you switched camera to existing Starship makes you stuck in control panel menu.
  • Initiating landing when tower has been deactivated doesn't work properly right now. Fix in future patch.
  • Ground plumes: When you stop producing plumes, but start new ones before the old ones fizzled out, all plume particles will be deleted after the old ones fizzled out completely, including the newly spawned ones.
  • There are reports of "game turning black", but nothing is confirmed yet. (Update: It happened to me just once so far. So seems to be a thing. The main menu did still work though and by changing quality settings I got it back to normal. Odd

Major

  • Changing quality setting (or enabling ray tracing) sometimes crashes the game or doesn't work properly. If you restart the game, it should start with the new quality setting. Alternatively you can change it in the settings.ini in the data folder.
  • On lower end systems like my laptop I also have sometimes crashes on game start. Not sure why.
  • Ray Tracing: There are some limitations right now with ray tracing in Unity. Some stuff looks buggy. DLSS blurs texts quite a bit. If it crashes a lot, try lowering the general quality setting, if you can.
  • Audio with Oculus headsets: There was a driver update some time ago which broke the audio settings when an Oculus device is connected or detected by the Oculus App. You have to go the Windows audio settings to de/activate the Oculus audio stuff as you need or close the App to get sound when you don't play in VR.
  • Linux: Player settings like windows size and keybinds are not saved, at least on my system. But it might happen in general.
  • Linux: Crash when changing quality or restarting or similar. Not sure, where this is coming from. But when you restart the game, it should start with the new quality setting. Alternatively you can change it in the settings.ini in the data folder.
  • VR doesn't like the high quality setting it seems. Try lowering the quality, if it's unplayable. Switch to clear sky, if the clouds look weird.
  • With clouds on and having time of day advance with the speed setting, it will have a huge impact on performance on large screen resolutions. It's a problem with the volumetric clouds in HDRP. But they are still in development. So maybe it gets fixed.
  • Transparency and the current Unity water system don't work very well together. So sometimes transparent stuff is not rendered properly or at all in front of water.
  • SPMT sliding on low speed on the build site. Unfortunately this seems to be already an issue with floating point precision. The further from the origin of the world, the worse it gets. Also other glitching like the Ship being off center or sliding off its transport stand is likely also related to this as well as the SPMT wheels appearing to move off axis when driving for a while (this is just a visual bug though).
  • Control Panel glitching out when far away from the origin (launch mount).
  • The booster engines are not aligned properly and don't really match up with the control panel UI. This will be fixed with the booster overhaul soon.

Minor

  • When changing time of day to night by not using the handle but clicking somewhere on the slider sometimes you need to adjust it a second time for the night lighting to fully become active. Not sure, whether I do something wrong here or if the day-night cycle in HDRP is just pretty odd.
  • On laptop with touchpad scrolling the control panel might flip when changing its size. Also, mouse scrolling is a  bit different on Linux it seems.
  • Not really an issue, but currently there is no way to make a fixed connection between ship and booster when you stack it. It's just held in place by gravity. So if you go straight up, the ship will stay on top of the booster. Everything else, it will come off sooner or later ;)
  • The stabilizers at the bottom of the catcher arms don't really do much at the moment other than helping to reduce swinging a little bit. But it takes some time until it comes to a rest after a large swing.
  • Camera sometimes get stuck in the catcher or other things. Just move it around a bit.
  • During landing the camera might jump or get stuck in strange places when you move to certain positions.
  • Linux/Mac: clicking with the mouse rotates the player camera a tiny bit. Seems like some Unity bug, which hopefully will be fixed by them. Not really noticeable though unless you click frantically.
  • FPS counter: GPU frame time and hence FPS value might not be available on some devices.
  • The Starlink satellites might get stuck when trying to dispense at high accelerations as there is no actual pusher. They just start with given velocity.
  • Starship engine chill seems a little slow compared to booster.
  • it is currently not possible or at least not easily doable to have transparent stuff like water rendered behind transparent reflecting surfaces like the high bay windows. So water will disappear there when you are looking out from the top of the high bay.
  • VR: Main menu slider not sliding, other seem to work fine
  • VR: crashes game on disabling (at least for me)
  • Key bindings: Some of the identifiers might not be working properly. It might be in German initially, but change to English when you rebind it. Seems like some bug with Unity's "new" input system.
moved this topic to UNITY version: Feedback / Help / Bug reports

game just crashes and says: memory not read (sorry ashtorak i couldnt get a photo since it would let me open the screen film during the crash)

What operating system, processor and graphics card do you have?

When does it crash? Immediately after launching? Every time?

My laptop has a 64bit processor on a windows 10.  16GB RAM

sometimes I get as far as the main menu but when I open it the mouse arrow turns into a loading circle and says "starbase sim not responding "

hm, I need more info.  By default a log file is saved in your user folder, which should be accessible via the following address where you have to replace the username with your name:  C:\Users\username\AppData\LocalLow\Ashtorak\StarbaseSim

Please send this file to me or post the content here. 

Alternatively, you could create a shortcut of the StarbaseSim.exe and then in its properties add " -logFile log.txt" to the target like shown below. Then if you use this to start the game, it will generate a log file in the same directory called log.txt.

sorry for my extremly late reply, it opens, then crashes saying unity stopped running

Can you tell me what is the name of your processor and graphics chip, if there is a dedicated one?

I assume you are on the latest StarbaseSim version and it still happens?

i have the latest from Itch.io ill look at my graphics chip, however it does not appear to be the issue, as this pc can run detailed flight sim just fine

hm, I didn't get any reports about start up crashes for the latest version from others.

If you could send me the log file, maybe I can find something there. See the readme.txt  next to the .exe for info about the log file.

I followed the instructions from readme but I couldn't find LocalLow on the list of files😔

There is also the option to have a local log file: Make a shortcut of the exe (via right click context menu entry), then right click on the shortcut and open its properties. In the target setting field add <-logFile log.txt> at the end without the brackets. Now when you start it via the short cut it should create the file now in the same folder.

On MacOS Monterey 12.2.1

I get this error after unzipping. “StarbaseSim.app” is damaged and can’t be opened. You should move it to the Trash.

Did you check this thread? https://itch.io/t/1816448/mac-feedback-and-trouble-shooting

If it doesn't work, you can also try to use the Itch app

(1 edit)

Game crashes every boot before the unity logo even has time to fade in.
The only knowledge I have of reproducing is it started after I clicked 'reset' in key binds. All buttons stopped working and eventually the game crashed. When attempting to restart the game, the unity logo doesn't even fade in before it crashes. After wiping every known trace of the game from my pc and reinstalling via manual download and unzip or installing itch and downloading it via that, the crash still occurs.
The furthest I've gotten in installing the 1/13/2023 build which loaded the opening menu, but crashed again shortly after trying to put the game full screen
Also, no crash text file is created (at least not one I can find in all known directories), which is rather odd

5600x
3060ti
16GB RAM

Thank you for you time btw, the game is amazing :)

After creating a log file as detailed in a previous post, this is the result of the log file:

    Driver:          31.0.15.3699

Begin MonoManager ReloadAssembly

- Loaded All Assemblies, in  0.113 seconds

- Finished resetting the current domain, in  0.002 seconds

XRGeneral Settings awakening...

[XR] [1368] [16:13:41.303][Error  ] xrEnumerateInstanceExtensionProperties: XR_ERROR_RUNTIME_UNAVAILABLE

[XR] [1368] [16:13:41.303][Error  ] xrEnumerateInstanceExtensionProperties: XR_ERROR_RUNTIME_UNAVAILABLE

[XR] [1368] [16:13:41.303][Error  ] xrEnumerateInstanceExtensionProperties: XR_ERROR_RUNTIME_UNAVAILABLE

[XR] [1368] [16:13:41.303][Info   ] Available Layers: (0)

[XR] [1368] [16:13:41.303][Error  ] xrCreateInstance: XR_ERROR_RUNTIME_UNAVAILABLE

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/OculusXRPlugin

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/OculusXRPlugin.dll

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/OculusXRPlugin.dll

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/OculusXRPlugin

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/libOculusXRPlugin

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/libOculusXRPlugin.dll

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/libOculusXRPlugin.dll

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/libOculusXRPlugin

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/OculusXRPlugin

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/OculusXRPlugin.dll

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/OculusXRPlugin.dll

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/OculusXRPlugin

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/libOculusXRPlugin

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/libOculusXRPlugin.dll

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/libOculusXRPlugin.dll

Fallback handler could not load library E:/Users/#####/AppData/Roaming/itch/starbase-simulator/StarbaseSim_Data/MonoBleedingEdge/libOculusXRPlugin

<RI> Initializing input.

New input system (experimental) initialized

Using Windows.Gaming.Input

<RI> Input initialized.

<RI> Initialized touch support.

d3d12: swapchain present failed (887a0001).

d3d12: swapchain present failed (887a0001).

Thx! That's strange though, it seems to crash right away for some reason. 

Did you also reset / delete the registry settings?

  1. open registry editor by typing "regedit" into the Windows search bar
  2. in the editor go to this address: Computer\HKEY_CURRENT_USER\SOFTWARE\Ashtorak\StarbaseSim (you can copy paste it into the address bar)
  3. delete the StarbaseSim folder to reset all settings to default at game start (it will recreate the folder)

This screen shot was from another issue where I showed where the key binds are stored:

Maybe something in the registry settings changed somehow after resetting key binds as they are saved there by Unity.

(+1)

We have a successful load of the game. Can't wait to play again, thank you! :)