Klem has already done this for everyone to download.
The red rings are a good idea.

What we really need is someone to write an autopilot that intercepts the directx inputs to control the aircraft. Surely the 46 one could be adapted, I'm afraid I don't know enough about directx.

56RAF_phoenix

Actually FST did it before klem

klem is using an older version of FST's, that klem made some changes too..

I have been working with FST to come up with a newer version with a standard file format that will match the format my website can accept

Thanks

It is something I came up with years ago back when I was doing IL-2 testing, only back than there were no RING to use, I had to create rings using LIGHTS

Sad things is the autopilot used with IL-2 used DeviceLink to get and set values.. And as far as I can tell the C# script only gets values.. That is to say there is no way to set values.. I have been looking into some other ways to set values, but that project is on the back burner right now.. Just too busy right now

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.

The existing C# script could be used to extract the values needed to fly the 'plane. Even if we can't get attitude values, you could calculate trajectories from the position data.

56RAF_phoenix

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

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

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!

We are in complete agreement.

However, you should be aware I did most of my programming in FORTRAN IV. But I have used almost every language under the sun from Algol68 to SNOBOL4. Just not on PCs (well, my first "PC" was an Altair 8800B using an Intel 8080, later I had a Personal Cray!)

56RAF_phoenix

Ah, thanks, I couldn't remember who's 'Black Box' script that was that I found many months ago. Credit to FST then. I played around with it, added some more parameters, worked in 'Standard Day', set it so the data could be stopped and started with the gunsight switch, etc. The Excel analysis was a logical extension of gathering the data in .csv format.

If they ever fix the (online?)Merlin problems I'll go back to testing but its a bit of a drag especially when its pointless.

Incidentally the two sets of low level TAS figures I did manage to get were:
3000 RPM +6.25lbs boost:
1000 feet, 270mph vs A&AEE's 286mph
2000 feet, 273mph vs A&AEE's 291mph

3000RPM +12lbs boost
1000 feet, 302mph vs A&AEE's 318
2000 feet, 309mph vs A&AEE's 322mph

All at Density Altitudes or 'Standard Day'. Incidentally, Z_Altitude_MSL was 194 feet and 1227 feet at those Density Altitudes.