Kujo Posted October 7, 2019 Posted October 7, 2019 Hello all, I realize that the FLCS BIT switch does not trigger the usual flight control surface movements the F-16 executes upon activating the system test. At the time of my discovery I was on the NTTR map in a single player mission with a clean loadout. The situation remains the same when on multiplayer servers with different loadouts. From 4:17 to 5:06 is displayed the pattern in which the surfaces move upon flicking the switch: Here's my attempt at bringing them to life after a complete startup of the other systems: https://www.youtube.com/watch?v=hSPvwmPI5YM My computer specifications are attached to this post as "DxDiag.txt".DxDiag.txt [sIGPIC][/sIGPIC] "Never quit. Never give up. Fly it to the end." - Chuck Aaron
rrohde Posted October 7, 2019 Posted October 7, 2019 Early access = work in progress. Over the next few months there will be a lot more updates coming to the Viper. PC: AMD Ryzen 9 5950X | MSI Suprim GeForce 3090 TI | ASUS Prime X570-P | 128GB DDR4 3600 RAM | 2TB Samsung 870 EVO SSD | Win10 Pro 64bit Gear: HP Reverb G2 | JetPad FSE | VKB Gunfighter Pro Mk.III w/ MCG Ultimate VKBcontrollers.com
Bouli306 Posted October 7, 2019 Posted October 7, 2019 Hello all, I realize that the FLCS BIT switch does not trigger the usual flight control surface movements the F-16 executes upon activating the system test. At the time of my discovery I was on the NTTR map in a single player mission with a clean loadout. The situation remains the same when on multiplayer servers with different loadouts. From 4:17 to 5:06 is displayed the pattern in which the surfaces move upon flicking the switch: Here's my attempt at bringing them to life after a complete startup of the other systems: https://www.youtube.com/watch?v=hSPvwmPI5YM My computer specifications are attached to this post as "DxDiag.txt". Because you are right you could move this post to the verified bugs forum.
Recommended Posts