Will FSuipc be needed in MSFS? 

Some current addons require it so if you want to use legacy aircraft in MSFS you might need it, assuming it works in MSFS. I do hope Asobo will be doing a proper job on setting up input devices in MSFS so it won't be needed there.
I spend countless hours tweaking FSX and without Pete Downson's work I could not have done half of it.

 

FSUIPC is an amazing tool to compensate for the unacceptable deficiencies of the previous FS editions (and in an extend, the half backed job of Microsoft at the time). Nonetheless, I really hope that a proper job is being done on the new sim so it is no longer required.

Probably it won't be needed. If you take a look at the fixes for the alpha build, they are trying their best to improve peripherals compatibility. 

Pete Dowson mentioned on another Forum that they are working on support for MSFS. I hope there is a FSUIPC, or equivalent, for MSFS including the ability to write Lua scripts. With Lua scripts you can significantly reduce the need for using a mouse while flying. For example, I much rather be able to quickly and easily enter radio frequencies, headings, altitudes, courses and airspeeds using the keyboard numberpad then hunting for elusive mouse click spots while bouncing around in bad weather while IFR. From a realism point of view, using the numberpad to enter frequencies, etc., is not much different than keying info into a FMC, or using the keyboard displayed on a touch screen GPS, at least for me.

Al

Edited April 17, 20206 yr by ark

I really hope, it is not needed anymore!

FSUIPC-like capabilities will always be needed by a significant percentage of simmers, but certainly not all. The only issue is will those capabilities be 'built in' to MS2020, or come via a 3rd party add-on. My guess is that with all Asobo has to do, a 3rd party add-on is likely, but time will tell.

Al

Edited April 20, 20206 yr by ark

Let's HOPE NOT!!

Why not? I have always just used the free version of FSuipc because some addons needs it,and never missed the things in the payware version. so if MS can integrate the "needed" stuff into the sim, the better. The less outside utilities it needs, the chances are it may work more flawlessly.

There will always be data or processes required beyond the scope of the SDK that hopefully some third party can access. I don't think you can ever say the concept of FSUIPC is redundant unless you understand how FSUIPC has come to exist. However I'm sure in the short term Microsoft will have much greater expansion of data and processes available straight from the core interface be that SimConnect or whatever they chose to call it in the new sim.

Of course it's a different question to ask for backwards compatibility and that I'm affraid would be beyond Microsoft's control, they didn't auther FSUIPC but I'm sure the functionality will be replicatable good word that!

Edited April 20, 20206 yr by dtrjones

7 hours ago, dtrjones said:There will always be data or processes required beyond the scope of the SDK that hopefully some third party can access. I don't think you can ever say the concept of FSUIPC is redundant unless you understand how FSUIPC has come to exist. However I'm sure in the short term Microsoft will have much greater expansion of data and processes available straight from the core interface be that SimConnect or whatever they chose to call it in the new sim.

FSUIPC came to be as a palliative to the mapping insufficiencies, the battery bug, the wind flaw, etc. One would have thought that the Aces and successors would have made all the corrections and enhancements along the way since.  To see a guy on the P3D forum who still cannot calibrate its quadrant with a vanilla 5 is surrealistic ! 

We have a large shark with a school of fishes cleaning its teeth. The palliative has grown into a symbiosis. Not to say an addiction for the shark. 

We see through the updates that alpha resters are raising mapping issues.This is what is great about this wide testing, users say their piece. Asobo had better to do it right and make a FSUIPC-like addon unnecessary.

FSUIPC will be useful if MS2020 does not provide a scripting capability. For example I have a script that measures landing performance to include landing distance over a 50 ft obstacle, rollout distance, vertical speed and ground speed and a/c pitch at touchdown, and bounce count (I really needed that last one 😃). I have another script that provides altitude callouts from 2000 ft down to 10 ft for any a/c does not inherently provide that type of information (few aircraft other than airliners, etc, provide such callouts). The point is, there are countless different capabilities that a particular user might want, and there is no way Asobo can guess what they all are, let alone implement them all. A scripting capability lets users develop what they want.  The main use of FSUIPC these days is not to fix things, but rather to provide a convenient way to expand capabilities.

To each his own.

Al

 

Edited April 21, 20206 yr by ark