Hi there,
I have watched many of your videos and have a couple of questions as I now have completed my Opencockpits setup:
1. How do you keep all your displays the same after each time you load your aircrafts? Each time I load a new aircraft I need to resize all of the displays for each of the monitors. Is there a better way?
2. You have been able to setup the two small displays to the left of the Upper EICAS. How did you do that?
Thanks for all you do!
Question re: panel view
Re: Question re: panel view
I am using P3D. After everything is set correctly I save a scenario and load it.
Then all displays are in the correct position.
If you are using FSX I know there is a program
http://www.casawave.fr/upload/fsx/Panel_Position.zip
How good this is I really do not know.
The 2 small backup instruments you see on my Cockpit image is fake. I have glued in 2 images of the backup instruments behind the MIP frames.
They looks just fine in my cockpit, but are fake.
Then all displays are in the correct position.
If you are using FSX I know there is a program
http://www.casawave.fr/upload/fsx/Panel_Position.zip
How good this is I really do not know.
The 2 small backup instruments you see on my Cockpit image is fake. I have glued in 2 images of the backup instruments behind the MIP frames.
They looks just fine in my cockpit, but are fake.
-
- Posts: 46
- Joined: Sun May 24, 2015 2:59 pm
Re: Question re: panel view
Hi
Maybe I can help you (both?), but probably you need P3D to get the same results. I created separate panel windows for my three MIP monitors and the two CDU screens. These make windows very stable. The standby instruments you ask for are combined in a separate definition in NGX. After I have found them (PMDG_737NGX!Standby), I combined these with the upper EICAS to my center MIP monitor. You need to complement your panel.cfg file as follows:
[Window Titles]
...
window20=CDU Display left
window21=CDU Display right
window22=MIP left
window23=MIP middle
window24=MIP right
//--------------------------------------------------------
.........
//
// CDU Screen Left
//
[Window20]
BACKGROUND_COLOR=1,1,1
size_mm=385, 600
window_size = 0.2, 0.25 // in Bezug auf FS Fenster
position=6
visible=1
ident=CDUScreenL
zorder=99
gauge00=PMDG_737NGX!CDU_Screen, 0,0,385,600,L #0
//
// CDU Screen Right
//
[Window21]
BACKGROUND_COLOR=1,1,1
size_mm=385, 600
window_size = 0.2, 0.25
position=8
visible=1
ident=CDUScreenR
zorder=99
gauge00=PMDG_737NGX!CDU_Screen, 0,0,385,600,R #0
//
// MIP left
//
[Window22]
BACKGROUND_COLOR=1,1,1
size_mm=1240, 560
window_size = 0.2, 0.25
position=3
visible=1
ident=MIPL
zorder=99
gauge00=PMDG_737NGX!DU, -50, -50, 677, 636, 1 LEFT_OUTBD #11 ZOOM
gauge01=PMDG_737NGX!DU, 625, -50, 677, 636, 1 LEFT_INBD #12 ZOOM
//
// MIP middle
//
[Window23]
BACKGROUND_COLOR=1,1,1
size_mm=850, 520
window_size = 0.2, 0.25
position=4
visible=1
ident=MIPM
zorder=99
gauge00=PMDG_737NGX!Standby, 0, -310, 300, 850
gauge01=PMDG_737NGX!DU, 300, -50, 600, 600, 1 UPPER #13 ZOOM
//
// MIP right
//
[Window24]
BACKGROUND_COLOR=1,1,1
size_mm=1240, 560
window_size = 0.2, 0.25
position=5
visible=1
ident=MIPR
zorder=99
gauge00=PMDG_737NGX!DU, -55, -50, 677, 636, 1 RIGHT_INBD #15 ZOOM
gauge01=PMDG_737NGX!DU, 625, -50, 672, 636, 1 RIGHT_OUTBD #16 ZOOM
Of course, some adjustment of size and position to your monitors may be needed. Please let us know if you succeeded
Best regards
Urs
Maybe I can help you (both?), but probably you need P3D to get the same results. I created separate panel windows for my three MIP monitors and the two CDU screens. These make windows very stable. The standby instruments you ask for are combined in a separate definition in NGX. After I have found them (PMDG_737NGX!Standby), I combined these with the upper EICAS to my center MIP monitor. You need to complement your panel.cfg file as follows:
[Window Titles]
...
window20=CDU Display left
window21=CDU Display right
window22=MIP left
window23=MIP middle
window24=MIP right
//--------------------------------------------------------
.........
//
// CDU Screen Left
//
[Window20]
BACKGROUND_COLOR=1,1,1
size_mm=385, 600
window_size = 0.2, 0.25 // in Bezug auf FS Fenster
position=6
visible=1
ident=CDUScreenL
zorder=99
gauge00=PMDG_737NGX!CDU_Screen, 0,0,385,600,L #0
//
// CDU Screen Right
//
[Window21]
BACKGROUND_COLOR=1,1,1
size_mm=385, 600
window_size = 0.2, 0.25
position=8
visible=1
ident=CDUScreenR
zorder=99
gauge00=PMDG_737NGX!CDU_Screen, 0,0,385,600,R #0
//
// MIP left
//
[Window22]
BACKGROUND_COLOR=1,1,1
size_mm=1240, 560
window_size = 0.2, 0.25
position=3
visible=1
ident=MIPL
zorder=99
gauge00=PMDG_737NGX!DU, -50, -50, 677, 636, 1 LEFT_OUTBD #11 ZOOM
gauge01=PMDG_737NGX!DU, 625, -50, 677, 636, 1 LEFT_INBD #12 ZOOM
//
// MIP middle
//
[Window23]
BACKGROUND_COLOR=1,1,1
size_mm=850, 520
window_size = 0.2, 0.25
position=4
visible=1
ident=MIPM
zorder=99
gauge00=PMDG_737NGX!Standby, 0, -310, 300, 850
gauge01=PMDG_737NGX!DU, 300, -50, 600, 600, 1 UPPER #13 ZOOM
//
// MIP right
//
[Window24]
BACKGROUND_COLOR=1,1,1
size_mm=1240, 560
window_size = 0.2, 0.25
position=5
visible=1
ident=MIPR
zorder=99
gauge00=PMDG_737NGX!DU, -55, -50, 677, 636, 1 RIGHT_INBD #15 ZOOM
gauge01=PMDG_737NGX!DU, 625, -50, 672, 636, 1 RIGHT_OUTBD #16 ZOOM
Of course, some adjustment of size and position to your monitors may be needed. Please let us know if you succeeded
Best regards
Urs
Re: Question re: panel view
Thanks Urs,
I think this panel setup modification deserves to be included in the latest OC4BAv4 documentation.
I have played around with this type of setup before, but never really used them. I have been using
the standard approach :
opening all MIP zoom windows and FMC windows by clicking all windows in the Virtual Cockpit
undocking all windows
moving the undocked windows to correct monitor and position in the monitor
saving this setup as a default scenario file called "MyCockpit"
and then just loading "MyCockpit" from the Scenario Startup Screen
I need to have a closer look at your setup and find a way to have the correct "MyCockpit" windows setup when loading any NGX livery and airport without having to load "MyCockpit" scenario file as this also put me on a predefined airport. I can always change my airport later, but I want a 1 step setup instead of a 2 step setup as I have to today.
I think this panel setup modification deserves to be included in the latest OC4BAv4 documentation.
I have played around with this type of setup before, but never really used them. I have been using
the standard approach :
opening all MIP zoom windows and FMC windows by clicking all windows in the Virtual Cockpit
undocking all windows
moving the undocked windows to correct monitor and position in the monitor
saving this setup as a default scenario file called "MyCockpit"
and then just loading "MyCockpit" from the Scenario Startup Screen
I need to have a closer look at your setup and find a way to have the correct "MyCockpit" windows setup when loading any NGX livery and airport without having to load "MyCockpit" scenario file as this also put me on a predefined airport. I can always change my airport later, but I want a 1 step setup instead of a 2 step setup as I have to today.
Re: Question re: panel view
Thats really good information. Thanks Urs. I'll try this tonight on P3Dv4
Re: Question re: panel view
Again, thanks Urs for the code.
I changed mine a little to be used with my Single trainer MIP. I also included the lower EICAS.
See below if anyone wishes to take:
//
// CDU Screen Left
//
[Window20]
BACKGROUND_COLOR=1,1,1
size_mm=385, 600
window_size = 0.8, 1.00 // in Bezug auf FS Fenster
position=6
visible=1
ident=CDUScreenL
zorder=99
gauge00=PMDG_737NGX!CDU_Screen, 0,0,385,600,L #0
//
// MIP left
//
[Window21]
BACKGROUND_COLOR=1,1,1
size_mm=1240, 560
window_size = 0.8, 1.0
position=3
visible=1
ident=MIPL
zorder=99
gauge00=PMDG_737NGX!DU, -50, -50, 677, 636, 1 LEFT_OUTBD #11 ZOOM
gauge01=PMDG_737NGX!DU, 625, -50, 677, 636, 1 LEFT_INBD #12 ZOOM
//
// MIP middle
//
[Window22]
BACKGROUND_COLOR=1,1,1
size_mm=850, 520
window_size = 0.8, 1.00
position=4
visible=1
ident=MIPM
zorder=99
gauge00=PMDG_737NGX!Standby, 0, -310, 300, 850
gauge01=PMDG_737NGX!DU, 300, -50, 600, 600, 1 UPPER #13 ZOOM`
//
// Lower DU MIP
//
[Window23]
BACKGROUND_COLOR=1,1,1
size_mm=451, 424
window_size = 0.8, 1.0
position=8
visible=1
ident=DUL
zorder=95
gauge00=PMDG_737NGX!DU, 0, 0, 451, 424, LOWER #4
I changed mine a little to be used with my Single trainer MIP. I also included the lower EICAS.
See below if anyone wishes to take:
//
// CDU Screen Left
//
[Window20]
BACKGROUND_COLOR=1,1,1
size_mm=385, 600
window_size = 0.8, 1.00 // in Bezug auf FS Fenster
position=6
visible=1
ident=CDUScreenL
zorder=99
gauge00=PMDG_737NGX!CDU_Screen, 0,0,385,600,L #0
//
// MIP left
//
[Window21]
BACKGROUND_COLOR=1,1,1
size_mm=1240, 560
window_size = 0.8, 1.0
position=3
visible=1
ident=MIPL
zorder=99
gauge00=PMDG_737NGX!DU, -50, -50, 677, 636, 1 LEFT_OUTBD #11 ZOOM
gauge01=PMDG_737NGX!DU, 625, -50, 677, 636, 1 LEFT_INBD #12 ZOOM
//
// MIP middle
//
[Window22]
BACKGROUND_COLOR=1,1,1
size_mm=850, 520
window_size = 0.8, 1.00
position=4
visible=1
ident=MIPM
zorder=99
gauge00=PMDG_737NGX!Standby, 0, -310, 300, 850
gauge01=PMDG_737NGX!DU, 300, -50, 600, 600, 1 UPPER #13 ZOOM`
//
// Lower DU MIP
//
[Window23]
BACKGROUND_COLOR=1,1,1
size_mm=451, 424
window_size = 0.8, 1.0
position=8
visible=1
ident=DUL
zorder=95
gauge00=PMDG_737NGX!DU, 0, 0, 451, 424, LOWER #4