Several things I figured out that seems to be relatively unknown.
F18 you can flip the battery, APU, crank and both engines to idle in one go and it'll start fine. I usually do this, turn some volume sliders down and oxygen on before leaving the panel. When I come back I crank left, set takeoff trim and reset FCS. Similar practices work on other planes but I haven't streamlined those yet.
A10C 2: There's a fast align. On the MFD press INS > Alt Align > Fast. If it doesn't select you took too long, turn the EGI and CDU switches off for a few seconds and back on then it should work. Didn't realize it took people years to figure this out.
Also A10C 2: Autopilot not working? After alignment, click the EGI/steerpoint nav buttons behind the stick and the EAC switch (behind throttle) on. The EAC switch will bounce back if you messed up, but it'll stay if you used a keybind (yet won't function)
Graphics settings: you can hover over the text for options to see how much of a CPU/GPU hit you're going to take, also usually there's descriptions.
IPD: has nothing to do with actual IPD, in VR it scales the world around you. I've noticed 45-50 to be a sweet spot outside of some exceptions
MAVs: [referencing F18] you can click it twice on the stores page and the three minute cooldown will start even if the manual says it won't until you're in the air.
No ground crew in fast mission: go into advanced options/mission editor, change the faction of your airport from neutral to your side. This is something that really should be done automatically. I usually check first thing by asking to remove wheel chocks regardless of having any.
Oculus users: get oculus tray tool (the second most recent version, current is bugged), turn ASW off, GPU scheduling off, CPU priority on high. If on a physical link manage that with OTT also.
Briefing Room/TTI is probably your best bet for a fast mission-esque mission but with far more customization and detail.
If you're pulling hard to the side consistently/can't pull up for takeoff etc., you likely have another input device interfering (oculus users, unbind the axis controls on the controllers for every plane or it'll do this - likely the same with other HMDs). Still if you're in a dual engine plane, check you remembered to even start the second one; it happens.
Again for VR users; the desktop resolution is JUST for the mirror, you can turn this way down. Same in OTT for the window but keep it above 720p or you won't be able to click some UI elements.
Mig21: I forgot how but you need to delete the mouse profile if you want to be able to bind the mouse for clickable cockpit like every other plane has. For some reason you can't assign this to the mouse otherwise
If you need to change a modifier, open the input file for the device in wordpad or something, use find and replace and just change the button (eg find BTN2, replace with BTN3). Stops you from having to do this for every single bind.
And for the love of god please don't run this game on an HDD
Last I can think of for now is non-most potato CPUs should probably be on the MT build unless it's causing abject issues. There's a separate MT launcher in bin-mt. BN OF ANYONE CORRECT THIS IF NEEDED and smack me on discord for good ol times. You were the one handling MT topics is all.
If any of this is wrong please correct me. For those of you in the discord I'm sterg so you know I have a habit of being wrong.
(ED pls stop giving me neutral airports in fast mission)