omegalex

I just got a contract to track asteroids using the Sentinel infrared telescope that lasts for 1054 years, advances me *4,268,930* credits and rewards me *6,403,399* credits, 174 science with an additional 239 reputation. if I fail I lose 4,268,930 credits! All the other contracts are normal, apart from this one. Has it ever happened to anyone before and could it be a cosmic ray?

The same issue happened on Assassins' Creed Black Flags today (only once), before I installed a new nvidia driver. The issue seems to be gone, but I haven't tried KSP yet. Must be a coincidence, since Subnautica also runs on unity, but it never crashed like that (not even last week).

No worries, take your time! I'm also having my own issues with ksp constantly crashing in the VAB and especially in the SPH (freezes or screen turns into a color), sometimes followed by an unity crash message. It's now happening to totally accurate battle simulator too. Even if I tried to play ksp, I can't even build one tiny satellite before the game crashing in 3-5 minutes... I'll still be looking forward to this mod, no matter how long it takes. Happy holidays! (soon to arrive)

Looking forward to this, since the new rtg's that come with NF Electrical are much more convenient to use

Awesome! I had no idea this existed. It deserves more attention

I got this inspiration from the game From The Depths. Rovers in ksp are kind of pointless, and driving them (without spawning the kraken by using physics time warp) takes forever. 2-3 years ago I visited every biome on Duna and it took me 2 weeks IRL (with physics time warp, including bathroom breaks, and other irl stuff). It's a shame because rover missions can be fun and practical when collecting science and doing contracts, but why drive all of the rovers manually or land 20 different rovers in different target locations when you can have an "Out-of-play" feature that "drives" your rovers from one point to another in the background (without using the physics engine). It doesn't have to be anything fancy. Just insert some parameters like: traveling speed, waypoints -> distance, risk factor (rover getting damaged because of dangerous terrain) based on chosen traveling speed if you want an extra challenge (better if it would be an optional feature); then calculate the time the rover would take. I would've made this mod myself if I had any knowledge in game/mod development... Hopefully someone could give this idea a shot. Anyone is free to take it, if it's even possible..

Yep, all good, Spacedock is working now.

Whenever I try to enter spacedock nothing happens. Clicking on links that lead to spacedock leave a blank browser page. Am I the only one having this issue?

This issue sometimes happens in other games, not just ksp, but less frequently than ksp. There's nothing I can do besides try getting a clean reinstall of my graphics driver, clean reinstall of windows or throwing my steaming pile of dog turd out the window and buying a new pc altogether, I've completely lost it.

Another update. Deferred rendering and/or shabby are causing the same issue, again! But this time it only happens in the VAB and SPH. I still think it has something to do with anti-aliasing, but the situation seems to be out of my control because turning off SMAA in editor mode in "Deferred.cfg" fixes nothing. There are no other cfg settings that turn off anti-aliasing, so... no more deferred rendering I guess.

Got it. Thank you I now have shabby installed too. Thanks for that

I genuinely have no idea where I went wrong or if this issue is ksp or hardware related. The only thing I did was turn off anti-aliasing in the settings and bam, problem gone (although it has been sneaking by from time to time, with AA at 2x and Highlight FX off) Yeah, it's very exhausting. And thanks man!

I don't know how to close this thread, but the update is that the crashes are caused by anti-aliasing. Even without a single mod I had these crashes (weirdly enough 100% of the times happening when entering the SPH with ani-aliasing turned on). Without it, the game works fine. It's a shame because I don't know what I'm supposed to do about this issue besides playing without anti-aliasing.

Now that the servers are back up I can finally say that I found the source of crashes. It is the god damn anti-aliasing. I have removed every mod and the issue persisted without them. Turns out it has something to do with my pc, not the game. What a goose chase...

update

