WhereAreTheBathrooms

Hey all, I'm trying to save telemetry data so I can display it in Google Sheets but I'm struggling to figure out how to convert the saved .json to .csv - Sheets does not accept .json formatting for data imports. I have no experience doing this so I don't even know where to start. Online converter tools spit out essentially garbage, or I assume, the data but in a completely different shape to what I need. Can anyone tell me where to begin? Or link a tutorial for this kind of thing?

Replying in case this is the thread they're looking at for feedback on this intended decision (as stated in K.E.R.B. 12/01/2024). I agree with most here that signal occlusion is a really important feature. At the risk of sounding reductionist, there do seem to have been a few decisions made to dumb down KSP. It's fine, but this ought to be a setting, because I know a lot of folks who play this game, myself included, who really enjoy the little realism challenges that come with features such as signal occlusion and CommNet in general. These are features which add to the game, not detract from it. They add a very real depth to the game and increase its replayability by a significant margin. Geostationary satellites are pointless now, despite there being a mission to put one in orbit. It was a disappointment when I found this out, because the game is a little shallower for it.

He's talking about TOOBs, the tubular fairing parts in the game. I agree so much with the OP. Everything needs the option to be precise. KSP is a game that lends itself so well to both ends of the math spectrum - none of the math, and ALL the math - and not being able to be precise with things like fuel fill, part size, etc., makes the game less appealing to people on the latter end.

Appreciate the helps, unfortuantely no change of any wheel values fixes the problem. The center of mass was too far back for the aircraft to take off but it still spins out around 40ms-1 even after making the aircraft flight-worthy. In the video above you can see that this behaviour can't be intended. It looks ridiculous :p

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 Home 64-bit (10.0, Build 19045) | CPU: AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs) | GPU: NVIDIA GeForce RTX 4090 | RAM: 32768 MB Severity: Medium. VERY irritating, but not game-breaking. Frequency: High (consistent) Description: Letters in flag names as you're naming them switch case according to the case of the name's other letters. Makes many names impossible, such as 'Kerpollo III' as I tried in the attached video. When you fix this, please also add the ability to rename flags from tracking station, so we can rename the flags we've had to name badly due to this bug. Included Attachments: KerbalSpaceProgram22023-12-2718-06-06.mp4

This is also happening to me, it sorta defeats the purpose of the LES if you can't also attach a decoupler to the abort action group

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 Home 64-bit (10.0, Build 19045) | CPU: AMD Ryzen 7 7800X3D 8-Core processor (16 CPUs) | GPU: NVIDIA GeForce RTX 4090 | RAM: 32768 MB Severity: Medium, taking off earlier avoids it but some planes can't do that Frequency: High, no settings seem to eliminate the problem Description: Just as was once an issue in KSP1, aircraft simply moving forward on the runway begin wobbling for no apparent reason, eventually spinning out. SAS on or off (SAS on is worse), high or low wheel friction. To reproduce, all I do is load the craft onto the runway, activate the engine, and provide no input, and the wobble begins at around 35-40ms-1. Seems worse on some craft than others, but always prevalent to some extent for me. Included Attachments: KerbalSpaceProgram22023-12-2311-48-35.mp4 PeregrineMk2.json

I don't think this is how a new player with a burgeoning but still rudimentary grasp of the concept of an SOI will read the situation. I agree with OP that the game presents the impression during the Mun missions and tutorials that entering the Mun's SOI means leaving Kerbin's, and that the mission objective should therefore clarify that the vessel must enter Kerbol's SOI exclusively.

I think they got this confused with a secondary mission which requires you to plant a flag on a mare.

