Odd to hear of someone disliking Chaseplane. For me, it’s a dealbreaker of moving to 2024. 

4 hours ago, Amon1973 said:

You won't buy it for 2024? You get it for free if you bought it for MSFS 2020.

Won't install it just not worth it for me.

1 hour ago, roesti said:

For me, the user experience is incredible and I'm very happy it exists

I'm glad for you and Parallel as they clearly put massive effort into its development.  I did probe with them about trying to duplicate the simple method to setup custom views, or somehow getting around their method which was to kill that method of setup and they seemed adamant that was the only way forward.  I only care to use those ten custom views and setup is vastly quicker and simpler.  One of your justifications for the greater time and hassle to setup simple custom views is that it's a one-time operation.  True.  But that doesn't change the fact default is far simpler and intuitive:  move your view to X position, hit the key combination, done.   No need to open up dialogues or what have you.   It's been so long since I used 2020 I forgot about the other feature that was appreciated which were the head and camera shakes.  But the rest, beyond fly-by and tower, mostly fly-by for me, is just not worth the hassle.

3 minutes ago, Noel said:

One of your justifications for the greater time and hassle to setup simple custom views is that it's a one-time operation.  True.  But that doesn't change the fact default is far simpler and intuitive:  move your view to X position, hit the key combination, done.

To me, the downside of the default camera system is you can not move your camera position in very small increments; one keypress goes to far and therefor it's impossible to finetune your view.

Edited December 14, 2025Dec 14 by Rimshot

Will Chaseplane for MSFS 2024 include a proper external view? You know, one that does not use a fish eye lens? I struggle to understand some of Asobo's design decisions, and this is one of them. Active Pause is another.

Edited December 14, 2025Dec 14 by Christopher Low

Just now, Rimshot said:

To me the downside is, you can not move your camera position in very small increments, one keypress goes to far and therefor it's impossible to finetune your view.

Ahh, but there is a way and as you probably know that mostly applies to the straight ahead VC view that you might need to align precisely to HUD graphics or what have you.  All you need to do is hit the Camera interface in the toolbar, and change Freelook Speed to a bit above 0 and you can dial in precise location, then go back to default Freelook Speed which is 50 here and you're good to go.

1 hour ago, Noel said:

But that doesn't change the fact default is far simpler and intuitive:  move your view to X position, hit the key combination, done.   No need to open up dialogues or what have you.   It's been so long since I used 2020 I forgot about the other feature that was appreciated which were the head and camera shakes.  But the rest, beyond fly-by and tower, mostly fly-by for me, is just not worth the hassle.

I'm with you that the approach of moving just the camera and pressing a button to save it is a way simpler approach. Especially for people who are new, it just works. But for me, it never really did. All what Asobo did is copy this "style of control" from X-Plane, which was good. But they stopped there and called it a day. I also like the X-Plane camera system, as it allows it many things, eventhough the workflow is completely different to FSX/EZdok/ChasePlane. But Asobo just never bothered to do more than the basics and this is from my point of view just not enough for a proper simulation, especially if you are not using VR or just have a fixed view like in a cockpit replica.

While the default system seems simple (and the principle certainly is), the reality is, it's not: You can't move in small increments like Rimshot said, so you are constantly moving left/right or up/down until you got to your point. I can do the same in ChasePlane, but I also can open the dialog you mentioned and just enter simple values and are done. If I have a plane with camera collision and I want to set up a wing view, I have to close the sim, edit a .cfg to adjust the default viewpoint, then start the sim again, save my now accessible view, close the sim again, revert the .cfg and start the sim again. With chaseplane, I just move the camera.

Next thing: Even if planes are almost identical, like the 737-700 and 737-800 - I have to set up the view for the other variant completely from scratch again. With ChasePlane, I just say "import profile", it then even automatically detects the most similar type, I press one button and are done. For all my views, they are just back (maybe some minor adjustments), with all my keybinds.

