Flight Model (FM) Testing Spitfire Mk.Ia 100 oct v1.10.20332 Beta

[ACE-OF-ACES]

Originally Posted by phoenix1963

I don't think there's any need to use DeviceLink to set values, one could generate a proxy DLL that intercepts DirectInput calls (assuming they've not switched to Xinput) and replaces the joystick values with your own to fly the aircraft. Though this is a "dangerous" thing to do because keyloggers do the same.

Need?

No, no need

Sorry if I gave you that impression.

I only brought up the way DeviceLink works with IL-2 is because you brought up the autopilot program for IL-2 46, which 'does' make use of DeviceLink to interface with the game..

As for a proxy DLL, no 'need' (pun intended) in that there are several virtual joystick programs/device drivers/etc out there that the autopilot program could use to send (set) commands to fly the plane

Originally Posted by phoenix1963

The existing C# script could be used to extract the values needed to fly the 'plane.

Which is what I am doing now in the C# script..

In that many of the same variables I am logging during flight are needed as feedback to an autopilot program

Originally Posted by phoenix1963

Even if we can't get attitude values, you could calculate trajectories from the position data.

You can get attitude values.. and more!

Neat thing about the C# over the old DeviceLink is we have many Many MANY more varialbes to 'get' than we had with DeviceLink in IL-2

Only down side is we have none to 'set' which is needed to have an exteranl autopilot fly the plane

In summary

You could write an autopilot program for CoD using (in) the C# script with calls to the virtual joystick..

That would provide all the capabilites that DeviceLink provided and more!