Anth

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Video Evidence: https://youtu.be/3WO_b-uKVp0 (17 Seconds) Steps to Replicate: Use Campaign MergedCraftStealsOriginal Attached below Go to VAB Load Top Stage Merge Bottom Stage Result: Now Top Stage (Workspace Name and Craft File Name) have been renamed to Bottom Stage Also when the game autosaves it will now autosave as Bottom Stage if all I did was from the video and nothing else. Campaign Folder: https://www.dropbox.com/s/uf4n0qqns7g5vt7/MergedCraftStealsOriginal.zip?dl=0 How this Should Work in My Opinion: The Bottom Stage is being added to the Top Stage so it should be added to the Top Stage Workspace/craft File. In KSP1 the first craft loaded maintains the craft name.

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Video Evidence: https://youtu.be/PUD0uDAmfrs (19 Seconds) How to Replicate: Using the Campaign Save Folder VABSaveWindowCampaignTest Attached Below: Go to the VAB Load ModeratelySizedRocket Click on the Save Button Select NotRocketLookingFor Exit Save Window Click on Save Button Note it didn't reset to ModeratelySizedRocket which is the current Workspace loaded. Campaign Folder: https://www.dropbox.com/s/n7kx9qln15ftgrv/VABSaveWindowCampaignTest.zip?dl=0

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Video Evidence: https://youtu.be/jif68QeJv6Q (11 Seconds) Speculation: Is this window eventually supposed to support just the available crafts that are under the current Workspace?

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Video Evidence: Happens to all the input boxes that I interact within the game: https://youtu.be/qqvlUfSccMg (18 Seconds)

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Picture in Picture with VAB and Craft Folder Showing it in Real Time: https://youtu.be/6gERqVmmtU8 (34 Seconds) Autosave Basically Spams the Save Folder Over Time: The following is a partial screenshot from Diana Gearhead on discord: Possibly the same code as the following:

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Video Evidence: Picture in Picture with Game and Game Folder Showing it in Real Time: https://youtu.be/BYYYRzNWfb4 (26 Seconds) Possibly the same code as the following:

@Filed.TeethYou are welcome