It seems like the "simplicity" of the default system saves time, when in reality - it just doesn't, because Asobo doesn't (or at least didn't in the past) care about the camera system. I saved way more time setting up views using ChasePlane than using the default system over all this time it exists just by using the import feature (and maybe minimal adjustments afterwards).

Tower Views, World Views, Fly-By, Cinematics etc. are just a bonus on top.

To be fair: I already used Ezdok in the past and switched to ChasePlane when it first occured and was still under the "OldProp"-brand before //42-days. So I'm accustomed to it and know it by heart. For a new user, it may seem "weird" at first because it's different.

49 minutes ago, Noel said:

Ahh, but there is a way and as you probably know that mostly applies to the straight ahead VC view that you might need to align precisely to HUD graphics or what have you.  All you need to do is hit the Camera interface in the toolbar, and change Freelook Speed to a bit above 0 and you can dial in precise location, then go back to default Freelook Speed which is 50 here and you're good to go.

That's cool, but sounds more complicated than just using ChasePlane - and you also have to open a dialog 😉

  

53 minutes ago, Christopher Low said:

Will Chaseplane for MSFS 2024 include a proper external view? You know, one that does not use a fish eye lens? I struggle to understand some of Asobo's design decisions, and this is one of them. Active Pause is another.

Yes! ChasePlane for 2020 already does it. You can zoom like default (changing FoV -> resulting in the "fish eye" effect you describe) but you can also just translate the external camera backwards, which moves you away from the plane without distorting the view. This was one of the main features announced before the initial version of ChasePlane even released.

 

P.S.: Most important thing, because we talk about setting up views.. after the views are set, it behaves the same like the default system. I'm using my numpad for most of my views (+ switches on my flightstick), so after the set-up, there's no difference in the user experience, except offering more options.

Edited December 14, 2025Dec 14 by roesti

16 minutes ago, roesti said:

That's cool, but sounds more complicated than just using ChasePlane - and you also have to open a dialog 😉

Nice try 😉  My memory of learning to setup CP was on a genuine par with learning how to setup controllers in 2024.  Vastly more complex than is default and again the ONLY view that really demands fine tuning, at least for me and I'm certain most all others, is the forward view vis a vis HUD graphics or other.  Folks with atypical needs will benefit from CP but for the average user this sums it up, and may well be before voters used CP:


 

Edited December 14, 2025Dec 14 by Noel

I’m also only interested in the Fly-By and Tower camera views, so I’m unlikely to buy something packed with extra features I don’t need, especially if it also performs poorly in VR.

The built-in MSFS camera system is actually much better than its reputation suggests.

13 minutes ago, Noel said:

Nice try 😉  My memory of learning to setup CP was on a genuine par with learning how to setup controllers in 2024.  Vastly more complex than is default and again the ONLY view that really demands fine tuning, at least for me and I'm certain most all others, is the forward view vis a vis HUD graphics or other.

😄 I'm completely with you regarding the controls setup in 2024 - for me, it's super messy and not good - the complete opposite of a good user experience.

So that's the reason why I use SPAD.next (there's also FSUIPC / Axis and Ohs etc. for people who prefer that) for my controls to be independant from the simulator. With a "growing collection" of peripherals, setting them all up for different planes / simulators is a big pain. Especially when a developer decides (like in the case of 2024) to completely revamp the system and "try something new" (but not neccessarily better). Using an external tool for this, I couldn't care less what Asobo decides to change with the controls, because an external tool (set up once) handles it for me.

That is the exact same reason why I use ChasePlane: To have a more powerful tool that works exactly how I expect with no sudden changes of a paradigm which was fine. There's no reason to re-invent the wheel: But I'm with you that //42 should just find a way to implement the "quick view save" function of the default interfaces for users like you who just prefer it. But besides this simple thing, ChasePlane is a very powerful tool which can't be compared to the possibilities (or lack of) of the default system.

Edited December 14, 2025Dec 14 by roesti

18 minutes ago, roesti said:

😄 I'm completely with you regarding the controls setup in 2024 - for me, it's super messy and not good - the complete opposite of a good user experience.

I have to say once you understand it it's fine, though when I first explored it couldn't help but think somebody 'on the spectrum' was responsible for its development 🤪 OMG!  And CP is vastly less confusing to setup even if nowhere as straightforward as default.

I hope they sell lots of copies but I truly believe they're missing a great opportunity by not creating a simpler version for less $$ which may act as a segue toward upgrading to the Premium version.  I hope for their sake another dev doesn't take it on before them.  

I'll close it out with this:  it's possible they listened and found a way to duplicate the simple setup method for basic views.  In fact, that may be a way to create a CP Lite within the app:  leave the default method alone as an option, but include Fly-By and Tower views.  If they go there I'm in, otherwise I'll stay out.

Cheers

Edited December 14, 2025Dec 14 by Noel

26 minutes ago, Noel said:

I have to say once you understand it it's fine, though when I first explored it couldn't help but think somebody 'on the spectrum' was responsible for its development 🤪 OMG!  And CP is vastly less confusing to setup even if nowhere as straightforward as default.

Absolutely, I also see some advantages of the new system. 2020 was not that much better, but easier. From the default control binding systems of all sims, X-Planes wins for me. I press a button, it shows me, which button I pressed and I can select an action for it and it has an easy search function. And I can control almost everything the sim exposes with an dataref, just via the default control menu. For MSFS, this is not possible without FSUIPC and Co.

