MechBFP

If you are controlling a vehicle you first have to go to the KSC, then go to the tracking station, otherwise the time warp multiplier will still be locked to low values.

You can already, it is just unintuitive at the moment. In the bottom right click on the buttons until you find the “Resource Manager” option.

This definitely needs to be fixed. I can already time warp through Kerbin’s atmosphere on a return trip, so may as well let me do the same kind of thing on other planets/moon since it doesn’t actually fix the problem anyway when time warping fast enough. I haven’t tried it yet, but I can probably time warp straight through a CB like in KSP1 if I have it turned up high enough.

I just stuck some I-beams onto the bottom of the fuel tank and put landing legs on those. But yes, that is not a good solution.

I have ran into this myself multiple times. Quite easy to reproduce after just playing normally and loading saves now and again.

The main issue I have with it right now is that it is annoying and tedious trying to find the experiment I just ran in order to read the flavor text. First I have to open the report tab, then I need to scroll down, then I need to usually click on the text to expand it, and then I need to almost squint to read it because of the size/font. That definitely needs to be way more straight forward for the player experience.

That bug and the one I posted above are probably one in the same.

This bug may be partially responsible.

My solution: Oops! All destroyed!

This was driving me nuts when I was trying to dock a rather unwieldy vehicle the other day, I didn’t understand why I was getting translational movement when just rotating the craft, and this explains it.

As far as I can tell the experiment shouldn’t care what biome it is above, as it only indicates high and low orbit. So assuming that is a bug, then once resolved it won’t pause anymore unless you switch from a high to low orbit or vice versa.

100% agree, I have tried using the MMB multiple times for this purpose while holding a part.

I have seen this a few times myself but this is definitely a low priority item since it is purely cosmetic.

After playing this update for a fair bit of time, I am not sure if it ran into release deadlines or if this is just the raw result of trying to push out as much content as possible and therefore being unable to do any sort of a polish pass. Thoughts?

Can also confirm this bug. Nothing special needs to be done to trigger it, happens all the time.

And it should keep that info in flight as well IMO. If anything it should at least be a setting you can change to pick the default layout.

That would be the auto-saves it is overwriting.

And then spend 10 times the amount of time fixing the staging in comparison to just finding and loading a separate workspace. Not seeing the benefit here at the moment anyway.

Alternatively save the game, warp to the SOI and then place the node and see what it does, and then either continue or reload.

As a side note, in KSP1 I believe you were able to click on the planets orbit line to select the planet instead, which isn't possible in KSP2.

It is practically unusable that way since the camera can't be freely moved, making it near impossible to place and move the node small amounts on that line.

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: i7-8700 CPU @ 3.20GHz, 6 Core(s), 12 Logical Processor(s) | GPU: Geforce GTX 1070TI | RAM: 16GB Steps to reproduce: 1) Put a vehicle in orbit around any CB, such as Eve. 2) Zoom out in the map view and try to right click and select Eve as the target. 3) Discover it is impossible because it will always select the vehicle in orbit.

Yup ran into this myself and wasn't sure what was going on and didn't pay much attention at the time. This was the cause though.

I appreciate the challenge but I think these missions need a difficulty rating associated with them so new players have some warning as to the impossibility of that contract before you have very advanced tech.

My vector powered rover (with wings configured to provide a constant down force through the centre of mass) gets thrown completely out of control.