Mushylog

it's yellow I like yellow

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Edition Windows 10 Home Version 22H2 Installed on ‎29/‎06/‎2022 OS build 19045.3803 Experience Windows Feature Experience Pack 1000.19053.1000.0 | CPU: CPU Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Base speed: 3.40 GHz Sockets: 1 Cores: 4 Logical | GPU: GPU 0 NVIDIA GeForce RTX 3060 Ti Driver version: 31.0.15.4633 Driver date: 06/12/2023 DirectX | RAM: Memory 32.0 GB DDR3 Speed: 1600 MHz Slots used: 4 of 4 Form factor: DIMM Hardware reserved: 4 Severity: Low Frequency: Description: I went to the Mun's orbit to decouple 2 satellites with a manned vessel, then returned to Kerbin: I landed in the desert biome and planted a flag. The mission "SECOND DIBS: GOLD EDITION" was successfully completed as the pop-up notification said even though I never went to Pol in this game save - and I was able to collect the reward and received the following mission: ARTIFICIAL SUPERPOWERS. Included Attachments: seconddibsbug.json .ipsImage { width: 900px !important; }

Well done, KSP2!! That game is beautiful, I am astonished every time I look at it. Will continue to report bugs and provide feedback!

I understood what you meant

I thought of this as a feature, but yes it can be annoying sometimes. Especially when creating maneuvers. I think the lock icon, like AP and PE have (the Ascending/Descending nodes also have it) is a good idea. I sometimes lock these name-bubbles to look at the altitude of certain vehicles, so I definitely would like to keep that feature.

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Edition Windows 10 Home Version 22H2 Installed on ‎29/‎06/‎2022 OS build 19045.3803 Experience Windows Feature Experience Pack 1000.19053.1000.0 | CPU: CPU Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Base speed: 3.40 GHz Sockets: 1 Cores: 4 Logical | GPU: GPU 0 NVIDIA GeForce RTX 3060 Ti Driver version: 31.0.15.4633 Driver date: 06/12/2023 DirectX | RAM: Memory 32.0 GB DDR3 Speed: 1600 MHz Slots used: 4 of 4 Form factor: DIMM Hardware reserved: 4 Severity: Low Frequency: High, reproduced 2 times Description: The M-Beam 200 Pocket Edition plasma effect during reentry does not display correctly. I re-entered Kerbin at orbital speed and the plasma did not cover the beams that were placed vertically, the heating effect looked as if the beams were placed horizontally: Included Attachments: AutoSaveBurn12_27_202310_28.json

You are time-warping, staging does not stage on time-warp

