I have defined interior views for all 8 directions of my POV switch, and want to know if is it possible to have them show whilst the button is pressed, and return to the forward cockpit view when released?
I know I could use an external app such as FSUIPC and keyboard shortcuts, but I’d prefer a CP only solution if it’s possible. I’ve searched high and low and can’t find a solution.
Is there any way to define the physics settings on a “per plane” basis? I’d like to make the camera physics behave a certain way on one plane, but behave in another way on a different plane. As far as I can tell, the physics settings apply across the board, unless I have a misunderstanding of how it works.
Someone correct me if I’m wrong but to my understanding, cameras fall into groups. (Instruments, pilot, hard mounted etc.) I think to have a specific behavior for one specific camera you might have to create a new group only for that camera? I know there’s an option to create a new group. I would try to create a new camera in a new group and then adjust camera behavior of that group
That’s a really good idea. I can create a plane-specific “group” and define the behavior there. I’ll test later and report back, but you may have solved my issue. Thanks for doing my thinking for me!
Pardon me please if this has been asked before, but it seems non-wwise aircraft sounds do not fade out on fly-by.
Some older 2020 released aircraft come without wwise sound sets and even newer ones have some sounds like fuel pumps which do not fade out in the distant on fly-by and continue playing on full volume.
ChasePlane cannot switch between allowing your Xbox controller to control the plane OR the camera. If you use an Xbox controller to fly your plane/helicopter or drive your vehicle, we recommend a second controller to bind camera controls, drone, etc.
So panning around in external view with one of the sticks on my controller won’t work, if I use my controller for flying the aircraft?
One thing I noticed with the Just Flight 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. 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” like it does with the Vulcan’s built-in camera switching (i.e. you need to navigate back to the cockpit with Chaseplane.
Does anyone know how to hide the on-screen messages when changing modes (Slow mode, Normal mode, etc.)?
I’ve been looking through the options, but I can’t find any setting that allows me to show or hide these messages when selecting modes.
Changing modes with a button is very useful, as it allows for some really interesting camera effects during recordings, but these effects are ruined when the selected mode notification appears on the screen.
I’m having constant issue’s with CTD’s in every aircraft. Not really sure if its CP causing it or just SU4. Do you have FlightControl Replay installed?
I had the opposite problem when I was trying to understand how to set up CP, I went looking for an option to enable an onscreen caption showing the view name! I’m no help to you though as I never found it. Will keep an eye on this thread as I’m curious to know the solution for you.
I don’t use FCR but crashes with ChasePlane are pretty common for some people, as are some other issues like occasional random spastic movements in PMDG aircraft and the mouse cursor getting “lost” and disappearing in the TFDi MD-11. //42 are aware of the issues and working on it. If you open a ticket with their Support, they usually respond within a day or so. They may be able to send you a test build that helps.
This is different. You’re referring to SmartViews.
They’re very easy to see. To show the view labels, simply hold down both mouse buttons down.
But it only works by moving the mouse. I haven’t found a way to make them appear using the Xbox controller.
Yes, it’s true that some things are still buggy and some features are yet to be implemented. Keep in mind that, as Parallel42 points out, they’re currently in an experimental release and testing many things.
I’m sure the add-on will improve significantly in the coming months. The guys at //42 never disappoint.
For anyone keeping up on the latest, has there been any talk of allowing visible pilots, working around the problem, or anything of the sort, even in an experimental way?