MadDog

Is it just me... or does everybody's sim always start in windowed mode since the latest patch? Normally, I reset it to full screen after every update and it sticks; but not anymore. It's a minor issue; but never had it happen before.

Just wanted to provide a heads-up that Calibx has released v3.01 of the Msfsdeck plugin for Loupedeck Live on Github: https://github.com/calibx/msfsdeck/releases I didn't have much success installing it by double-clicking the .lplug4 file (Windows was probably blocking it); but opening the Add-on Manager in the Loupedeck UI and selecting "+Install plugin from file" allowed me to update it. Right now, the Marketplace still has the older version (2.4)

Yup... I updated the response: In the case of block 2, cameras.cfg will go from FNX320 to FNX_320_CFM and FNX_320_IAE....

In the case of block 2, cameras.cfg will go from FNX320 to FNX_320_CFM and FNX_320_IAE.... You may experience a loss of your custom camera views in FenixSim on the occasion you update the program. In this article we provide the correct file path for your custom camera views. Your custom camera configuration file will be held in the location below. C:\Users\<yourusername>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SimObjects\Airplanes\Fenixsim_A320DEV\camera.CFG You will need to copy this file to the following location C:\Users\<yourusername>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SimObjects\Airplanes\FNX320 This will return your custom camera views. You will need to restart the program in order for this change to take effect.

You can try checking the GitHub repository of the plugin author here: https://github.com/calibx/msfsdeck There hasn't been much activity there for over a year, but it appears that a new version may be in the works. The plugin is open source; so if you know anything about C#, you're free to dive in and tinker.

Is anyone else having problems getting the Fenix App to automatically load with the sim? I've checked my exe.xml file and FenixBootstrapper.exe is where it should be and I've excluded all of the Fenix folders/executables from Windows Defender; but it refuses to load automatically. Note that if I start the app manually, it starts up fine... not sure what the issue is. I did see the following in the latest patch notes: ○ Inhibited Fenix auto-launch after installation ... but I assumed that only applied once after the initial install. Am I wrong?

It sounds like a neat idea; but I predict that at some point in the near future, this utility is going to cause all kinds of problems with getting the sim to function. Just one change from Asobo and I can see things going awry very quickly.

Weird indeed. I'm pretty much out of suggestions. Make sure to press Okay instead of Cancel to exit the calibration screen (I think Okay is what actually saves the settings. It probably doesn't make a difference; but maybe make sure the gust lock is disabled when calibrating. Lastly, check the sim's Sensitivity settings for the Warthog Throttles and make sure your curves are linear and you don't have any odd Extremity Dead Zones. That's about all I've got... hope you're able to work things out. Good luck!

That's odd... you don't appear to be getting the full range of your throttle axes... with mine, the EFB depicts the full travel: -16384 to 16384. After calibration, my Idle is -16384, Notch is around 9900, and Ramp is around 14300. I think you mentioned earlier that you were using FSUIPC... I wonder if that may be causing your problem? I haven't used it in a long time; but I think I recall that FSUIPC intercepts the raw hardware inputs, applies curves, filters, etc. and sends its own values to the sim... I wonder if it's restricting the range for some reason? Not saying that's necessarily the culprit; but it's the only thing I can think of. You may want to try the ATR with FSUIPC disabled and see how things go. If that solves it, maybe try creating a new profile in FSUIPC just for the ATR that uses completely linear curves for the throttles.

Since the reverser gates on the Warthog are buttons, make sure that "Throttle hardware has reverser axis" is UNSELECTED in the EFB setup (it's directly below the Dual Axis option - which should be selected). You will probably also need to re-calibrate the throttles in the EFB after making this change. Next assign the Warthog Throttle reverse buttons correctly in the Sim's controller options: Left Reverser (button 30) should be assigned to "Throttle 1 Decrease" (it's a command, not an axis). Right Reverser (button 29) should be assigned to "Throttle 2 Decrease" (again, not an axis). Now when you pull the throttles into the reverse gates, the buttons will continuously send throttle decrease commands which results in reverse thrust. Afterwards, moving the throttles just slightly forward of the gates will re-engage the normal forward thrust axes. This is what works for me.

For me, the easiest way to change time in the main screen is at the bottom left corner of the world map. Once in the sim, the time can be changed with the weather pop-up (cloud icon). Unfortunately, the sliders aren't real precise... usually 2-3 minutes per tick.

ATR is $19.99... $12.99 with the discount.

To actually answer your question, yes, ProATC will work with any aircraft (the 4 airliners mentioned also provide enhanced co-pilot functionality). To use a GA callsign, Select Tail (REG) in the airline drop-down and type the registration in the Flight ID box. As guenseli mentioned, it only supports IFR flights.

...says the man that figured out a way to stick a 750 in a C152. 😉