VoidSquid's post in Tiny unKerballed probe into LKO? Stability trouble over 25km. was marked as the answer
You could use an engine with gimbaling, e.g. the Spark, or the Caravel from the RLA Reborn part mod pack.
VoidSquid's post in Costum flag not working was marked as the answer
Interesting... firing up my 1.11.0 test installation gives me this:
EDIT: And the flags I see in your screenshot are not in the usual flags folder but here \GameData\Squad\Agencies , and they are in DDS format, not PNG. As if KSP is starting from a wrong directory / path, very odd....
What happens if you quit Steam, copy your whole KSP folder directly to the C:\ drive, open it there, and double click the KSP_x64.exe, not using the launcher?
EDIT2: You log file starts with:
Mono path = 'D:/#Steam/steamapps/common/Kerbal Space Program/KSP_x64_Data/Managed'
Mono config path = 'D:/#Steam/steamapps/common/Kerbal Space Program/MonoBleedingEdge/etc'
while mine starts with
Mono path = 'D:/Kerbal Space Program 1.10.1/KSP_x64_Data/Managed'
Mono config path = 'D:/Kerbal Space Program 1.10.1/MonoBleedingEdge/etc'
You see the difference, there is a # in your path. And I'd almost take a bet that this special character is the root of the issue.
As I said earlier, try copying the whole KSP folder to another place, e.g. C:\KSP, and try playing from there.
VoidSquid's post in How can I get the new Place-Anywhere 1 Linear RCS Port working? was marked as the answer
Looks like this bug, I'd think:
VoidSquid's post in SPH and VAB are not fully upgraded according to the game even though I am on a science mode playthrough. was marked as the answer
Corrupted save game then?
And while I can't find that post now, I actually do remember having seen a post recently about an annoying bug that happened after repeatedly switching the editor between SPH and VAB.
VoidSquid's post in Batteries not draining when not flying vessel was marked as the answer
Well, yes, it's occasionally a bit buggy, in particular with time warp, I admit. That's why I'm using this mod here:
In general though: if you're more than 2.5 km away for any given vessel, physics, incl. EC, won't be calculated at all. Easy proof: Have a vessel with a negative EC rate. Switch to another vessel (or the KSC) being far away. Time warp some hours, switch back: the vessel will have exactly the EC it had when you switched away from it, i.e. EC won't be drained any more than the very moment you left it.
VoidSquid's post in Staging Causes Engine Toolbar to Disappear was marked as the answer
As per this sheet
INSERT toggles the staging display (it does, just checked).
Maybe check your settings.cfg if you accidentally changed that to your staging key (or added it as a secondary key) ?
VoidSquid's post in Upgrading to Windows 10, will my Win7 saves break? was marked as the answer
I'm still happy with my Win7, but if you feel to go for W10, go ahead
Yes, they will, do not worry
Just copy your old KSP folder to your new rig, and that should be it. Provided you have a working graphics card and a good driver for it.
VoidSquid's post in Is there a way to get the new textures without updating? was marked as the answer
Mun already has the new textures since 1.8., do you have adjusted your graphical settings? Mine are:
VoidSquid's post in Weird UI glitch happens from VAB, Crew center, and possibly all the other buildings in the KSC was marked as the answer
That's quite a mod list, I give you that
Pretty sure there are a couple of mods you're using that are not compatible / updated yet to 1.9.0, e.g. TexturesUnlimited 18.104.22.168 is listed as compatible with 1.8.1, not 1.9.0. Same with TextureReplacer v4.1, ReStock 1.0.3, etc.
I suggest you check if all your mods are good for 1.9.0
Also, I did read a couple of times in the past that UI scalings not 100% often caused weird graphic anomalies.
VoidSquid's post in How to remotely control a lander. was marked as the answer
...or having a pilot in the vessel.
You need a probe core for that, plus connection to Kerbin.
Or: have it controlled by a pilot from another vessel.
In general there are two different types of antennas, direct (e.g. the Communotron DTS-M1) and relay (e.g. RA-15 Relay Antenna), the latter ones can relay a signal, the former can not.
So, let's assume you have a vessel with just a Communotron 16 antenna in orbit of Duna. That antenna, even if you have the most powerful ground station at the KSC, is simply too weak for a direct communication. Now add a RA-100 Relay antenna in Duna orbit to that picture: the little Communotron 16 is powerful enough to connect to the close by RA-100 Relay antenna, which in turn is powerful enough to connect to the KSC: voila, you have communication, provided the Communotron 16 has line-of-sight to the RA-100, and the RA-100 has line-of-sight to the KSC
Of course, this is just a simplified picture, but you get the idea behind direct antennas and relays.
I followed this guide here, works perfect, might even be a bit overkill:
Here's an excellent video explaining the whole CommNet concept, including how to remotely control another vessel with a pilot:
If you really want to dive into this topic, you can check out this post
VoidSquid's post in Game Crashes on Startup was marked as the answer
I wouldn't go that far yet.
As per the error log, you have an "HP Pavilion 15 Notebook PC" with an Nvidia 840M. Many notebooks (including my own) have two graphic card chips nowadays, can you check the Nvidia one is enabled for KSP? Can you try the other, not-enabled chip (there should be a utility program allowing you to select which graphics chip would be used by what application)?
Quite possible the low-power-consumption standard chip is used and that that one can't do DX11 properly.