Anth

Thank you. Added a screenshot showing them as well.

Nice. This also works for this bug report which is about a Splashed state. I have seen others talking about needing to change PhysicsMode from AtRest to RigidBody as well.

Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: i9 9900K | GPU: 3070ti | RAM: 32GB Screenshot of Missing Kerbals and Cockpits: Screenshot of Mk1 "Tin Can" and Mk1-3 "Gumball' showing the same issue: How to Replicate: Load CockpitsKerbalsMissingTestSave.json Note Cockpits/Kerbals in Command Chairs are visible Go to KSC Screen Go to VAB Launch Cockpit so its on the runway Change Crafts to confirm cockpits/Kerbals in Command Chairs are still there Revert to VAB Launch the cockpit again Change to Crafts/Kerbals Note: Cockpits and Kerbals in Command Chairs are now missing. Additional Information: Reverting to VAB and then going KSC/tracking station, and then to the crafts will do the same thing. Kerbals on EVA stay visible, its only if they are in command chairs, or are in a cockpit. Work Around: F5 F9 Video Evidence: Video Starts at 26s where I show the following: I change to the crafts (to indicate they look ok currently) after launching a cockpit to the runway I revert to VAB I launch the cockpit again and show the crafts looking like the screenshot https://www.youtube.com/watch?v=pL9NRVTj0Ak&t=26s

Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i9 9900K | GPU: Nvidia 3070ti | RAM: 32GB Steps to Replicate: Load NoECCrossFeedOnDockingTestSave.json Let the two rovers dock Close the Flight Report Reorientate camera to the same as before docking Open Resource Manager Show Battery Levels Timewarp to show changes in batteries being charged Turn off Timewarp [Work Around] Turn one of the docking port's crossfeed off and then back on again Again Timewarp to show changes in batteries being charged Note: The right rover's batteries aren't being charged by the left rovers solar panels, until crossfeed is turned off and then back on again. Video Evidence: https://youtu.be/NMQ2YDL1Ygk (33 seconds) Additional Work Around: Save and reload.

Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i9 9900K | GPU: Nvidia 3070ti | RAM: 32GB Steps to Replicate: Load GumBallCockatooPCRCSTestSave.json Move craft (QEWASD) Turn on Precision Control (Capslock) Move Craft again. Video Evidence: https://youtu.be/scrBIIHV54k (26 Seconds) Additional Information: SAS still uses RCS when precision control is on. Its just the player input. Not new to 0.1.4.0 Craft File: GumBallCockatooPCTestCraft.json

To make it easier can you do the following?: Submit another bug report with my name in the title Add a link to this bug report Add the save file You don't need to do the entire bug report again. I will add the file directly to your original post. Thanks for doing this, its appreciated

@Haflado Thanks for submitting this bug report. Is there anyway you can supply a save file for testing what is in the video? Definitely something weird going on there.

I have noticed that happening as well.

This is fixed as of 0.1.4.0

Yeah. This is fixed. Moving to the archive.

My attempt to simplify replication. Steps for Replication: Load quicksave_129.json Press M (map view) Zoom out and rotate to see Jool Focus on the craft for Jool (actually Laythe) Zoom in Rotate planet so the perspective is over the top of the craft (may or may not be important) Control craft on Laythe Press M repeatedly in just the right way Note: Its hard to get to work sometimes. Video Evidence: Screenshot:

New Bug Report created for this:

@Tazmaniak That looks like another bug. Do you have a save file from that video for testing?

@Socraticat @QwertyHpp @NaughtyMonster @Tazmaniak Moved into a new topic for the following reasons: The other bug has the orbital lines for the planets missing The other bug has AP/PE indicators which this one doesn't Save files supplied crafts all had a state of "splashed"

Thanks. Done. Changed my title to suit both.

@Jaypeg Not fixed yet by the looks of it.

Nvidia: Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: i9 9900K | GPU: 3070ti | RAM: 32GB AMD: Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i7 4770K | GPU: Radeon RX 6600 | RAM: 24GB Navball Comparisons: Please left click on the image to see to see the difference more clearly. Original Screenshots: IngameScreenshots.zip

@hidearimjosh Interesting.

They have made some progress to fixing this. Maybe it will be fixed in 0.1.5.0

Yeah. That's definitely weird looking.

This one might be fixed.

@Krzysztof Jaromir Can you remember what autosave_1.json was supposed to load? Looks like it loads into an empty VAB. Outside the VAB, it looks like you have a lot of debris + 1 craft on Dres?

@Spicat Thanks for reporting this bug. Your efforts are appreciated.

Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Window 10 | CPU: i9 9900K | GPU: 3070ti | RAM: 32GB Steps to Replicate: Load DecoupleREPTimeWarpTestSave.json Stage Press ] Change to prograde Go to Full Throttle for a few seconds watching the change in velocity Press . or go to 2x timewarp Now try to change to different timewarps In Addition: Press / to disengage timewarp entirely Change throttle. Results: Changing to different timewarps does nothing The other craft moves away too fast for 2x timewarp Can never throttle down again after disengaging timewarp Additional Information: If something is connected to the engines plate's other node, this still happens. Video Evidence: https://youtu.be/0WLCowWvZQc (30 Seconds) Craft File: ReversedEPDecoupleTestCraft.json Credit: @Abelinoss for showing me the issue which appeared to be a specific timewarp under acceleration bug, but it ended up being something else instead.

@NexusHelium Merged your bug report with this one.