No New Kerbals To Recruit

[MacJSteele]

Hello, I am playing a modded save with Galileos Planet Pack and several other mods. For unknown reasons no new kerbals are available to be recruited despite the astronaut complex being upgraded to its highest level.  It has been like this sense the start of the game, it is only now though that it has become an issue. Any idea what could be causing the issue?

Note the time difference, top left, there should be new kerbals available.

https://www.dropbox.com/s/xtlh9hou2fsojit/Player.log?dl=0

Here is the player.log along with the mod list.

KSP: 1.12.3 (Win64) - Unity: 2019.4.18f1 - OS: Windows 10  (10.0.0) 64bit
000_AT_Utils - 1.10.1
ClickThroughBlocker - 2.1.10.18
Filter Extensions - 3.2.7
Harmony - 2.2.1
Toolbar - 1.8.0.8
ToolbarControl - 0.1.9.8
B9 Animation Modules - 1.7
B9 Part Switch - 2.20
Chatterer - 0.9.99.2788
Community Category Kit - 0.1.0.112
Community Resource Pack - 112.0.1
CommunityTechTree - 3.4.4
ConfigurableContainers - 2.6.2.1
Contract Configurator - 2.2
Contract Pack: Exploration Plus - 2.0.1
Contract Pack: Field Research - 1.2.2
Contract Pack: Kerbal Academy - 1.1.10
Contract Pack: Bases and Stations - 3.7.3
Contract Pack: Tourism Plus - 1.5.2
CryoEngines - 2.0.6
CryoTanks - 1.6.5
DeployableEngines - 1.3.1
Distant Object Enhancement (DOE) /L - 2.1.1.9
DynamicBatteryStorage - 2.2.5
Easy Vessel Switch - 2.3.7852.41352
Environmental Visual Enhancements - Redux - 1.11.7.1
GalileosPlanetPack - 1.6.8
HeatControl - 0.6.1
HideEmptyTechTreeNodes - 1.3.2
JanitorsCloset - 0.3.7.8
RasterPropMonitor - 0.31.7
KAS - 1.12.8285.34332
KerbalAtomics - 1.3.3
Kerbal Engineer Redux - 1.1.9
Keridian Dynamics (KDVA) - 0.8.99.2
Kerbal Inventory System - 1.29.8039.40483
Kopernicus - 1.12.1.139
KSP-AVC Plugin - 1.4.1.9
MarkIVSystem - 3.2
ModularFlightIntegrator - 1.2.10
Docking Port Alignment Indicator - 6.10
NearFutureAeronautics - 2.1.1
NearFutureConstruction - 1.3.1
NearFutureElectrical - 1.2.3
NearFutureExploration - 1.1.2
NearFutureLaunchVehicles - 2.2
NearFutureProps - 0.7.1
NearFuturePropulsion - 1.3.5
NearFutureSolar - 1.3.2
NearFutureSpacecraft - 1.4.3
PlanetShine - 0.2.6.6
Kerbal Inventory System - No Fun (QBKN) - 0.1.11
ReStock - 1.4.3
ReStockPlus - 1.4.3
SCANsat - 1.20.4
ScienceAlert - 1.9.10.1
SpaceDust - 0.4.4
ButtonManager - 1.0.1.1
SpaceTuxLibrary - 0.0.8.4
VesselModuleSave - 1.0.1.2
StageRecovery - 1.9.5.7
StationPartsExpansionRedux - 2.0.10
SystemHeat - 0.5.6
Trajectories - 2.4.3
Transfer Window Planner - 1.8
Universal Storage 2 - 4.0.0.7
Waterfall - 0.9
WaterfallRestock - 0.2.3
Waypoint Manager - 2.8.3.4
Kerbal Actuators - 1.8.5
ZeroMiniAVC - 1.1.2.4

[jimmymcgoochie]

If you just need more Kerbals, try this: activate the debug menu (alt+f12) then open the Kerbals tab, go to Create and make some new ones; you can choose all their stats and even their names and they'll automatically be added to your roster of active Kerbals, you can deduct some funds in the cheats tab if you like.

As for the root cause, this exception in the logs is probably relevant, but it's also pretty weird because KerbalRenamer isn't on your mod list:

NullReferenceException: Object reference not set to an instance of an object

  at KerbalRenamer.VeteranRenamer.Start () [0x00061] in <c0228513e9ce49ab8d3eca95c04c6e55>:0

Steam breaks modded KSP a lot, the best way to avoid this is to make a copy of KSP that's outside the Steam folders and put your mods in that copy:

1.       Right click KSP in Steam library > browse local files.

2.       Copy KSP/saves/<your save name> and paste that on the desktop.

3.       If you used CKAN to install your mods (and you should!), click File > export modpack and save that to your desktop too. Screenshot your GameData folder with mods installed (even if you use CKAN) so you can check that you’ve reinstalled them all later.

4.       Uninstall all mods from KSP.

5.       Right click KSP in Steam library > properties, disable Steam cloud.

6.       Completely uninstall KSP through Steam.

7.       Reinstall KSP through Steam, right click > Properties > local files > verify integrity of game files. If you want to play a version other than the current release (1.12.3), pick that version in the Betas tab and verify the files once Steam has installed that version.

8.       Run KSP and make sure it loads properly without mods.

9.       Browse local files again, then go up one level (to Steam/steamapps/common) and copy the Kerbal Space Program directory, then paste it where you want to keep it- make sure it’s outside Steam’s folders so it can’t meddle with it in future.

10.   Rename the KSP folder so you know what mods you’re using in it (e.g. 1.10.1 RO/RP-1, 1.12.3 JNSQ), then add this new copy to CKAN and use the modpack created in step 3 to reinstall all your mods; or reinstall them by hand if you don’t use CKAN. Double-check that all files and folders you had in GameData before uninstalling/reinstalling everything are there again, if not then you’re probably missing some mods.

11.   Move your saves from your desktop into your new KSP copy’s saves folder, run KSP, load save. A warning about vessels having missing parts is usually because a mod is missing or wasn’t installed correctly.

If there's still an issue, try (re)installing Kerbal Renamer?

[Ravlain]

Probably better off removing KerbalRenamer, it seems to cause assorted problems with other mods , and I think @OhioBobis dropping it from the pending update of GPP for that reason. Just delete the KerbalRenamer folder from  under the GPP folder.

Edited October 5, 2022 by Ravlain
added detail