Maybe it's similar with ChasePlane - first time it's confusing but when you make yourself familiar with it, it clicks. I think //42 has a clear philosophy when it comes to user experience, this is also shows with Flow (the toolbar replacement) which I also prefer. But people are different.

 

26 minutes ago, Noel said:

I hope for their sake another dev doesn't take it on before them.  

I think they would still be fine. The main problem isn't in my opinion that //42 isn't developing ChasePlane versions or light editions pleasing everybody, but more that Asobo isn't willing to open up several APIs like the camera API. These APIs were accessible in older sims and made tools like CP or EzDok possible. And people just prefer different things, I guess there are hundreds of topics with people arguing whether EzDok or ChasePlane is / was better.

But without an API, developers have to be extremely creative to get things like custom cameras working, including "memory hacks". That's why it took so long for //42 to develop ChasePlane for 2020 and now 2024 (which changed things again). If Asobo just opened up the API, then more developers could develop these simple tools like a simple fly-by view or other things.

But for now, it seems like a very hard task to manipulate the camera system, which is probably why //42 is currently the only developer doing it. If Asobo decides to reconsider, it would also benefit //42, because they could then do even more - and people who don't need chaseplane get their small tools and be happy with default.

The same goes for the weather API. Also an API, which existed in the past, but Asobo did not open up (they gave reasons for it, but that doesn't help us simmers). In my opinion, it's a shame that we (or developers) have now less options than in the past.

And that's why it's important to appreciate these tools (even if you don't plan to use it), because more options are better than less. A dedicated API would benefit way more users, even those who don't plan to use a tool like ChasePlane.

Edited December 14, 2025Dec 14 by roesti

6 hours ago, outermarker said:

which has since been released, and the one on the 19th is suspected to be ChasePlane for 2024.

I hope you’re right, but //42 have several products in the works.  CP was excellent in P3D and I really miss it in MSFS 2024.

1 hour ago, roesti said:

regarding the controls setup in 2024 - for me, it's super messy and not good - the complete opposite of a good user experience.

Agree, 2024 is better than 2020, but still has a LONG way to go.  I don’t understand why MSFS 2024 UI has to follow the same path as XBOX and defined to scope of XBOX controllers.  PC users have a mouse, they use the mouse, so why do they have to scroll thru 50 aircraft control profiles to find the one they want?  A simple dropdown with type and narrow search to on character input would be 1000% more efficient.

Then there is the issue of filtering “Assigned, Unassigned, Essential” … how the heck do they expect an end user know what is encompassing in “Essentials” and if that covers what they’re looking for?  Users aren’t going to remember every single mapping that is defined by “Essentials” … it’s pointless.  The Filter forces me to change filter from unassigned (so I can find what I just assigned) to assigned after I’ve added a mapping.  Someone needs to introduce Asobo devs to a Telerik Grid with built in filters as needed, UI/UIX is definitely not their strong point.

There is currently no way to easily see a side-by-side compare of assigned mappings between two or more aircraft so I can determine if I can re-use an aircraft profile or create a new one or duplicate and modify.  The only option is to scroll thru 50+ aircraft profiles I’ve created, look at assigned mappings, take screenshots, then scroll thru the aircraft profiles again to my other aircraft profile, take a screenshots, then look at my screenshots and do a compare, then go back in and adjust/create mapping.

Fortunately the rest of MSFS 2024 SU is excellent so it overcomes some of these issues with the flight experience.  But it’s such an easy thing to fix, and the 2nd attempt is better but still WAY off the mark as far as UI/UIX is concerned.  Or maybe Asobo don’t want us buying aircraft and we should only stick with one and only one aircraft forever 😉 

With that said, it’s not a show stopper, but it does make me shy away from purchasing aircraft since I know I’ll need to go thru the hassle of control interface and losing my motivation to do that.

The only real show stopper in MSFS 2024 is the missing landing gear for AI models that I hope will be addressed one way or another.

 

 

Edited December 14, 2025Dec 14 by SayAgain

22 minutes ago, SayAgain said:

With that said, it’s not a show stopper, but it does make me shy away from purchasing aircraft since I know I’ll need to go thru the hassle of control interface and losing my motivation to do that.

Fortunately, can't relate that that sentiment.  I use 6 planes, and use all yoke/TQ/keyboard assignments the same in all of them, save sensitivities.  Once I understand that last aspect it's been a piece of cake to setup per airframe, makes landings and free control wonderful, though was disappointed to learn they didn't include the Specifics per airframe in SU4 as I had read they would.  But, at least you can use the middle option and most of the time it does link to the plane I'm in.