14 minutes ago, roesti said:

Why chime in on a thread of a software you don't use and bring out your frustration about lacking tower or fly-by views towards //42

With the title I thought there was a fair chance //42 might visit the thread, that's why.  //42 has already done it and certainly MS/A haven't done this yet despite over a thousand votes to do this on the FS forum to which I provided one of the votes.  I truly believe it would be in their financial interests to create a CP-Lite, and I've conveyed this in other forums as well in the hopes they're watching, that's all.  Once more, as you can see I"m not alone.  I appreciate for those those with more view needs, great, glad it's there.  But nope, don't want this complex piece of software just to address the occasional desire for an FB or T view, and truly, it was occasional for the months I had CP installed.  

 

Edited December 15, 2025Dec 15 by Noel

I'm with Noel on this but I'm a less is more kind of guy.

MSFS has the view thing covered.  Fly bys?  What ever.

MSFS drone view?  Right on.

dd

Edited December 15, 2025Dec 15 by Sky_Pilot071

23 minutes ago, Noel said:

CP-Lite

Okay, I understand your wish for something like ChasePlane Light with a few simple views. I try to explain, why this is (in my opinion, because I don't work at //42) not as easy as you might think.

What I told you above the camera API is the core issue here. Asobo doesn't expose this Interface to 3rd party developers, while every other simulator (even the older iterations like P3D, FSX and older) is doing it. This is a basic feature, but I remember threads years ago, before ChasePlane even released or it wasn't clear to if it's possible to create for MSFS, there were many people shouting):

"We don't need ChasePlane, please less 3rd party software, it should be all part of the core sim!". In my opinion, this is a very unrealistic view. Without any blame, one company alone, let it be Asobo, Microsoft or whoever can't develop every single aspect of a simulator. It's like that you can't expect Asobo to make default planes as detailed like Fenix, JustSim or any developer you like.

So it's important to open up the APIs. Some users insisted that's not neccessary, because "Asobo should just do it instead". And here we are, years later and obviously: Asobo didn't, and probably never will do.

The request for opening up the API was highly upvoted, so there was apparently quite some demand from both users and developers. Asobo acknowledged this feature request, but never implemented it and at the same time never said, why they didn't open up the API. So chances are high there is a reason, like the weather API (Meteoblue / contract issues).

//42 then found a way to do ChasePlane without an official API, and this is the crucial point here: To make this work, they have to recreate the camera system from scratch, essentially replacing the default system from MSFS.

So I'm quite certain that the wish for a "simple fly-by" or other views is just not possible while maintaining the original camera system. It's either: //42 can do everything you want with cameras, but you have to use their system - or live with default (but don't expect improvements from Asobo anytime soon), because I doubt //42 can just "piggyback" on Asobos default system.

If it were possible, I'm sure they had done it, but I doubt it's that easy. That's also the reason I explained, why no other developer popped up to create something similar.

Even if you don't use ChasePlane, be happy it's there: It gives back long missing features to users who want it, and if not: Maybe some day Asobo will realize there is a demand to improve on the camera system.

And the demand for these tools exist, otherwise ChasePlane wouldn't exist, let alone the upcoming 2024 version.

Dedicate your whishes at Asobo to finally open up the camera API after 5+ years and your dreams may come true - or continue hoping //42 is developing a tool they probably can't.

Edited December 15, 2025Dec 15 by roesti

4 minutes ago, roesti said:

We don't need ChasePlane, please less 3rd party software, 

BINGO!

dd

4 minutes ago, roesti said:

So I'm quite certain that the wish for a "simple fly-by" or other views is just not possible while maintaining the original camera system. It's either: //42 can do everything you want with cameras, but you have to use their system - or live with default (but don't expect improvements from Asobo anytime soon), because I doubt //42 can just "piggyback" on Asobos default system.

If it were possible, I'm sure they had done it, but I doubt it's that easy. That's also the reason I explained, why no other developer popped up to create something similar.

Even if you don't use ChasePlane, be happy it's there: It gives back long missing features to users who want it

I appreciate your points that might be valid but I don't think the conclusion is solid.  They may not have done because they didn't consider doing this.  Since they do include a way to disable CP completely, perhaps they can disable all but those features.  Yes, I'm happy it's there as I have said several times, but for me, I won't know it's there unless I hit the FB or T view buttons.  I also found it confusing re the Drone camera which is a simple key press, then moved w/ keys from there.   Learning a whole new environment for something this simple is just not worth the time spent for me, and I"ll venture to say many others.  

Now again, if you and I can manually recreate our preferred views using their configuration interface which I did find way too much compared  to....Ctrl-Alt-#, as you also acknowledged in one of your responses above, perhaps they are working on just that:

***Check this box to completely import all default camera locations to all existing controller buttons, then I'm in.  I wouldn't mind when a new plane I've picked up that needs setup using their interface, but again, it is VASTLY more complex than what we enjoy now.  I don't have 50 planes like Rob does and it's rare to adopt new ones.  Hopefully they're listening 😉

2 minutes ago, Sky_Pilot071 said:

BINGO!

Obviously, people need features that ChasePlane brings, even users who don't want to use ChasePlane, as shown on this thread. So a bit contradicting. Asobo should be "enough" to develop everything neccessary, yet they just did not. But the frustration is now dedicated towards ChasePlane or it's developers instead of Asobo. This doesn't make much sense, sorry.

3rd party software like ChasePlane don't take anything away, they just add stuff (for people who buy on a voluntary basis) so I certainly don't get the attitude "I don't need it, so nobody else should".

3 minutes ago, Noel said:

Since they do include a way to disable CP completely, perhaps they can disable all but those features.

Nope. I try to explain it better, in case of it's not clear what an API is. It's an interface for 3rd party developers to interact with the sim. In this example, the camera. If such an API exists, I just can "piggybick" on it and can access all ingame cameras like you as a user and can manipulate it.

But this API does not exist in MSFS. So //42 used tricks to manipulate the camera in MSFS without relying on Asobo, Microsoft or a software interface to MSFS. Yes, ChasePlane can disable itself. But like you said, its "ALL off" or "ALL on". You can't just disable it "partly", that's now how these things work. It will only work if Asobo implements this interface for developers, and if they do: Chances are high many other tools pop up, creating exactly the things you want (maybe even as freeware on .to) or like you said, //42 improves ChasePlane to work in conjunction with the default.

But that's not how it is right now.

7 minutes ago, Noel said:

Check this box to completely import all default camera locations to all existing controller buttons, then I'm in

This import box? It exists for quite some time🙂

I haven't touched ChasePlane in months, but my biggest issue with it is that it killed the default drone, which is actually good. 

7 minutes ago, roesti said:

3rd party software like ChasePlane don't take anything away,

 

As I see it, CP for MSFS is a nostalgia purchase because it worked well in past sims.

Today it simply is not needed.

I do like //42 scenery however.

dd

 

Edited December 15, 2025Dec 15 by Sky_Pilot071

6 minutes ago, chapstick said:

I haven't touched ChasePlane in months, but my biggest issue with it is that it killed the default drone, which is actually good. 

Which proves my point, that ChasePlane is either "ALL on" or "ALL off". They can't use the default drone, they had to create their own. Because the camera system is completely separate from default.

But what you quoted, in case you misunderstood: The existance of 3rd party software like ChasePlane doesn't take anything away from anybody. Don't need it? Don't buy or use it. But don't say "it shouldn't exist, because I don't need it" - other people appreciate having it. It's like saying I don't need whatever brand of your car you drive, so nobody else needs it and it shouldn't exist. (It just doesn't make sense to be against it)

