jimmymcgoochie

Kerbalism counts anything above 90kPa as fully pressurised, not entirely sure if that also applies in RO but I haven’t seen anything that says it’s not so you should be fine for a while. Have fun with that lander!

It's Tylo time! Except it's also Pol time, so a carefully choreographed ballet of undockings and re-dockings were required to assemble the Tylo lander and send it off to Tylo while the Eve lander was sent off to Pol: The trip to Tylo was timed to perfection- it's right on the edge of Jool's outer radiation belt and half of the surface and orbit will be radiation-free. The landing was difficult due to the high orbital velocity and delta-V requirements, but eventually successful. The ascent was fairly routine, right up until the fuel ran out and Connor had to use RCS to circularise then wait for the Ion Space Tug to do the rendezvous before he docked to it. There was a complication during the escape burn as one of the Hall effect thrusters spontaneously exploded, with no warning and well within its operational limits, but that won't be too much of a problem. It'll take about 60 days (one single orbit of Jool) to get a burn back to Indefatigability, but the ISTs have nearly a year of supplies each so that won't be an issue even if a stress breakdown happens. Over at the other IST, Phoebe and the Eve lander were approaching Pol for a much easier landing. I wanted to do that landing in this report too, but a combination of game glitchiness and my internet connection going out yesterday meant I haven't done that yet. Full album: https://imgur.com/a/OoCBjua Flag count so far: 6.

You could try using MechJeb or KER to get delta-V read outs, they seem to work when the stock one sometimes doesn’t, but if all else fails just calculate it yourself: delta-V = ISP * standard gravity * natural log (ln) of wet mass / dry mass. ISP and standard gravity are fixed and known (800s and 9.807m/s/s respectively) so that half of the equation is always 7845.6m/s; you can get the dry and wet masses in the VAB or in flight by enabling the ‘start mass’ and ‘end mass’ options in the stock delta-V widget, which shows them in each stage.

Can you provide a video of the problem? Or if not, some screenshots of the rocket at the point where the stage separates, with the PAW (right click menu) for the second stage engine pinned open. Which engines have you tried? Check your MechJeb settings to ensure that you have ‘prevent unsafe ignitions’ on so that engines only start when 100% ullaged, and that you’re using the right propellant mix for each engine or RCS thruster. Check your avionics limits too, if your rocket is too heavy for the avionics then you won’t have control. It might be worth getting the most recent master branches of RO and RP-1 from GitHub and installing those, as there might be a bug fix for the problem you’re having. If none of that helps, ask in the RO/RP-1 discord channel as you’re more likely to get help there than here on the forums.

Put a plane on Lua! Sure, the atmosphere is tenuous at best (about 0.1atm IIRC) but it’s oxygenated and should be just about usable for flying. Think of the science!

There’s your answer. Try using RSSVE, or EVO if your PC is up to the task: https://github.com/KSP-RO/RSSVE or

I’m interested to know this too. @ShuttlePilothow do you re-root a craft in flight?

A few reasons- there’s a lot of stuff being carried around just for Jool (Laythe plane, Tylo landing stage and heavily-shielded Vall lander) that I can get rid of to improve range and/or TWR on Indefatigability; transfer windows don’t align very well for Eve>Duna>Jool>Eeloo, I’d arrive at Jool too late to do all the landings and then catch the ideal Jool>Eeloo alignment; Jool has some of the biggest hazards and trickiest landings in the whole system- Laythe and Vall are serious radiation threats and Tylo requires massive delta-V- so I’d rather get that out of the way as soon as possible; and the sooner I get to Jool, the less chance there is for critical parts to break and cause the whole mission to fail.

@fourfathat looks exactly like Restock and Restock+ which does have the single Boar engine. Logically, the closest thing to a single Boar without mods would be the KE-1 Mastodon since that’s the F1 analog, but that’s Making History DLC and also significantly more than half the thrust of the Twin Boar. If more thrust is required, use the Vector, Mastodon or even Mainsail which have progressively more thrust but lower ISP; if less thrust is needed use the Skipper if you can get away with it, it has better ISP than the others but 2/3 the thrust of the Vector (and ~1/3 of a Twin Boar).

