KerbalBK

When KSP2 first launched into early access we DID have a proper orbital camera view that acted just like KSP1’s! You can see this around 31:50 in Scott Manley’s launch stream; I’ll link it below. After the 2nd or 3rd EA update is when I remember this disappearing. I’ve made a bug report about it before and so have one or two others since it disappeared. I believe Celestial mode in KSP2 is supposed to be what Orbital mode is in KSP1 I’ve figured out two “workarounds” that allow me to fake a proper orbital view: 1) using Capture mode and then manually adjusting the camera with the numberpad controls. 2) using Body mode and having my craft lock to the “Normal” orientation on the navball. It’s frustrating to not have a proper orbital view, so I really hope this gets fixed.

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel Core i7-7820X | GPU: AMD Radeon RX 6600, 8GB | RAM: 32 GB Landing legs in 0.2.0 don't seem to be working quite right. I discovered this after landing on the Mun with the tiny landing legs on a probe, and when deployed the feet of the legs hovered above the ground no matter what I tried to do. Tiny landing legs: After being deployed, the feet sit visibly hovering above the ground. Small landing legs: When pre-deployed from the VAB, the feet of the small landing legs are at an angle. This is fixed when you retract them and re-deploy. Medium landing legs: When pre-deployed from the VAB, the feet are also at a weird angle. This is fixed when you retract and re-deploy. Large landing legs: When pre-deployed from the VAB, everything seems ok. After retracting and re-deploying, the legs along with the entire craft bounce off the ground after the deployment is finished. In addition, all the landing legs seem to have an unnatural looking glitch/stutter moment at the end of deployment/beginning of retraction. All of this is very repeatable. Just put landing legs onto any kind of structure, launch the "vehicle" and test out for yourself. Included Attachments: KerbalSpaceProgram2_TinyLandingLegIssue.mp4 .ipsImage { width: 900px !important; }

