Hey friends! I just wanted to share this in case someone else finds it useful.
I have been flying the F-16 with heavy bomb loads, and, upon returning from mission I would always land and find my tires got punctured (flat tires). I kept thinking I was landing too hard, forgetting to put the anti-skid switch correctly, not selecting the right CAT I or III. Even when doing PERFECT landings, I ended up with punctured tires.
So, as the trained classical pianist that I am, I went and practiced landing after landing after landing... all great. No punctured tires. Went back to the missions, again punctured tires.
If someone is facing this, this NOT happening on landing, these are being torn up AT TAKEOFF!
Turns out that I was not rolling strong enough if the runway was long, and "waiting" for the F-16c to take off naturally. At around 220 kts, you can hear the tires disintegrate. I actually thought this sound was the back fins scratching through the runway (thinking I was pitching too hard), so I started using less and less attitude pitch up during take off, which in turned ended up presenting even more punctured tires.
So, long story short: in case you are seeing this, the solution is to correctly roll up at max 160 knots or so (less if without load) and keep the correct pitch attitude so that the plane takes off before the tires disintegrate under your but.
You can move the cursor from one screen to the other in two ways:
- As mentioned a specific button in the collective that can be bound, but... more useful for me to remember less bindings,
- If you move the cursor to the right limit of the left MFD it will stop at the border. If you double-tap in the same direction (like you were "hitting" the border) the cursor will jump to the other screen. This can be done the other way around as well and bring it back to the left.
RafaPolit's post in CTLD JTAC error: 5618: attempt to index local '_enemyUnit' (a nil value) was marked as the answer