Vulcan AEO and Navigator camera positions + Chaseplane 2024
-
This is more of an observation, rather than a bug report. I've recently bought the superb Chaseplane for MSFS 2024. It's still in "experimental" phase of release so there are a few rough edges and limitations.
One thing I noticed with the Vulcan is that the EFB buttons for switching to AEO and Navigator positions do not work when Chaseplane is running. I'm not surprised about this, since it takes complete control over the entire camera system. Just wanted to make the JF dev team aware of this in case you hear of other reports where people are unable to switch to those camera views. I'm doubtful there's any "fix" for this unless P42 and JF worked together on some clever solution, but it's not a showstopper anyway. It's still possible to switch to those views manually in the Chaseplane UI (I didn't try the native sim camera controls), but worth noting the EFB doesn't "come with".
Also it's possible to find the ingenious "secret compartment" housing those AEO and Navigator controls, since Chaseplane allows complete freedom of camera movement!
-
Unfortunately, as you say, I believe this will be a limitation of using Chaseplane with some of our products. The Vulcan, and a few of our other products, rely on the core MSFS camera system to move the user to certain locations in and around the aircraft. As Chaseplane overrides the default camera system, the cameras that we trigger in the code no longer exist, so the camera will not change.
It's something we have logged on our internal trackers for further investigation, and to see if there is any form of a workaround we can find for Chaseplane users. In the meantime with the Vulcan, it should be possible to create custom Chaseplane cameras inside the AEO/Navigrator compartment and then trigger those via the Chaseplane interface.
Mark - Just Flight
