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.

How to change the default cockpit camera view in your planes

Featured Replies

2 hours ago, lownslow said:

whoa. Everyone is making this way harder than it has to be. No need to edit files!

Mmmm

 

2 hours ago, lownslow said:

Just find the cockpit position you want, and press ctrl+shift+f10

Did you tried to fine tune the position (what the OP want) with Arrow keys??? You need to edit .cfg to do It right

 

2 hours ago, lownslow said:

One exception this will CTD Carenado airplanes. I don't know why and it is highly annoying.

Not the only one, most 3th party planes wont save VFR view (instaCTD). You need to edit .cfg to do It right

  • Replies 39
  • Views 29.1k
  • Created
  • Last Reply
33 minutes ago, Alfye20 said:

Not the only one, most 3th party planes wont save VFR view (instaCTD). You need to edit .cfg to do It right

Maybe I haven't tried too many. DC-6 and JF Arrows all work on this method perfectly. Set it and forget it.

The OP is also asking about setting the camera position of the default C172. So my suggestion will work well.

3 hours ago, lownslow said:

whoa. Everyone is making this way harder than it has to be. No need to edit files!

Just find the cockpit position you want, and press ctrl+shift+f10.

One exception this will CTD Carenado airplanes. I don't know why and it is highly annoying.

We do know the simple way, and we have been using it for some time.  It is just that since SU5, the sim is showing incorrect camera behaviours in some default aircraft such as the C172.

Unless you do a bit of fiddling first, as described above, you cannot move the camera position up above the dashboard to get a decent view.  You seem to hit a hard wall.

This bug was present for a short while early on, maybe last December, and they fixed it once - it's back! 

 

Edited by bobcat999