The clouds are now a little less pretty around the flying craft. Before the (great) update, the clouds around the active vessel looked great, no bleeding edges or anything. Now, the weird zone around the vessel is visible again, despite an even more beautiful shadow render for the clouds. So I'm curious: Why was this decision taken? Will we get a better performing rendering system for the clouds? Will this change be permanent, regarding the clouds edges rendering?

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Edition Windows 10 Home Version 22H2 Installed on ‎29/‎06/‎2022 OS build 19045.3803 Experience Windows Feature Experience Pack 1000.19053.1000.0 | CPU: CPU Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Base speed: 3.40 GHz Sockets: 1 Cores: 4 Logical | GPU: GPU 0 NVIDIA GeForce RTX 3060 Ti Driver version: 31.0.15.4633 Driver date: 06/12/2023 DirectX | RAM: Memory 32.0 GB DDR3 Speed: 1600 MHz Slots used: 4 of 4 Form factor: DIMM Hardware reserved: 4 Severity: Low, visual bug Frequency: High, reproduced twice Launch a vessel with parachutes (Mk12 R, Mk16 R). Send it to space, then return in the atmosphere to land, using the parachutes. After landing, the parachutes are open and they need to be repacked: Save. Reload. The parachutes appear repacked when they should have remained open. A 3rd reload does not bring back the deployed parachutes to normal appearance, they still appear shut when they actually are in a "deployed" state. Landed, before reloading: After reloading: Included Attachments:

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Edition Windows 10 Home Version 22H2 Installed on ‎29/‎06/‎2022 OS build 19045.3803 Experience Windows Feature Experience Pack 1000.19053.1000.0 | CPU: CPU Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Base speed: 3.40 GHz Sockets: 1 Cores: 4 Logical | GPU: GPU 0 NVIDIA GeForce RTX 3060 Ti Driver version: 31.0.15.4633 Driver date: 06/12/2023 DirectX | RAM: Memory 32.0 GB DDR3 Speed: 1600 MHz Slots used: 4 of 4 Form factor: DIMM Hardware reserved: 4 Severity: Low I remember the developers talking about how they want to clean up the terrain on planets - in a forum post or in a video I don't remember. But I found one of those messy terrain rendering glitches on the Mun: a nice ridge that goes for kilometers, I got the coordinates too: Latitude: 0 Longitude: 49.655 Altitude: 0 (surface) You should teleport right on it, or at least very close to it, and if you zoom out you notice the ridge even more. It's like a texture was cute and pasted onto another one, without a proper blending. These are rare, and I hope I'm helping out (discord links expired, replacing with imgur) Zoomed out:

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Edition Windows 10 Home Version 22H2 Installed on ‎29/‎06/‎2022 OS build 19045.3803 Experience Windows Feature Experience Pack 1000.19053.1000.0 | CPU: CPU Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Base speed: 3.40 GHz Sockets: 1 Cores: 4 Logical | GPU: GPU 0 NVIDIA GeForce RTX 3060 Ti Driver version: 31.0.15.4633 Driver date: 06/12/2023 DirectX | RAM: Memory 32.0 GB DDR3 Speed: 1600 MHz Slots used: 4 of 4 Form factor: DIMM Hardware reserved: 4 Severity: Low, but the devil's in the details! (The attention to details in this game is amazing) Frequency: High Foot steps sound effect are incorrect around the launchpad 1. Grass terrain sounds like metal terrain, when the kerbal walks on it. Other terrain around seem to sound correctly, so the bug would only be around the "biome" of the launchpad (invisible to players). It would be worth checking other areas on the KSC to make sure they have their respective audio too.

A workaround for this bug was to... bring the vessel back! The crew survived, I launched the vessel again and it worked fine.

A quick workaround is to re-load the save file.

I had trouble with this mission as well. I tried with the basic "wheels" (landing gear) parts, and it did not work. After asking around in the discord, I was told it had to be rover wheels, and these parts are a little harder to unlock, so it took a little bit of science to finish this mission. I don't think the location of the parts themselves is a problem, it's more so about the objective of the mission that was unclear. This is not the only mission that got me, and others, confused. But I have a lot of fun playing them, finishing the missions, and a very hard time staying away from my computer, now!

