StyrofoamBoy

I have taken a short video of the bug in action and uploaded it to YouTube: This happens immediately after launch, on vanilla KSP 1.1.2 x64. This machine is a quad-core i7, with an AMD graphics card (latest drivers, non-beta).

I also still having this problem. The only lyrics solution I've come up with, at this point, is to try and meeting at the first intersect point (which requires more fuel, because of the extra speed) or "guess" on the separation for the second intersect and then adjust at the apoapsis. After you setup your initial maneuver, warp to the apoapsis. The second intersect point and separation will then show. Usually, I can turn prograde (orbit relative) at the apoapsis and use my RCS to burn a little faster or slower and get the separation to a reasonable distance.

I am having the same problem. It seems like it's almost always the markers for intersect 2 that blink in and out. Once I pass intersect 1, the intersect 2 markers come back, but that's often too late to discover that your trajectory "guess" was off.

I'm seeing the same thing on an AMD Radeon card, where it crashes after saying that the device was "lost". In my case, the next line says "device no longer lost" then crashes. It's happening multiple times per day, and is getting rather annoying.