The update patch for MSFS is out, which claims to solve many issues in the first release.   I still haven’t tried re-installing MSFS yet due to various personal matters.   But surely will do it again very soon.

During these days, have received many emails questioning about the compatibility of my FIP gauges with MSFS.

Frankly, due to my current situation of not an MSFS user, I am really not a good person to give a proper answer.

However, some users of my gauges have reported successfully running FIP gauges in MSFS with SPAD.neXt.   Michael is one of them.   You can check out his note in the comment section for my Post 615 here.

Three more feedbacks from new users of my gauges who aimed for MSFS in the last few days are as follows:

“For the records: everything works perfectly on Asobo Baron 58 on MSFS 2020 via SpadNext,” Andrea.

“Just checked them in the sim and they freaking work like a dream!” Saif.

“I am now using these in MSFS2020 with SPAD.next, and they work well and look great,” Grant.

Of course, there are other solutions available on the market.  Probably many of you have heard of them already.

I am not sure how the other solutions work and I have no idea whether Logitech will do something for MSFS very soon.

Although MSFS is still not a full-fledge simulator, since all my FSX/P3D gauges support SPAD.neXt, I would definitely recommend it if anyone wants to run my FIP Gauges with MSFS at this stage.

Again, since I haven’t tested the gauges on MSFS myself, I couldn’t guarantee whether there are differences in layouts, features and operations or not.