If you look at the latest SH3Cmdr changes, you'll see that there were no changes made that could result in this error. Indeed SH3Cmdr has never "tinkered" with any sub compartment.
Unless, it is somehow related to the Thermal Layers addition... So, can you pls, as a test, rename the SH3Cmdr "Randomised events.cfg" file to anything else and try again?
BTW, I assume that you have not installed Hemisent's Sabotage Mod nor have you made any other changes to the SH3Cmdr cfg files? If so, I'd remove those first before testing again.
And, what other mods do you have installed? I'd be curious if there was a common theme (it's how we identified the repeating patrol grid problem which had been attributed as an SH3Cmdr bug and which turned out to be nothing related to SH3Cmdr).
What happens if you just load the game the "conventional" way, and not via SH3Cmdr?
@Herr Karl: The "not enough crew" message is definitely not SH3Cmdr related. What mods are you running?
Quote:
|
Originally Posted by Herr Karl
Funny that we are having strange or irrelevant messages about the same compartment. I'm sure JS will know whats up.
|
Well, no, apart from assuring users that the stock SH3Cmdr makes *no* adjustments to this aspect of the game. Because of the way SH3Cmdr works, it has quite often had the finger pointed at it for problems which in the end are totally unrelated to it. I suspect that, unless the problem
is somehow related to Hemisent's Thermal Layers addition (and I think that is grasping at straws), the problem rests with another one of the recently released mods that *does* tinker with the sub compartments, hence the need to know what mods affected users are running.