idenwen

Was one of about 30 that day and just went through them one by one.

Not F-16 specific and linked in the text above. Now embedded here too:

2x GBU-31 on 2 Shelters resulted in (I didn't count) about 100 "Target hit" with ascending numbers in the result screen. Hitting Shelter with GBU-31 results in target hit spam.trk

Seems I never did that Thanks for the correction.

After rewatching some basic flight maneuver videos i went to the Viper to refly them and it seems the fly by wire system prevents some of them - like the "falling leave" for example. In high AOA scenarios with slow airspeed (> 18-20° AOA & below 160 knots) the rudder input is just ignored. With raising speed and lower AOA control comes back partially and then full. Is that a correct input override by the flight computer?

The MSL Tone Knob (left side of the cockpit) does not reduce AIM-9 volume but instead make it stutter for a fraction of a second and then continue on max volume.

LB2 did not have F-16s. Air Cover was by the longbows themselves. IIRC there was even a CAP role in the dynamic campaign you could assign to a flight.

You can replace that - not even difficult. Made a huge difference for me here!

Was using Helios to generate the initial Monitor lua but then adjusted it myself to the positions I wanted. My Monitor config lua name = _('My 2 Screen Setup') description = 'My 2 Screen Setup' F_16C_EHSI = { x = 1142, y = 1481, width = 190, height = 190 } F_16C_LEFT_MFCD = { x = 552, y = 1080, width = 520, height = 520 } F_16C_RIGHT_MFCD = { x = 1410, y = 1080, width = 520, height = 520 } F_16C_RWR = { x = 1142, y = 1281, width = 190, height = 190 } Viewports = { Center = { x = 0, y = 0, width = 1920, height = 1080, aspect = 1.777777777777778, dx = 0, dy = 0 } } UI = { x = 0, y = 5, width = 1920, height = 1080 } UIMainView = UI GU_MAIN_VIEWPORT = Viewports.Center dcs.log

It worked before the latest OB Update but isn't working anymore after the latest patch. Secondary monitor goes black but there are no exports showing up on them. Where do I even start to look?

I was on the track of getting back into the F5 for the cold war server stuff but... you know... no wings and zero warnings... makes me question that plane again.

F_16C_EHSI = { x = 1142, y = 1481, width = 190, height = 190 }

The opening missions for the apaches on desert storm would be perfect

You can either edit the monitor configs yourself or use a nice tool like helios (https://github.com/HeliosVirtualCockpit/Helios) for that.

Looks nice, will try! Question: Isn't the FCS Bit test necessary anymore for the 18? Can't see it in the list.

Pro F18: Additional weapon station on centerline Longer legs Can take/tank more vertical speed on landings Carrier ops Way more SA and information available (May change when dev of f16 takes speed) Pro F16: Agility Visibillity Better Pilot-Plane interface Power

Both with wow and in air. yep switching master modes back and forth helps most of the time.

In the "Stick, Hotas" controls section there is a binding for "Select xxx" with xxx beeing AAMRAM, Sparrow, Guns, AIM-9. When using these the AC automatically switches to A/A Mode, selects the weapon and changes HUD symbology to the necessary items. Sometimes it don't. It switches mode and selects weapon but HUD stays in navigation mode all the time. Link of recording: https://imgur.com/a/urQo7Kk

Are the fuel valves set correctly? Maybe a double keybind that switches of someting you're not aware off?

Whole plane shuts down on cat after you got control while the script continues to run "control surfaces check ... fine" (No my 2nd engine is only starting again right now). You can manually go through the restart procedure but INS refuses to align again.

And I thought I'm the only one:

Noticed it too, coords seem to be slightly off.

Ah my fault. Windows 10 1909 (tried two machines) and Windows 7 SP1 Tried USB Hubs, direct connection and USB2 and USB3 Ports.

Long story short - got a new computer, took a while to have time for the gaming peripherals to setup. Plugged in the Thrustmaster Warthog HOTAS throttle and windows stated "USB Device not properly recognized". Tried it at the old machine, same error. Tried the bootloader fix from the support site on a old windows 7 machine but instead was instantly greeted by the same error "USB Device not properly recognized". Any other ideas how to save the device, long out of guarantee, and rebuying isn't an option because money. Stick from the same set works and all other devices too - so it's something throttle specific. Edit Specs: Windows 10 1909 (tried two machines) and Windows 7 SP1 Tried USB Hubs, direct connection and USB2 and USB3 Ports.