Found a lot of weird new things, posted the new log in the google drive link. -KSPCF wrote 39 memory leak logs (from 20:46:42.169, might be the same stuff at LOG 20:46:17.339) -Dynamic battery storage exception related to the error code I saw in the console (at EXC 20:45:30.987) and a dozen more being spammed one after another (from EXC 20:45:31.810) -Argument null exception related to parallax (from EXC 20:46:32.999) -other KSPCF logs (also 39) about memory leaks (from LOG 20:46:17.339) that involve system heat, kerbal actuators, dynamic battery storage, kopernicus solar panels, space dust, hullcamvds, near future electrical and something related to EVAConstructionMode (no clue what it is) 373 memory leaks, and there might be more details that I missed Jesus H. Christ Edit: I updated kopernicus and now the console is no longer being spammed with exceptions. Uploaded the new log after updating kopernicus, the dynamic battery storage exceptions are gone, but there are still some nasty memory leaks. I noticed the following things: LOG 21:41:27.740 (19 memory leaks this time) EXC 21:41:34.009 (tufx? object reference not set to an instance of an object) WRN 21:41:36.720 (something about kopernicus solar panel and changed configurations, has appeared multiple times after the logs listed below) LOG 21:45:13.249 (241 memory leaks, apparently right after I unloaded a probe in polar orbit around minmus) LOG 21:46:23.863 (changed from space center to trackstation, 14 memory leaks) LOG 21:49:08.965 (tracking station to space center, 28 memory leaks) LOG 21:49:27.405 (same as LOG 21:46:23.863) LOG 21:49:55.040 (tracking station to flight, this has to be a minmus mission I launched for a surface base, 17 memory leaks) LOG 21:52:05.383 (flight to space center, 370 memory leaks) LOG 21:53:51.871 (flight to space center, 656 memory leaks) LOG 21:54:15.369 (space center to editor, 14 memory leaks) LOG 21:54:36.000 (editor to flight, 112 leaks) LOG 21:55:12.510 (flight to editor, 624 leaks) All of the memory leaks that I mentioned above had an exception "NullReferenceException: Object reference not set to an instance of an object" related to KSPShaderTools right after the leaks. The number of leaks also seems to grow in number. LOG 21:56:14.559 (editor to space center, 120 leaks, different save file) LOG 21:56:39.427 (space center to main menu, 14 leaks) LOG 21:58:23.606 (flight to main menu, 509 leaks) All of the memory leaks logged by KSPCF had the same mods I listed previously. @Nertea DynamicBatteryStorage is no longer an issue (I don't think it ever was tbh) , so therefore I don't think these issues I'm listing are relevant anymore. I'll continue on a separate forum. But who knows, maybe you'll catch something important in the logs, since most of the mods that were listed in the leaks involved some of yours. Sorry for wasting your time, if that was the case. Sigh, crashed again... 5630 memory leaks and 700 moments before the crash.... fun

Logs and mods are here in this google drive link. ---------------------------------------------------------------------------------------------------------- [LOG 12:42:51.599] Vessel destroyed - Regenerating scatters [LOG 12:42:51.600] [PlanetariumCamera]: Focus: Kerbin [ERR 12:42:51.614] Exception handling event onPlanetariumTargetChange in class KnowledgeBase:System.NullReferenceException at (wrapper managed-to-native) UnityEngine.Component.get_transform(UnityEngine.Component) at KSP.UI.Screens.KbApp_PlanetResources.ActivateApp (MapObject target) [0x0007d] in <4b449f2841f84227adfaad3149c8fdba>:0 at KSP.UI.Screens.KnowledgeBase.ActivateApps (KSP.UI.Screens.KnowledgeBase+KbTargetType targetType, MapObject target) [0x000fa] in <4b449f2841f84227adfaad3149c8fdba>:0 at KSP.UI.Screens.KnowledgeBase.OnMapFocusChange (MapObject target) [0x000f4] in <4b449f2841f84227adfaad3149c8fdba>:0 at EventData`1[T].Fire (T data) [0x000b0] in <4b449f2841f84227adfaad3149c8fdba>:0 [EXC 12:42:51.615] NullReferenceException KSP.UI.Screens.KbApp_PlanetResources.ActivateApp (MapObject target) (at <4b449f2841f84227adfaad3149c8fdba>:0) KSP.UI.Screens.KnowledgeBase.ActivateApps (KSP.UI.Screens.KnowledgeBase+KbTargetType targetType, MapObject target) (at <4b449f2841f84227adfaad3149c8fdba>:0) KSP.UI.Screens.KnowledgeBase.OnMapFocusChange (MapObject target) (at <4b449f2841f84227adfaad3149c8fdba>:0) EventData`1[T].Fire (T data) (at <4b449f2841f84227adfaad3149c8fdba>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:LogException(Exception) EventData`1:Fire(MapObject) PlanetariumCamera:SetTarget(MapObject) PlanetariumCamera:OnVesselDestroy(Vessel) EventData`1:Fire(Vessel) Vessel:OnDestroy() Might no longer be relevant, the vessel destroyed stuff was just flights being unloaded ---------------------------------------------------------------------------------------------------------- About reproduction, I have genuinely no idea when or how these crashes happen (screen freezes or turns into a blank color, but the game still runs in the background until it crashes), it's entirely unpredictable, but once one crash happens then there will be more coming after much frequently, sometimes after something like 5 minutes. Most of the times it happens in flight (had 5 consecutive crashes in a span of 20-30 minutes when I was testing a rocket, and 5 more in orbit around the mun), sometimes in the VAB (happened twice yesterday after some hours of playing ksp). I also noticed that when I played ksp with an empty mod folder I was no longer stuck facing crashes minutes after minutes (been testing for 1-2 hours). When I added back all the mods I have, except for the visual mods, no crashes happened until at some point, much later, the screen turned into a blank color (matching the color of the texture I was facing, for example if I was looking at the mun, I'd see a grey screen of death). When this happened I did have DynamicBatteryStorage installed. I thought I could work with this, so I went back to playing ksp regulary. I was testing a lander for a minmus probe, and instead of teleporting to minmus I decided to lower the gravity down to 0.05 to simulate it. When I opened the cheat console, I saw this exception being spammed like 3 or 5 times a second, over and over, without stopping: Exception: NullReferenceException: Object reference not set to an instance of an object Turns out it's caused by DynamicBatteryStorage. When I removed the mod, the console looked clean, the exception was no longer being spammed. I don't think that DynamicBatteryStorage causes the crash, since I had similar ones in a game called From the depths and in War thunder (sometimes rarely, sometimes would suddenly crash over and over), but the spam of exceptions I saw in the console doesn't seem right. Right now I am playing without DynamicBatteryStorage and will all the mods I had previously installed just to make sure that I've checked out everything I could. One more thing, I changed drivers and all of my hardware except for the hard drive I have the OS installed on. Unless this somehow causes issues (although I highly doubt that), then I really can't guess why this would still persist with new components for so many years. ***EDIT: Crash happened again without dynamic battery storage, I guess all the crashing stuff above is pointless to address in this forum. The only thing that remains is the exception spam in the console.. Also updated the log file, there are some freaky parallax exceptions happening at 23:01 and 23:30 ish seen on both crash logs I linked.

Exception: NullReferenceException: Object reference not set to an instance of an object This error gets spammed in the cheat console when I'm in flight (on runway, launchpad, flight any situation outside). It only happens when I have anything that generates electrical power, including stock photovoltaic panels. Recently I've also had an issue with the game suddenly crashing out of nowhere, the screen turning into a color that would fit the environment (camera faces the surface of the mun => grey screen of death). I don't know if these 2 issues are related, but this exception being spammed continuously does feel like some sort of time bomb.

update

update

update

I removed every single mod, got a fully stock ssto from a very old save file from 2 years ago (when I had no mods installed), and went on a minmus-mun run. There were no crashes this time, very depressing without mods ngl These are my theories: 1. The mods accelerated the speed and frequency of the crashes because I still can not explain why other games like FtD crash the same way (twice, yesterday and 2 days before) 2.Memory leaks, or faulty memory? (since these act like time bombs, somewhat correlating with my first guess). I don't know what to say about this, I've changed my RAM 3 times, and always made sure that they are placed correctly (1-3, 2-4). Why would a memory issue still persist? I also have 32GB of RAM, more than enough to sustain any RAM intensive applications 3. Some mods are conflicting/broken. Doesn't explain why other games crash, but if this is true then I'm going to pull all my hair out finding the culprit(s).

-It now happens to every single vessel I use (or at least that's what I'm assuming, since this crash seems indiscriminate now). The vessel is fully stock apart from one modded space capsule called the Proteus advanced command pod. (I don't know how to upload screenshots on this forum) -Craft has 68 parts, roughly 86t. What is weird is that the engineer's report says my net heat flux is 1W, when it actually is -4kW in the system heat tab. EDIT: Oops, cryo propellants and cryo engines are 100% not stock, lmao. The upper stage uses the engine called Buzzard that runs on Methalox -I have quite a lot of mods, basically every single one (recommended by Matt Lowne) for visual improvements, IVA, near/far future tech, mk2 extra's mk3 extra's, mark 4 system, OPM, system heat and heat control, heap padder, kerbal atomics, hull camera vds, community resource pack/kit/techtree, cryo engines, reentry particle effect, planet shine, station parts redux, TUFX, trajectories, UmbraSpaceIndustries, better time warp, kerbal engineer (absolutely mandatory for every ksp player ever), mech jeb 2, JSI, FSHangarExtended, kerbal joint reinforcement, parking brake and the rest of the essential mods that are necessary for everything else to work (like kopernicus, USItools, module manager, dynamic battery storage etc) I recently installed the volumetric clouds mod, but removing it changed absolutely nothing. The rest of the mods I had for months, unchanged. I tried replacing it with the old EVE mod, still the same.. I installed volumetrics manually, uninstalled it manually, then reinstalled old EVE through ckan. Still the same results. -I verified the integrity of game files, 3 times. First time, 104 files were validated (which broke EVE for some reason, bloom was gone, clouds were almost nonexistant and the milky way skybox didn't load) I don't have the mod Hypoxia, that must've been a coincidence tho. I have to note that, this problem has been around for a year, and it's only getting worse. You might think it's hardware related, or driver related.. which makes a lot of sense. But... I literally changed every, single, piece, of, hardware, that I had with new one. THe only thing that didn't change is the main C drive, I still have the same old one with the windows I had on it. I also changed the drivers multiple times, yet... here I am.. and it's getting worse. It seems to happen in From The Depths too (the game) Another side note, if I wander around the VAB, KSC, tracking station, main menu etc, the game won't crash. It works just fine. It's only when I'm in flight when the screen goes bust and the log goes crazy.

It didn't work, same thing, same crash log with a dozen of "vessel destroyed, regenerating scatters" being logged, whatever the hell they are I'm out of options

I tried installing a compatible driver for the gpu I have a while back, but without difference, unless I did something wrong. I have an Nvidia GeForce GTX Titan X GPU, and the currently installed driver is at version 552.22. Did I get unlucky with the driver or am I worrying too much about driver compatibility? Edit: I just realized, the driver I currently have is not the one I remember installing, what the hell