If you’re running the latest version of scatterer, try downgrading to the previous version. I’ve had some issues with the newest scatterer including weird low-res shadows and other effects looking off, quite similar to what you’ve described, running in KSP 1.11.2 with EVE and scatterer (and Spectra rather than the default EVE configs), rolling back the scatterer version completely resolved it.

Sounds a lot like this issue: Maybe the same solution will work for you?

You’ve installed mods into the Steam copy of KSP. Don’t do that- Steam loves to meddle and has a habit of corrupting stuff when mods are installed, leading to game crashes. This might not be the cause here, but it never hurts to rule that out plus keeping modded copies of KSP separate from Steam means you can get game updates without breaking all your mods. If you’re using CKAN to install your mods, which looking at the number of mod folders in that list I really hope you are (managing all that by hand will be a pain!), try this: Save your installed mods as a mod pack in CKAN, which will allow you to quickly reinstall them later, and save that somewhere e.g. desktop; Copy your save games from KSP/saves and keep those somewhere e.g. desktop; Clear all mods from your Steam copy of KSP; Using Steam, disable cloud saving for KSP, then verify the KSP game files (right click KSP > Properties > Local files > verify integrity of local files) which will check the game files and fix anything that’s not right; Run KSP and make sure it works with no mods; If it works, copy KSP entirely from steamapps/common and paste it somewhere else outside the Steam folders. Add the new copy to CKAN and reinstall your mods using that saved modpack, then add your saves back in and fire it up.

Logs please! A mod list would also help, but logs are pretty much mandatory for any “game failed to load” problem.

I think the problem is that the root part of the rover is a physicsless part which confuses the whole game. Re-root the rover/skycrane assembly in the VAB so that the root part is the rover’s probe core and then cheat it out beside the broken one, then delete the broken one.

A pretty uninteresting trip from Eve to Jool, parking up in a nice high orbit (similar altitude to Bop but less eccentric) to visit the five moons in due course. First up will be Tylo in just 10 days, and in a position where it’s right at the edge of Jool’s outer radiation belt too so minimal exposure for whoever I send down there.

It's time to say goodbye to Eve... And hello to Jool! There were some inevitable part failures along the way, but nothing too critical- the main reaction wheel on one of the Ion Space Tugs failed permanently but I have spares that can be attached radially; the motor on one of the graphene radiators failed, but they don't actually move so no biggie; and a few other parts needed repaired or serviced. Connor hit 100% stress and broke that radiator motor, but Phoebe had a breakdown at just 32% stress and dumped about 4 years' worth of food which isn't ideal. Water and oxygen, I could live with as I can recycle both, nitrogen is no biggie and dumping CO2 or ammonia is fine as they're waste products, but food is the one thing I can't make any more of. During the maintenance EVA I also dumped a load of empty xenon tanks: The capture burn was completed with the VASIMR engines at 100% efficiency, meaning it took over an hour of game time but the ship was stable even at 8x time warp. The resulting orbit is high- beyond the orbit of Bop for the majority of each orbit- and a bit off-plane with the inner moons, but safely above the furthest reach of Jool's radiation belts a.k.a. The Death ZoneTM and I can easily adjust it if necessary. There's a nice window to get to Tylo in ten days which will catch that moon when it's right at the very edge of the outer belt, giving plenty of time to do the landing and then get out again without any significant radiation threat. There's also a Pol window in 10 days, and a Bop window in... 62 years!? MechJeb, you and I need to have a conversation about some of the nodes you've been plotting lately Full album: https://imgur.com/a/vCmAI29 Flag count so far: 5.

Sounds like something is causing a problem during the loading process. To tell what it is, we need the log files. The easiest log to find is KSP.log, you’ll find it inside the KSP main folder (if you downloaded KSP via steam it’s in steam/steamapps/common/Kerbal Space Program, otherwise it’s wherever the installer put it). There’s a more detailed log called Player.log, but it’s harder to find so for now just get hold of KSP.log, upload it to a file sharing site and post a link to the file here- please don’t copy and paste the contents of the log directly into the forums, it’s a real pain to look at especially on a tablet or mobile, as I currently am. If you got KSP on Steam, you could also try verifying the files- right click KSP in your Steam library, click ‘properties’, then the ‘local files’ tab, then ‘verify integrity of local files’ which should find out if you have any missing or corrupted files and re-download them; it might fix the problem. If that doesn’t solve the problem, read this and see if anything helps: https://forum.kerbalspaceprogram.com/index.php?/topic/83213-stock-support-bug-reporting-guide/

