Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

P3Dv4.1/A320X F11 spot and F12 top down view problem

Featured Replies

Hi Keven -

Migrated to P3Dv4.1 this fall, and Chaseplane has been running fine with most aircraft, including the F11 spot and F12 top down views that you re-enabled last spring for all sims.  But after installing the new FSL A320-X for P3Dv4.1, and importing my P3Dv3 CP presets for the A320, ran into a strange problem.  All the CP on-board, outside and static camera presets work fine, but the F11 spot and F12 top down views now don't work.  Instead they show two different cockpit camera views, similar but not identical to my CP onboard camera views.   I realize I can create a pseudo-locked spot outside view in CP using gimbal, but I miss the top down view.

I am guessing that when CP added its camera definitions to my A320 aircraft.cfg, something got messed up. 

I noticed that there were two in-cockpit views with hotkeyselect 3 (and tied to the F11 key) and hotkeyselect 4  (and tied to the F12 key).  I remembered from an old post that with CP on FSX you could simply disable or delete the corresponding hotkeyselect lines in the aircraft.cfg, and it restored proper F11 spot and F12 - this had worked for me last year.  But when I try it with P3Dv4, each time I launch P3D, the aircraft.cfg file is getting "corrected" and the hotkeyselect numbers restored (even if CP isn't running !), so effectively I can't delete the assignments.

Has anyone else reported this F11/F12 problem with A320 or other aircraft ?  I can email you my appdata cameras.cfg and aircraft.cfg if you think that would provide a clue as to what is going on.

BTW I've also noticed that the legacy FSX A and S view mode and camera selection keys still work in P3D, even though I don't see the keys assigned anywhere in the P3D options/controls key assignment list.  Did you add their functionality back in CP ?  Their views work OK in stock P3D a/c, but are also messed using the A320.

Appreciate any insights on how to restore top down !

Regards

Chuck

Yeah I have the  exact same issue with 4.1 and the a320x.

 

 

Hilkiah G. Lavinier

P3d v4.3, ORBX (global/trees/vector/LC,airports), Envshade/Envtek, Pilot2ATC, PRO-ATC, Navigraph, PFPX, ASCA/AS, Freemesh 2.0, Aivlasoft EFB v2, Various addon airports, FSL A319X/A320X, PMDG 737/777/747, TFDI 717, QW 787, Carenados jets

Intel i7 4790k (no OC & no hyperthreading), 16gb, Nvidia 980ti (no OC), 3xSSDs, Acer Predator XB281HK (4K resolution), Windows 10 (1803 build) - runs P3D 

Intel NUC7i7BNH i7, 16gb, M2 ssd, Windows 10 (build 1803) - runs AS/ASCA, Pilot2ATC, Aivlasoft EFB 

  • 1 year later...

How can I delete these addon custom cameras so that F12 reverts to the original/default Top Down view?

Best regards,

Wanthuyr Filho

Instagram: AeroTacto

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.