Hello all,

Having purchased and installed a new Saitek yoke and throttle plus additional Throttle quadrant yesterday, I have developed a problem which is confined to P3Dv4.5 and v5.1.

The hatswitch simply does not move the cockpit view either up, down or sideways ... no movement at all.

I tested it with FS2004, XPlane 11 and MSFS2020 with all functions working perfectly.

I had flown P3dv4.5 this morning and it was all OK.

I removed the .cfg and rebooted to rebuild the config file. No difference.

I changed from raw input to direct input and rebooted, No difference.

I calibrated the yoke and it all appears normal with the hatswitch indicating each and every direction of the circle. No difference.

I then imported previously working and saved, axis and key assignments.  No difference. 

I then went to View/change view and noticed that under Cockpit at the top was on-board (ChasePlane).  This is VERY strange in that I do not own Chase plane nor has it ever been installed on my system. I used to use EziDok but have not used it for probably 12 months. 

How do I get rid of this ChasePlane rubbish????

I have run a search on all of my drives (lengthy process as I have 😎 and there is no reference to ChasePlane in any of them.

I have no idea where this is coming from unless it is a glitch.

Hoping you guys can help.

Tony

Edited February 5, 20215 yr by himmelhorse
Title change

3 minutes ago, himmelhorse said:

 

I then went to View/change view and noticed that under Cockpit at the top was on-board (ChasePlane).  This is VERY strange in that I do not own Chase plane nor has it ever been installed on my system. I used to use EziDok but have not used it for probably 12 months. 

How do I get rid of this ChasePlane rubbish????

I

Tony

Hi Tony. Give me a minute to search for the files which you have to delete to get rid of chaseplane entrances.

But THIS is probably the cause of your issue.

I come back

Marcus

Sorted Guys,

I deleted my camera cfg and let P3D rebuild and that sorted it out.

I could not find any reference to Chase plane in the .cfg at all, but letting it rebuild has given me my pan back.

Cheers to you all

Tony

Tony,

 

delete the camera.cfg located at:

C:\Users\YOURUSERNAME\AppData\Roaming\Lockheed Martin\Prepar3D v5

This file contains Cahseplane entrances which "override" some default P3D settings, especially to the camera movements.

How chaseplane made in in there when not ever used it is a complete puzzle to me! Very strange.

Can it be happened via ORBX Central (which would NOT be good).

Whatever. Delete this file and let P3D build a new one. Then try.

Marcus

1 minute ago, himmelhorse said:

Sorted Guys,

I deleted my camera cfg and let P3D rebuild and that sorted it out.

I could not find any reference to Chase plane in the .cfg at all, but letting it rebuild has given me my pan back.

Cheers to you all

Tony

OK! Then I was 1 minute to late..... 😉

Glad you sorted it out.

Maybe add "SOLVED" to your Topic Headline......;-) 

Marcus,

Thanks for your reply mate.  I had fixed this before you replied but you were right on the money with the deletio9n of the .cfg.

I have not been to ORBX Central either for at least 3 months so I can not see it coming from there, although, I cannot see it coming from anywhere as I have not been to a "Camera" site for probably 12 months,  

Certainly very baffling to me but the "on-board (chase plane) was the initial clue I suppose.

I would also summise that finding out where it came from would be a word not allowed sight harder to sort out than the "Fix" LOL

Thanks again for your input mate

Tony

1 minute ago, mpo910 said:

Maybe add "SOLVED" to your Topic Headline......;-) 

How on earth would I be able to do that mate????

6 minutes ago, himmelhorse said:

How on earth would I be able to do that mate????

By "Edit" your first post the Headline is also editable (If I recall correctly) 😉

Yes, you are probably right. Finding the rootcause would be more effort than the fix itself.