Closed cgibsonmm closed 4 years ago
Second this. People are pretty desperate for working panels.
Does it support communication with the sim engine as DCS do? Spad.next perhaps will support it?
@jdahlblom If you're referring to 'SimConnect' then there are massive lag issues with using that tech, so no tools that use it (lordy's AxisAndOhs, spad.NEXT) are working.
Does this use 'SimConnect' or do you do it a different way?
I browsed through this thread: https://forums.flightsimulator.com/t/saitek-flight-panels/123511/48
The question isn't if there will be proper support but when. So the alpha/3rd party devs says it worked in alpha but somehow produces stutters in first release. This will be solved I am sure, no need for me to get involved. I have no experience of that sim genre.
@ZoeESummers No I don't use SimConnect, I don't know what it is.
@jdahlblom Sim connect is a .net api that allows 3rd parties to write add-one for fsx and prepar3d.
As you don’t use it then there’s no reason for any lag as it’s sim connect that’s been identified as the culprit.
As if I happen to have code laying around that can be used you mean? Before I have a resemblance to a concept of proof those guys will have that fixed. As they clearly states in the thread, SimConnect, spad.next etc etc worked in alpha.
@jdahlblom No, that's not what I meant. I meant that the 'lags / stutters / frame rate' issues people are reporting are because they are using 3rd party tools that all hook into the 'SimConnect' api.
As you don't use that (AFAIA) then there is no reason that DCSFlightPanels would cause any of those reported issues.
That's what I meant.
What would it take to start looking into support for 2020