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.

change view in steps

Featured Replies

Hello guys

 

Before I bought fs9 I used to fly Fly! and Fly2. And I still sometimes fly Falcon 4.0. In those sims you use the hat switch in a different way than in fs9. If you look forward and then click once to the right on the hat switch, the view is changed 45 degrees to the right (to right-forward view) and stays there even after you release the hat switch. Next click to the right moves the view another 45 dgs to the right etc (to 90 dgs right view). If you want to go back to forward view you must now press the hat switch to the left twice.

 

The advantage of this is that when you e.g. are in a right turn on the final, you just press the hat switch once to the right, and you will stay in the right forward view and see the runway without having to keep the hat switch pressed all the time.

 

I have tried to set this up in fs9, but not succeeded. Is there any way to do this in fs9? Or perhaps with the help of Active Camera or FSUIPC? Or maybe there is a prgram that could solve my problem. Any help is appreciated. I have searched some forums and used Google without finding anything that could help me. Thanks!

 

rgds

 

Krister R

I guess you're talking about 2D cockpit view. In VC it's sort of what you're asking for.

For 2D, what you need is to look for this line in fs9.cfg, in the [Controls] section:
pan_in_cockpit_mode=1

This edit will allow you to pan in the same way you do in VC. Hope this helps.

Sent from my Nokia 1100 using Tapatalk
 

Best regards,
Luis Hernández 20px-Flag_of_Colombia.svg.png20px-Flag_of_Argentina.svg.png

Main rig: self built, AMD Ryzen 7 5700X3D (with SMT off and CO -50 mV), 2x16 GB DDR4-3200 RAM, Nvidia RTX 5060Ti 16GB, 256 GB M.2 SSD (OS+apps) + 2x1 TB SATA III SSD (sims) + 1 TB 7200 rpm HDD (storage), ID-Cooling SE-224-XTS air cooler, Viewsonic VX2458-MHD 1920x1080@120-144 Hz (G-sync compatible), Windows 11. Running P3D v5.4 (with v4.5 scenery objects as an additional library, just in case), FSX-SE, MSFS2020, MSFS2024 and even FS9! Lossless Scaling for all my sims. What a godsend...

Mobile rig: ASUS Zenbook UM425QA (AMD Ryzen 7 5800H APU @3.2 GHz and boost disabled, 1 TB M.2 SSD, 16 GB RAM, Windows 11 Pro). Running FS9 there .

VKB Gladiator NXT Premium Left + GNX THQ as primary controllers. Xbox Series X|S wireless controller as standby/mobile.

  • Author

Yes you are right, I am talking about 2d view. I will follow your instructions. Thanks a lot!

rgds

Krister R

  • Author

Hi again,

 

Luis Miguel: The pan_in_cockpit_mode=1 did not do what I wanted it to do. This command makes the whole instrument panel pan, i.e. when looking 90 dgs to the right you still have the panel i front of you. This is rather confusing during a landing, as the plane is not moving in the same direction as the panel is pointing. You would rather soon loose your sense of direction during the busy landing phase. But thanks for trying to help out.

 

RJ: I will try the tips you link to, they look promising. Thanks.

 

Krister R

  • Author

I downloaded the Flusifix freeware program according to one of the suggestions under the link I got. It solved my problem, at least partly. The only drawback is that you have to use the numerical keyboard (it does not work with the hat switch on the yoke). I will try to program my hat switch as ordinary buttons. This should work.

 

The function is not exactly what I wanted (to change view in steps 45 dgs for each hat switch press). But it will still be an improvement. Thanks guys!

 

rgds

 

Krister R

Another option, is to write a very simple xml gauge, and place it on each window view.  You then hover your mouse over a hidden click spot and your view is changed.

 

If your interested, I could quickly write the xml code which will shift your view "Forward Left" as an example.  You could then do the other views with a simple notepad edit.

 

RJ. 

Another option, is to write a very simple xml gauge, and place it on each window view.  You then hover your mouse over a hidden click spot and your view is changed.

 

