Search the Community

Hi Kerbonauts, challenger here, having some problems! I play KSP 1.2.2 Because IT SUPPORTS A VERY CUTE MOD, THE SPACE SHUTTLE SYSTEM MOD. The problem is that 2 parts (the shuttle cargo bay and the shuttle crew cabin) are completelly black with no texture when loaded. I have the same problem with the 1.7.x version of the mod I just have the SpaceShuttleSystem mod and its dependencies wich, according to the original spacedock link of the mod (https://spacedock.info/mod/1178/Space Shuttle System?noedit=True) , are: SSTU; KSPWheel; JSI; CommunityResourcePack; ASET This are the names of the mods folders, I DONT HAVE ANY OTHER MODS EXCEPT FOR THE SQUAD STOCK FOLDER. Hope you can help, thank you and go at throttle up!

This is the official thread for the Kerbal Galactic Expansion mod. This mod adds new star systems to Kerbal Space Program Prerequisites: Most recent version of Kopernicus. Images: http://imgur.com/a/uEfmo Releases: Release v0.3 is now available on both sites. Changelog: v0.3 - Version: "How the heck does finalizeOrbit work?" Added the Kel system Added the Kernol system Added the Kiris binary system Added a new planet to the Kerbol system Added rings and a corona to Xurbol Moved Kerbol System closer to the Xurbol to minimize floating point errors and orbits shifting Cleaned up the file system Known Issues Xurbol's rings appear extremely dim in the tracking station Xurbol's rings can be seen through it when zoomed out Some planets are have low quality textures Planned Features More star sytems(like 1 or 2, 3 at most) Black hole gamma ray bursts More detailed rings on Xurbol Wormholes(most likely wont happen) SigmaBinary support Expand the Kel system(more planets and maybe binary) Biome maps -Brightness curves on the stars v0.2 - Version: "I guess this is an actual project I'm doing now" Added small asteroid like planet in the asteroid belt named Kre Re-did the Trappist-1 star to have a corona Smoothed out terrain Re-aligned some of the planets to be tidally locked Switched Trappist-1b and c SpaceDock: https://spacedock.info/mod/1232/Kerbal Galactic Expansion GitHub: https://github.com/RyderReed15/KerbalGalacticExpansion/releases If you have any comments or bugs please leave a reply on this thread or on the GitHub repository. License: MIT

I noticed this in the 1.2.2 changelog: +++LoadGameDialog When a game is saved it now creates an associated metadata file - called .loadmeta alongside the .sfs. This file contains a hash of the sfs save. When the loadgame dialog opens it will compare the hash in the .loadmeta file with the hash of the savegame, and if so it will use the data in the .loadmeta file for the load dialog details instead of parsing the whole save file. Ew. Gross. Really? You take my nice clean Saves directory and clutter it up with a bunch of garbage? Can I suggest the developers eliminate this disgusting, amateur hack and put the cached information in the sfs files themselves, near the beginning of the file? The dialog could just read up to the end of the cached data. That would provide the same speedup, without littering the user's folder with files that are meaningless to them. It should be trivial to do this in a way that maintains compatibility with old/new saves. That's my friendly and opinionated two cents.

Greetings everyone, I have a 1.2.2 version of the game and moded with RSS/RO and I have encountered this problem during my virgin flight with a 3 satellite mission. Hope to have some help, otherwise it would be impossible for me to move on to further exploration. After I got my first satellite undocked from the main ship, it was clearly moving downward, instead of moving a bit away from the docking direction. Then I switched to the separated satellite, it seems like under an invisible acceleration to the direction of nadir. Going all the way back into the atmosphere. but the satellite is on zero thrust, after all, there's no engine nor fuel tanks. And come to think about it, when the separation of 2nd/3rd stage was made, the 2nd stage debri seems moving strangely downward too, instead of backward, should be the same problem. Here are the mods I have: Does anyone know where the problem is and how to solve it? Thanks to all helps in advance -------------- yea I should be a bit more specific about it. The injected orbit for the entire craft is 450 km both at Ap/Pe, and the Karman line of the earth in the game is 140 km. The orbit of the satellite after undocking was NOT stable. The Ap kept rising and Pe kept to dropping all by themselves, resulting in the undocked satellite reentry to the atmosphere at last. Like I have said in the main post, it was like an invisible and constant thrust toward nadir is applying to the satellite. And it was undocking from the port, not separating by staging so it should not be adding to much force.

Apr 08, 2018 - Now on CKAN. Based on what I've seen, I will not be supporting CKAN problems. it's supposed to be a 'one click and done' on Spacedock, according to the Spacedock FAQs. So please address any questions/problems with CKAN installations to the CKAN team. Thanks for your understanding. Apr 01, 2018 - 0.1.4.4 Correcting the fuel/oxidizer mix in the K1 second stage. I hate to see really great mods languish, so I'm going to try to bring NovaPunch up to date. The original mod thread can be found here. I know, "No pics, No clicks". So here's one Launch Vehicle: ![]() Imgur Gallery with other images: http://imgur.com/a/xiRRn (Nov 20, '16 Updated to include a sampling of the engines) Change Log Next Major Step: Start working on getting the legs functional (Gotta learn Blender, Unity and Gimp, so this won't be quick.) Still to do overall: (In no particular order) RealPlume support Other stuff as I think of it Listen to your comments and suggestions Look at other requested mods once I get this one fully up to date. Tiberion's shuttle parts has been requested. I'm up for that, but I need to get a handle on Blender & Gimp. Interested? For now, it's only on Known Issues: Credits: License: CCA-SA4 The contents of this mod are copyrighted by their respective original authors and released under the Creative Commons Attribution-ShareAlike 4.0 International License. You can read the full terms of the license on the Creative Commons webpage by visiting Creative Commons Attribution-ShareAlike 4.0 International License.

I just found an awesome mod for 1.2 and tried it out. Game crashed. Only 3 mods, KER, Kerbal Kommander, and Module Manager. All crash report files are here. Also, the crash happened twice. Please help. Oh, also, I'd love it if someone would take it upon themselves to take command (rimshot) of the Kerbal Kommander development. The mod seems pretty dead, but is really cool.

I've installed RO and RSS following Scott Manley's tutorial. It's great fun except for one annoying issue; all RCS thrusters/blocks add at least 100kg to the spacecraft's mass when added in the VAB. I've already gone into the .cfg file for the RCS thrusters and made the mass 100x smaller, but this made no difference. Any idea what I need to do to get the correct part mass in-game? Thanks in advance!

Not ready to be reviewed on YouTube, still under heavy development Benjamin Kerman's Welding Supply Co. Is proud to present Ludicrous Propulsion Systems v.0.2.5.2 "Adding new throttleable hybrid engines and taller fuel tanks in all stock sizes since 4/11/17" DOWNLOAD REMOVED (This alpha release includes just the hybrid engines and an interstage plate) Description: Have you ever felt tired of having to stack two Rockomax Jumbo-64's on top of each other? Have you ever felt like you could use a set of longer 0.625m Liquid Fuel Tanks? Have you ever wanted THROTTLEABLE SOLID FUEL BOOSTERS??? Well, you are in luck! Ludicrous Propulsion Systems adds all of these things to your game, as well as radial-size adapting LFO engines! Hybrid SRBs, longer and even longer fuel tanks, and more, LPS is the only solution to high part count. Pics!!! This mod is licensed under a MIT license. I have spent many hours working on the code, so I would appreciate it if you don't pass it off as your own work without at least mentioning me. Copyright (c) 2017, @Benjamin Kerman Source Code: The code is functional, but uses stock textures. We are still working on the final models and textures. I would be grateful for anyone to go through the code I have so far and make a bug report if you find anything wrong about it. Planned Features: Changelog: Known Problems: Compatibility: Ludicrous Propulsion Systems is currently compatible with: Engine Igniter: Download Engine Igniter Not compatible with KSP 1.3 RealPlume support coming soonTM Contributions: @hedgey579: Doing all the modeling and being my "partner in crime". @linuxgurugamer: Thanks for answering all my questions about .dll files. @Streetwind: Thanks for answering my questions about the differences between all the kinds of mods. @Nertea: Thank you for getting me into modding, as your mods were the first I downloaded. @Supercheese: Help with balancing part prices. Want to help? Feel free to make a pull request on my GitHub page for any of your mods. This mod includes ModuleManager (MM) and miniAVC, all credit for those goes to the authors @sarbian and @cybutek respectivly.

KSP: 1.2.2 Windows 64bit Problem: Mars entry glitchy. My ship start spining and become uncontrollable after pass 124 000 Km. Mods installed: https://ibb.co/eCHKuR https://ibb.co/jpJg8m https://ibb.co/gZMvZR Reproduction step : Start Mars entry , in any angle it start spining , and become uncontrollable. I've try dozen of ship , with wings , high rcs power. Pod with heatshield are less glitchy. Log : Can't find it sorry Thank you for your time. Ps: Sorry for my bad inglish , i'm French.

ATTENTION: The Curseforge link has been removed since I no longer have the time to maintain it. Anyone who would like to maintain the Curseforge page, please PM me. This is mainly a repackaging and expansion of DeltaDizzy's Flag Pack. It consists of 11 flags by me and 14 by @cratercracker. Now compatible with Decal Stickers by @blackheart612. blackheart612 had no role in this mod's development. If you encounter a bug, report it with the Github Issue Tracker. If you don't, it will be ignored! You can use it in 1.3, but it has not been tested. cratercracker's flags are marked with the prefix "CC". Mine are Marked with the prefix "DD". It is compatible with all versions of KSP that support PNG flags. It only contains flags and the config files for the Decal Stickers. My flags were made in paint.net, and cratercracker's were made in MS Paint. Examples: All code is licensed under GPLv3. If you have contributions or suggestions, comment here: https://github.com/DeltaDizzy/Lambda-Station-Decals/issues/2 DOWNLOAD: Github These mods can improve your experience: You will need this if you want to take advantage of the compatibility. -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Venus she's easy! or maybe not. She's hot, and has great tracts of land. Not that its a high pressure arrangement to sample her wonderful science. It will take more time to float to her surface than to do three full moon missions. Playing a Career mode game (Hard setting except for load/save allowed) using RSS as my baseline mod. This is a 1.2.2 game so I’m using SMURFF, SpaceY and other mods to get to an acceptable power to weight ratio for launches, Using tweakscale and procedural fairings, SXTcontinued and near future mods for extended tech tree parts, community tech tree and SETI for an unmanned first push, TACLS for life support and I'm full enforcing a cleaned up orbit ( If i have to delete space junk it costs me 100k funds) and use Stage Recovery to get funds back (Set 7k Burnup Speed and 7-14m/s Landing, otherwise default) I tested various re-entries to make sure the 7k Re-entry speed was actually survivable for my designs. SCANsat and CactEye pad out the game but I’m using Comnet with only KSC ground station instead of RemoteTech for communications. Um oh and 104 mods in my CKAN installed list total... I have Saturn Second stage Nuclear and Timberwind nuclear engines in custom modded items, generally don't use them, specifically only on missions leaving from above 500km orbit. None of the designs is dangerous outside of the basic nukes in space argument. I use a minimum of 12m from crew compartments as a design requirement for nukes. Some of the more extreme nuclear engine design would warrant more though. If I’m using a Timberwind 450 the engine is likely 30m+ back just because of the amount of tank it needs to be useful. Regardless once i get the SSME available it was all that for main and second stages. I use Solids only if really needed or its a real simple mission. After Luna I started deciding what to do next, mars window was way out and I started to investigate Venus first. Time to set up comms. I probably could have got away without the comnet first but I believe its the first step given how many missions have failed because communications are crap. It also eliminated the need for huge antenna on the landers and probes. COMSATS Venus Comsat Network, sent 4 relays in an array planned aero-braking to drop dV, middle of aero-brake maneuver, deflated heat shield, and ejected compacted relay sats, barely staying out of atmosphere, each sat had barely enough maneuver 680m/s to get circular in a reasonable Eq. orbit. in trying to switch craft during the near disaster, got locked onto the structural frame that the relay sats coupled to during transit, (just some pipe sections a de-orbit motor and small probecore, mechjeb, antenna and batteries, one small solar panel). nothing burned up, very close but high drag really slowed it down fast. followed to ground, it litho-braked with the sacrifice of one of the spent couplers and I got my first Venusian data (telemetry & temperature). The Comsats got me a few more experiments and squarish 1200km orbit network (Intended to be 3000km). SCANSATS Scansat probes went out next, didn't have SAR yet. Radar altimetry, Biome scanner and Survey scanners along with High orbit and Low Orbit Science Sats, discovered that venusian day is longer than its year! Very long scan time, skipped two useful transfer windows. As the last of my Apollo moon missions finished scienceing the crap out of the moon I sent a second science/Scansat wave. SAR high altitude, recon and Survey detail sats along with my missing space science. Took a while to get all the gravity scans. Kerbal Alarm Clock estimates took front stage. My first comsats & scansats went to mars during this time so it was hectic. Descent to the surface! Originally I had intended to ignore Venus landings unless the were historical missions from RSS Historical missions pack. However the ease of landing space junk on the surface made me prioritize it given the shorter transfer and delay times for manned missions and sample return. Venera Missions, first two missions sent using my best guesses and did not include all the instruments since I did not have all at this point, using DMagic's instruments also. Midlands for the win. Stopped using the Inflatable shield because it was to hard to control drag, and it flipped on my first mission, lucky that a couple of solar panels was all that was lost. Landers overbuilt soviet style. Found out parachutes won't deploy at 12m/s in 70atm. drogue shoots in pre-deploy would not stop spinning, but full deploy brought the landers down straight. Any lifting surface is detrimental to landing except maybe airbrakes/gridfins. Reality is that they probably melted on the way down since they didn't include temperature control of any kind. past initial re-entry anything that is dropped will make it to surface probably with a safe speed (kinda 12m/s seems like max on higher terrain). Major Probe Volley! After re-design of the probes, left me with R2D2 looking canisters filled with science I tried sending two for testing. Mainly finding more accurate landing position. The agonizing wait during the drop! don't like x4 physical landings regardless of speed, read a book, made some tea. Determined that below 50k altitude ASL engines are indeed totally useless. Determined total batteries i could get away with. Solar is great assuming they survive re-rentry heat. Next eight came in as a docked cluster. Horrible experience with all eight lagging my computer. They consisted of unmanned landers, transmit only, everything possible to fully transmit, all biomes. Still very slow descent, probes hit 11m/2 without drogues, tiny landing gear, set of small airbrakes. Temperature was not an issue, though activated thermal panels cooled the pods. Even at 4xphysical time warp the descent was horribly long, cheated gravity to x10 for the 4th and later probes just to lessen the real time spent on the mission, took over 4 real hours to get all biomes sampled. Noticed during the first and second mission that engines and RCS became useless for anything except re-entry phase, determined 300-800 m/s of retro and 40-50 RCS got a good accurate landing, both mechjeb and trajectories projected over shot landings. Rovers might be faster than planes on venus. Trajectories as usual seemed more accurate. Sample return! Attempt one consisted of a real simple pod, stack of ascent rockets, stack of batteries and eight ducted fans. ran out of batteries at 20km, drag was to high for the system to get up. Second try replaced most of the batteries with capacitors and almost made it. The ducted fans didn't have enough thrust to get me above the point I needed for thrust on my bottom stage (4xlarge Ullage motors with flat ISP). floated back down. Third try, nukes, capacitors in drop pods, more ducted fans (too many). the ducted fans started crashing the computer with some bad interaction of mechjeb's dV calculation. Think it had something to do with staged capacitors, the ducted fans and some kind of circular calculation. After 12 program restarts including one full on computer freeze I gave up on the ducted fans. I think it can work. Fourth try, Balloons! Used the HL inflatable parachute. Made it too small. I didn't see the dirigible icon in VAB so I undersized the balloon and it wasn't enough to get me up to 50km. Also discovered the kraken hates unbalanced balloon lifted craft, spinning it until my probe core sped off at Sol escape velocity. Try Five. Bigger balloon, used RoverDude's control pod. was great but in dropping from the balloon frame I clipped a tank and blew up. Try Six. made it to orbit. Barely 165x147km Orbit and forgot a docking port. Using a Timberwind 45 design basis Nuclear rocket for everything except initial separation and orientation. Tumbled a lot, need cleaner separation and deploy-able control surfaces. Spinning and very slow ascent to be safe enough. Agonizing pain of slowly changing inflation of the balloon as the velocity dropped below 10m/s. Going above 30 resulted in explosive spin (actually five iterations of this design blew up on ascent) because I got impatient and inflated too fast. Try Seven. Changed balloon “Cirrus” real lift variant, started including life support (TACL) and more support in general. (return vehicle prepositioned in 350x350km EQ orbit). Lift vehicles started passing 500k for the missions, plus one 180k refueling mission in my planetary band parking orbit. Determined need for 140+ days on orbit life support and ~100days transit (3500m/s dV transit + 3000dv to bring it into parking orbit for re-use). So generally needing 13k dV for fast missions. Total life support of near a year. Loaded Solyent Green/Red life support mod for TACL. Tested 5 iterations most problems were hard to control on drop, re-entry. Had one burn up too bad for use, two had hard landings as they came in at an angle and fell over. Try eight. After a successful orbit and rendezvous and realizing my rcs balance and SAS sucked on the final manned return pod, removed all but 5days LS from pod. Pod is located inside a set of cargo-bay modules, Three cooling stages are included, larger amount of RCS. Has about 1200dV to spare for any orbital maneuvers. First unmanned test, drop from balloon at 0.35atm, drop first stage tanks, drop second stage tanks, drop third on way to circ burn, mechjeb ascent.... takes me in 180deg counter orbit. 14kdv to get plane change. /sigh Second test I get to balloon separation and drop, launch and start up, run into balloon and explode. Load and try again, manually pilot, then beginning the ascent guidance to nice clean 350k orbit. Try Nine. new design includes sepatron to get balloon spun away from vertical. Full flight plan unmanned test including return using a large nuke powered 5m transit bus. Optimized the balloon to get a stable point of 100m on earth, gave me >1atm on venus lift final so ascent using my normal motors is possible, Used timberwind 45 again as ascent motor and staged the tanks on layered side pods. Transit bus includes LS reprocessing, cargo bay with supplies and excess life support equipment space for 3 crew (Intended for one man missions) that includes an earth orbit return pod. Is 10tons of Fairing excessive? 750k funds to orbit, a refueling and off it went. Mission went great, max inflated to balloon from ground level, it goes supersonic immediately and starts climbing fast (150m/s peak), drop the science and landing gear stage just as take off happens. Nice stable verticle ascent with a little wobble. Fins might help be they are hard to include. Ballon shot clear and spun off to the side, ascent arced nicely past it and almost all my spare dV went unused. Docking went a little rough, not sure if its the Covered Jr. docking ports I used. So now I have an extra emergency return vehicle in orbit. 5million Funds well spent. Time for Real Manned Mission(tm). Manned (Womaned) Mission! Valentina did the first mission solo 144days of waiting, 96d+102d transit, 5 seconds of EVA (hot hot hot), and many minutes of up and down above venus. Now for 7 more times, all in transit, Valentina sits in the abort return vessel. A spare lander is coming along also. Rescue mission at worst case or if I miss a biome target. Best case 1.2m worth of orbiting space junk. Thought about exploring using a rover or folding aircraft, but its way to slow unless I’m right on a boundary even then its a serious mission to get one and also have the balloon launched rocket in the same place. I kinda doubt i could even get close enough for a rescue mission to actually work. Should have positioned a grapple rover to avoid to EVA problems (fire clad space suits). Now on to more missions, to places like the canyons (looked kinda dunish to me) as harley kerman plants his flag...too hot, oh well maybe just the EVA report. I wonder why he had that red bar over him during his EVA. I think I heard him swear at the ground control. Glad I installed chatterer also glad I didn't waste weight on the ladders. Kerbals must be highly compressible mushrooms! Manned mission ascents on venus involved, SAS set to radial out, gridfins retracted, set balloon inflation to 100%, drop landing stage and speed off into the sky. Final peak ascent speed 192.5m/s at 12-15km. Crossed 50km at 150m/s and dropping rapidly. oscillated at 0.80-0.63atm ~55-56km. Set mechjeb for ascent 350km -180deg Inclination (because 0=180deg on Venus for no apparent reason), Ascent path numbers [60km, 100m/s, 250km, 1deg, 35%] Let go of balloon, fire engines, active autopilot. Orbit 350x349km with 1600-1800m/s maneuver fuel, meet up with transit bus at 300km orbit. Off equator I had the bus maneuver a bit for plane changes. In those cases I had left it in a higher 500km orbit and it performed most of the plane maneuvers. Venus Rotates so slow that I didn't ever spend more than 500m/s to get co-planar even considering the lack of control over launch window. Only needed 100-300m/s to compensate for any bad timing in the Hohmann transfers. That said I’m pretty sloppy with rendezvous maneuvers. Really want RP-0 1.2.2 now, need to try this again. (Am i a masochist?)

Chatterer+ This add-on adds additional chatter for your game! Current version: 0.4 Requres Chatterer to work! So currently it adds: Apollo 15 chatter(still in work) Apollo 8 chatter (in work too) Mercury 6 chatter (in work...) Installation: Paste GameData in your game folder(overwrite if new version); In chatter menu(settings tab) enable show additional stettings; In chatter menu press ChatterSets and type apollo15, apollo8 and mercury6; Press Load; Check it. Picture: To do list: Known issues: Mercury 6 chatter is a litle bit loud. I`l fix it. Changelog: 0.4 Added Mercury 6 chatter Licensed under: CC-BY Attribution 4.0 International Download: Spacedock Dropbox

Right after Christmas 2016, I made one Steam backup and one Windows 10 backup (that one by just copying the KSP folder and moving it into another folder on my desktop), then used the built-in Steam functionality to downgrade my game to 1.1.3 in order to install Real Solar System, Realism Overhaul, Realistic Progression Zero and all of the recommended mods using CKAN. What do I do now that KSP RSS RO RP-0 can be played on 1.1.3? How do I update the game? (I'm new here, so I'm being conservative on the formatting before I can develop a pattern.)

Hello guys, I'm a new user to the fourm. I've been playing KSP for quite awhile on Windows, and it works great, but when I try to run on Ubuntu with limited Mods, the game crashes half-way through loading. I will post my KSP.log below. [snip]

Game crashes as soon as try to EVA crash.dmp https://www.dropbox.com/s/sm72csvu23l6r8i/crash.dmp?dl=0 error.log https://www.dropbox.com/s/n2d7o0i47wbdbu1/error.log?dl=0 ksp.log https://www.dropbox.com/s/tziwwj6wvxcso7d/KSP.log?dl=0 output log https://www.dropbox.com/s/vzk3y4qmhb5nhlo/output_log.txt?dl=0

Seeing as Principia is getting to the point where it is quite useable, it seems to be a good time to do this. The challenge is fairly straight forward. A space station has been placed in a magical square orbit around Mun. The objective is to pilot the cargo vessel, which is in low Kerbin orbit, and rendezvous with the station, using as little delta V as possible. You will need a 1.2.2 installation of KSP with a stock planetary setup, and Principia Catalan, then load this save file. https://www.dropbox.com/s/d9vbdw0wba0jkxv/rendezvous.zip Rules: No use of cheats or performance altering mods. Telemetry and visual enhancement mods are allowed. Since this is not a docking challenge, you only have to park within a 100 meter distance from the station, with a relative velocity less than 0.3 m/s. Submissions are scored based on how much delta V remains after rendezvous is complete. The Kerbals must not exit the station. Also crashing into the station to slow down is not allowed The time limit is 5 Kerbin years. This is just a technicality since I can't be certain the orbit of the station will be stable 1000 years from now. This is not a super serious challenge so extensive documentation is not really required. Just post an screenshot showing your overall approach, and one after you've completed the challenge showing how much delta V you have left. However, feel free to show your approach in greater detail if you complete the challenge with a small amount of delta V.

DeltaDizzy's Flag Pack This thread has been moved and renamed at @cratercracker's request. The new thread can be found below.

Hello everyone! Kerbal Space Program 1.2.2 is live! Here's the changelog for this patch: =================================== v1.2.2 ============================================================ +++ Bug Fixes * Fix crash to desktop when using Aero Overlay display and Part highlighting in Flight. * Fix one final GUI flickering issue regarding the Parts List Scrollbar. * Fix CommNet occlusion multiplier GUI setting. * Fix to prevent kerbals with existing name being created. * Fix MPL(Science lab) ladder sliding. * Fix Grass textures around Research and Development Facility. * Fix for corrupt save files breaking the resume menu. * Fix where some science experiments only trigger once on action groups. * Fix part action menus remaining on screen when switching to the Astronaut complex. * Fix Building Picker Lines in Space Center not being cleared when application loses focus. * Fix null reference exception when overwriting SubAssemblies in VAB/SPH. * Fix resource converters load percentage display not updating after start/stop. * Fix for several issues with the KSC flagpole outside the Administration Centre. * Fix for vessel on the Launch pad at Baikerbanur (KSC 2) blocking ability to launch vessels from the KSC. * Model fixes to the large drill part. * Fix some more Text overflows in GUI. * Fix where Fairings Disappears After using settings in flight. * Fix for strut connectors attaching below surface on SRB-KD25k. * Fix edge smoothing on Mk1 Inline. * Fix particle effects on drills. * Fix asteroid drill mass calculations. * Fix for selecting/focusing craft that are very late for maneuver nodes. * Fix for contracts app showing the wrong number of contracts. +++Modding Stuff * Add a common base class to all gameevents to allow mods to register and fire their own gameevents. * Add method for searching for gameevents and mods can register to other mods gameevents. * Add title to ResourceInfo so we can have a displayname that's not the key. +++LoadGameDialog When a game is saved it now creates an associated metadata file - called .loadmeta alongside the .sfs. This file contains a hash of the sfs save. When the loadgame dialog opens it will compare the hash in the .loadmeta file with the hash of the savegame, and if so it will use the data in the .loadmeta file for the load dialog details instead of parsing the whole save file. +++Miscellaneous Stuff * Biome refresh for Ike, Moho and Dres. * Add Right-Shift as a default secondary binding for editor scroll when not OSX. * Stop inactive aero/thermal data being shown in the editor scenes. * Add display format to difficulty options values. * Vessels now remember active navigation (Waypoints) when loading save games. * Apply Engineer bonuses to drills and ISRU correctly. * Update more details in DOxygen api docs. Cheers!

Hello people of ksp! I have been having a problem with loading up ksp. its in both 1.2.2 and 1.3, and here are the mods I have: BDArmory, Cameratools, Hullcam VDS and scatterer. How do I post the crash log? thanks.

Hello, I'm running the steam version of KSP and while I am able to run the 32bit version any attempt to start 64bit has resulted in an instant crash before even entering the loading screen. I have attempted to start in clean versions of both 1.3 and 1.2.2 to no avail. I am running 64 bit windows 10 version 1703 build 15063.296 with 16GB of RAM, Intel i7-4790 and a Geforce GTX 1060 SSC with MSI afterburner v. 4.3.0 and Rivatuner at v.6.5.0. 1.3 Crash logs https://www.dropbox.com/sh/aolcfj8fbd9qvy1/AABDny17Kkn5LMP8dYe1SU-ba?dl=0 1.2.2 Crash logs https://www.dropbox.com/sh/pjo20itxn51rlde/AAAxTrAEE9lmh-1CGqyJGOLwa?dl=0 If any other information is needed please ask. *UPDATE* Updated Rivatuner to 7.0.0 Beta 19 and Nvidia driver to 382.33. Issue has subsided, remove at earliest opportunity or leave open for future reference.

So, I finally came back to playing KSP, gradually and carefully built my mod list... only to realize that the game is unplayable with my mod setup (nothing excessive, mind you - all fits under 2Gb). I have not "the latest and greatest" but still a pretty decent CPU, GTX780, 16G ram. EDIT: Removed "observations from prior versions" comment because I did proper testing with 1.1.3 and found that it was just false memory on my part - tendencies are the same in terms of slowness (except that 1.1.3 is ~25-30% slower overall). Now in 1.2.2 (identical behavior in 1.2.9, at least for those mods that work with it) I see huge performance hits. Example: a 300-part airplane on the runway: 1. Full stock: 50fps, down to 35 over ocean (btw, why such a drastic drop in fps, when there is little to render and nothing has changed in physics/parts?) 2. Scatterer: 48-35 fps 3. Scatterer + Kopernicus + SVT: 41-29 fps 4a. SVE + SVT (+EVE, Kopernicus, Scatterer)): 21-12 fps 4b. Same mods, but flying Aeris 3a: 60-44 fps (!!!) 5. KJR only: 31-12 fps (!!) So, these are heavy visual mods and one physics mod, so one would expect a performance hit (even though it was not nearly as noticeable in 1.1.3). BTW, at no point do I get 100% CPU core usage - at most it goes up to ~75%, with a couple more cores at ~25-30%. Graphics is definitely not the bottleneck either (see 1 and 4a/b above). So, what if we install a few essential and light-weight mods that should, in theory, have minimal impact on in-flight performance? 6a. MM, Toolbar, Better burn time, Better time warp, KAC, CCK, CRP, CTT, AGX, EasyVesselSwitch, EditorExtensions, KAS, KIS, MechJeb2, Docking alignment, Vanguard Parachutes, no KJR, same 300-parts airplane: 31-25fps (just a reminder - 50-35fps in pure stock). 6b. Same mods, but flying Aeris 3A: 60 fps (limit!!!). At some point I tended to blame the total memory footprint as being the culprit, but it does not seem to be the case - although total RAM consumption and part count (existing in game, not on vessel on in the scene) does have some effect, it is nothing compared to number of mod DLLs installed. Conclusion: what (tf) is going on here? Why mods that should not work on per-part basis (visual enhancements, utility non-physics mods) slow the game down proportionally to the size of the craft? And even if, for some bizarre reason, they are called on each part, why the execution is so slow for what is essentially just a few lines of code (from my long-past days of hands-on programming, this feels like every call to third-party procedures is wrapped in several layers or extreme debug exception handling - btw, no exceptions reported in the log)? Do you experience something similar, or perhaps you have 200 mods and more than 5GB in GameData folder and yet everything runs just as smoothly as in stock? Either way, please report your experiences here (keep it civil, avoid excessive quoting, and include your rig configuration and specific test results if available).

Hi, I'm playing KSP for 2 months and have Some Experience, But to Some cause, I needed to re-start my Game and Now I'm in Early-Mid Carrer. As in this Phase Many, Build subassemblies for Fast and Effective Missions. Most subassemblies are Launcher. I want to Request our Modders to Create a Mod that creates a Report for a Launcher about its Specification. I.E. Weight, Thrust, Delta-V, Thrust Vectoring, Speed and most Important for Choosing a Perfect Launcher, A Launch Capability Report, about, Weight to Low Kerbin Orbit, Kerbin Stationary Transfer, Stationary Orbit and Trans-Munar and Trans-Minmas Injection Orbit. Plz Recommended An Mod or Create one, Its an Idea for Modders not a Planned Project. Plz ,Thanks

OK. I'm a semi-new player, and i started with ckan because once i found the "advanced tweakables" option in settings, the game got pretty simple... on ALL difficulties. but, I'm still new and with the volume of mods... basically, I'm looking for a "must-have" list of mods that are realism based, add a bit more challenge, and DON'T add too many buttons. the 70 some mods i have are mostly parts (science mostly, but also bases and colonization-type), and seti/umbm/tac... but they seem to rely on other mods that create buttons on the toolbar that get overwhelming at this point. so,.. I NEED YOUR HAAALP! lol

In KSP 1.2.2 there is an extension for GameEvents that allows mods to register their own GameEvents and for any Mod to find and register a callback for said GameEvents. How to use (example): Define your GameEvent as a static in Mod A: public static EventData<Part, ProtoCrewMember> onKerbalFrozen; and Initialize it somewhere early before ModB tries to find and register it. onKerbalFrozen = new EventData<Part, ProtoCrewMember>("onKerbalFrozen"); Find the GameEvent and register a callback in ModB: private EventData<Part, ProtoCrewMember> onKerbalFrozenEvent; ... //in say Awake or Start: onKerbalFrozenEvent = GameEvents.FindEvent<EventData<Part, ProtoCrewMember>>("onKerbalFrozen"); if (onKerbalFrozenEvent != null) onKerbalFrozenEvent.Add(onKerbalFrozen); //don't forget to remove them in OnDestroy: if (onKerbalFrozenEvent != null) onKerbalFrozenEvent.Remove(onKerbalFrozen); Fire your event at the appropriate time from Mod A: DFGameEvents.onKerbalFrozen.Fire(this.part, CrewMember); ModB callback will be called.

I have built my own engines for KSP by the usual methods; Blender, Unity, and then modifying a .cfg file to fit my specific engine. The engines work just great in KSP 1.1.3. However, when I install them in KSP 1.2.2, they have no thrust. They use fuel, produce smoke, and make noise; they just do not have any thrust on the pad and no thrust is computed on the stats in the VAB. I am using a completely stock install of 1.2.2, except for the engines, which are in their folder under GameData. Here are two photos of the same part in action in both versions. Here is my .cfg file: PART { name = hybridFirstStage module = Part author = Peter Balholm, after Kartoffelkuchen mesh = model.mu rescaleFactor = 0.7 node_stack_top = 0.0, 33.42, 0.0, 0.0, 1.0, 0.0, 1 node_stack_bottom = 0.0, -4.4, 0.0, 0.0, -1.0, 0.0, 1 TechRequired = start entryCost = 0 cost = 2000 category = Engine subcategory = 0 title = Hybrid First Stage Engine manufacturer = Sarawak Tank Company description = A hybrid rocket engine which can be clustered to build the first stage of the Cassandra rocket. The oxidizer tank is bamboo plywood and holds nitrous oxide pressurized with gaseous oxygen. The fuel is paraffin wax and powdered aluminum. The sea-level nozzle made of Baekelite reinforced with asbestos fiber. // attachment rules: stack, srfAttach, allowStack, allowSrfAttach, allowCollision attachRules = 1,1,1,1,0 // --- standard part parameters --- mass = 3.33 dragModelType = default maximum_drag = 0.2 minimum_drag = 0.2 angularDrag = 2 crashTolerance = 7 breakingForce = 200 breakingTorque = 200 maxTemp = 3600 RESOURCE { name = LiquidFuel amount = 6012 maxAmount = 6012 } RESOURCE { name = Oxidizer amount = 24048 maxAmount = 24048 } EFFECTS { running_closed { AUDIO { channel = Ship clip = sound_rocket_hard volume = 0.0 0.0 volume = 1.0 1.0 pitch = 0.0 0.2 pitch = 1.0 1.0 loop = true } PREFAB_PARTICLE { prefabName = fx_smokeTrail_veryLarge transformName = smokePoint emission = 0.0 0.0 emission = 0.05 0.0 emission = 0.075 0.25 emission = 1.0 1.25 speed = 0.0 0.25 speed = 1.0 1.0 localOffset = 0, 0, 1 } MODEL_MULTI_PARTICLE { modelName = Squad/FX/ksX_Exhaust transformName = thrustTransform emission = 0.0 0.0 emission = 0.05 0.0 emission = 0.075 0.25 emission = 1.0 1.25 speed = 0.0 0.5 speed = 1.0 1.2 } } engage { AUDIO { channel = Ship clip = sound_vent_soft volume = 1.0 pitch = 2.0 loop = false } } flameout { PREFAB_PARTICLE { prefabName = fx_exhaustSparks_flameout_2 transformName = smokePoint oneShot = true } AUDIO { channel = Ship clip = sound_explosion_low volume = 1.0 pitch = 2.0 loop = false } } } MODULE { name = ModuleEnginesFX thrustVectorTransformName = thrustTransform engineID = AJ-26-62 runningEffectName = running_closed exhaustDamage = True ignitionThreshold = 0.1 minThrust = 0 maxThrust = 924 useEngineResponseTime = False engineAccelerationSpeed = 20 heatProduction = 400 fxOffset = 0, 0, 1.5 PROPELLANT { name = LiquidFuel ratio = 0.4 DrawGauge = True } PROPELLANT { name = Oxidizer ratio = 1.6 } atmosphereCurve { key = 0 345 key = 1 268 } } MODULE { name = ModuleGimbal gimbalTransformName = AJ-62_Engine_Nozzle gimbalRange = 4 } MODULE { name = ModuleAnimateHeat ThermalAnim = --None-- } MODULE { name = ModuleAlternator RESOURCE { name = ElectricCharge rate = 8.0 } } RESOURCE { name = ElectricCharge amount = 0 maxAmount = 0 isTweakable = false hideFlow = true } }