I like these ideas!

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Edition Windows 10 Home Version 22H2 Installed on ‎29/‎06/‎2022 OS build 19045.3803 Experience Windows Feature Experience Pack 1000.19053.1000.0 | CPU: CPU Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Base speed: 3.40 GHz Sockets: 1 Cores: 4 Logical | GPU: GPU 0 NVIDIA GeForce RTX 3060 Ti Driver version: 31.0.15.4633 Driver date: 06/12/2023 DirectX | RAM: Memory 32.0 GB DDR3 Speed: 1600 MHz Slots used: 4 of 4 Form factor: DIMM Hardware reserved: 4 Severity: Medium Frequency: High, reproduced the bug twice Description: In the VAB, when in symmetry mode (the one for the planes wings and other horizontal crafts), placing the ASCM B "Little Sniffer" science part on a surface (RC-R "RoveMate" command part, in my case), the Little Sniffer is not mirrored correctly. It appears to be mirrored as if it were a 2x symmetry mode. Notice the 2 science parts are facing the same direction.

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Edition Windows 10 Home Version 22H2 Installed on ‎29/‎06/‎2022 OS build 19045.3803 Experience Windows Feature Experience Pack 1000.19053.1000.0 | CPU: CPU Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Base speed: 3.40 GHz Sockets: 1 Cores: 4 Logical | GPU: GPU 0 NVIDIA GeForce RTX 3060 Ti Driver version: 31.0.15.4633 Driver date: 06/12/2023 DirectX | RAM: Memory 32.0 GB DDR3 Speed: 1600 MHz Slots used: 4 of 4 Form factor: DIMM Hardware reserved: 4 Frequency: Low (not sure how to trigger it; can provide save file) Severity: High (the lack of trajectory makes it impossible to create new maneuver node) Description: The game does not know my vessel is in flight, in space, orbiting Kerbin. The trajectory of my vessel is not showing, however the planets and other crafts still have white trajectory lines. The Experiment button on the left side of the screen shows my vessel's state: Kerbin/Landed/Water when I am in fact 127 KM above Kerbin, in orbit. Additionally, this allows me to collect Science as if I was landed but at orbital speed, without having to worry about air friction or heating! Included Attachments: almostorbit-landedbug.json .ipsImage { width: 900px !important; }

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Edition Windows 10 Home Version 22H2 Installed on ‎29/‎06/‎2022 OS build 19045.3803 Experience Windows Feature Experience Pack 1000.19053.1000.0 | CPU: CPU Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Base speed: 3.40 GHz Sockets: 1 Cores: 4 Logical | GPU: GPU 0 NVIDIA GeForce RTX 3060 Ti Driver version: 31.0.15.4633 Driver date: 06/12/2023 DirectX | RAM: Memory 32.0 GB DDR3 Speed: 1600 MHz Slots used: 4 of 4 Form factor: DIMM Hardware reserved: 4 Frequency: High This visual bug has been nerfed since the For Science! update, but it is still present. Under Jool's clouds, I look up and slowly move the camera around at the sun. Stop the camera a bit, move again, and a black artifact will appear. The bug is far less aggressive, as the pixels are not eaten as much. Related post: Included Attachments:

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Edition Windows 10 Home Version 22H2 Installed on ‎29/‎06/‎2022 OS build 19045.3803 Experience Windows Feature Experience Pack 1000.19053.1000.0 | CPU: CPU Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Base speed: 3.40 GHz Sockets: 1 Cores: 4 Logical | GPU: GPU 0 NVIDIA GeForce RTX 3060 Ti Driver version: 31.0.15.4633 Driver date: 06/12/2023 DirectX | RAM: Memory 32.0 GB DDR3 Speed: 1600 MHz Slots used: 4 of 4 Form factor: DIMM Hardware reserved: 4 Resource Manager (RM) duplicates tank parts when attempting to delete them from the RM list The UI of the respective parts are duplicated when attempting to delete them from the Resource Manager list. The parts are not actually duplicated, I don't know if the resources themselves are duplicated as well. Severity: Low Frequency: High First, I add the tanks to the Resource Manager (RM) transfer list. Then, I remove one tank, which is placed back on the left list. Finally, I click the cross X to remove the part - it is supposed to be an arrow that allows to put the parts back in the right-side list .ipsImage { width: 900px !important; }

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Edition Windows 10 Home Version 22H2 Installed on ‎29/‎06/‎2022 OS build 19045.3803 Experience Windows Feature Experience Pack 1000.19053.1000.0 | CPU: CPU Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Base speed: 3.40 GHz Sockets: 1 Cores: 4 Logical | GPU: GPU 0 NVIDIA GeForce RTX 3060 Ti Driver version: 31.0.15.4633 Driver date: 06/12/2023 DirectX | RAM: Memory 32.0 GB DDR3 Speed: 1600 MHz Slots used: 4 of 4 Form factor: DIMM Hardware reserved: 4 Severity: Low (not a serious bug, just a test issue maybe?) When you go in the VAB and place the first pod, in exploration mode, and you open the Action Group Manager, the last group of the "reserved" category is called "displayname" when - I think - it should represent the Science button.

Great progress, KSP2 team! This is wonderful to see. I would love to read more posts like these, to know how you approach a certain challenge (whether you succeeded or not). It is a shorter post than other big ones but I welcome it still! It is a nice read, not too long for those who fear the long ones. Good balance.

Very interesting insight for the rendering systems. And the improvements look very promising! Let's gooo

Yes, this seems to be related to the fix of camera collision with terrain. Back when there was no collision with the terrain, in early versions of the game, it would not happen. It's a frustrating bug that happens when you try to move the camera close to the vessel (or kerbal), zoom in, move it around and the camera will jerk upward at the sky.

It looks like it is! These trails are very wide, very opaque, not transparent at all nor smooth like what the normal trails look like. I wonder, was the FPS count getting lower and lower for @FluffyHood?