KSP2 Version: 0.1.0.0.20892 KSP2 Version: 0.1.1.0.21572 KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Important Vessels for this bug report are: Craft Files: Main Issue: Both the ShortLander2 (9fps) and Kerbal Transporter (13fps) are collectively causing fps drops in the game when in map view if either is the active vessel. If anything else in the scene is the active craft the fps isnt negatively affected in map view in the same way. Kerbal Transporter appears to be a more significant issue than the ShortLander2. Note: I didnt realise the Kerbal Transporter was a more significant part of the problem until later on in this bug report so it might seem a little odd which crafts I was testing but it will still show the issue. Sorry about that. In the videos below I am focused on testing ShortLander2 and KerbalTestStand (Platform): Video Evidence: Save File From Videos: https://www.dropbox.com/s/b8e82dqqu4jwpji/0120LowFrameRateLander.zip?dl=0 The following graph's information are from the videos and shows differences in fps in Flight View vs Map View between 0.1.0.0, 0.1.1.0 and 0.1.2.0: Excel Sheet for Graph: https://www.dropbox.com/s/l1muzuyqylzr4o2/PerformanceDifferences.xlsx?dl=0 Important Information: Try deleting the Kerbal Transporter first and then reload the save and then delete the ShortLander2 first to see how the Kerbal Transporter seems to be a more significant problem than the Shortlander2.

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Issue: Highest/Top Icon/Name Display Priority Should be the Targeted Craft Video Evidence: Showing Blue behind White with Moving the Camera: https://youtu.be/8sIO4tTi2C0 (11 Seconds) Save File for Video: https://www.dropbox.com/s/yx87fj2wtum93on/TargetedUnderUntargetted.zip?dl=0 Additional Information: If it is actually a transparency problem instead then the Targeted icon should be Opaque and on top.

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Issue: KSP1 I can see exactly which way the probe core is facing (with the ones I have shown below) KSP2 I have no idea Screenshot Comparisons: Suggestions: Without changing how the probe cores look in KSP2: Have an indicator that shows direction and its angle on picking up the probe core/craft (If it's going to be upside down for example for a rover) Another way might be to have something similar to the COL/COM/COT buttons to turn the orientation indicators off and on.

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Two Parts to this bug report: Part 1: Light Rovers with TR-2L Wheels Float Above the Surface and Rotate on Their COM in an Unnatural Way. Part 2: Draining of Fuel Showing Transition from Wheels Contacting the Surface to Floating Above the Surface. Additional Information: The approximate weight that a rover needs to be is 1.93t or over for the wheels to look like they are working naturally. Here is a picture of the craft file from Part 2:

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None How to Replicate: Have a simple craft in orbit (Because I have no idea how docked vessels affects the view display) Set to an obvious view like Chase or Capture Save Load Test for actual view that is active Note: That "Auto : Orbital View" is displayed. "Auto : Orbital View" is NOT the correct view. The correct view is STILL active as it was when the game was saved. Additional Information: There is no display at all of what view is active when landed. Tested on the Mun and on Kerbin.

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None How to Reproduce: Load Existing Craft Preferably in Orbit or in Space Change to Capture Mode Tap on Numpad * a few times Press Numpad - to get a good distance from the craft Change to KSC Screen Change to VAB Launch Craft Change to Capture Mode. The distance will be the same for both crafts when the camera should reset between scenes. Additional Information: The distance and speed of the camera is maintained changing to the KSC Screen, VAB, Launch, Tracking Station craft change, Map Mode craft change.

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None The Keybinds Below are From the Following Link: https://forum.kerbalspaceprogram.com/index.php?/topic/216100-ask-me-a-few-more-things/ zoom in: keypad + Works zoom out: keypad - Works roll left: keypad 7 Works Only if NumLock is on roll right: keypad 9 Works Only if NumLock is on orbit up: keypad 8 Works Only if NumLock is on orbit down: keypad 5 Works Only if NumLock is on orbit left: keypad 4 Works Only if NumLock is on orbit right: keypad 6 Works Only if NumLock is on pan up: keypad 2 (or up arrow) Only up arrow works. Numpad 2 is bound to Music On/Off pan down: keypad 0 (or down arrow) Only down arrow works. pan left: keypad 1 (or left arrow) Only left arrow works. Numpad 1 is bound to Sound On/Off pan right: keypad 3 (or right arrow) Only right arrow works. mouse toggle: backslash Doesn't Work. speed up camera movement: keypad * Works slow down camera movement: keypad / Works. Recommendations: Make 4, 5, 6, 7, 8 and 9 work in Flight View with NumLock off (and on maybe?) Took me a little while to figure out why they weren't working. Make speed up/down camera movement limited to stepped increases and decreases when pressing * and / Currently it feels more out of control when I can hold down the keys to get extreme opposites.

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Expected Behavior: For KSC to turn to 3D when the Capture Mode's camera gets close enough. Steps to Replicate: Load a craft in orbit above the KSC Pause the game. Change to Capture Mode Use the appropriate keys to move the camera to what it looks like in the screenshot below Additional Information: In 0.1.0.0 I could see a rocket on the pad though the detail of KSC was the same. I can't get the rocket to render most of the time in 0.1.2.0

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None How to Replicate In Space: How to Replicate On Land:

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None How to Test: Launch a craft from the VAB or load a craft in scene. Change to Capture Mode Move Camera in some way Go to the KSC Screen Things to Note: Sometimes the incorrect KSC Screen perspective will persist. Sometimes it will face in a different direction but then the camera will attempt to reset to the default KSC perspective a moment later. Sometimes its successful. Sometimes it isn't. At least once the KSC Screen inherited the Capture Mode's Speed. Screenshot of One that Persisted:

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Observed Behavior: Using the Asterisk key to speed up camera mode also speeds up camera rotation. Expected Behavior: Rotation speed should maintain whatever the default is for the game. How to Replicate: Launch a Craft Change to Capture View Hold the NumPad * Key Down for a few seconds or more and then move the camera using the mouse.

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None When in Precision Mode the Place-Anywhere 7 Works for the Following: IKJL Translation And Doesn't Work for: WASD Pitch/Yaw/Roll QE Rotation HN Forward/Back

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None When in Precision Mode the RV-105 Doesn't Work for any of the following: WASD Pitch/Yaw/Roll QE Rotation HN Forward/Back IKJL Translation

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None When in Precision Mode the VR-N1ER Works for the Following: QE Rotation HN Forward/Back IKJL Translation And Doesn't Work for: WASD Pitch/Yaw/Roll

KSP1 Version: 1.12.5.3190 KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Three Sections for this one: Section 1: Shows how the Pitch/Yaw works via the indicators in KSP1 compared to KSP2 Section 2: Shows how Reaction Wheels work in KSP1 vs KSP2 Section 3: KSP2 vs KSP1 RCS under Precision Control which is actually pretty good. Conclusion: Reaction Wheels need to still access their potential maximum Pitch/Yaw/Roll in a dampened way like KSP1 does it (Make it Analog). RCS just needs to stay the same or similar to what it is already other than input issues (3 bug reports I put in Section 3)

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Video Evidence: https://youtu.be/myDyXQTDlJU (23 Seconds) Steps to Replicate: Load PrecisionControlSChangeTester Press 1 to undock Press R and then T Test to see that Precision Control is off Use the Caps Lock key Test to make sure that Precision Control is on Go to KSC Screen Go to Tracking Station Change to TestCraft2 Press 1 to undock Press R and then T Test to see that Precision Control is still on. Save File From Video: https://www.dropbox.com/s/170p07pi3qkqvis/PrecisionControlSChangeTester.zip?dl=0 Additional Information: It does reset if going back to the Main Menu. Question: Can the Caps Lock key be turned on/off via an application or operating system?

KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Observed Behavior: Caps Lock is turning on/off capitals for the game and the operating system when in flight view or map view. Expected Behavior: 1. Caps Lock should ignore turning on/off capitals when in flight view or map view. 2. Caps Lock should only globally turn on/off capitals when: In the VAB or in the Tracking Station. When in the Main Menu. When the ESC key menu is open. When KSP2 isn't in focus (Alt Tabbed or typing on another monitor) Video Evidence: https://youtu.be/VMQlKV9AWSM (28 Seconds) Steps for Replication: Load PrecisionControlCapsLockTester Press 1 for undocking Press R and T Test to see that precision control is off Press Caps Lock and test to make sure precision control is on Go to Tracking Station Click on Default Name-3 Click on edit on right Click on the textbox Type something Save File From Video: https://www.dropbox.com/s/q1qy7cqfsd7ld9k/PrecisionControlCapsLockTester.zip?dl=0

KSP2 Version: 0.1.0.0.20892 KSP2 Version: 0.1.1.0.21572 KSP2 Version: 0.1.2.0.22258 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods Used: None Video Evidence: https://youtu.be/_Umxp6djskY (11 Seconds) Save File: https://www.dropbox.com/s/x7yytoau97nn8l0/0120TStationScrollIssueSave.zip?dl=0