I am running into a 'crash to desktop' issue when using only the sigma mods.
To reproduce, start with a clean KSP install, and only install sigma mod(s) (any variant, such as Texture, Heads, SkyBox, etc). There is no need to actually install any other mods that uses sigma (like GPP).
Next, load a new game (no need to adjust any KSP settings), and aggressively switch between the facilities (@ ~.5 seconds). I've found the more sigma mods I use (Texture, Descriptions, Heads, Suites, etc all of them) the quicker the crash occurs.
It feels as if, there is some sort of time delay that needs to occur before 'sigma' replaces 'stuff' as I am registering a hard fault? But thats just my poor debugging attempts.
[Edit]: This issue is more prominent the more mods you have. Meaning, the more mods one has, the less aggressive one needs to be in order to trigger the issue (full seconds between facility switching).
I am running into a 'crash to desktop' issue when using only the sigma mods.
To reproduce, start with a clean KSP install, and only install sigma mod(s) (any variant, such as Texture, Heads, SkyBox, etc). There is no need to actually install any other mods that uses sigma (like GPP).
Next, load a new game (no need to adjust any KSP settings), and aggressively switch between the facilities (@ ~.5 seconds). I've found the more sigma mods I use (Texture, Descriptions, Heads, Suites, etc all of them) the quicker the crash occurs.
It feels as if, there is some sort of time delay that needs to occur before 'sigma' replaces 'stuff' as I am registering a hard fault? But thats just my poor debugging attempts.
[Edit]: This issue is more prominent the more mods you have. Meaning, the more mods one has, the less aggressive one needs to be in order to trigger the issue (full seconds between facility switching).
Video link: https://drive.google.com/open?id=1pagM1Pv4WTT3YSK3s66pTqZdehOl2lNx output_log.txt error.log