Technical problems - Revision history

AuraFB: /* Other online problems */

2022-03-17T13:54:35Z

AuraFB: /* Waiting on servers in Main Menu */

2021-10-11T14:53:41Z

Waiting on servers in Main Menu

← Older revision		Revision as of 17:53, 11 October 2021
Line 212:		Line 212:

	One workaround that has worked is to delete options.txt in %Appdata%/Starbase, and to verify game files by right clicking Starbase in the Steam library and going to Properties > Local Files > Verify Integrity of Game Files.		One workaround that has worked is to delete options.txt in %Appdata%/Starbase, and to verify game files by right clicking Starbase in the Steam library and going to Properties > Local Files > Verify Integrity of Game Files.

			Try also unplugging all USB devices, including controllers, before starting the game. There has been at least one case where having a PlayStation controller plugged in interfered with the loading process for some reason.

	= Server related issues =		= Server related issues =

JoelFB: /* General help */ detailed notes about game log and memory commits

2021-08-11T16:13:52Z

General help: detailed notes about game log and memory commits

← Older revision		Revision as of 19:13, 11 August 2021
Line 61:		Line 61:

	This can happen when the LODs are still loading. Relogging and moving out of the structure before the LODs have loaded in usually helps.		This can happen when the LODs are still loading. Relogging and moving out of the structure before the LODs have loaded in usually helps.

			== Looking into the ingame log and memory consumption ==

			Starbase writes game output to a log file, located in %APPDATA%\Starbase\log\ with the filename starbase.log (you can copypaste the folder location to File Explorer and it will automatically redirect you to e.g. C:\Users\yourusername\AppData\Roaming\Starbase\log ).

			Here is an example log of a successful startup of the game:

			<small><pre>
			2021-08-11 14:21:39
			INFO: - Changed from MemoryLogger to real one
			INFO: - Logging messages from MemoryLogger
			INFO: - Allocator initialized with 256 MB initial size
			INFO: ************************************************************************************************************* -
			INFO: Version - Starbase Early Access (Steam), build 545
			INFO: Version - Build date: 2021/08/10 15:21, revision: 491019
			INFO: ************************************************************************************************************* -
			INFO: - Running on Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (4 core / 8 thread CPU). Physical memory: 16716100 kB. Commit (total / peak / limit): 14201096 / 15733200 / 49221956 kB
			14:21:40.005 INFO: - Running in Steam branch:
			14:21:41.173 INFO: - Chosen Adapter: NVIDIA GeForce GTX 1060 6GB (6052 MB dedicated memory, 0 MB dedicated system memory, 8162MB shared system memory)
			14:22:01.858 INFO: - Started as 'username' userId: 7656XXXXXXXXXXXX netVersionHash: XXXXXXXXXX
			</pre></small>

			Some of the things here are self-explanatory, such as the CPU and GPU used. However, the memory needs further explanation. Here's our programmers' quick guide to how to read this:

			# ''Commit total'' means the amount of all the memory Windows has in use. That includes e.g. memory on the GPU in addition to what's used of the main physical memory ("RAM") and page file. Basically, if you open new programs or load more textures in Starbase, the total number goes up.
			# ''Commit peak'' just means the highest the total memory has reached.
			# ''Commit limit'' is more interesting. Windows wants to be able to swap out anything swappable at any time<sup>(1</sup>, including most of the GPU memory. This means in practice that the limit is pretty much page file<sup>(2</sup> size + main memory size (minus some unswappable memory).
			#* Some of that unswappable is just disk cache. If Windows runs low on memory, it will reduce the disk cache size and increase the page file size. Or just increase the page file size and push more stuff there.
			#* Due to the above, it is possible, perhaps unintuitively, that if the page file is too small (either limited by the user or Windows couldn't make it larger in time), there can be a case of free memory and out-of-memory at the same time.

			<small><sup>[1]</sup> There are good reasons for this, but most other operating systems work differently.
			<br /><sup>[2]</sup> Note that from the OS point of view, every .exe and .dll in use is also a page file. There's also a thing called "memory mapped file" that many programs use and that count as page file in this case.</small>

			Here are two examples analyzed:
			<small><pre>
			Running on Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (4 core / 8 thread CPU). Physical memory: 16716100 kB. Commit (total / peak / limit): 14201096 / 15733200 / 49221956 kB
			Chosen Adapter: NVIDIA GeForce GTX 1060 6GB (6052 MB dedicated memory, 0 MB dedicated system memory, 8162MB shared system memory)
			</pre></small>
			* In the above example, there's 16 GB of RAM and 6 GB on the GPU, but also a seemingly large page file being used as the limit is a whopping 49 gigabytes. Most likely there's a lot of programs and other stuff open in the background but Windows can service memory requests even if the physical memory is full. This can easily cause noticeable slowdowns however, and it would be generally recommended to not have the total committed memory be so near the physical memory amount - i.e. get more physical memory in this kind of a situation. Here's another example:

			<small><pre>
			Running on Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz (4 core / 4 thread CPU). Physical memory: 16724308 kB. Commit (total / peak / limit): 8076368 / 16861916 / 19214676 kB
			Chosen Adapter: NVIDIA GeForce GTX 1050 Ti (4018 MB dedicated memory, 0 MB dedicated system memory, 8166MB shared system memory)
			</pre></small>
			* In this example, the physical memory + GPU memory is about 20 GB total, but the limit is considerably less (about 19 GB). The page file is likely just a few gigabytes, but that's normal (it will grow if needed). This would be a normal, expected amount of memory used.

			As an extreme example, we can consider a system with 8 GB memory (RAM), no page file and a 11 GB modern GPU. One can't use more than 8 GB of that GPU memory, at best, and even that only in a case where no main memory is in use (which of course can't happen while Windows is running). This is why the page file size should not be limited. It needs to be there, even if only so Windows can count on pushing all that GPU memory to disk, if it feels like it.

	= Steam issues =		= Steam issues =

