muskysim

Yes, I have a lot more hardware such the HC Bravo throttle and also the WinWing Airbus Sidestick and they have a lot of buttons that I could not program using SimAppPro and when this software was running it was conflicting with SPAD.NEXT particularly with the WinWing Airbus Throttle. So thats why I went this way. Anyway I don't know why I couldn't see the (INI_FPA_DIAL) LVAR cause all of a sudden in was there and it is an internal lvar of the A320 neo so I was able to complete the FCU in SPAD.NEXT You raise a good point though, if I could have manually specified what Winwing products I wanted SimAppPro to drive ie Only the FCU and not the throttle I would have been good to go.

I have got one outstanding issue to resolve to complete programming my WinWing FCU using SPAD.NEXT. Title says it all, I cannot find the variable that displays the FPA value. I even checked a Mobiflight module for A320neo but they seem to have created their own variable (INI_FPA_DIAL) which doesn't exist outside of mobiflight. Thanks In Advance

There has been a lot a bugs reported relating to the lights of the A320neo V2 since last update including that the strobe light was lighting up the cockpit. I assumed this was a bug and hoped it would be fixed in the rollout of MSFS 2024. However in a video by A330 Driver on the Fenix A32X Sharklets enhancement he stated that this was actually a design fault and was a problem when sharklets were first installed on A320s. They lit up both the cockpit and the cabin and at best were a distraction, which I certainly found, but in the worst case could cause a medical emergency in someone suffering from epilepsy. In response to this Airbus masked the inside of the strobe light cover and on the Fenix you can see its blacked out preventing any light contamination from the strobe light into the cabin or cockpit. In the Inibuilds A320neo V2 the Strobe light cover is completely clear. So the strobe could working properly but its the strobe light cover that is the problem.