Rob (but call me Bob or Rob, I don't mind).

I like to trick airline passengers into thinking I have my own swimming pool in my back yard by painting a large blue rectangle on my patio.

Intel 14900K in a Z790 motherboard with water cooling, RTX 4080, 32 GB 6000 CL30 DDR5 RAM, W11 and MSFS on Samsung 980 Pro NVME SSD's.  Core Isolation Off, Game Mode Off.

  • Author
2 hours ago, lownslow said:

Maybe I haven't tried too many. DC-6 and JF Arrows all work on this method perfectly. Set it and forget it.

The OP is also asking about setting the camera position of the default C172. So my suggestion will work well.

You're missing the point of what I'm trying to do. I am fully aware of the custom camera views. That's how I've originally had em. But I am referring specifically to the initital "default" pilot view. If you set this up via the custom camera method, then that particular camera will have 2 views. Which is quite annoying. For example on the FBWA320, I have a custom view made and saved for the pilot. I saved it to NUM+0. But if you pan around the cockpit and hit NUM+0 it will reset your view to either the one you created or what you previously panned to. That is the part that annoys me. So basically there are 2 views if you do it this way. Which is why I rather change the default VFR pilot view and then assign the 'F' key to a button on my mouse, and no matter how many times I push the button, it will reset the view and I don't have to worry about it the default pilot view having 2 different camera angles.

ASUS ROG Maximus Hero XII ▪︎ Intel i9-10900K ▪︎ NVIDIA RTX 3090 FE ▪︎ 64GB Corsair Vengeance RGB Pro ▪︎ Windows 10 Pro (21H1) ▪︎ Samsung 970 EVO Pro 1TB NVME SSD (OS Drive) ▪︎ Samsung 860 EVO 2TB SATA SSD ▪︎ Seagate 4TB SATA HDD ▪︎ Corsair RMx 850W PSU

As promised....

Some third-party aircraft that don't have a default VFR pilot view pre-defined will crash when executing the "VFR Pilot View Save" command.  For these aircraft, a custom view must be created and the CAMERAS.CFG file must be edited to convert the custom camera into a default view.

The CAMERAS.CFG is a standard text file and the edits are very simple; but the biggest challenge is finding the correct path.

For the MS Store version on MSFS, the path is:

--drive--\Users\--username--\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SimObjects\Airplanes\--target aircraft--\CAMERAS.CFG

Here's the step-by-step:

1. Load up your desired aircraft, position the camera where you want it, and save it to a custom camera (default is Left Ctrl + Left Alt + Numpad 0 to 9).  Any will do, but for this example, I'll save my desired view to Custom Camera #1 (Left Ctrl + Left Alt + Numpad 1).

2. Exit the sim and navigate to the CAMERAS.CFG for the desired aircraft (see the path above).

3. Open CAMERAS.CFG with Notepad or your favorite text editor.  Depending on the circumstances, there may be several camera definitions, or there may only be one.  The definition you want to edit has a Title that corresponds to the camera you defined in Step 1.  In my case, I saved to Custom Camera #1, so I want to edit the definition with Title="1".

4. Edit the following 4 lines in the definition (substituting "1" for your custom camera # as necessary).  Don't worry about the definition's sequence number ([CAMERADEFINITION.#]) or Guid... they're fine as they are and shouldn't be changed.

[CAMERADEFINITION.0]
Title="1" "Pilot"                                                                              <Change to "Pilot"
Guid="{B7C50B63-1029-49E0-A831-0EF6257F1D77}"
UITitle="1" "TT:GAME.PANEL_CAMERA_PILOT_VFR"              <Change to "TT:GAME.PANEL_CAMERA_PILOT_VFR" 
Description=""
Origin="Virtual Cockpit"
Track="None"
TargetCategory="None"
ClipMode="Normal"
SnapPbhAdjust="None"
PanPbhAdjust="None"
XyzAdjust=0
ShowAxis="NO"
AllowZoom=1
InitialZoom=0.35
SmoothZoomTime=5
BoundingBoxRadius=0.1
ShowWeather=0
CycleHidden=0
CycleHideRadius=0
ShowPanel=0
MomentumEffect=0
ShowLensFlare=0
PanPbhReturn=0
SnapPbhReturn=1
InstancedBased=0
NoSortTitle=0
NodesToHide=""
Transition=0
Category="Cockpit"
SubCategory="Custom" "PilotCustom"                                            <Change to "PilotCustom"
SubCategoryItem="None" "DefaultPilot"                                          <Change to "DefaultPilot"
InitialXyz= 0.05, 0.1, -0.8
InitialPbh= -4.719444, 0.005864, 0.00041

5.  Save the file and go enjoy your new default view.  Note that the Custom Camera you used to temporarily save your default view in step 1 is now available again to save a different custom view.

I hope this is helpful.

  • 1 month later...
  • Author

@MadDog thanks a lot! That worked for me! 🙂

ASUS ROG Maximus Hero XII ▪︎ Intel i9-10900K ▪︎ NVIDIA RTX 3090 FE ▪︎ 64GB Corsair Vengeance RGB Pro ▪︎ Windows 10 Pro (21H1) ▪︎ Samsung 970 EVO Pro 1TB NVME SSD (OS Drive) ▪︎ Samsung 860 EVO 2TB SATA SSD ▪︎ Seagate 4TB SATA HDD ▪︎ Corsair RMx 850W PSU

On 8/4/2021 at 8:59 PM, lownslow said:

whoa. Everyone is making this way harder than it has to be. No need to edit files!

Just find the cockpit position you want, and press ctrl+shift+f10.

One exception this will CTD Carenado airplanes. I don't know why and it is highly annoying.

After the latest set of updates, the Carenado airplanes no longer CTD when saving the view... but the view does not appear to stick..

Bert

On 8/4/2021 at 6:30 AM, MadDog said:

Here's a step by step:

5.  Now that you have a default view defined, custom cameras may also be saved the same way using the associated key bindings... default is Left Ctrl + Left Alt + Numpad 0 to 9.  These views are recalled using the corresponding "Load Custom Camera #" commands... default is Left Alt + Numpad 0 to 9 
 

  •  

default custom camera views are saved and loaded with Left Ctrl + Left Alt + 0 to 9 (save) andf Left Alt + 0 to 9 (load). (the numbad numbers 0 to 9 are not the default bindings, it uses the regular numbers on the keyboard top row).

5800X3D, RTX4070, 600 Watt, one or two 1440p 32" screens, 64 GB RAM, 4 TB  PCle 3 NVMe, Warthog throttle, VKB NXT EVO stick, Honeycomb Alpha yoke, CH quad, 3 Logitech panels, 2 StreamDecks, Desktop Aviator Trim Panel. Crystal Light VR.

 

spacer.png

5800X3D, RTX4070, 600 Watt, one or two 1440p 32" screens, 64 GB RAM, 4 TB  PCle 3 NVMe, Warthog throttle, VKB NXT EVO stick, Honeycomb Alpha yoke, CH quad, 3 Logitech panels, 2 StreamDecks, Desktop Aviator Trim Panel. Crystal Light VR.

 

6 hours ago, Fielder said:

the numbad numbers 0 to 9 are not the default bindings, it uses the regular numbers on the keyboard top row

Good Catch!  I changed my bindings to use the Numpad long ago and didn't notice the discrepancy (I actually use Ctrl + Numpad # to save and just Numpad # to load custom views).  Since the original posts are too old to edit, I've made the corrections and submitted the new guide to the Tips and Tricks forum.

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.