JoelFB: /* General startup troubleshooting steps */ set affinity and priority + major style overhaul

2021-08-10T23:52:31Z

General startup troubleshooting steps: set affinity and priority + major style overhaul

@@ Line 77: / Line 77: @@
 == General startup troubleshooting steps ==
-There can be multiple reasons for the game not starting up. Solutions are usually found as long as your system meets the [[System requirements]] (or close - generally a DirectX 11 graphics card is enough to launch the game, and this should include many integrated GPUs as well.
+There can be multiple reasons for the game not starting up. Solutions are usually found as long as your system meets the [[System requirements]] (or close - generally a DirectX 11 graphics card is enough to launch the game, and this should include many integrated GPUs as well).
 If the game does not start, follow these steps:
-* Reboot the computer
+{{quote4|'''<big style{{=}}"color:orange;">Reboot the computer</big>'''<br />Have you tried turning it off and on again? Generally helps with 50% of all computer issues and makes sure all the drivers etc. are being used correctly.}}
-* Close all software such as screensavers, Discord and other messaging programs, anything that you can
-** You could also disconnect your internet and use Steam in [https://support.steampowered.com/kb_article.php?ref=3160-agcb-2555 Offline Mode] to see if launching the game is in any way related to your internet connection
+{{quote4|'''<big style{{=}}"color:orange;">Close all other software</big>'''<br />Close all software such as screensavers, Discord and other messaging programs, anything that you can, including any mouse/keyboard/headphones helper programs and similar. You could also disconnect your internet and use Steam in [https://support.steampowered.com/kb_article.php?ref{{=}}3160-agcb-2555 Offline Mode] to see if launching the game is in any way related to your internet connection.}}
-* Try out a smaller resolution and run the game in Windowed mode (see [[Technical_options]])
-* Check the game's log folders in the Steam folder, i.e. SteamLibrary\steamapps\common\Starbase\log and open <code>log.txt</code> and see if there's anything strange at the end of this file (such as warnings or errors)
+{{quote4|'''<big style{{=}}"color:orange;">Tweak game resolution from config file</big>'''<br />Try out a smaller resolution and run the game in Windowed mode (see [[Technical_options]]).}}
-* Check the Windows Event Viewer application for checking for any crashes (see e.g. this [https://www.howtogeek.com/123646/htg-explains-what-the-windows-event-viewer-is-and-how-you-can-use-it/ How-To-Geek article] for more help)
-* Reinstall the game or verify the integrity of files through Steam
+{{quote4|'''<big style{{=}}"color:orange;">Check log files</big>'''<br />Check the game's log folders in the "appdata" folder, i.e. %APPDATA%\Starbase\log\ and open ''starbase.log'' in e.g. Notepad and see if there's anything strange at the end of this file (such as warnings or errors). For a successful launch it usually lists the graphics card and then the game nick and Steam ID of the user who starts the game.}}
 === Further things to test ===
 * If you have both an integrated and a dedicated/discrete graphics card (such as a laptop with a discrete GPU for gaming, or a desktop computer with a modern CPU that also has an integrated GPU), you should try running the game on the _other_ graphics card. You can usually set this on a per-application basis in the main drivers or software (i.e. NVIDIA Control Panel or AMD Radeon Settings/Catalyst Control Center).
-* Sometimes audio settings can mess things up in rare cases, and changing some of the settings helps:
+If nothing works, we recommend a refund on Steam, or looking into [https://play.geforcenow.com/mall/#/layout/games/gameSectionGrid?search=true GeForce NOW by NVIDIA] which is a cloud-based streaming service that uses your Steam account and in most territories works with Starbase.
 == Game screen is white ==

JoelFB: servers disconnected issue

2021-08-09T00:19:06Z

servers disconnected issue

← Older revision		Revision as of 03:19, 9 August 2021
Line 117:		Line 117:

	One workaround that has worked is to delete options.txt in %Appdata%/Starbase, and to verify game files by right clicking Starbase in the Steam library and going to Properties > Local Files > Verify Integrity of Game Files.		One workaround that has worked is to delete options.txt in %Appdata%/Starbase, and to verify game files by right clicking Starbase in the Steam library and going to Properties > Local Files > Verify Integrity of Game Files.

			= Server related issues =

			== Server Disconnected ==

			Some users are experiencing disconnecting servers, i.e. the top-right corner is full of "Server disconnect: xxxx" messages. There's a couple of things to try to fix this:

			* Steam Settings -> In-Game -> Steam Networking, set to Never
			* Steam Settings -> In-Game -> Browse server pings, set to 250 instead of Automatic/5000
			* Run the game as administrator

			These have helped multiple people (but not everybody). There's been suggestions that the Steam ping setting may lead to "ping spikes", so if you have the networking knowhow to check for this, it may lead to solutions. If you find a working solution, please send a Discord DM to JoelFB#7362.

	= Crashes =		= Crashes =

JoelFB: /* Startup problems */ some initial troubleshooting steps

2021-08-08T22:45:20Z

Startup problems: some initial troubleshooting steps

@@ Line 74: / Line 74: @@
 = Startup problems =
 == Game screen is white ==
@@ Line 95: / Line 117: @@
 One workaround that has worked is to delete options.txt in %Appdata%/Starbase, and to verify game files by right clicking Starbase in the Steam library and going to Properties > Local Files > Verify Integrity of Game Files.
 = Crashes =

JoelFB: added template

2021-08-05T21:41:50Z

added template

← Older revision		Revision as of 00:41, 6 August 2021
Line 1:		Line 1:
	{{Official_Info}}		{{Official_Info}}
			{{Starbase_Support}}
	__TOC__		__TOC__

AuraFB: /* Private servers? */

2021-07-27T13:13:59Z

Private servers?

← Older revision		Revision as of 16:13, 27 July 2021
Line 34:		Line 34:
	Not planned. Starbase uses a peer-to-peer hybrid tech with some server-side things (for security and matchmaking and such), but it's mostly peer-to-peer so there are no traditional servers and there is one persistent world. The way it works is basically that every player hosts their character/their ship, and physics are calculated at the player's side instead of servers. It's a pretty complicated structure, but peer-to-peer handles all the simulation.		Not planned. Starbase uses a peer-to-peer hybrid tech with some server-side things (for security and matchmaking and such), but it's mostly peer-to-peer so there are no traditional servers and there is one persistent world. The way it works is basically that every player hosts their character/their ship, and physics are calculated at the player's side instead of servers. It's a pretty complicated structure, but peer-to-peer handles all the simulation.

	===Can I play alone?===		==Can I play alone?==

	All features of Starbase are playable alone, but as it is an MMO, progression alone will be slower than it would be in a group. Enormous battleships also need a crew and aren't designed to be manned by a single Endo. If you're a solo player, we recommend smaller ships and investing in good gear. Leaving your valued possessions in the safety of the safezone and only bringing what you absolutely need with you is also recommended.		All features of Starbase are playable alone, but as it is an MMO, progression alone will be slower than it would be in a group. Enormous battleships also need a crew and aren't designed to be manned by a single Endo. If you're a solo player, we recommend smaller ships and investing in good gear. Leaving your valued possessions in the safety of the safezone and only bringing what you absolutely need with you is also recommended.

AuraFB: /* General help */

2021-07-27T13:13:44Z

General help

@@ Line 10: / Line 10: @@
 Send your bug reports directly in-game via the Feedback Tool, which can be accessed at any time with F1. You can find help with most common technical issues on this Wiki page.
-=General help=
+= General questions =
 ==Basic troubleshooting tips==

AuraFB: /* Crash: GPU error detected */

2021-07-27T13:09:19Z

Crash: GPU error detected

← Older revision		Revision as of 16:09, 27 July 2021
Line 156:		Line 156:
	Looks something like this.		Looks something like this.

	If you are using an NVidia graphics card, make sure to update your GPU drivers. There was a driver issue affecting at least the NVidia 16XX and 20XX (possibly even 30XX) graphics cards, causing this error to pop up at certain points during Starbase Alpha. Updating to driver version 466.47 (or newer) fixes it. You can find more info [Technical_help#Graphics_driver_issue_April-May_2021\|here].		If you are using an NVidia graphics card, make sure to update your GPU drivers. There was a driver issue affecting at least the NVidia 16XX and 20XX (possibly even 30XX) graphics cards, causing this error to pop up at certain points during Starbase Alpha. Updating to driver version 466.47 (or newer) fixes it. You can find more info [[Technical_help#Graphics_driver_issue_April-May_2021\|here]].

	There can be many other causes to this error as well, but one likely cause is that your GPU is too old. For example, the GTX 9800 is too told and does not support Direct3D version 11, which Starbase needs to run. [https://en.wikipedia.org/wiki/GeForce_9_series#GeForce_9800_GTX This GPU only supports Direct3D up to version 10, more info here].		There can be many other causes to this error as well, but one likely cause is that your GPU is too old. For example, the GTX 9800 is too told and does not support Direct3D version 11, which Starbase needs to run. [https://en.wikipedia.org/wiki/GeForce_9_series#GeForce_9800_GTX This GPU only supports Direct3D up to version 10, more info here].

← Older revision		Revision as of 16:54, 17 March 2022
Line 358:		Line 358:
	* Add Starbase and Steam to your security programs’ (anti-virus, firewall, etc.) exceptions		* Add Starbase and Steam to your security programs’ (anti-virus, firewall, etc.) exceptions
	* Check that correct Steam ports are open: https://support.steampowered.com/kb_article.php?ref=8571-GLVN-8711		* Check that correct Steam ports are open: https://support.steampowered.com/kb_article.php?ref=8571-GLVN-8711
			* Check that you're not using Family Sharing. Family Sharing is disabled for Starbase.

	= Performance issues =		= Performance issues =