RJ. 

 

Exactly what I do RJ. I like the fact that the view reverts to the default using the yoke hat so I can have a quick peek at a view.

Exactly what I do RJ. I like the fact that the view reverts to the default using the yoke hat so I can have a quick peek at a view.

+1

 

Us "old" 2D panel guys... B)

 

RJ

  • Author

To RJ,

 

Yes please. Thanks! I would be very intested in looking at that code.

 

bst rgds

 

Krister R

And as another 2D panel dinosaur, I would as well, please.

 

Colin B

A very simple "hidden" XML "Views" gauge used on the 2D default b737-400 panel.

 



The default 737-400 is not the best example of using hidden click spots, because there's really no room on the panel to place them properly.   I only used the default b737-400 as an example how you could use hidden click spots on other panels.  You can use these gauges on "fixed" 2D side views as well.  

The xml code for "View Forward left" looks like this:

<Gauge Name="VIEWFORWARDLEFT" Version="1.0">
<Image Name="Clickspot.bmp" ImageSizes="12,12,19,19"/>
      <Mouse>
        <Tooltip>View Forward Left</Tooltip>
        <Cursor Type="Hand"/>
        <Click> (>K:VIEW_FORWARD_LEFT)
                </Click>
    </Mouse>
</Gauge>


You can download these simple gauges here and try them out on your default b737-400 2D panel.
If you wish to edit an XML gauge, right click on the gauge and open with notepad.

RJ

RJ has given the easiest to understand option.

 

I currently use transparent clickspots in a single xml gauge with no bitmap and multiple clickspots.

 

The gauge size is the same as my panel bitmap (which makes it easy to define clickspot areas)

 

I have attached and example.

<Gauge Name="VFR" Version="1.0">

<Size X="1600" Y="1200"/>



   <Mouse>

  <Area Left="1470" Right="1600" Top="762" Bottom="1014">
      <Tooltip>Rear Right View</Tooltip>
      <Cursor Type="Hand"/>
      <Click>(>K:VIEW_REAR_RIGHT)</Click>
   </Area>

  <Area Left="0" Right="434" Top="250" Bottom="660">
      <Tooltip>Forward Left View</Tooltip>
      <Cursor Type="Hand"/>
       <Click>(>K:VIEW_FORWARD_LEFT)</Click>
   </Area>

  <Area Left="1328" Right="1600" Top="200" Bottom="544">
      <Tooltip>Forward Right View</Tooltip>
      <Cursor Type="Hand"/>
       <Click>(>K:VIEW_FORWARD_RIGHT)</Click>
   </Area>

  <Area Left="1200" Right="1600" Top="0" Bottom="150">
      <Tooltip>Overhead</Tooltip>
      <Cursor Type="Hand"/>
      <Click>(>K:VIEW_FORWARD_UP)</Click>
   </Area>

  <Area Left="1215" Right="1383" Top="1100" Bottom="1200">
      <Tooltip>Navigator View</Tooltip>
      <Cursor Type="Hand"/>
      <Click>(>K:VIEW_REAR)</Click>
   </Area>

  <Area Left="0" Right="150" Top="744" Bottom="1032">
      <Tooltip>Rear Left View</Tooltip>
      <Cursor Type="Hand"/>
      <Click>(>K:VIEW_REAR_LEFT)</Click>
   </Area>

   </Mouse>  

</Gauge>

Hi again,

 

Luis Miguel: The pan_in_cockpit_mode=1 did not do what I wanted it to do. This command makes the whole instrument panel pan, i.e. when looking 90 dgs to the right you still have the panel i front of you. This is rather confusing during a landing, as the plane is not moving in the same direction as the panel is pointing. 

 

Thank you for the feedback, Krister.

 

 

RJ has given the easiest to understand option.

 

I currently use transparent clickspots in a single xml gauge with no bitmap and multiple clickspots.

 

 

