Facilities are fully upgraded on a new career

[Kerbrud]

Hi, all!

I'm on KSP 0.90, x86, Windooze

Well, this is seriously annoying; I've just started a new career, and all buildings are fully upgraded! I've tried the fix where you edit the persistent-file as to set all values in ScenarioUpgradeableFacilities to 0. What happens, is that after first saving the persistent-file, closing the document, and loading the career, buildings are still fully upgraded, and all values are re-set to 1 in the persistent-file.

0.90 offers wonderful new features for me, coming directly from 0.24.2, but this really ruins the game for me.

Here's the content of my GameData-folder:

000_Toolbar

AnimatedDecouplers

BackgroundProcessing-0.4.0.1.BTSM.dll

BoulderCo

BTSM

Chatterer

CoherentContracts

ContractConfigurator

ContractPacks

Contracts Window

CustomAsteroids

DeadlyReentry

Diazo

DistantObject

FinalFrontier.dat

Hyomoto

JSI

KerbalEngineer

KerbQuake

KittopiaSpace

ksp-advanced-flybywire

KSP-AVC

KWRocketry

MechJeb2

mods.txt

ModuleManager.2.5.9.dll

ModuleManager.ConfigCache

ModuleManager.ConfigSHA

NASAmission

Nereid

RCSBuildAid

RcsSounds

RealChute

RemoteTech

SCANsat

SDHI

Squad

StageRecovery

SurfaceLights

TextureReplacer

toolbar-settings.dat

TweakScale

VesselView

Upon startup, no erroneous versions show up.

Please help!=)

Edited March 10, 2015 by Kerbrud
Added information

[Superfluous J]

32 bit or 64 bit? There's a known bug in 64 bit where the buildings look upgraded and can't be upgraded, but they're at the lowest level.

As far as I know there is no fix. It's just one of the many ways 64 bit is borked.

[Kerbrud]

Hi, thanks for replying! Like I said at the top, I'm running 32-bit (x86).

[SpaceExplorer]

I would suggest that you open your regular career game, save it, close KSP, then go to the persistence file, edit it, and save. After you have completed that, I would suggest that you delete the ModuleManager.ConfigCache and ModuleManager.ConfigSHA files, then boot up KSP. If that does not work, and you are running Steam, I would verify the integrity of the game cache. Or if you are not running with Steam, to uninstall, and reinstall the game. It could have been a problem converting from 0.24.2 to 0.90 (although this is very unlikely). I hope this helps! I have personally never encountered this problem before.....

Edited March 10, 2015 by SpaceExplorer
Grammar and Spelling

[Kerbrud]

I would suggest that you open your regular career game, save it, close KSP, then go to the persistence file, edit it, and save. After you have completed that, I would suggest that you delete the ModuleManager.ConfigCache and ModuleManager.ConfigSHA files, then boot up KSP. If that does not work, and you are running Steam, I would verify the integrity of the game cache. Or if you are not running with Steam, to uninstall, and reinstall the game. It could have been a problem converting from 0.24.2 to 0.90 (although this is very unlikely). I hope this helps! I have personally never encountered this problem before.....

The first suggestion seems to be a good way to do it - I didn't see those two files, actually. Cache-files can make a lot of fuss when one is facing config-trouble!

What's weird, is that although I installed KSP via Steam, I don't run it through it - I use ksp.exe manually. Also, in case 0.90 was borked altogether, I moved all the 0.24.2 to a different folder, making it playable still. Therefore, there's no conversion, as this install of 0.90 was practically a clean install. I may try reinstalling it, and from there install one mod at a time (which is hell, I imagine) until it breaks, if applicable.

Thanks for your suggestions!

[Kerbrud]

I think I found the culprit!

As it alters things that has to do with upgrades, I suspected that Better Than Starting Manned was the reason why the buildings start off being fully developed. First, I got rid of everything in GameData, except for the Squad and NASA folder. I then installed BTSM, MM and Toolbar only. In the first test, I started a new career, and everything worked as it's supposed to. In the second test, it broke again.

The error COULD be due to MM as well, I might add.

I noticed a few other things as well (here, "modded" means that BTSM and MM ONLY are installed)

1: Difficulty settings in vanilla had more options, such as starting funds etc - when modded, these were not present.

2: The gizmos worked in vanilla - not when modded

3: With ALL mods in the OP installed, RemoteTech worked, but the Stayputnik had no omni antenna capabilities.

I hate upgrading KSP.

[Thnd3r]

The BTSM mod doesn't support upgrading the buildings. It builds it into the tech tree instead.