But one question: What do you miss from the default drone what ChasePlane in your opinion can't replicate?

  

4 minutes ago, Sky_Pilot071 said:

As I see it, CP for MSFS is a nostalgia purchase because it worked well in past sims.

Huh? Older sims offered more possibilties regarding the camera even without ChasePlane. One thing ChasePlane can't even recreate nowadays but older sims could: Attach to AI / multiplayer traffic.

Edited December 15, 2025Dec 15 by roesti

1 minute ago, roesti said:

Which proves my point, that ChasePlane is either "ALL on" or "ALL off". They can't use the default drone, they had to create their own. Because the camera system is completely separate from default.

But what you quoted, in case you misunderstood: The existance of 3rd party software like ChasePlane doesn't take anything away from anybody. Don't need it? Don't buy or use it. But don't say "it shouldn't exist, because I don't need it" - other people appreciate having it. It's like saying I don't need whatever brand of your car you drive, so nobody else needs it and it shouldn't exist. (It just doesn't make sense to be against it)

But one question: What do you miss from the default drone what ChasePlane in your opinion can't replicate?

Ah I took you out of context, my bad. 

Did CP add a drone after release or something? When I tried it, I didn't see a similar function. I'm planning on giving it another go when the 2024 version comes out. 

4 minutes ago, chapstick said:

Did CP add a drone after release or something? When I tried it, I didn't see a similar function. I'm planning on giving it another go when the 2024 version comes out. 

Yes, I bound it to the pinky button of my flight stick 🙂 But like you said, it's not the default drone but CPs own version.

Loved chaseplane in P3d...enabled me to set up different cockpit view heights...worth it just for that

3 hours ago, roesti said:

But don't say "it shouldn't exist, because I don't need it" -

Who said that? 

 

When did you install CP?  I don't recall seeing that when I installed.  I assume you meant to circle 'Your 10 configured views' since we wouldn't want default views which don't exist anyway except for ones the plane builder sets accessed by Ctrl-# versus the custom views we set w/ Ctrl-Alt-#.  When it says 'Import', is it absolutely meaning it will take my custom views, per plane, AND assign them to my assigned buttons?  I doubt that question could be answered reliably with 2024 because it's so different.  We have each controller with its categories of pre-sets, General, Plane, Specific in 2024.

1 hour ago, Noel said:

Who said that? 

This was dedicated to the generalization "it is not needed" from one person here in this thread instead of saying "I don't need it" and the rest was a simple misunderstanding.

1 hour ago, Noel said:

When did you install CP?  I don't recall seeing that when I installed.  I assume you meant to circle 'Your 10 configured views' since we wouldn't want default views which don't exist anyway except for ones the plane builder sets accessed by Ctrl-# versus the custom views we set w/ Ctrl-Alt-#.  When it says 'Import', is it absolutely meaning it will take my custom views, per plane, AND assign them to my assigned buttons?  I doubt that question could be answered reliably with 2024 because it's so different.  We have each controller with its categories of pre-sets, General, Plane, Specific in 2024.

I was an early access customer of CP for 2020 and used it with past sims, like I said. I don't know how long this option is in there, but I'm quite sure it's been quite some time. And yes, the "10 configured views" are your set views. The default views should be the preset-views by some developers that come with the aircraft. That's my confusion: These issues you describe with unassigning / reassigning stuff is something I never encountered. It's a one-time setup and they made it as easy is as possible from my point of view. The reasons you say why you don't use this software (which you still don't have to) are for me like saying "I don't play MSFS, because I don't like the installation process".