Manul

The K2 rescue mission works just fine with Parallax and terrain detail high. Other missions that spawn Kerbals and vehicles work fine too. Didn't test Operation Manley Freedom yet.

That's giving me SM AFV flashbacks

I'm using it on 80% of my aircraft and I never had this issue. Always have to adjust suspension because it doesn't have the stock auto adjustment mode. And when used in combination with stock nose gear, the stock one needs some friction adjustments (to make it as slippery as the ALG) to prevent the tail from drifting.

If you are that old, I would suggest using Total Commander, it allows to do all the copypaste thing by just hitting F5 how it was done in pre-windows era in Norton Commander. Selecting files and folders with RMB click is also more convenient than the windows rubber frame. And I'm using Total Commander on Android devices too because it's the only way to manage hundreds of files on the Android device without going nuts.

How are you going to do it if (0, 0, 0) rotation gives you the same orientation as (180, 180, 180) ? And why do you need three arduinos, for multithreading? There is no need for multithreading. Using one microcontroller and one thread will allow to make adjustments to avoid problems with Euler angles describing the same orientation in multiple ways.

Nope. Heading is relative to the planet's surface, pitch is relative to horizon: if your spacecraft is pointed at the north pole, it's 0 degree heading. If you pitch 180 degrees you will be facing the south pole and that's 180 degrees heading. If you are pointing towards the center of a planet' it's -90 degree pitch, pointing in the opposite direction is 90 degree pitch. Pitch is horizon-relative so it doesn't care if you are pointing forward or backwards, this is attitude. You can't have 3 axis of 360 degree rotation without 2 axis intersecting and representing the same orientation with 2 different sets of numbers. That is unacceptable for calculations and causes errors or gimbal locks. There are 2 ways to fix this: limit one axis to 180 degrees or use quaterions. This is why Unity uses quaterions, they don't have such a problem. Using prograde vector as a pitch reference doesn't make any sense unless you are in a perfectly circular orbit. Otherwise it might be confusing: the navball indicates 0 pitch (prograde-relative) but actually your pitch is -70 and you are on a collision course.

PartTools list was not designed to deal with this amount of props so there are no search tools or any other means of navigation. Props are just placed there in their loading order based on the GameData folder structure. The only way to locate a certain prop is to look through the ASET folder structure and find the group of props it belongs: push buttons go after circuit breakers and before switches and so on.

That's impossible: both of these mods contain only parts and their config files, no dll and no MM patches, so there is no way one of these mods can affect anything outside of it's own folder. And there are no parts with the same name or resource definitions with the same resource name (there are no resource definitions at all). Some third-party mod is causing the issue. Maybe there is a MiniAVC.dll hidden somewhere or you have a messed up Firespitter or BDarmory install. Or having another GameData folder inside the GameData. This is a parts-only mod, how is it supposed to be "updated"? cfg files retyped in a newest version of notepad? The only way parts-only mods can be outdated are missing textures or broken behavior of PartModules like wheels or lights because there were several changes in KSP how lights and wheels work. Airplane plus had been having landing gear issues since KSP v 1.4 switced to another version of Unity that changed the landing gear behavior. But it is not the reason of KSP not loading or crashing.

KSO sedan and rover are undersized even for the Kerbal scale. Kerbals can't actually fit inside without clipping through the vehicle and through each other with their feet, hands and heads sticking out with the interior overlay engaged With it's undersized lower body and tiny wheels the KSO sedan is cartoonish and clumsy, unable to climb the ramp of an aircraft or drive into the parking lot. The KSO bus and lorry are okay though (still have some problem with ramps). CWA vehicles are real scale and they are big in real life, I had hard times climbing into a suspension-lifted UAZ with 34 inch tires, it's a real beast with an average sedan's roof barely reaching it's hood, and it is the smallest vehicle in the entire CWA collection. That's a bit too much for 1 meter tall creatures so they need a ladder. Mini Moke versatile offers a nice collection of Kerbal scale vehicles that do get the Kerbal scale correctly: they are neither cartoonish or clumsy and don't feel oversized. So you can use this mod as a size reference instead of KSO. No matter which style and size you choose, just don't forget to check if the crew does actually fit inside

You know the name of this module, we all know: ModulePartVariants

That's the second time I'm getting out of modding subforum's gravity well (as far as I remember). The first one was when I decided to pour some gasoline into the KSP2 dumpster fire. Hi @Caerfinon

Unfortunately that's not an option for Airplane Plus because placing landing gear without symmetry mode is hell. So the backwards spinning left wheel can't be fixed. Symmetry bug doesn't affect suspension and wheel colliders so bumpiness and sinking are fixable.

How is anybody supposed to know this without KSP log or at least a list of mods you are using? My extrasensory abilities say that you have OrdinaryKonstruction v0.1.3 mod installed, try removing it or replacing with a previous version, there is a messed up folder structure that causes Kerbal Konstructs to freak out.

Kerbin is not altered by OPM so there is no way it can interfere with KK bases on Kerbin. The problem is entirely within KK. I've recently noticed that one broken mod for KK statics can break all other KK mods and make all KK statics disappear. See your log and search for KK-related errors. In my case it was Ordinary Konstruction.

KSP hates asymmetrical landing gear that has to be actually mirrored and not just flipped up side down in mirror symmetry. My attempts to make a diagonal landing gear with a working suspension made me want to hit my head with a keyboard, rip it off and throw it out of the window (my head, not a keyboard). No matter what I tried (about 36 hours of failed experiments), something always ended up mirrored wrong so I finally gave up and made right and left landing gear separate parts. P.S. here is the design I ended up with, but I still hate the retraction animation with suspension arms being ripped out of their upper joints so this abomination is a subject to change. And now I understand why the diagonal shock absorber of A+ KS-16 Slant Landing Gear doesn't work, there is just no way to make it work in symmetry without using the KSPwheel plugin. And my mirrored landing gear suffers from reverse spinning as well.