Anth

@Douces Changed the title. @Quasar2007 Thanks for the additional information. Developers know about the issue. Hopefully will be fixed in 0.1.5.0

Your video card is under minimum specs. I recommend trying the following: Change your resolution to minimum Avoid loading saves that are in Low Kerbin Orbit

Hi @Abelinoss

@Filed.Teeth and @DoomsdayDuck555 Merged your bug reports with this one . @Davidian1024 Changed title to include both the text increasing and decreasing in size, and now this bug report has got a significant boost in upvotes.

Needed to be the Kerbug

Being anything else other than the native resolution has caused issues with that area in the VAB. I wonder if KSP2 knows that even when you set both windows and KSP2 to 1440p Good to know. Thanks. If you do look for duplicates, I recommend doing a few searches in the archive as well as the main public area. I wouldn't do anything more than maybe 5 minutes of searching though. If an original bug report is missed after a short search, so be it. I don't want people spending so much time looking for existing bug reports that they lose motivation to report the bugs themselves.

@Filed.Teeth Good to see you around. Its been a while. Can you tell me what resolution that was happening at?

@Abelinoss and @NovaRaptorTV Merged your bug reports with this one. @QwertyHpp Changed the title so I could combine Wings and Fairings into one bug report.

@Spacefan101 There's an issue with the SWERV where while using timewarp its position will change on the craft. Weirdly I had it happen with a poodle today. It was so far off center that the craft just spun around and around. Saving and loading can counter the issue. Is that what possibly happened in your situation?

If its limited to only one craft then its not the same issue. This bug report is for every trajectory that is missing including planets.

@The Aziz Merged with this one.

@Vortygont Changed Control Station to Tracking Station and added Note: as a title to your the conclusion. Tested it. Confirmed.

I am pretty sure that they are what are called physicless parts. Something about their statistics is added to the part they are connected to. So I am guessing that KSP2 is very upset when one physicless part cant add its statistics onto another part.

Reported Version: v0.1.4.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: i9 9900K | GPU: 3070ti | RAM: 32GB Issue: Auto-hide Navball in Mapview set to On, turns it Off. Auto-hide Navball in Mapview set to Off, turns it On. Video Evidence: https://youtu.be/r7evCgU2X1I (31 Seconds) Credit for putting Jeb behind Bars in the Video: @Suppise

@Vortygont The following bug report has nothing to do with the throttle:

@The0Frank Those small cubes that make up the rover are most likely what are causing that issue.

@Kersifal Thanks so much for all the information you supplied. The following is a bug report I did based on my investigation of yours:

Reported Version: v0.1.4.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: i9 9900K | GPU: 3070ti | RAM: 32GB Video Evidence: https://youtu.be/IKrnvUrdGm0 (22 Seconds) Steps to Replicate: Load Rhino70000PlusTestSave.json Deactivate Engine (It will say Activate which isn't correct) F5 F9 Activate Engines Full Throttle Timewarp Error Spammed in the Log File: Log File: Ksp2.log Additional Information: I found this issue by investigating the following bug report: Identical error spams in the log file as above. Save File from their Bug Report: quicksave_4.json Replication Step: Timewarp once loaded. Credit: Thank you @Kersifal for supplying the necessary information needed to test the issue.

Reported Version: v0.1.4.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: i9 9900K | GPU: 3070ti | RAM: 32GB Video Evidence: https://youtu.be/TCwRwmZvKMU (20 Seconds) Steps to Replicate: Load TargetCraftPlanetTestSave.json Undock left docking port Target other craft Go to Map View and target the Mun Go back to flight view. Right click the other craft's docking port Note: The other craft still thinks its targetted. Credit: @00Dave Found this. Not me. I just reported it.

Updated it. Hopefully it will make more sense now.

Reported Version: v0.1.4.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: i9 9900K | GPU: 3070ti | RAM: 32GB Following Shows the issue when it's bugged (0.1.4.1) and when it isn't (0.1.2.0): Following shows it bugged but slower to give a better idea of what is happening: Credit: Thanks to Discord chat for helping me get this bug report to a point of being more simply explained.

Reported Version: v0.1.4.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: i9 9900K | GPU: 3070ti | RAM: 32GB Observed Behaviour: Prograde/Retrograde Indicators are moving based on the other crafts rotation. Expected Behaviour: Navball indicators only move in reference to the two crafts relative positions. Video Evidence: https://youtu.be/rzTCBmVMpTc (27 Seconds) Steps to Replicate: Load TargetInheritorTestSave.json Load again to counter spinning bug Undock the docking port on the left Target the other crafts docking port Change to Target mode. Change to the other craft Push a little rotation Change back to the original craft Results: Retrograde indicator is reflecting other crafts rotational movement when it shouldn't be. Credit: @00Dave For help with getting the perfect way to demonstrate this for the video evidence.

Reported Version: v0.1.4.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: i9 9900K | GPU: 3070ti | RAM: 32 GB Video Evidence: https://www.youtube.com/watch?v=Vc5sAOnTpt8 (30 Seconds) Steps to Replicate: Load TargetSpeedBasedOnRotation.json Load again to counter the spinning bug Undock one of the crafts. Target the other crafts docking port Turn off SAS Start rotating the craft around using A or D Results: Target Speed increases to around 12m/s before settling around that point. Speed drops in an oscillating way when releasing the A/D keys.

Might be something intermittent.

Moving this to the archive. The hotfix has reduced this considerably. Please do a new bug report for any further issues.