For context to add to the post, I play at 2560x1440

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 Home 64-bit (10.0, Build 19045) | CPU: AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs) | GPU: NVIDIA GeForce RTX 4090 | RAM: 32978 MB Severity: Medium, could conceivably cause disaster but hasn't for me so far Frequency: low? so far? I've only noticed it once but I've also only looked properly at the altimeter once, so it could be happening all the time for all I know Description: See in the attached video, while my craft is orbiting above Kerbin's seas, I expect to see ground and sea altimeter display the same value, the craft's height above sea level, or, alternatively, the ground altimeter should show a higher value than the sea altimeter, reflecting the craft's height above the sea floor (would be weird but at least makes sense). Instead I see the ground altimeter displaying a lower number than the sea altimeter, suggesting I am above ground - judging by the way it rises and then falls, hilly or mountainous ground. However you can see my craft is orbiting above the ocean, so this doesn't make sense. Am I being dense and missing something obvious? Included Attachments: KerbalSpaceProgram22023-12-2120-31-31.mp4

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 Home 64-bit (10.0, Build 19045) | CPU: AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs) | GPU: NVIDIA GeForce RTX 4090 | RAM: 32978 MB Severity: Medium, doesn't seem to cause any damage or escalate too much but pretty unnerving. Frequency: High, happens every time I do this. Description: When a Kerbonaut goes on EVA from the Mk1-3 "Gumball" command pod, then climbs down the ladder to the bottom, they stop moving as expected but at this extreme the craft begins oscillating for no apparent reason. It does not occur when climbing to the top of the ladder, and the craft stops shaking when the Kerbonaut moves away from the bottom rung. It seems to impart some force on the craft, as in the attached video, with SAS off the craft begins a sudden rotation when the Kerbonaut goes on EVA. It still happens if SAS is on. Included Attachments: KerbalSpaceProgram22023-12-2120-32-56.mp4

Just completed this mission and can confirm, pretty egregious. Also, the mission does not at all mention actually needing a ladder on your craft when you read it in MC. I included a ladder on my probe, so I don't know if it's actually necessary to complete the mission or not. but it isn't in the mission tracker app.

This is actually a problem with most games, it's a limitation of how the hunger system works, devs can only do so much unfortunately. I've found having a really good setup is the only way around it, by incorporating an IV drip into your gaming rig you can have a constant feed which sates your hunger while you play. But it's a shame this kind of thing is so innaccessible due to the cost. It also requires you to give up flavour, but I haven't found that to be an issue when the trade-off is playing KSP non-stop. Seems like an easy choice to me.

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 Home 64-bit (10.0, Build 19045) | CPU: AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs) | GPU: NVIDIA GeForce RTX 4090 | RAM: 32978 MB Severity: Medium, some of this information can be really helpful for planning a flight/manoeuvre but if it's incorrect it's worthless Frequency: High, any time you open this screen Description: The information shown for planets in the tracking station is quite bad. For Kerbin, for example, in Orbital Characteristics, the sidereal period is displayed as 9,204 k/m/s. Kilometres per metre per second is not the appropriate unit of measurement for an orbital period. It should be in seconds, or days given its scale. The figure itself is probably correct, but for some reason the unit is absurd. It would be nice to see the planet's apses in addition to its semimajor axis. Useful information for bodies in elliptical orbits. In Physical Characteristics, gravity is shown as 1.00 m/s2 which of course should be 1g or 9.81 m/s2 (or 9.81ms-2 but that's a matter of taste). Circumference is shown as 7.56 AU (sic). I don't know what that's supposed to mean here. Even using the ingame 'AU' equivalent it's way off of the actual figure, 3.769Mm. Atmosphere is shown to be 1.22 atm, which doesn't make much sense either. AFAIK atmospheric pressure on Kerbin at sea level is the same as on Earth so it should be 1 atm in that case. If that's changed fair enough, although it's a little weird to use Earth's 'atm' baseline for Kerbin. It would be confusing to use 'atm' ingame if it doesn't refer to Earth's 'atm', however, so it might be better to just use kPa here. These are not all the problems in this part of the Tracking Station screen, there are others. This issue was raised on the forum back in March but the forum told me to consider starting a new thread instead of necromancing that old one, so I did. Included Attachments: .ipsImage { width: 900px !important; }