I can’t speak to the third-party list, but I will vouch that for base sim aircraft, right now it’s the Cessna 152, 172 G1000 only (the steam gauge one has not been migrated yet), Caravan, and King Air.
The impression I got from Asobo was that it was a “easy” thing for developers to apply. I was expecting a quicker uptake on this than what we have had so far, even by Asobo. Must have misunderstood what they said.
Applying it is “easy” in the sense that they just have to add a few lines to the flight_model.cfg, but then they have to completely retest and re-tune the whole flight model to get things working as they want.
It would be a whole lot easier if it were documented in the SDK somewhere. I assume its a little more complicated than simply CFD_EnableSimulation = 1
As luck would have it, I kept a backup copy of the old AS1000 172, but its very old, from 13/04/2021. I wish I had one more recent than that. In any case I can see a lot of differences between the two, other than the CFD additions.
This entire chunk has been removed from the latest version:
I’ve just been looking over the flight_model files, and assuming my code is correct, the only plane I can find with CFD enabled is the 172 AS1000. I checked by eye the ones you mentioned, and they don’t have any CFD attributes listed.
Yesn’t It’s a way more easy thing to implement and also you can activate CFD for any aircraft using dev mode by clicking one checkbox BUT tuning the CFD is hard for now as the SDK documentation does not provide information about the exact parameters to be used
Current flight models use workarounds to be more realistic but these workarounds would basically be ignored by the CFD so some devs not yet move to the new flight model until they know what they can tune and how