Julian wrote:Source of the post If an addon .pak contains a locale\eng-db.cfg file to store "Franchise" attributes, after Steam updates Space Engine the addon's eng-db.cfg is no longer loaded, unless it's edited so that the file modification date becomes newer than that of the Space Engine app.
A-L-E-X wrote:Source of the post I am getting this console error with Ceres even though I have never been there, how can it be fixed?
A-L-E-X wrote:Schübatamann wrote:after build 0.990.35.1660 all terrain in procedual planets became black or dark grey, i can still see terrain details but is dark and completally dessaturated.
clouds, gas giants and solar system object are still nice
Really? I love 1660. I can make all the colors pop by boosting saturation, contrast and sharpness to maximum! I keep saturation illuminator (whatever that is) on auto!
Schübatamann wrote:Source of the post for example the location "Terra with life in LMC" looks like this to me
JackDole wrote:That is completely normal.
SpaceEngine can only detect on the date which version of two scripts of the same name should be used.
Julian wrote:Source of the post Yes, but it'll become inconvenient for distributing .paks that include locale\eng-db.cfg. Either SE needs to make an exception for handling the modification date of eng-db.cfg, or should addons use config\usr-eng-db.cfg instead?
JackDole wrote:Schübatamann wrote:Source of the post for example the location "Terra with life in LMC" looks like this to me
Post your 'se.log'. It is in the 'system' folder of SpaceEngine.
Schübatamann wrote:Source of the post here is it
JackDole wrote:Schübatamann wrote:Source of the post here is it
Remove 'rodrigosmod.pak'. This does not work with SE 0.990 and is most likely the reason that your planets are black.
By the way, you should also remove all addons that have not been explicitly made for SE 0.990!