On 5/16/2025 at 11:18 AM, simfan1983 said:

Have people tried the fix I posted a few days ago? Turn off Minimise to Taskbar in the CP general preferences.

Thank you so much for this fix. It solved my Chaseplane issue and it's fully usable now.

On 5/16/2025 at 10:18 AM, simfan1983 said:

Have people tried the fix I posted a few days ago? Turn off Minimise to Taskbar in the CP general preferences.

I turned Updates back on this morning and allowed W11 Pro to install all its updates which included the problematic ones.

I'm pleased to report that having disabled that option panning is restored to its former state. 😁

Well done for finding a solution which hopefully will not get broken again with more updates. 👍

Well butter my buns and call me a biscuit. After singing the praises of exdok my panning stop so out of frustration I’m back on Chaseplane. Well, like my Daddy use to say, “a fool and his money are soon parted”. 

Having tested this fix it appears to be session limited.

Starting a new session the CP option needs to be toggled on/off for panning to work. I’ve decided that is going to be a pain so I’ve uninstalled the first of the two updates. The second will be done tomorrow.

If I have to constantly fight with the OS over this I’ll have a think of my options. Buying an alternative product is not an option.

57 minutes ago, Ray Proudfoot said:

If I have to constantly fight with the OS over this I’ll have a think of my options. Buying an alternative product is not an option.

Hi Ray. Care to share what those other options might be?

18 minutes ago, Patco Lch said:

Hi Ray. Care to share what those other options might be?

1) Leaving the problematic updates alone and toggling the CP option with each session.

2) Uninstall those updates. No further action required unless Windows Updates insist on reinstalling them.

Whatever is the lesser of two pain in the bums! 🤨

Just to clarify, are you talking about panning in cockpit view to look out the windows, or outside the plane altogether??

11 minutes ago, IanHarrison said:

Just to clarify, are you talking about panning in cockpit view to look out the windows, or outside the plane altogether??

Both. Inside panning plus locked spot view.

9 hours ago, Ray Proudfoot said:

Both. Inside panning plus locked spot view.

I have never used panning in the cockpit previously, so I have now set it up and will try and see what happens with my system.

I am on W11 Home  version 10.0.26100 -fully updated.

I have never had problems with locked spot outside views.

I will test with the "fix" and without.

13 hours ago, Patco Lch said:

Well butter my buns and call me a biscuit. After singing the praises of exdok my panning stop so out of frustration I’m back on Chaseplane. Well, like my Daddy use to say, “a fool and his money are soon parted”. 

Well biscuit, there is a manual for EZCA and reading it, really helps. After defining some keys and using this instead of the former ones from CP is all you have to overcome.

 

12 hours ago, Ray Proudfoot said:

Having tested this fix it appears to be session limited.

Starting a new session the CP option needs to be toggled on/off for panning to work. I’ve decided that is going to be a pain so I’ve uninstalled the first of the two updates. The second will be done tomorrow.

If I have to constantly fight with the OS over this I’ll have a think of my options. Buying an alternative product is not an option.

As said before, it is not a solution. I don't even think it is a session limited solution but only 30 seconds, like any other modification of the settings from CP.

I also do not have no second monitor. The CP window stays on top of my P3D window. Of course I could spare part of my monitor between P3D and CP or buy a new monitor, but I don't want to do that for a solution, that does not work on my system. Also this so called fix is presented by a pre 24H2 User. Do I really want to use a former windows 11 version? No way.

1 hour ago, blaunarwal said:

As said before, it is not a solution. I don't even think it is a session limited solution but only 30 seconds, like any other modification of the settings from CP.

I also do not have no second monitor. The CP window stays on top of my P3D window. Of course I could spare part of my monitor between P3D and CP or buy a new monitor, but I don't want to do that for a solution, that does not work on my system. Also this so called fix is presented by a pre 24H2 User. Do I really want to use a former windows 11 version? No way.

Fair enough but I was only passing on a potential fix from a friend that said it worked for them, and others have also said it helped. I'm sorry if it doesn't work for you. As you say, not having a second monitor might be the issue.

The reason I don't have H224 is that it doesn't improve Windows functionality or performance, and introduces a raft of issues that Microsoft are hardly going to address. Some older P3D aircraft don't function properly on H224. The original reason I rolled back was that after H224 installed P3D would periodically open across both screens and I couldn't get it to stop doing that, which was super annoying. So it's not just ChasePlane that is affected by H224. I can still install security and other updates and simply avoid H224 for now. Others can't avoid it or can't roll back as it is too late. At some stage support will end for Windows 11 that is not on at least the H224 build, but I will cross that bridge when I come to it.

I generally avoid all updates to all my apps such as GSX, OBS, Nvidia Broadcast, Navigraph Simlink, Nvidia drivers, SODE etc. because I have everything working with no CTDs and can reliably do a long haul flight without and performance issues. Every week or two I take a system image backup so if anything gets installed I can roll back to where I was. This approach has saved me on several occasions from a lot of hassles. I continue to buy scenery and aircraft for P3D and am more than happy avoiding MSFS and enjoying what I think is currently the best sim available with a fully functioning ChasePlane.

2 hours ago, IanHarrison said:

I have never used panning in the cockpit previously, so I have now set it up and will try and see what happens with my system.

Me neither. I have NumPad keys for view changes. I use it externally when customising GSX jetways.

2 hours ago, blaunarwal said:

As said before, it is not a solution. I don't even think it is a session limited solution but only 30 seconds, like any other modification of the settings from CP.

I’ll test this on my next session.

I have tested now. Confirmed that the fix seems to work on a session basis.  CP worked fine on first flight after the fix.

Restarted Sim. and it was dead slow again. Flicked CP minimise button on and immediately off and it restored to full speed. 

Outside not affected.

7 hours ago, blaunarwal said:

Well biscuit, there is a manual for EZCA and reading it, really helps. After defining some keys and using this instead of the former ones from CP is all you have to overcome.

Well young man, I used the manual extensively setting up ezdok and thoroughly uninstalled chaseplane. It worked quite well for days then the hat switch stopped panning. The key short cuts worked fine as they do in CP. I decided if one was going to be as much a problem I would use CP as it is more intuitive. Seems you posted the same or similar issue with EZCA above. 
Basically am tired of fighting camera addons and went back to flying and adapting. 

6 hours ago, Patco Lch said:

Well young man, I used the manual extensively setting up ezdok and thoroughly uninstalled chaseplane. It worked quite well for days then the hat switch stopped panning. The key short cuts worked fine as they do in CP. I decided if one was going to be as much a problem I would use CP as it is more intuitive. Seems you posted the same or similar issue with EZCA above. 
Basically am tired of fighting camera addons and went back to flying and adapting. 

I'm not in my twenties anymore ... almost 60 but I still see the new camera software (EZCA) as a challenge for my brains. I had to force me to read the manual. I also prefer intuitive programs and EZCA is pretty cryptic. But after reading it works better. After I programmed some things, I have less problems. Me too I had loss of panning quite a lot of times. But  it became better after removing view commands in the sim. I think this is the hardest part to give up the S and A commands used to since 35 years. I had to restart EZCA to make it pan again but now, it works more reliable. I still hope, it was my fault and not a software bug, not detected for so long. We two are not the only users of this software. 

I prefer flying too, but sometimes one has to fix something first. 

Edited May 20, 20251 yr by blaunarwal