AlamoVampire

@Harry Rhodan did not know that. I will dig up the log later today and file dropper it here for you and any persons that can make use of it. I will add for now at least I am not seeing any adverse results from the aforementioned issues other than the game itself saying these issues.. op 05:27:30

Ok, I want to start off here by saying, I just got back into the game after a LONG absence and updated my mods to the best of my ability. I cant see any real way to duplicate this as frankly I dont know what if anything I am directly doing aside from starting the game and loading my save... EDIT: I just reloaded the game and saw a RED error message go blitzing past. Took multiple reloads to grab a screen cap via print screen. In RED: MissingMethodException: Method not found: "Unityengine.Texture2d.LoadImage". and in an Orangeish color right below it: [KSPSteamController]: Failed to initialize Steam API! I am playing a Steam copy of the game with a shortcut on my desktop and I run as Admin. End Edit 1. EDIT2: It seems the Error above is only on launch, and the ones below are when I go from being in one scene to the next, like for example, I checked on my munar base and got the error, returned to the KSC and got the below errors again. VAB back into the KSC generates it yet again. Perhaps something is missing from my game or I need a fresh install? Any thoughts would be appreciated. End EDIT2 Error I am getting: Error: Cannot find a module of typename "Discoverableobjects" Error: Scenariomodule is null. I have absolutely zero clue what is going on here. I dont think this is a game breaking error as I can jump from craft to craft with no real issues being seen, just that those two errors are randomly popping up. And before anyone asks my most recent output log is from about 2 years ago from what I can tell, well that is to say, the output log I see is dated October of 2016.... Any how, here is a list of mods that I am running, all as up to date as they can be: MechJeb, SpaceY, SpaceY Expanded, KIS, KAS, Chatterer, Cacteye, Proc Fairing, Planetary Base, Reentry Particle Effects. I will of course be updating this with edits as I learn more information on what I am seeing. If it is as simple as I borked something up with putting in the DLC or my mods and re-installing the game to fix it as well as my mods and DLC please tell me With that said, I will go back to punting Kerbals around to see what if anything else I can shake out of the tree on this. OP )2:59:30 EDIT3: The Following actions generate the dual errors listed below EDIT2: VAB into KSC, SPH into KSC, KSC into Tracking Station, Tracking Station onto any vessel <best as I can tell> that is NOT landed, and returning to the Tracking Station from ANY vessel regardless if its in flight or landed. End EDIT3 EDIT4: Here is a filedropper link to my output log generated at around 350am: http://www.filedropper.com/outputlog_19 here is hoping someone can use this to make sense of what I am seeing.

@KSPrynk Thanks for the response, ill give the post/thread you pointed me at a read later this afternoon or evening. 14:33:30

Either my cold has gotten the best of me or im missing something but is SpaceY and its expansion good with 1.5.1ksp? Its page only mentions 1.4.X Sorry if im asking a redundant question. 01:15:30

i am so beyond happy to have located this particular thread as I was worried about Procedural Fairings! You sir get a major nod of my hat to you for managing this wonderful mod! op 02:23:30

Well, if you ask me, career/sci only is not really worth playing. The IDEA of gathering science from experiments is fundamentally a spectacular one. In practice however its just a glorified experience point grind. To me it is poorly balanced. So much so that a simple command pod with the basic starter experiments can gather enough points on the pad to let you unlock enough parts to vaccuum thee KSC deeply enough to fill the tree if not fully then nearly so. At least this was the case in mid/late 2016 when last I tried career. It needs to be tweaked (again going on likely obsolete data) for sure. I would love to have a story driven career mode, but I guess thats why I prefer sandbox mode. Get to write the story as I go lol. Uh so in conclusion? Science needs to be tweaked to be made more meaningful and to give us a reason to push beyond LKO. Smoothing out how we gather science somehow (Not sure how as I lack enough experience with career/sci modes to make a meaningful suggestion) couldn't hurt. op 05:55:30

Life support could be entertaining if done right. I am all for mods going stock. Especially if it means using less mods and seeing what new toys I can play with lol.

Oh thx Deddly

@Deddly well that stinks that that visual is still inoperable as a stock feature. I hope that it becomes stock someday soon. But you are right that it would need tweaks, chief among which imho would be a toggle to turn on or off at player discretion. Oh and silly question the dlc is on Steam? op 0440 10/18/18

Thanks for the Welcome Back! Allow me to clarify, I refer to extended plasma trails behind objects on reentry. My understanding of the Reentry Particle Effects mod that I used a year or so ago is that it activated code already in game. You know the plume of smoke that you have as you launch? My understanding is that plume is similar to the plasma trails but those trails are longer and well orange and firy lol. Id share a picture but im not at my pc. The logic back then for not having it enabled as more than just around say your command pod was something about 32 bit and unity limits at the time, but even before I left we had 64 bit support, unity 5 iTHINK, and I think we have an even newer Unity now. Thus my curiosity to know if proper plasma trails were turned on now. I hope I clarified better but fear I was too rambling. op 0213 10/18/18

I have been absent from ksp for over a year and was wondering if Squad has ever flipped the code to on for the Reentry plasma effects that have been a dormant set of code for a very long time. I know of the mod for it and used to use it and will again if needs be. Feel free to relocate this query if I missed proper placement, it just felt like here was a reasonable spot. op 0103 10/18/18