Kerbin Side Remastered [1.0.1] [1.7.3]

[Generic_Timothy]

For those who can't launch the game with this mod, I might have found a solution. Rolling Kerbal Konstructs back to version 1.8.4.0 seems to solve the problem of the game not responding on the final loading screen.

From what I can gather with my limited technical knowledge, it seems that KK of higher versions changes something that breaks Kerbin Side Remastered.
 

[Elite_937]

On 9/5/2024 at 4:06 PM, Generic_Timothy said:

For those who can't launch the game with this mod, I might have found a solution. Rolling Kerbal Konstructs back to version 1.8.4.0 seems to solve the problem of the game not responding on the final loading screen.

From what I can gather with my limited technical knowledge, it seems that KK of higher versions changes something that breaks Kerbin Side Remastered.
 

By the gods you fixed it. I thought i had summoned the holy Eskandere to fix it, but i guess you can. Thank you so very much. 

[theogameren]

Hey, can you make a static pack for those that don't want more launch sites?

[Nightside]

2 hours ago, theogameren said:

Hey, can you make a static pack for those that don't want more launch sites?

You could  just delete the launch sites and keep the building models if you want to create your own.

[Hank Kerman]

On 9/5/2024 at 10:01 AM, Jenyam said:

Hopefully Eskandare didn't abandon the Sea Launch platform

Where did you get that??

[Jenyam]

On 9/28/2024 at 3:17 AM, Hank Kerman said:

Where did you get that??

It was in the original kerbinside mod in 2014

[Elite_937]

Alright, new problem. Doesn’t launch with KSR no matter what i do. Help?

[Elite_937]

Its been a few months, and i still have no answer. Kerbinside remastered doesn't work no matter what i try, on 2 different computers. no clue what's wrong, and want the assets desperately. no previous technique works. My only guess is someone, somewhere, has a working copy. I have no other options, and just in case. I'll summon him. 
@Eskandare. 

Edited December 31, 2024 by Elite_937

[Manul]

11 hours ago, Elite_937 said:

Its been a few months, and i still have no answer.

How is anyone supposed to help you if you do not provide any information? And KSR works just fine for everyone else.

[Elite_937]

On 12/31/2024 at 3:37 AM, Manul said:

How is anyone supposed to help you if you do not provide any information? And KSR works just fine for everyone else.

Alright, what do you need and where is it? I know it’s probably obvious but I continue to have the intellect of a rat.

Quote

 

How is anyone supposed to help you if you do not provide any information? And KSR works just fine for everyone else.

 

I can get any text or log file or anything. 

Edited January 1 by Elite_937

[Drew Kerman]

On 1/1/2025 at 3:43 AM, Elite_937 said:

Alright, what do you need and where is it?

 

[Elite_937]

Alright. I know, i procrastinated on this issue, but i got the link. all mods involved are up to date (pretty sure), refollowed mod instructions (best i could, i am pretty stupid),  and my stock KSP runs fine. i dont think anyone else has this issue, and it happens on 2 seperate computers. the issue is that KSR worked fine for a bit, then stopped working, then the guy that reccomended the downgrading the KSR install got it to work, then after 2 more game launches, stopped working. here is my player.log, and if you need any more info i can get it. it may be a me being dumb issue, and i'm ok with that. 

https://www.dropbox.com/scl/fi/troxtu7d7z3atfhstvqzt/Player.log?rlkey=3805sidwfpah48znsz6q3ff8q&st=k7mye108&dl=0

[Elite_937]

On 1/17/2025 at 2:33 AM, Elite_937 said:

Alright. I know, i procrastinated on this issue, but i got the link. all mods involved are up to date (pretty sure), refollowed mod instructions (best i could, i am pretty stupid),  and my stock KSP runs fine. i dont think anyone else has this issue, and it happens on 2 seperate computers. the issue is that KSR worked fine for a bit, then stopped working, then the guy that reccomended the downgrading the KSR install got it to work, then after 2 more game launches, stopped working. here is my player.log, and if you need any more info i can get it. it may be a me being dumb issue, and i'm ok with that. 

https://www.dropbox.com/scl/fi/troxtu7d7z3atfhstvqzt/Player.log?rlkey=3805sidwfpah48znsz6q3ff8q&st=k7mye108&dl=0

