#Starsector console commands not working mod#
#Starsector console commands not working drivers#
#Starsector console commands not working driver#
#Starsector console commands not working full#
#Starsector console commands not working mods#

If that isn't applicable or doesn't work, try updating your graphics drivers and restarting.Ģ. Ensure that your computer's primary graphics device is being used by Starsector.

#Starsector console commands not working driver#

Intermittent glitchy / artifacted graphics in combat!Īs above, this problem is caused by incompatibility between your graphics driver and GraphicsLib. If you still have problems at this point, then GraphicsLib is not at fault.

#Starsector console commands not working mods#

This completely disables all GraphicsLib functionality, but remains compatible with mods that require GraphicsLib. Disabling this will reduce the quality of lighting.ġ0. Material maps use a lot of video memory, which could cause issues on some graphics drivers. Disabling this will noticeably reduce the quality of lighting.ĩ. Normal maps use a lot of video memory, which could cause issues on some graphics drivers. Disabling this will slightly reduce the quality of lighting.Ĩ. Surface maps use a lot of video memory, which could cause issues on some graphics drivers. This disables the HDR bloom effect in the lighting engine, which could potentially improve performance.ħ. This disables distortion effects, as some users find that their graphics device does not support it.Ħ.

The large ripple uses a lot of video memory, which could cause issues on some graphics drivers.Ĥ. This will disable post-processing effects, which are fortunately not used in many situations.ģ. After each step, check to see if the problem is gone:Ģ.

The following is a step-by-step guide to get GraphicsLib to work on your system by editing the GRAPHICS_OPTIONS.ini file within the GraphicsLib folder in a program like Notepad++. If that does not work, then you will need to change the GraphicsLib configuration settings until the artifacts go away. If that isn't applicable or doesn't work, try updating your graphics drivers and restarting. The exact method to do this depends on laptop manufacturer, but ultimately you should set Starsector.exe and also java.exe in the jre/bin folder to use your primary graphics device (typically, a dedicated graphics card instead of the integrated chipset on your CPU). First, if you are using a laptop, ensure that your computer's primary graphics device is being used by Starsector. This problem is caused by incompatibility between your graphics driver and GraphicsLib. Make sure that Starsector.exe and java.exe are set to not force vsync.Ĭonstant glitchy / artifacted graphics in the menu! This is usually caused by your graphics driver forcing vsync on for Starsector, which will cause the loading screen to take an extremely long time (a half an hour or more). This disables distortion effects, which use some video memory.Ĩ. This disables the HDR bloom effect in the lighting engine, which uses some video memory.ħ. Disabling this will reduce the quality of lighting.Ħ. Disabling this will noticeably reduce the quality of lighting.ĥ. Disabling this will slightly reduce the quality of lighting.Ĥ. The 64-bit buffer option uses some video memory.ģ. The large ripple uses a lot of video memory.Ģ. After each step, check to see if the problem is gone:ġ. The culprit, in this case, is GraphicsLib. If you are not running that many mods, or if the previous step doesn't fix the problem, this could indicate that your graphics device cannot handle the number of textures being loaded into the game. Do this by increasing the -xms and -xmx values in 'vmparams'. If you are running a huge number of mods, this could indicate that you need to allocate more memory to Starsector.

#Starsector console commands not working full#

Out-of-memory / heap full crash! (OutOfMemoryError)

#Starsector console commands not working mod#

Occasionally, this can also indicate that a mod is out-of-date with the current version of Starsector, or that your own Starsector version is out-of-date. This crash is usually due to having a prerequisite mod disabled, such as LazyLib, GraphicsLib, or TwigLib. Rarely, other issues can cause the launcher to not appear for more information about your problem, run Starsector.exe from the command line.Īrray-index crash! (ArrayIndexOutOfBoundsException) If this is the case, you should switch the JVM in that folder to a 64-bit JVM. If the -xms or -xmx values are over 1024m, this could indicate that the 'jre' folder contains a 32-bit JVM. Check to make sure that the 'jre' folder is present and that the 'vmparams' settings are valid. This usually indicates that Java is not configured correctly. Starsector won't launch to the main menu. Please suggest additional items or sections for this guide, in the comments. Have a problem with modded Starsector? Look no further!