Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

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.