Grab one of the backup persistent files (in saves/your save name/backups), paste that into saved/your save name and rename it persistent.sfs, that should salvage it but you’ll lose a bit of progress.

Depends very heavily on what I’m playing- just spinning up base KSP on my SSD takes about a minute, but booting up my RP-1 save on the same SSD takes about 10-15 minutes depending on various factors like “is it an odd-numbered day of an even-numbered month that begins with a T or an S”…

Nope. Assuming copies of such ancient versions of the game still exist, they'll be slow, clunky, barely functional and generally rubbish compared to the new version which will be bigger and better in pretty much every way. A significant number of players (I'd suggest a sizeable majority) never played KSP back then and have no interest at all in playing it when instead they could play the version that's had a decade of improvements and additions. Take off those rose-tinted glasses and focus on the brand new update that's about to arrive.

Looks like a glitch in a graphics mod, but without any more information it's impossible to say what could have caused it or how to fix it. At the very least, your version of KSP and a list of mods are needed, and having the log files might help too. Here's how to get those:

Moho is a pain to get to- a very low, inclined and eccentric orbit means delta-V requirements are very high- and when you get there it's not even that interesting. Still, at least this time I actually got there! The first time I tried, Connor hit 75% radiation exposure before getting half way to Moho; second time round I nicked one of the active shields from Indefatigability which made all the difference- he arrived at Moho with 0% exposure, but the delta-V for the Moho Space Tug tanked substantially due to the considerable extra weight. Burn times with ion engines are extremely long, good thing I can push physics warp up to 20x to make it happen a whole lot faster. Landing was uneventful and soon enough the flag was planted, sample taken and science gathered: And then it was time to go back again. Fortunately the Moho>Eve window was open as soon as Connor arrived, but unfortunately there was no way to make the ~4500m/s escape burn inside Moho's SOI without crashing into it. This required a very long course correction in solar orbit which used up most of the remaining xenon, but got an Eve intercept with mere days of oxygen left; the oxygen supply was the main limiting factor on this trip due to my not checking how long an Eve-Moho round trip would take. After arriving, the Moho Space Tug tried valiantly to get an intercept of Indefatigability but ran out of fuel. Connor swiped some useful parts- solar panels, capacitors and monopropellant tanks- before the Space Tug arrived to take him back to Indefatigability. 92% stress from that trip, but amazingly not a single stress-related incident; 14% radiation exposure which can be healed away during the trip out to Jool. The shield is now attached to the front docking port of the ship since you can't attach parts if they clip into other parts in EVA construction mode, while the solar panels are still attached to the Tylo lander for now to get better exposure. Full album: https://imgur.com/a/xcqG7op Flag count so far: 5, and I made it to Moho this time unlike with Intrepidity.

A long and arduous trip from Eve to Moho. Despite leaving with a mildly preposterous 33km/s of delta-V I still ran out during the final rendezvous around Eve and had to send out a rescue mission to bring the wayward lander back to the mothership. With barely a day's worth of oxygen left too!

In an attempt to bring this thread back from the brink of moderation and return it to the original topic... I use Texture Replacer in pretty much every save I do to make my Kerbals look different from each other and more like individuals as a result. Generic male and female faces that look exactly the same are boring and make them look like nothing more than clones, and it's not like the game doesn't already include different looking Kerbals- look at Gene's blond hair, Walt's beard stubble or Wernher's moustache- so why shouldn't the Kerbals that go on missions look different from each other too? I don't care if they're lime, chartreuse, olive or viridian or if their hair is brown, black, blond or retina-searing purple as long as I can look at them and they aren't copy-pasted duplicates of each other.

When you’re all quite finished with the melodramatic “nooo KSP is dead! waaaah “ nonsense… Nonody is going to delete KSP off your hard drives, or remove the ability to download it, or shut down the many, many mods that can now be updated for the last game version and then focus on their own content instead of worrying about game updates. Or not- there are plenty of people still running much older versions of KSP because they use specific mods that haven’t been updated beyond, say, 1.3, so why would it be any different once 1.12 is released? Besides, as final updates go adding stock KAC and stock transfer planner is a good way to go out with a bang.