Are the views hardcoded at a 45° separation? I mean, I've never been able to see the runway from 2D when turning from base to final. The 2D-saur in me would like to see at intermediate angles. I mean, instead of having 0-45-90-135, having something more like 0-22.5-45-67.5-90-112.5-135.

Best regards,
Luis Hernández 20px-Flag_of_Colombia.svg.png20px-Flag_of_Argentina.svg.png

Main rig: self built, AMD Ryzen 7 5700X3D (with SMT off and CO -50 mV), 2x16 GB DDR4-3200 RAM, Nvidia RTX 5060Ti 16GB, 256 GB M.2 SSD (OS+apps) + 2x1 TB SATA III SSD (sims) + 1 TB 7200 rpm HDD (storage), ID-Cooling SE-224-XTS air cooler, Viewsonic VX2458-MHD 1920x1080@120-144 Hz (G-sync compatible), Windows 11. Running P3D v5.4 (with v4.5 scenery objects as an additional library, just in case), FSX-SE, MSFS2020, MSFS2024 and even FS9! Lossless Scaling for all my sims. What a godsend...

Mobile rig: ASUS Zenbook UM425QA (AMD Ryzen 7 5800H APU @3.2 GHz and boost disabled, 1 TB M.2 SSD, 16 GB RAM, Windows 11 Pro). Running FS9 there .

VKB Gladiator NXT Premium Left + GNX THQ as primary controllers. Xbox Series X|S wireless controller as standby/mobile.

Luis you're correct, the views are hardcoded at 45° separation.  The biggest limitation are the number of views you have.  

For example looking left you only three views:
VIEW_FORWARD_LEFT
VIEW_LEFT
VIEW_REAR_LEFT

You can change the angle of these three views to any value you wish, if you don't like the default 45° increments.

 

You have to add this line to the panel.cfg file for each view you want changed:
VIEW_FORWARD_LEFT_DIR=1.0, 0.0, 315    
The 315 in the line above is the default angle looking forward left.  If you want say 23° (left of center), you can change the 315° to 337°. Now the hardcoded view (for this panel only) is 337°, not the default.

If you don't have a "Views" section in your panel.cfg, add one something like this and then tweak away.

Note:  the zoom=1 is default.  I prefer 0.75 for all views which also helps increase your field of view.


[VIEWS]

VIEW_FORWARD_DIR=1.000, 0.000, 0.000
VIEW_FORWARD_ZOOM=1.00

//VIEW_FORWARD_RIGHT_WINDOWS=30
VIEW_FORWARD_RIGHT_DIR=1.000, 0.000, 45.000
VIEW_FORWARD_RIGHT_ZOOM=1.00

//VIEW_RIGHT_WINDOWS=31
VIEW_RIGHT_DIR=1.000, 0.000, 90.000
VIEW_RIGHT_ZOOM=1.00

//VIEW_REAR_RIGHT_WINDOWS=32
VIEW_REAR_RIGHT_DIR=1.000, 0.000, 135.000
VIEW_REAR_RIGHT_ZOOM=1.00

//VIEW_REAR_WINDOWS=33
VIEW_REAR_DIR=1.000, 0.000, 180.000
VIEW_REAR_ZOOM=1.00

//VIEW_REAR_LEFT_WINDOWS=34
VIEW_REAR_LEFT_DIR=1.000, 0.000, 225.000
VIEW_REAR_LEFT_ZOOM=1.00

//VIEW_LEFT_WINDOWS=35
VIEW_LEFT_DIR=1.000, 0.000, 270.000
VIEW_LEFT_ZOOM=1.00

//VIEW_FORWARD_LEFT_WINDOWS=36
VIEW_FORWARD_LEFT_DIR=1.000, 0.000, 315.000
VIEW_FORWARD_LEFT_ZOOM=1.00

//VIEW_FORWARD_UP_WINDOWS=37
VIEW_FORWARD_UP_DIR=1.000, 0.000, 0.000
VIEW_FORWARD_UP_ZOOM=1.000


RJ

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.