TheCrows1

Don't know if anyone else does this, but I listen to chromanova.fm on SHOUTcast within Winamp. I typically turn the ingame music off and let this type of music play. This station normally plays chill/ambient/ type space tracks. Check them out sometime while you play! You won't be disappointed! Goes VERY well with the game!

Hello again my fellow Kerbalnauts! Okay, so during my three day weekend which I rarely ever get anymore (Woohoo!!!), I had some spare time available for me to setup a testing environment for KSP to see which mods I use play nice with the ISA MapSat 4.0 Dev Build and which ones seem to bog things down. Below posted are the results of my findings. First, let me list which mods I specifically have at this time: ISA MapSat 4.0 Dev Build (of course! ) NovaPunch v. 2.02 - Updated for 0.21.1 B9 Aerospace Pack R3.3 KSPX Parts Expansion Kosmos Space Station Parts Pack Kerbal Engineer Redux v0.6.1.1 Chatterer v0.5 To commence the best testing environment possible, what I would do is I would load each mod individually of each other and check memory usage to see which mods would have the most impact when used in conjunction with ISA MapSat. Let me just clarify that while watching my Task Manager, ISA MapSat always skyrockets my physical memory usage to about 38% - 40% capacity, in my case this is around the neighborhood of 3,000,000 K (around 5.0 GBs give or take. I will usually experience crashing situations when my memory hits about 3,900,000 K or beyond (around 5.5 GBs). So with that being said, let me post how the above listed mods impacted my playing experience while using MapSat with KSP! KSP (vanilla) no mods\extensions - Memory usage would be in the neighborhood of about 1,700,000 K. Extremely stable and no CTDs to report. KSP w\ KSPX Parts Expansion - Memory usage hardly changed, would be in the neighborhood of about 1,800,000 K, extremely stable and no CTDs to report. KSP w\ KSPX Parts Expansion and NovaPunch 2.02 - Memory usage signifigantly increased with addition of NP to KSP, shot memory usage to the neighborhood of around 2,100,000 K, sometimes fluctuating to 2,200,000 K in some cases. Still very stable, no CTDs to report. KSP w\ KSPX Parts Expansion, NovaPunch 2.02, and B9 Aerospace Pack - Memory usage signifigantly spiked with the addition of B9, right around the neighborhood of around 2,700,000 K. There was on instance of a CTD during my transition from VAB to Space Port, but no others the hour after that. KSP w\ KSPX, NovaPunch 2.02, B9 Aerospace, and Kosmos Space Station Parts Pack - This increased memory usage to the neighborhood of 2,900,000 K. CTDs were more prevalent after the addition of Kosmos, roughly once every 10 - 15 minutes. KSP w\ KSPX, NovaPunch 2.02, B9 Aerospace, Kosmos, and Kerbal Engineer Redux v0.6.1.1 - No major increase in memory usage. Still around 2,900,000 K of memory in use. CTDs still happening due to the addition of the other mods. No reason to believe this mod causes crashes itself. Will test individually upon request. KSP w\ KSPX, NovaPunch 2.02, B9 Aerospace, Kosmos, Kerbal Engineer, and Chatterer v0.5 - No major increase in memory usage. Still around 2,900,000 K of memory in use according to Task Manager. CTDs still happening due to addition of the other mods. No reason to believe this mod causes crashes. Will test individually upon request. KSP w\ KSPX, NovaPunch 2.02, B9 Aerospace, Kosmos, Kerbal Engineer, Chatterer v0.5, and ISA MapSat 4.0 Dev Build - Immediate crash to desktop upon launching craft equipped with ISA GPS and ISA Dish. Memory spikes to around 3,900,000 K, sometimes surpassing 4,000,000 K (approx 5.50 - 5.75 GBs of RAM). What I am using now, and have not had ANY CTDs at this time since I've started: KSPX Expansion Parts NovaPunch 2.02 Kerbal Engineer Redux v.0.6.1.1 Chatterer v0.5 ISA MapSat 4.0 Dev Build The above combination has my phyiscal memory usage at approx 3,300,000 K. To test, I left a MapSat running last night when I went to my girlfriends house and when I returned this morning 6 hours later, it was still running perfectly. Also, please note I updated the map resolution in the Kerbalpedia section to 720 from 200. I navigated around the game very comfortably also with no CTDS (navigated from VAB to Space Port, SpacePort to Tracking Station, ect.). So in summary, I removed B9 and Kosmos and the removal of these two seems to have freed up a lot of system resources to be used with KSP. Just wanted to share with everyone. Please feel free to shoot any questions my direction!

Hello. Just wanted to report that I too have previously had problems with the ISA MapSat Dev 4.0 release. The issue I would have is I would be able to load the mod into the game just fine and the parts (i.e. GPS and MapSat Dish) would be available for use, but when I would go to launch the craft after adding said parts, the game would crash to desktop quite immediately. Unrelated to ISA, I have had various other problems with mods causing game crashes as well, most notable Ferram Aerospace Research and K9 Rocketry, and to my understanding, these are supposed to be fairly functional mods with little to no CTDs. I picked up on an awesome tip while skimming through the posts here, and wanted to share it with everyone else in the event that this was not already mentioned so here goes! Before, I had KSP_win folder installed into a subfolder directly onto my Desktop. The game would essentially load and run just fine but as I indicated before, I was always plagued with the possibility of CTDs and in some extreme, but rare circumstances, blue screen of death. The problem would compound itself further with the addition of mods. It was suggested in the forums that you do not place your KSP_win install folder onto your Desktop anywhere. Instead, make a folder on your C:\ (i.e. C:\Squad\KSP_win). When I did this, I deleted my old saves and started fresh. When I loaded everything back up, I installed KSPX Expansion, NovaPunch, B9, LazorDockingCam, and Komos SSPP along with ISA MapSat Dev 4.0. I constructed a satellite geared with the ISA GPS and ISA MapSat dish, launched, and surprisingly, no CTDs this time. Okay, so far so good. I proceeded to put the sat in a parking orbit 500km above the surface of Kerbin. I turned on SCN and RAW options, and everything is working perfectly. As long as i do not time accelerate too quickly during scanning, the scans are spot on and match the planets topography (at least as visually as I can tell) and everything seems to function. So in summary, I deleted my folder off my desktop, made a new one on my main harddrive under C:\Squad\KSP_win, ran the Patcher (not sure what this accomplishes, but to me, Patcher suggests that it updates my KSP to correct various bugs and issues), started a brand new game, constructed a small satellite with one ISA GPS unit and ISA MapSat dish, parked at 500km, and turned it on. I hope this can help someone out there that has been having issues with this. This is such an ESSENTIAL need to the game if you plan on landing on other celestial bodies efficiently! Please feel free to shoot any questions over to me! Thanks!