Again, i reply, nothing happens. I mean, it’s not a dealbreaker, still need help. There’s probably something wrong im doing somewhere, and i’m sorry about that, i’m somewhere between new at ksp and just plain dumb. Anyways, updates?

[ColdJ]

3 hours ago, Elite_937 said:

Again, i reply, nothing happens. I mean, it’s not a dealbreaker, still need help. There’s probably something wrong im doing somewhere, and i’m sorry about that, i’m somewhere between new at ksp and just plain dumb. Anyways, updates?

With all that has gone on last year, the maintainers may not be around any more. I will ping @Lisias who is good at reading logs. If they get a free moment they may be able to pin point the issue.

[Lisias]

5 hours ago, Elite_937 said:

Again, i reply, nothing happens. I mean, it’s not a dealbreaker, still need help. There’s probably something wrong im doing somewhere, and i’m sorry about that, i’m somewhere between new at ksp and just plain dumb. Anyways, updates?

How much memory do you rig have? Apparently, you are running out of memory. The one "saying uncle" on your log is the JIT!!!!

0x0000023C50212F79 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.GameObject:Internal_AddComponentWithType (UnityEngine.GameObject,System.Type)
0x0000023C50212EB3 (Mono JIT Code) UnityEngine.GameObject:AddComponent (System.Type)
0x0000023C56F19C13 (Mono JIT Code) AddonLoader:StartAddon (AssemblyLoader/LoadedAssembly,System.Type,KSPAddon,KSPAddon/Startup)
0x0000023C52377E53 (Mono JIT Code) AddonLoader:StartAddons (KSPAddon/Startup)
0x0000023C52377813 (Mono JIT Code) AddonLoader:OnLevelLoaded (GameScenes)
0x0000023C523777A3 (Mono JIT Code) AddonLoader:OnSceneLoaded (UnityEngine.SceneManagement.Scene,UnityEngine.SceneManagement.LoadSceneMode)
0x0000023C523757F1 (Mono JIT Code) (wrapper delegate-invoke) UnityEngine.Events.UnityAction`2<UnityEngine.SceneManagement.Scene, UnityEngine.SceneManagement.LoadSceneMod
e>:invoke_void_T0_T1 (UnityEngine.SceneManagement.Scene,UnityEngine.SceneManagement.LoadSceneMode)
0x0000023C523755D3 (Mono JIT Code) UnityEngine.SceneManagement.SceneManager:Internal_SceneLoaded (UnityEngine.SceneManagement.Scene,UnityEngine.SceneManagement.LoadScene
Mode)
0x0000023C52375679 (Mono JIT Code) (wrapper runtime-invoke) <Module>:runtime_invoke_void_Scene_int (object,intptr,intptr,intptr)
0x00007FFE133FD6D0 (mono-2.0-bdwgc) mono_get_runtime_build_info
0x00007FFE13382932 (mono-2.0-bdwgc) mono_perfcounters_init
0x00007FFE1338B98F (mono-2.0-bdwgc) mono_runtime_invoke
0x00007FFDDB019A6D (UnityPlayer) UnityMain
<yada yada yada>
0x00007FFDDAEDD5BC (UnityPlayer) UnityMain
  ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFDDAC9272E)
0x00007FFDDAC9272E (UnityPlayer) (function-name not available)

This apparently happened after entering the Main Menu (or slightly before it being shown), I'm right?

[HighLogic]: =========================== Scene Change : From LOADING to MAINMENU =====================

Well... I have two workaronds for you, assuming of course that this is the problem (lack of useable memory):

1: Use the MONO_THREADS_PER_CPU=1 stunt, described here.

2: Uninstall the DLCs, or at least the Making History that is memory hungry. If you still want to use the parts, delete/rename the file "<KSP>/GameData/SquadExpansion/MakingHistory/makinghistory.kspexpansion"

The first will allow the Garbage Collector to run more times (and, at the moment of this writing, no collateral effects on a Vanilla KSP installment. And this stunt is known to work on Linux, Windows and MacOS - including Steam Deck - in many different Unity Games. But, as usual, backup everything before trying it, just in case.

The second will, well, remove all the MH functionalities from the game. Very few people really use them, unfortunately... But it may save about 2GB of RAM.

Of course, there's also the Elephant in the Room. It may be a faulty memory stick in your rig - it's very, very rare, but it happens. Check your memory using memtest86 or similar tool. Also, do a Installation Check if you are using Steam and the game is on a SSD/NVME/whatever-using-flash-memory - these storage technology is known to corrupt files pretty easily.

--- POST EDIT ---

A fellow Kebonaut just found another post of mine with the steps needed to set a Environement Variable on Windows!

mine

Edited Monday at 04:11 PM by Lisias
POST EDIT

[Elite_937]

19 hours ago, Lisias said:

How much memory do you rig have? Apparently, you are running out of memory. The one "saying uncle" on your log is the JIT!!!!

I wasn't expecting to summon the other god of mod fixing, but here we are. Thank you so much for your effort, even though neither of your methods worked. I have done the enviroment variable thread to the best i can (possibly just me being dumb, still always a possibility), i ripped out MH, still wouldn't work, took out both DLCs, still nothing. 

my machine has excrements memory since the dawn of time, and is an Alienware R11 if that gives any context. this has worked previously, and has had this same malfunction on a seperate machine of mine (suped-up office PC). however, it has worked in recent ish times (mid-late 2024). it is possible. it is unlikely to be a new mod i installed, given my current installation is just the necessitiies. i have the dropbox of my most recent player.log (no DLCs, enviroment variable workaround applied, nothing else open)

Player.Log DB

The only other hail mary i can think of at the moment (you probably have a better solution), is for me to give you my copy of my current KSP installation and Game Data folder to make sure i didn't install anything incorrect. other than that, i could try yours if you think that may work.

as for any security measures, i don't know what is even sensitive if anything in the GD folder, and am definietly not smart enough to try it. You have no way to trust if i put malware in there aside from my word and promise, as well as general lack of ability to do that. and i can't find any sensitive info in your copy nor do i want to. i have nothing to gain from it, and dont know enough KSP to get anything from it. you can scan it if you want (recommended, no clue what's in there and better to be safe than not) and do whatever to the copy. after a bit of trying, it said it would take 8 hours to copy it to dropbox, so tell me if there's another way. 

[Lisias]

2 hours ago, Elite_937 said:

I wasn't expecting to summon the other god of mod fixing, but here we are.

Spoiler

Loki is also a god!!!

 

Well, it's embarrassing that I had left this go unchecked, but..

Mod DLLs found:
Stock assembly: Assembly-CSharp v0.0.0.0
CustomPreLaunchChecks v1.0.0.0 / v1.8.1.0
KerbalKonstructs v2.0.0.0 / v1.8.4.0
MiniAVC v1.0.3.2    <---- HERE!!!!
Stock assembly: KSPSteamCtrlr v0.0.1.35

and

Load(Assembly): KerbinSideRemastered/MiniAVC
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)

Delete the file D:\Steam\steamapps\common\Kerbal Space Program\GameData\KerbinSideRemastered\MiniAVC.dll . I think this should improve your status quo significantly.

I never really understood why MiniAVC triggered a so nasty crapfest on Unity, but recently I got into trouble myself on a completely different situation, and I think I finally understand the underlying trigger. Of course, it's Mono.

Anyway, delete this file and let us know if it worked for you.

[Elite_937]

3 hours ago, Lisias said:

  Reveal hidden contents

Loki is also a god!!!

 

Well, it's embarrassing that I had left this go unchecked, but..

Mod DLLs found:
Stock assembly: Assembly-CSharp v0.0.0.0
CustomPreLaunchChecks v1.0.0.0 / v1.8.1.0
KerbalKonstructs v2.0.0.0 / v1.8.4.0
MiniAVC v1.0.3.2    <---- HERE!!!!
Stock assembly: KSPSteamCtrlr v0.0.1.35

and

Load(Assembly): KerbinSideRemastered/MiniAVC
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)

Delete the file D:\Steam\steamapps\common\Kerbal Space Program\GameData\KerbinSideRemastered\MiniAVC.dll . I think this should improve your status quo significantly.

I never really understood why MiniAVC triggered a so nasty crapfest on Unity, but recently I got into trouble myself on a completely different situation, and I think I finally understand the underlying trigger. Of course, it's Mono.

Anyway, delete this file and let us know if it worked for you.

So, yet again. it doesn't work. i can try to repeat these steps on another machine and see if it works. my only guesses now is hardware. all that this did was i think delay the crash (slightly) and remove the "use 1.7.3" message (that has been proven to be previously irrelevant and doens't matter as i have tried 1.7.3 and KK doesn't work). again, here's the crash: 
Player.Log DB

so, any other witchcraft workarounds? im open to any and all hail marys.

[Lisias]

33 minutes ago, Elite_937 said:

So, yet again. it doesn't work. i can try to repeat these steps on another machine and see if it works. my only guesses now is hardware. all that this did was i think delay the crash (slightly) and remove the "use 1.7.3" message (that has been proven to be previously irrelevant and doens't matter as i have tried 1.7.3 and KK doesn't work). again, here's the crash: 
Player.Log DB

so, any other witchcraft workarounds? im open to any and all hail marys.

At least is deterministic. In all 3 logs, the problem happened on KK's Awake:

0x0000028241AB1D8A (Mono JIT Code) (wrapper managed-to-native) UnityEngine.Object:Internal_CloneSingle (UnityEngine.Object)
0x0000028241AB1BB3 (Mono JIT Code) UnityEngine.Object:Instantiate<T_REF> (T_REF)
0x00000281CAA1659B (Mono JIT Code) KerbalKonstructs.Destructable:CreateCollapsables (KerbalKonstructs.Core.StaticInstance,UnityEngine.Transform,System.Collections.Gene
0x00000281CAA15A93 (Mono JIT Code) KerbalKonstructs.Destructable:MakeDestructable (KerbalKonstructs.Core.StaticInstance)
0x00000281CAA1237B (Mono JIT Code) KerbalKonstructs.Core.StaticInstance:Spawn ()
0x00000281CAA11703 (Mono JIT Code) KerbalKonstructs.Core.StaticInstance:TrySpawn ()
0x00000281CAA1130B (Mono JIT Code) KerbalKonstructs.Core.StaticInstance:Activate ()
0x00000281CAA017DB (Mono JIT Code) KerbalKonstructs.Core.StaticInstance:get_mesh ()
0x00000281CAA01153 (Mono JIT Code) KerbalKonstructs.Core.LaunchSiteManager:RegisterLaunchSite (KerbalKonstructs.Core.KKLaunchSite)
0x00000281CAA0FDB3 (Mono JIT Code) KerbalKonstructs.Core.LaunchSiteManager:CreateLaunchSite (KerbalKonstructs.Core.StaticInstance,ConfigNode)
0x00000281CAA0FC9B (Mono JIT Code) KerbalKonstructs.Core.LaunchSiteManager:AttachLaunchSite (KerbalKonstructs.Core.StaticInstance,ConfigNode)
0x00000281CAA0D1B3 (Mono JIT Code) KerbalKonstructs.KerbalKonstructs:LoadInstances (UrlDir/UrlConfig,KerbalKonstructs.Core.StaticModel)
0x00000281CAA0C89B (Mono JIT Code) KerbalKonstructs.KerbalKonstructs:LoadModelInstances ()
0x00000281CA9E2113 (Mono JIT Code) KerbalKonstructs.KerbalKonstructs:Awake ()
0x0000028244DFDBB0 (Mono JIT Code) (wrapper runtime-invoke) object:runtime_invoke_void__this__ (object,intptr,intptr,intptr)

Well, from this point, it's a guess game. I looked into the loaded libraries during the crash looking for anything I could remotely link to anything that could be screwing you right now, and found:

C:\ProgramData\Microsoft\Windows Defender\Platform\4.18.24090.11-0\MpOav.dll:MpOav.dll (00007FFE58C60000), size: 536576 (result: 0), SymType: '-deferred-', PDB: '', fileVersion: 4.18.24090.11

<yada yada yada>

C:\WINDOWS\SYSTEM32\xinput1_3.dll:xinput1_3.dll (0000000000400000), size: 122880 (result: 0), SymType: '-deferred-', PDB: '', fileVersion: 9.18.944.0

<yada yada yada>

D:\Steam\gameoverlayrenderer64.dll:gameoverlayrenderer64.dll (00007FFE26930000), size: 1675264 (result: 0), SymType: '-deferred-', PDB: '', fileVersion: 9.47.67.56
D:\Steam\tier0_s64.dll:tier0_s64.dll (00007FFDF3080000), size: 1683456 (result: 0), SymType: '-deferred-', PDB: '', fileVersion: 9.47.67.56
D:\Steam\vstdlib_s64.dll:vstdlib_s64.dll (00007FFE048E0000), size: 774144 (result: 0), SymType: '-deferred-', PDB: '', fileVersion: 9.47.67.56

Try to run KSP directly, outside Steam Client. This should remove the gameoverlay from the equation.

I'm also guessing that perhaps Windows Defender could have a role on the mess, perhaps denying something it considered "dangerous" that the JIT never considered it could be denied, leading to mistbehaviour due a unhandled fault. There's a way to deactivate the Windows Defender for a single binary?

The xinput is almost surely not involved this time, but I marked it here so we could cross-reference it in the future.

Hummm.... One of that posts make me remind of something that I shoult had asked before: are you using an SSD/NVME/something-that-uses-flash-memory ? There's a chance that you have some corruption on a critical file. Do a Steam Instegrity Check and see if any file gets refreshed....

 

 

[Elite_937]

1 hour ago, Lisias said:

Hummm.... One of that posts make me remind of something that I shoult had asked before: are you using an SSD/NVME/something-that-uses-flash-memory ? There's a chance that you have some corruption on a critical file. Do a Steam Instegrity Check and see if any file gets refreshed....

well, it does repeatedly say 1 file failed validation. no clue what, doesn't bother redownloading it (more likely does but faster than steam can reigster) and i don't know what it is. 

as for windows defender, it doesn't say it's protecting me from any threats and i don't know how to navigate there if it is. 

and as for running it out of the steam client, i don't have a non-steam copy. but i did run the EXE and it still failed. as well as it from the "launcher" file in there, some archaic launcher from probably back in the really old days of KSP. 

and i actually don't know what you mean about the last one. it's more than likely a memory issue as my excrementsbox has not great memory. if nothing else, i guess i could just try and import someone else's copy of Gamedata. 

[Lisias]

1 hour ago, Elite_937 said:

well, it does repeatedly say 1 file failed validation. no clue what, doesn't bother redownloading it (more likely does but faster than steam can reigster) and i don't know what it is.

Redownload this file. There's a way bigger than zero chance that it would be the root cause of the problem.

 

1 hour ago, Elite_937 said:

and as for running it out of the steam client, i don't have a non-steam copy. but i did run the EXE and it still failed. as well as it from the "launcher" file in there, some archaic launcher from probably back in the really old days of KSP.

So, yeah, you bypassed the Steam Launcher. Just for the sake of completude, do it again and post the Player.log again. I think I know how the log will look, but I want to be sure. I want, in special, to check if any of the mentioned address changes.

 

1 hour ago, Elite_937 said:

and i actually don't know what you mean about the last one. it's more than likely a memory issue as my excrementsbox has not great memory. if nothing else, i guess i could just try and import someone else's copy of Gamedata. 

SSD/NVME/whatever are a "new" kind of hard disk that uses flash memory (more or less the same one used on thumb sticks, but more advanced) to store data instead of spinning metal disks.

These things are prone to corrupt data pretty easily if anything wrong happens while writing data. On HDs, usually you lose a 512 bytes sector, that not rarely can be error corrected. On these flash memories, you lose a macrocell with 64KB size or even bigger, and the damage is not rarely way worse.

It's the reason you should not ignore that failed verification file above. It may be the root cause of your problem.

[Elite_937]

On 1/28/2025 at 1:06 PM, Lisias said:

These things are prone to corrupt data pretty easily if anything wrong happens while writing data. On HDs, usually you lose a 512 bytes sector, that not rarely can be error corrected. On these flash memories, you lose a macrocell with 64KB size or even bigger, and the damage is not rarely way worse.

It's the reason you should not ignore that failed verification file above. It may be the root cause of your problem.

So, still i don't know what file it redownloads. The best guess i have is to reinstall my game or something. And as for this drive stuff, i dont know how to tell if i have it, or what they look like. or what to do about it anyways. 

[Lisias]

Gee!! We are derailing this thread by now!

Moved the discussion to a new one:

 

Edited 8 hours ago by Lisias
Moving!