Search the Community

I'm making this topic largely in case someone else comes across the same issue I did, so that they can (potentially) find the answer to their problem sooner rather than later. The title says it all, basically. Principia, which changes the way physics are handled in KSP, does not play nice with the Firespitter plugin-- specifically, "FSengineBladed" and "FSbladeLiftSurface". I've looked through the code but I haven't found an obvious source for this incompatibility, but I am certain that it comes from those two classes conflicting with/improperly using Principia's slightly different physics. In practice this incompatibility manifests basically only with helicopter parts. If you throttle up a helicopter blade while Principia is installed, your helicopter will flop from side to side and bounce up and down like a fish out of water. It's quite funny, actually. Tellingly, the "current force" field of the rotor will always remain at 0. Simply put, the parts won't work for their intended purpose. Remove Principia, and boom- Helicopters can take off, hover, and crash catastrophically into the VAB just as you would expect. I know for certain that this issue affects the Firespitter rotors, as well as those from "Airplane Plus". Another separate but very similar issue occurs with lifting bodies that use the mod "Hooligan Labs Airships"-- the parts from that mod also bounce about like convulsing fish when you attempt to use them in conjunction with Principia, so I can only assume that something very similar is causing both issues. At the moment, since my cursory knowledge of unity modding doesn't afford me the ability to really find out what's wrong, and possibly fix it, There's not much that can be done if you find yourself with the same mod conflict. However, on the bright side, in the case of "airplanes plus", many of the parts cause no conflicts: so, you could simply hide the offending parts with something like "Janitor's Closet", and not encounter any problems. Hopefully this little write-up serves to help someone figure out why their helicopters just won't work, without having to check for mod incompatibilities one at a time for hours on end like I did

Since recently I became a owner of a new computer that has a Gigabyte Aorus GTX 1080 TI graphics card on the new Z370 platform with a 8800K by the way. I like the this over pouring of graphical juice in my videogames and it works nice on my Acer Z35P Ultra Wide Quad HD monitor which can display 120hz nicely. Unfortunately, KSP does not like this graphical setup, for whatever reason that is currently unimaginable to me. My experience and knowledge goes as far to try out the spare variety of graphics drivers from the Nvidia site, but beyond that I do not know what to do. Whats your issue at hand mate? Whenever I play KSP (that is beyond the main menu) my monitor starts signalling in and out randomly, as if the physical cable were disconnected. It then stays like that for 5 to 7 seconds or thereabout and then the signal gets back again. Sometimes it happens several times in a row. So the monitor signals out and in again and repeatedly. This is completely random, I say, completely. However, when I then at the time of incident put the displayport cable in another port it always remedies the problem, but again, for a random given time and then it re-appears again, on any of the display ports I must add. This happens only in KSP, not any other game, application or graphical environment does suffer from this anomaly (at least those programs that I run) Hence why I registered on this forum instead of some computer help site or Steam since it's then clearly KSP related, am I right? So I tried all the latest drivers for the GTX 1080 TI. I tried putting my display port cable in all 3 the display ports on the back of the videocard, and I used a secondary display port cable to see if it was the cable itself. Which can't be as logic tells me because then it would be reproduceable in other games also. The same goes for the argument that it may be faulty ports. Which it can't be because then all 3 of them would be faulty and isn't that just to unlikely to happen on a new videocard? I think it would be. I know you and I like plentiful of information in troubleshooting scenarios but I don't know what to give, so just ask me. I currently play 1.4 but I got my new rig still in the 1.3.1 phase and both versions have the same problem, my bet any version before that also.