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.

My F12 is messed up

Featured Replies

when i push F12 on my desktop, instead of top down view I get a view of the rudder pedals! However the F12 works properly on my laptop. what could i copy and paste over from my laptop to my desktop to fix this? or is it something else i can do? thanks...........Bill

Packard Bell i11....64gb ram....1tb SSD....Nvidia 99000 4tb......400watt corsair......Windows ME 64.

Is that only in a certain aircraft? I seem to remember having a similar issue with the FSD Commander which was solved by editing the aircraft.cfg...G

Gary Davies aka "Gazzareth"

Simming since 747 on the Acorn Electron

spacer.png

You should find this key being defined in the FSX Options then, Controls tab. Just click any free command there, press F12 and you will see if it is already assigned and also how that current command is named since FSX will report any conflicts then. If you want to have it back for the top down view, switch the Event Category to Views and assign F12 to the Top Down View Shortcut.viewsn.jpg ´views2.jpg That would be the way for the general assignment of F12. For the aircraft specific one, please follow Gazzareth's advice since some aircraft may define own stuff or make their gauges 'grab' some standards. FSX saves the controls stuff at C:\Users\your name\AppData\Roaming\Microsoft\FSX\Controls in a xml file called standard.xml in case you want to backup any assignments.

when i push F12 on my desktop, instead of top down view I get a view of the rudder pedals! However the F12 works properly on my laptop. what could i copy and paste over from my laptop to my desktop to fix this? or is it something else i can do? thanks...........Bill
Bill, I encountered this problem when I installed EZdok, and I fixed it by using (registered) FSUIPC4 to assign F12 to Camera Definition 4. The problem then reappeared when I installed the RealAir Duke, and the fix in this case was to comment out the Camera Definition 4 line in the Duke's aircraft.cfg. Dugald

Bill, Sorry, I missed out an important step in the fix for the problem after installation of EZdok. First, in cameras.cfg (in C:\Users\Username\Roaming\Microsoft\FSX), under [CameraDefinition.006], I set the value for HotKeySelect to 4 (Marniftarr suggested 8, but that didn't work for me), and THEN I assigned F12 to View Camera Select 4 (as indicated in my earlier reply, I used FSUIPC4, but you can probably do the same in FSX via Options - Settings - Controls). Dugald

Create an account or sign in to comment

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.