Hi dear community.
My name is Oleg. I am main developer of Ezdok Software.
I have some very ipressive camera ideas which was stopped since first news about FS2020 (since 2019 year the developing of EZCA was stopped actually) . Those ideas was intended to P3D v5… but I decided to implement them in a new simulator.
I need to know current situation about CameraRelative6DOF function.
As I understood this function was remoded from SDK , but some “camera” variables arrived to “simconnect variables” section.
But now there is no way to read the position of the camera and control the camera.
In other words, I need full control over the position of the camera by coordinates Pitch Bank Yaw , X, Y , Z , Zoom like old CameraRelative6DOF function.
Where I can get any info about plans of MSFS developers about feature of camera variables or camera functions ? Is this possible ?
Please any help.
I wouldn’t go as far yet to say “it’s dead” - it is more likely that the functionality “simply isn’t there yet”.
So unless you have some privileges (as a 3rd party developer, possibly including an NDA) to look into Asobo’s internal roadmap as far as SimConnect is concerned the only option that we currently have is “wait and see”, I guess…
Nothing to do but wait and see…
An interesting situation.
There is no feedback from the developers FS.
Only a few add-on developers who work with cameras know what variables and functions are needed to create unique add-ons like EZ or CP or Xcam. We have list of those variables . The quantity of variables is 5. Only 5! This will open the way for other developers and our addons will be on a new level than the previous versions for FSX or P3D. Just need to add a few variables and that’s probably a few lines of code to sources. But if no feedback, what to expect? a set of useless camera functions like in FSX, when most of the add-on code is designed to work with undocumented variables …
Asobo added(and spent precious time on it) some camera variables to simconnect variables , but those variables will absolutely useless for most camera addons. Strange solution.
It was my opinion. It remains to wait and see …
Not really looked into it and this may prove to be a bit of a red herring, however, I did discover a Config file specifically for defining cameras in the APPDATA folder, copy/paste the line below into your File Explorer window:
%AppData%\Microsoft Flight Simulator\CAMERAS.cfg
Also, some old documentation relating to this file at:
https://docs.microsoft.com/en-us/previous-versions/microsoft-esp/cc526984(v=msdn.10)#camera-configuration-file-format
It’s not much to go on and it doesn’t provide any coding examples, but there are pre-defined cameras for different scenarios, such as tower, runway, multiplayer etc.
I suspect there will be limited support via SimConnect coming soon as there are ~34 variables mentioned in the SimConnect docs relating to either Cockpit or Drone cameras, none of which seem to provide access to absolute position though.
They’re not fully defined yet, in fact only the Sim Var names are there, but it’s a start.
Search the API docs for “camera” to find them:
https://docs.flightsimulator.com/html/Programming_Tools/SimVars/General_Simulation_Variables.htm
Yes. I found they 2 week ago. I tested those variables. But those varuiables can not allow to continue add-ons like EZCA, X Camera, chaseplane or any others in FS2020. Absolutely useless variables.
Continue avaiting.
Well, this is a user forum: don’t expect any “official responses” here from Asobo and/or Microsoft employees 
But I could imagine that there are (or will be) ways to “buy offiicial support contracts for recognised 3rd party developers” (in the near future)
It is fair to assume that Asobo knows this as well. And that’s probably exactly the reason why their own “replay system” still takes some while, too