This has happened to me, except I don't even see a Ap or Pe indicator when this happens. I'm on v0.1.4.1, no mods. Nothing seems to fix this for my craft that is currently affected. I've tried going to the KSC, then back to the tracking station to take then control of my craft. I've tried saving and exiting out of the game entirely. And just going to tracking station and then back to craft. I did some investigation and found some interesting things: My save opens up straight to the craft in flight. If I go straight to the tracking station and back to controlling the craft, it continues to follow along its trajectory (even though I can't see what that is in map view). BUT if I go to the KSC and then back to the tracking station and take control of the craft, the craft heads straight downward towards Kerbin like all momentum was lost. This is repeatable. Either way I go to the tracking station (straight from flight or from KSC) the craft's state says "landed" in the tracking station. It seems like, at least for me, the game believes the craft is landed and therefore is not showing a trajectory line. In the screenshot example below I wasn't even in orbit yet, just suborbital: I would like to be able to provide a save file, I'm just not sure how to do that.

I’ve been experiencing this for a while. It is still occurring as of 0.1.4.1 for me. I haven’t seen any chatter about this in the forums. It seems to be widespread though, because this happens in any videos I’ve watched from KSP2 content creators in the past several months. Here’s my bug report:

Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel Core i7-7820X | GPU: AMD Radeon RX 6600, 8GB | RAM: 32 GB Expected behavior: Once orbit has been reached, the camera orientation changes as to appear looking at the craft & planet from a sideways view, not top-down. In other words when holding the right mouse button and dragging, the camera should pivot about the radial in/radial out axis, in line with a 0 degree inclination orbit. This should happen in auto camera mode, as well as celestial. This expected behavior is how KSP 1 behaved. I remember this occurring in earlier KSP 2 versions as well. An example of this is at the 31:50 mark KSP2 livestream video: Observed behavior: The camera orientation does not adjust once reaching orbit while in auto camera mode. Cycling through the various views does not bring me to the desired camera view. Holding the right mouse button and dragging while in auto or celestial camera mode has the camera rotating around the normal/anti-normal axis, perpendicular to a 0 degree inclination orbit. Below is a video of my experience in 0.1.4. I made sure I was in Auto camera mode, and when I reached orbit at 0:18 you can see a notification in yellow appear saying "auto: orbital" . Unlike in Scott Manley's video, however, my camera orientation did not change. Azt8f8s.mp4 Steps taken to fix: I have tried deleting my saves & starting new ones, re-downloading KSP 2, Making sure I am on auto camera mode before launching. Getting different crafts into orbit. Nothing is fixing this issue. To be honest I remember this issue starting around update 1.3, but I never saw any bug reports about it so I figured maybe it was just me and that the next update would fix things for me. This is an annoying bug that makes it frustrating to go from one celestial body to another, which is one of the core gameplay loops.

The magboots are a cool feature, letting your kerbal walk on the side of your spacecraft. I don't always want this to automatically happen when I'm close to the side of my spacecraft, however. Maybe make it a pop-up alpha key function option like boarding a spacecraft is. Honestly the first time this happened I thought it was a bug, and didn't know it was a "thing" until reading about it in the forums.

All good suggestions. Being able to save "favorite" colors & color combos, copy & paste colors onto other parts, being able to see the color values, etc. I've thought all of these things every single time I'm making a new craft in the VAB. These would all be worthwhile things for the devs to implement. This would make customization so much easier and consistent!

KSP version: 0.1.1.0.21572 Icons in the tracking station become more obstructed by a celestial body the closer you zoom into a celestial body. This makes it hard to see where crafts, etc. are in the tracking station. OS: Windows 10 Pro, Version 22H2 CPU: Intel Core i7-7820X @ 3.60GHz, 8 cores RAM: 32GB DDR4 GPU: 8GB VRAM, AMD Radeon RX 6600 GPU driver: 23.2.2 Screen Resolution: 1920x1080

Yep, not a mod issue. I don't have any mods. Same problem. KSP2 version: 0.1.1.0.21572 OS: Windows 10 Pro, Version 22H2 CPU: Intel Core i7-7820X @ 3.60GHz, 8 cores RAM: 32GB DDR4 GPU: 8GB VRAM, AMD Radeon RX 6600 GPU driver: 23.2.2 Screen Resolution: 1920x1080

This is still an issue for me after downloading the first patch, 0.1.1.0.21572 My specs: OS: Windows 10 Pro, Version 22H2 CPU: Intel Core i7-7820X @ 3.60GHz, 8 cores RAM: 32GB DDR4 GPU: 8GB VRAM, AMD Radeon RX 6600 GPU driver: 23.2.2 Screen Resolution: 1920x1080

I spent some more time in the save file from my post two days ago in this thread & found a solution (well, more of a workaround than a solution): Issue: My save would open up in the VAB, probably because that's where I had saved it last (I don't remember at this point). Immediately upon the save opening in the VAB it loaded with the workspace I had made that caused the bug. I tried taking away each part one by one, saving the workspace as a new name (which could not be loaded even when I supposedly saved it. Only the stock workspaces were available to load), & exiting to the KSC to save my save file as a new save. When I went back to the main menu, the save I had just created was not there. Attempting to load the save with this "corrupted" craft now ended in me being stuck on the main menu screen without the UI to select anything. I did this for every part of my "corrupted" craft, force-quitting KSP2 using the Task Manager every time I got stuck on the main menu screen. None of these attempts worked I also tried just trashing the entire craft itself, exiting the VAB & then doing the rest of the same like I described. This didn't work either. Also, I could load the stock workspaces but could not launch them. Solution: I already had a craft in orbit. After loading my save file again, exiting the VAB without saving (I went back to check if I could load any workspaces, & only the stock ones were there as options to load), I went to the tracking station & took control of my craft in orbit. I then went back to the KSC, and then back to the VAB. I could now load any of the workspaces I had worked on previously! NOTE: Going straight to the VAB from taking control of my craft in orbit did not bring my workspaces back. Only going from my craft in orbit, to the KSC, and then to the VAB worked. I tried duplicating this more than once and I was able to every time when taking the steps I just mentioned. KSP2 version: 0.1.0.0.20892 OS: Windows 10 Pro, Version 22H2 CPU: Intel Core i7-7820X @ 3.60GHz, 8 cores RAM: 32GB DDR4 GPU: 8GB VRAM, AMD Radeon RX 6600 (XFX Speedster SWFT210) GPU driver: 23.2.2

