- User Since
- Aug 23 2015, 7:07 PM (380 w, 30 m)
Nov 18 2020
End users resolve this by installing libgconf-2-4, but only experienced Linux users would know they need to do this. If you are using gconfig to store configuration information, you can just use a static file or directory "$HOME/.starmade" to store configuration info. This is the more traditional way of storing application specific configuration data on Unix systems, and works just as well on Mac OS X (it would also be a great place to store game session independent blueprints).
Apr 5 2018
Mar 29 2018
Oct 18 2017
Oct 17 2017
Oct 15 2017
Jan 28 2016
I'm still seeing this. The effect seems to be linked to when the blocks fade in and out to bright white when entering build mode. It doesn't appear that the blocks are allowed to fade completely back to normal before the blocks are lightened again. Lets just remove this flash completely and see what happens. I doubt anyone would notice this flash effect disappearing anyway as it's so brief.
Sep 2 2015
Reading over the commends on here, it looks like it would be useful for me to point out that my CPU doesn't have an on-chip GPU--just 8 processing cores of AMDx64 goodness. so there's only one video card my OS has to contend with, there's no switching.
After disabling shadows I haven't seen the issue come back. Interesting thing though: after exiting the client and re-connecting last night, I still had the same haze as shown in the second picture. I suspect something is being set in the video card which is not being cleared out later.
I did some more testing.. This first image was taken soon after logging into my local server.
Yeah I've noticed this too on Linux with my nVidia 960 GT. It seems like everything now has a white haze in astronaut mode. Areas that should be totally black have generalized illumination. When the flashlight is activated, this haze disappears.
I've seen this happen to. The other problem encountered when undocking a ship is that it can be impossible to activate the core. Instead of activating the core, the anchor is selected (which does nothing, of course). If the anchor block activation area was made smaller than all other blocks, then this would resolve the issue. Or, better still, make the anchor block an inactive/invisible entity unless in flight or build mode.
Looks like this only happens on this ice world where gravity is a little wonky. Randomly when walking on the planet I'll be outside of the effect of gravity and be able to fly around until I cross over to the next plate.