Same thing here. Bug description: Radially attached parts are becoming more and more offset from the center of the craft body once in flight for an unknown amount of time. The actual center around which they are radially attached seems to be offsetting, which then offsets the parts. This has gotten worse over time after doing other things in KSP2, letting time pass and then going back to the craft. First time I noticed this happening, the radial parts on the side of the craft that were "sinking in" to the craft were still somewhat visible: This was the opposite side of the craft, where the radial parts were offsetting away from the craft: After doing some other things in KSP2, discovering more bugs, & coming back to KSP2 after exiting it for a while, these radial parts had offset even more: As you can see, now the radial parts that were offsetting into the craft were no longer visible & were truly inside the body of the craft: As for the opposite side, those radial parts were even further away than before: Oh and poor Bill Kerman can't exit the craft either because one of the offset batteries is blocking the hatch. This means the parts are also offsetting upwards a bit, which is visible in my screenshots. I did manage to get this craft, which is the upper stage of the stock K1 rocket, to an orbit around the Mun. So that means the craft is still functional at least. Certainly less game-breaking than other bugs I've encountered or read about, but still not good. KSP2 version: 0.1.0.0.20892 OS: Windows 10 Pro, Version 22H2 CPU: Intel Core i7-7820X @ 3.60GHz, 8 cores RAM: 32GB DDR4 GPU: 8GB VRAM, AMD Radeon RX 6600 GPU driver: 23.2.2

I had a very similar thing happen, except it happened after I reverted a craft I made back to the VAB from the launchpad. After reverting, I could not launch my craft, save it, or load any workspaces I had made (only stock ones could be loaded) because they were all seemingly gone. I then decided to save my game file, exit KSP2, & come back. I found that I could not overwrite the save file I was in because it was NOT THERE as an option to do so. Instead, only one save file was there to overwrite, & it was named Vessel Unavailable: The current game save I was in was called "main save", so I decided to try saving as "main save 2" & exit KSP2 & come back. I did that, came back. "main save 2" was not there at all, but "main save" was. However, it had a subtitle that said "vessel unavailable". So did all of my other saves, which were autosaves: I could load into all these saves except "autosave_1" for some reason, which just resulted in me being stuck on the main menu screen like this without any GUI options to choose from (this was a repeatable issue): All the other saves, once I loaded into them had the same result. Only stock workspaces were there, none of the ones I had created since Early Access launch a few days ago. I have not tried to dig any further than this. My specs: OS: Windows 10 Pro, Version 22H2 CPU: Intel Core i7-7820X @ 3.60GHz, 8 cores RAM: 32GB DDR4 GPU: 8GB VRAM, AMD Radeon RX 6600 (XFX Speedster SWFT210) GPU driver: 23.2.2

Same here KSP2 build: 0.1.0.0.20892 OS: Windows 10 Pro, Version 22H2 CPU: Intel Core i7-7820X @ 3.60GHz, 8 cores (Turbo Boost & Hyperthreading disabled for other software) RAM: 32GB DDR4 GPU: 8GB VRAM, AMD Radeon RX 6600 GPU driver: 23.2.2 Storage: KSP2 is stored on a Samsung 980 PCIe x4 Gen3 M.2 NVME SSD Screen Resolution: 1920x1080