George, the obvious thing for you and I to do would be to create a Zip of panel.cfg files for all the default aircraft, tweaked for triplehead, and make this publicly available.
I'm not sure how much time I have, at the moment. However, what do you think?
Problem With TripleHead2Go and FSX 2D View
Problem With TripleHead2Go and FSX 2D View
John,
I think that's a great idea. I've been going through all my installed aircraft (both default and 3rd party) and have been making the size and position changes to each, and then saving each panel.cfg file into a faux folder structure to mimic the install paths, to make it easy for me to restore them at a later time, should a reinstall become neccesary. The last default aircraft I finished was the Extra 300, and the Goose is up next. We can work out a list of aircraft that we can each tackle, and get almost twice the work done in half the time. Let me know which ones you've done or are working on, and we can get these knocked out fairly quickly I'd think. :)
-George
Edited to add: John, check your pm's here. :)
I think that's a great idea. I've been going through all my installed aircraft (both default and 3rd party) and have been making the size and position changes to each, and then saving each panel.cfg file into a faux folder structure to mimic the install paths, to make it easy for me to restore them at a later time, should a reinstall become neccesary. The last default aircraft I finished was the Extra 300, and the Goose is up next. We can work out a list of aircraft that we can each tackle, and get almost twice the work done in half the time. Let me know which ones you've done or are working on, and we can get these knocked out fairly quickly I'd think. :)
-George
Edited to add: John, check your pm's here. :)
Problem With TripleHead2Go and FSX 2D View
Hi George and John,
I'm getting better, but the Pilatus PC-12 Overhead still ignores any changes and I can't grab the border with the mouse. Here's the original config and the new one after I edited the size line. It opens across the whole center monitor and extends part way into the left and right monitors. Can you figure what's up? :? Thanks again. Tom :)
---------------------------------------------
[Window03]
file=PC-12_overhead.bmp
file_1024=PC-12_overhead.bmp
size_mm=1828,813
window_size_ratio=1.000
position=0
visible=0
ident=70
window_size= 0.810, 0.472
window_pos= 0.105, 0.000
AFTER MY CHANGES
//--------------------------------------------------------
[Window03]
file=PC-12_overhead.bmp
file_1024=PC-12_overhead.bmp
size_mm=1828,813
window_size_ratio=1.000
position=0
visible=0
ident=70
window_size= 0.540, 0.315
window_pos= 0.000, 0.000
I'm getting better, but the Pilatus PC-12 Overhead still ignores any changes and I can't grab the border with the mouse. Here's the original config and the new one after I edited the size line. It opens across the whole center monitor and extends part way into the left and right monitors. Can you figure what's up? :? Thanks again. Tom :)
---------------------------------------------
[Window03]
file=PC-12_overhead.bmp
file_1024=PC-12_overhead.bmp
size_mm=1828,813
window_size_ratio=1.000
position=0
visible=0
ident=70
window_size= 0.810, 0.472
window_pos= 0.105, 0.000
AFTER MY CHANGES
//--------------------------------------------------------
[Window03]
file=PC-12_overhead.bmp
file_1024=PC-12_overhead.bmp
size_mm=1828,813
window_size_ratio=1.000
position=0
visible=0
ident=70
window_size= 0.540, 0.315
window_pos= 0.000, 0.000
Problem With TripleHead2Go and FSX 2D View
Hi Tom.
I've encountered this on one aircraft so far, though I don't remember which one it was off the top of my head. In my case, it had something to do with the size being defined on one of the gauges. I don't know which one, but I made the changes to each gauge for that window.
Here's what worked in my situation, I can't say if it will or won't work for you, so as always, make a backup copy of your panel.cfg file before making any changes.
What you can try is highlight and copy the entire 'gauge.x' for window.3, then paste it in directly below the highlighted section. Then go up to the first set of gauge entries, and comment out those lines, so that only one set of gauges is 'active'. Finally, remove the size entry for each defined gauge, save the file, and try firing it up in Flight Sim.
For example, if this is roughly your window entry:
[window.3]
file=blah
sizemm=blah
window_size=blah
gauge.0=gaugename 0, 0, 200, 150
gauge.1=gaugename 200, 150, 200, 150
gauge.2=gaugename 400, 150, 200, 150
Then when you've made your changes, it should look something like this:
[window.3]
file=blah
sizemm=blah
window_size=blah
//gauge.0=gaugename 0, 0, 200, 150
//gauge.1=gaugename 200, 150, 200, 150
//gauge.2=gaugename 400, 150, 200, 150
gauge.0=gaugename 0, 0
gauge.1=gaugename 200, 150
gauge.2=gaugename 400, 150
If the changes don't work, you can just remove the new gauge entries, and then un-comment the original entries.
Good luck, and I hope that works for you. It worked for me on a different aircraft, but I don't have the PC-12, so I can't say if this will or won't work for you.
-George
I've encountered this on one aircraft so far, though I don't remember which one it was off the top of my head. In my case, it had something to do with the size being defined on one of the gauges. I don't know which one, but I made the changes to each gauge for that window.
Here's what worked in my situation, I can't say if it will or won't work for you, so as always, make a backup copy of your panel.cfg file before making any changes.
What you can try is highlight and copy the entire 'gauge.x' for window.3, then paste it in directly below the highlighted section. Then go up to the first set of gauge entries, and comment out those lines, so that only one set of gauges is 'active'. Finally, remove the size entry for each defined gauge, save the file, and try firing it up in Flight Sim.
For example, if this is roughly your window entry:
[window.3]
file=blah
sizemm=blah
window_size=blah
gauge.0=gaugename 0, 0, 200, 150
gauge.1=gaugename 200, 150, 200, 150
gauge.2=gaugename 400, 150, 200, 150
Then when you've made your changes, it should look something like this:
[window.3]
file=blah
sizemm=blah
window_size=blah
//gauge.0=gaugename 0, 0, 200, 150
//gauge.1=gaugename 200, 150, 200, 150
//gauge.2=gaugename 400, 150, 200, 150
gauge.0=gaugename 0, 0
gauge.1=gaugename 200, 150
gauge.2=gaugename 400, 150
If the changes don't work, you can just remove the new gauge entries, and then un-comment the original entries.
Good luck, and I hope that works for you. It worked for me on a different aircraft, but I don't have the PC-12, so I can't say if this will or won't work for you.
-George
Problem With TripleHead2Go and FSX 2D View
hi Guys,
Been searching and reading a lot about FSX and multimonitorsetup. I have to reread everything over again because some information in forums is not completly 100% true in all situations. Glad I found this discussion. I don't get it 100% for sure yet but i am convinced that you guys know what is and what isn't possible.
What I want:
- universal glass cockpit working with payware like 737 pmdg for fsx (upcoming) or other payware aircraft.
- seperate pc only for generating outside view
- full screen mode, at least no ugly windowed mode for instruments preferred
pc1 fsx with hardware controls, throttle etc MCP pro en steering
on 3 screens: all additional instruments in 2D mode with or without TH2GO
pc2 outside view 3x 22" with or without TH2GO
done with Wideview
Seems easy..too many possibilities and problems to run into... though is not...at least not to me yet..
I already have TH2GO 3x 19" ("1280x1024 4:3) and 2x 22"(16:9) on 2 pc. Last year I did not use FSX much and i am in the process of builing my ultimate (universal) glass cockpit and also encounterd problems like described in this thread.
so my questions:
Will I for 100% sure be able to display 2D instruments on the 3 19" Screens ? With or without TH2GO preferred ? In full screen mode and payware aircrafts ?
at the moment I have TH2GO with 3 19"and 1 22"on one pc. Lots of problems in 2D. Have to test again when I have more time but hoping due to your experiences in this specific thread some of you can point me in the "best"direction.
Maybe it all sounds a bit stupid: how the heck can I when displaying main panel remove the outside view in 2D mode ?
Thanks
Remco
Been searching and reading a lot about FSX and multimonitorsetup. I have to reread everything over again because some information in forums is not completly 100% true in all situations. Glad I found this discussion. I don't get it 100% for sure yet but i am convinced that you guys know what is and what isn't possible.
What I want:
- universal glass cockpit working with payware like 737 pmdg for fsx (upcoming) or other payware aircraft.
- seperate pc only for generating outside view
- full screen mode, at least no ugly windowed mode for instruments preferred
pc1 fsx with hardware controls, throttle etc MCP pro en steering
on 3 screens: all additional instruments in 2D mode with or without TH2GO
pc2 outside view 3x 22" with or without TH2GO
done with Wideview
Seems easy..too many possibilities and problems to run into... though is not...at least not to me yet..
I already have TH2GO 3x 19" ("1280x1024 4:3) and 2x 22"(16:9) on 2 pc. Last year I did not use FSX much and i am in the process of builing my ultimate (universal) glass cockpit and also encounterd problems like described in this thread.
so my questions:
Will I for 100% sure be able to display 2D instruments on the 3 19" Screens ? With or without TH2GO preferred ? In full screen mode and payware aircrafts ?
at the moment I have TH2GO with 3 19"and 1 22"on one pc. Lots of problems in 2D. Have to test again when I have more time but hoping due to your experiences in this specific thread some of you can point me in the "best"direction.
Maybe it all sounds a bit stupid: how the heck can I when displaying main panel remove the outside view in 2D mode ?
Thanks
Remco
-
john bentley
- Posts: 123
- Joined: 13 Oct 2008, 07:06
Problem With TripleHead2Go and FSX 2D View
Remco,
Indulge my repeating your problem in my own words. You want, in general:
* Top row: 3 screens to display outside view as one continuous scene (rather than forward plus port plus starboard view).
* Bottom row: 3 screens to display instruments in 2D.
* Hardware controllers (eg throttle, MCP pro module, and Yoke).
You want to know the best way to achieve this. That is, you want to know how TH2GO, wideview, and any other alternative might fit into the mix.
Some further specific questions you have are:
* Will payware work just as well as the default aircraft, under the above configuration?
* How can I remove outside view when using a monitor to display only a main panel?
Sorry in advance for not being able to provide a full answer. I have only worked with a maximum of 3 screens, never used payware, nor used WideView.
I'm not close to 100% sure of any of the following as each setup has the potential to through up exceptions to the general rule. I'll tell you want I think is likely.
Consider first using Eyefinity. This is new technology from ATI in their newer graphics cards that allows multimoniter setups. I believe one card can drive 6 monitors (?), which has the potential to simplify many of your issues. However, at the moment you loose bezel management. I consider this a deal breaker for FSX in outside view.
So I'll continue to outline a TH2GO based solution.
For the top row I think you will need TH2GO (I have only used the Digital Edition) in order to have the one continuous scene (with the bonus of bezel management). This could be in windowed or full screen mode although full screen mode is recommended by MS for performance reasons.
SoftTH would be an possible alternative but probably not practical given that FSX is frame rate intensive.
For the bottom row I do not think you will need TH2GO. You just have 3 independent monitors driven by two graphics cards.
The main lesson from this thread, in brief, is that for 3 screens, under TH2GO (and probably for eyefinity or SoftTH), you should resize panels by a third in the width dimension. You leave the height dimension untouched. You do this by altering, in the panel.cfg for your aircraft:
window_size= width, height
eg to
window_size=0.333, 1.000
The rest of this thread goes into further details and exceptions.
The above (brief) rule applies equally for windowed mode or full screen mode. However if you are not using TH2GO (nor eyefinity nor SoftTH) to drive your 3 screens, that is, if you are just using 2 graphics cards to drive 3 screens independently, then you do not need to touch the panel.cfg. This is because you will have 3 screens at single monitor resolutions, eg 3 X (1280 x 1024), rather than 3 screens at a surround resolution, eg 3,840 X 1024.
In other words, for your setup, you shouldn't need touch window_size in panel.cfg.
Syncing the FSX between your two PCs might be best achieved through WideView. However, I seem to recall on this forum someone using daisy chained TH2GO units rather than WideView (for more than 3 monitors) .... so keep searching for that thread :)
Edit: I'm not clear how you preserve your panel layout using Wideview. Presumably, at least, after manually arranging your main and sub panels you can save the whole thing as a flight.
Payware should work just as well as default aircraft. However, this is provided that they conform to MS conventions. If there exists a panel.cfg for a payware aircraft I don't see why it shouldn't work.
There are several suggested methods to remove outside view using wideview settings (or using methods independent of wideview).
If none of those work for you I tried:
* Open your aircraft's panel.cfg
* Set each of the values under [Default View] to 0. That is,
This give squashed the outside view to a 50px X 50px square in the top left corner. Less than ideal but something.
Indulge my repeating your problem in my own words. You want, in general:
* Top row: 3 screens to display outside view as one continuous scene (rather than forward plus port plus starboard view).
* Bottom row: 3 screens to display instruments in 2D.
* Hardware controllers (eg throttle, MCP pro module, and Yoke).
You want to know the best way to achieve this. That is, you want to know how TH2GO, wideview, and any other alternative might fit into the mix.
Some further specific questions you have are:
* Will payware work just as well as the default aircraft, under the above configuration?
* How can I remove outside view when using a monitor to display only a main panel?
Sorry in advance for not being able to provide a full answer. I have only worked with a maximum of 3 screens, never used payware, nor used WideView.
I'm not close to 100% sure of any of the following as each setup has the potential to through up exceptions to the general rule. I'll tell you want I think is likely.
Consider first using Eyefinity. This is new technology from ATI in their newer graphics cards that allows multimoniter setups. I believe one card can drive 6 monitors (?), which has the potential to simplify many of your issues. However, at the moment you loose bezel management. I consider this a deal breaker for FSX in outside view.
So I'll continue to outline a TH2GO based solution.
For the top row I think you will need TH2GO (I have only used the Digital Edition) in order to have the one continuous scene (with the bonus of bezel management). This could be in windowed or full screen mode although full screen mode is recommended by MS for performance reasons.
SoftTH would be an possible alternative but probably not practical given that FSX is frame rate intensive.
For the bottom row I do not think you will need TH2GO. You just have 3 independent monitors driven by two graphics cards.
The main lesson from this thread, in brief, is that for 3 screens, under TH2GO (and probably for eyefinity or SoftTH), you should resize panels by a third in the width dimension. You leave the height dimension untouched. You do this by altering, in the panel.cfg for your aircraft:
window_size= width, height
eg to
window_size=0.333, 1.000
The rest of this thread goes into further details and exceptions.
The above (brief) rule applies equally for windowed mode or full screen mode. However if you are not using TH2GO (nor eyefinity nor SoftTH) to drive your 3 screens, that is, if you are just using 2 graphics cards to drive 3 screens independently, then you do not need to touch the panel.cfg. This is because you will have 3 screens at single monitor resolutions, eg 3 X (1280 x 1024), rather than 3 screens at a surround resolution, eg 3,840 X 1024.
In other words, for your setup, you shouldn't need touch window_size in panel.cfg.
Syncing the FSX between your two PCs might be best achieved through WideView. However, I seem to recall on this forum someone using daisy chained TH2GO units rather than WideView (for more than 3 monitors) .... so keep searching for that thread :)
Edit: I'm not clear how you preserve your panel layout using Wideview. Presumably, at least, after manually arranging your main and sub panels you can save the whole thing as a flight.
Payware should work just as well as default aircraft. However, this is provided that they conform to MS conventions. If there exists a panel.cfg for a payware aircraft I don't see why it shouldn't work.
There are several suggested methods to remove outside view using wideview settings (or using methods independent of wideview).
If none of those work for you I tried:
* Open your aircraft's panel.cfg
* Set each of the values under [Default View] to 0. That is,
Code: Select all
[Default View]
X=0
Y=0
SIZE_X=0
SIZE_Y=0This give squashed the outside view to a 50px X 50px square in the top left corner. Less than ideal but something.
Problem With TripleHead2Go and FSX 2D View
thanks for your answer.
But I meant:
When I have the main panel of an aircraft on lower screens (no wideview just fsx) i dont want to see above the 2D panel, an outside cockpit view (because that outside view is already on upper 3 screens)
(in the picture I have undocked instruments though not the main panel)
Problem With TripleHead2Go and FSX 2D View
Hi George,
Here is my entire Window3 file. What do you mean by removing the size entries? As you can see, the gauge entries are quite complicated and I am not sure what to remove. Thanks for hanging in there with me. Tom
[Window03]
file=PC-12_overhead.bmp
file_1024=PC-12_overhead.bmp
size_mm=1828,813
window_size_ratio=1.000
position=0
visible=0
ident=70
window_size= 0.810, 0.472
window_pos= 0.105, 0.000
gauge00=F1PC12!Overhead VoltAmps, 585,167,130
gauge01=F1PC12!Engine Start, 177,667,70
gauge02=F1PC12!Switch Beacon Lights, 287,286,70
gauge03=F1PC12!Switch Taxi Lights, 175,87,70
gauge04=F1PC12!Switch Master Power, 1203,73,220
gauge05=F1PC12!Switch Nav Lights, 287,185,70
gauge06=F1PC12!Switch Strobe Lights, 175,288,70
gauge07=F1PC12!Switch Landing Lights, 287,87,70
gauge08=F1PC12!Switch Fuel Pump L, 175,534,70,70
gauge09=F1PC12!Switch Fuel Pump R, 287,534,70,70
gauge10=F1PC12!Switch Logo Lights, 287,386,70,70
gauge11=F1PC12!Switch Recognition Lights, 175,386,70,70
gauge12=F1PC12!Switch Wing Lights, 175,185,70,70
gauge13=F1PC12!Switch Fire, 67,287,70,70
gauge14=F1PC12!Switch Boots, 1580, 88 ,70,70
gauge15=F1PC12!Switch Boots 3min 1min, 1477,88,70,70
gauge16=F1PC12!Switch Cabin Heat, 1477,687,70,70
gauge17=F1PC12!Switch Cooling Fan, 1580,543,70,70
gauge18=F1PC12!Switch Cooling Recirc, 1477,420,70,70
gauge19=F1PC12!Switch Cooling System, 1580,420,70,70
gauge20=F1PC12!Switch WS Washer L, 1580,190,70,70
gauge21=F1PC12!Switch WS Washer L HL, 1477,190,70,70
gauge22=F1PC12!Switch WS Washer R, 1580,289,70,70
gauge23=F1PC12!Switch WS Washer R HL, 1477,289,70,70
gauge24=F1PC12!Switch Cooling Vent, 1477,543,70,70
gauge25=F1PC12!Switch Ignition, 286,666,70,70
gauge26=F1PC12!Switch Inertial Separator, 1685,190,70,70
gauge27=F1PC12!Switch No Smoking, 1685,420,70,70
gauge28=F1PC12!Switch Probe Heat, 1685,289,70,70
gauge29=F1PC12!Switch Prop Deice, 1685,88,70,70
gauge30=F1PC12!Switch Seatbelt, 1685,543,70,70
gauge31=F1PC12!Switch Pusher, 67,186,70,70
gauge32=F1PC12!Switch AV1, 624,664,52,102
gauge33=F1PC12!Switch AV2, 518,664,52
gauge34=F1PC12!Switch Battery 1, 624,374,52,102
gauge35=F1PC12!Switch External Power, 729,374,52,102
gauge36=F1PC12!Switch Gen 1, 520,374,52,102
gauge37=F1PC12!Switch Gen 2, 1185,370,52,102
gauge38=F1PC12!Switch Inv Gen 1, 1078,662,52,102
gauge39=F1PC12!Switch Non Essential, 730,664,52,102
gauge40=F1PC12!Switch Standby Bus, 1184,662,52,102
gauge41=F1PC12!Switch Overhead Test, 67,90,70,68
gauge42=F1PC12!Light Gen 1, 533,472,25,25
gauge43=F1PC12!Light Gen 2, 1199,472,25,25
gauge44=F1PC12!Light Battery 1, 638,472,25,25
gauge45=F1PC12!Light Avionics, 638,638,25,25
gauge46=F1PC12!Light External Power, 743,472,25,25
gauge47=F1PC12!Light Standby Bus, 1247,640,58,25
gauge48=F1PC12!Light Avionics, 532,637,25,25
Here is my entire Window3 file. What do you mean by removing the size entries? As you can see, the gauge entries are quite complicated and I am not sure what to remove. Thanks for hanging in there with me. Tom
[Window03]
file=PC-12_overhead.bmp
file_1024=PC-12_overhead.bmp
size_mm=1828,813
window_size_ratio=1.000
position=0
visible=0
ident=70
window_size= 0.810, 0.472
window_pos= 0.105, 0.000
gauge00=F1PC12!Overhead VoltAmps, 585,167,130
gauge01=F1PC12!Engine Start, 177,667,70
gauge02=F1PC12!Switch Beacon Lights, 287,286,70
gauge03=F1PC12!Switch Taxi Lights, 175,87,70
gauge04=F1PC12!Switch Master Power, 1203,73,220
gauge05=F1PC12!Switch Nav Lights, 287,185,70
gauge06=F1PC12!Switch Strobe Lights, 175,288,70
gauge07=F1PC12!Switch Landing Lights, 287,87,70
gauge08=F1PC12!Switch Fuel Pump L, 175,534,70,70
gauge09=F1PC12!Switch Fuel Pump R, 287,534,70,70
gauge10=F1PC12!Switch Logo Lights, 287,386,70,70
gauge11=F1PC12!Switch Recognition Lights, 175,386,70,70
gauge12=F1PC12!Switch Wing Lights, 175,185,70,70
gauge13=F1PC12!Switch Fire, 67,287,70,70
gauge14=F1PC12!Switch Boots, 1580, 88 ,70,70
gauge15=F1PC12!Switch Boots 3min 1min, 1477,88,70,70
gauge16=F1PC12!Switch Cabin Heat, 1477,687,70,70
gauge17=F1PC12!Switch Cooling Fan, 1580,543,70,70
gauge18=F1PC12!Switch Cooling Recirc, 1477,420,70,70
gauge19=F1PC12!Switch Cooling System, 1580,420,70,70
gauge20=F1PC12!Switch WS Washer L, 1580,190,70,70
gauge21=F1PC12!Switch WS Washer L HL, 1477,190,70,70
gauge22=F1PC12!Switch WS Washer R, 1580,289,70,70
gauge23=F1PC12!Switch WS Washer R HL, 1477,289,70,70
gauge24=F1PC12!Switch Cooling Vent, 1477,543,70,70
gauge25=F1PC12!Switch Ignition, 286,666,70,70
gauge26=F1PC12!Switch Inertial Separator, 1685,190,70,70
gauge27=F1PC12!Switch No Smoking, 1685,420,70,70
gauge28=F1PC12!Switch Probe Heat, 1685,289,70,70
gauge29=F1PC12!Switch Prop Deice, 1685,88,70,70
gauge30=F1PC12!Switch Seatbelt, 1685,543,70,70
gauge31=F1PC12!Switch Pusher, 67,186,70,70
gauge32=F1PC12!Switch AV1, 624,664,52,102
gauge33=F1PC12!Switch AV2, 518,664,52
gauge34=F1PC12!Switch Battery 1, 624,374,52,102
gauge35=F1PC12!Switch External Power, 729,374,52,102
gauge36=F1PC12!Switch Gen 1, 520,374,52,102
gauge37=F1PC12!Switch Gen 2, 1185,370,52,102
gauge38=F1PC12!Switch Inv Gen 1, 1078,662,52,102
gauge39=F1PC12!Switch Non Essential, 730,664,52,102
gauge40=F1PC12!Switch Standby Bus, 1184,662,52,102
gauge41=F1PC12!Switch Overhead Test, 67,90,70,68
gauge42=F1PC12!Light Gen 1, 533,472,25,25
gauge43=F1PC12!Light Gen 2, 1199,472,25,25
gauge44=F1PC12!Light Battery 1, 638,472,25,25
gauge45=F1PC12!Light Avionics, 638,638,25,25
gauge46=F1PC12!Light External Power, 743,472,25,25
gauge47=F1PC12!Light Standby Bus, 1247,640,58,25
gauge48=F1PC12!Light Avionics, 532,637,25,25
-
john bentley
- Posts: 123
- Joined: 13 Oct 2008, 07:06
Problem With TripleHead2Go and FSX 2D View
When I have the main panel of an aircraft on lower screens (no wideview just fsx) i dont want to see above the 2D panel, an outside cockpit view (because that outside view is already on upper 3 screens)
Yes I understood this to be your case. My suggested changes under [Default View] are one possible way to (inadequately) achieve this. For my default 737 I get the main panel (in 2D), a black screen replacing outside view, except the 50 x 50 pixel top left window containing the outside view.
Problem With TripleHead2Go and FSX 2D View
Hi Tom,
in the gauge definitions, the first two numbers correspond to placement based on a scale that is defined in size_mm. Any numbers following the placement coordinates are used to define the gauge's size relative to the size of the panel window. For example, in the line:
gauge08=F1PC12!Switch Fuel Pump L, 175,534,70,70
gauge08=F1PC12!Switch Fuel Pump L, (This part of the line defines the gauge to use)
175,534 (These first two values define the coordinates to position the gauge in relation to the panel's size_mm definition)
,70,70 (These values define the size of the gauge in relation to the panel's size_mm definition)
In most cases, the sizes defined for individual gauges do not have a negative impact, however I have encountered one plane where the panel window wouldn't resize until I had removed the size entries from that particular panel window.
Here's a modified version of the window code you posted above for you to try. I can't guarantee that this will or won't work for you, so as always, make a backup of your panel.cfg file before making any changes. Then try replacing the [window03] entry with the one from below:
[Window03]
file=PC-12_overhead.bmp
file_1024=PC-12_overhead.bmp
size_mm=1828,813
window_size_ratio=1.000
position=0
visible=0
ident=70
window_size= 0.810, 0.472
window_pos= 0.105, 0.000
gauge00=F1PC12!Overhead VoltAmps, 585,167
gauge01=F1PC12!Engine Start, 177,667
gauge02=F1PC12!Switch Beacon Lights, 287,286
gauge03=F1PC12!Switch Taxi Lights, 175,87
gauge04=F1PC12!Switch Master Power, 1203,73
gauge05=F1PC12!Switch Nav Lights, 287,185
gauge06=F1PC12!Switch Strobe Lights, 175,288
gauge07=F1PC12!Switch Landing Lights, 287,87
gauge08=F1PC12!Switch Fuel Pump L, 175,534
gauge09=F1PC12!Switch Fuel Pump R, 287,534
gauge10=F1PC12!Switch Logo Lights, 287,386
gauge11=F1PC12!Switch Recognition Lights, 175,386
gauge12=F1PC12!Switch Wing Lights, 175,185
gauge13=F1PC12!Switch Fire, 67,287
gauge14=F1PC12!Switch Boots, 1580, 88
gauge15=F1PC12!Switch Boots 3min 1min, 1477,88
gauge16=F1PC12!Switch Cabin Heat, 1477,687
gauge17=F1PC12!Switch Cooling Fan, 1580,543
gauge18=F1PC12!Switch Cooling Recirc, 1477,420
gauge19=F1PC12!Switch Cooling System, 1580,420
gauge20=F1PC12!Switch WS Washer L, 1580,190
gauge21=F1PC12!Switch WS Washer L HL, 1477,190
gauge22=F1PC12!Switch WS Washer R, 1580,289
gauge23=F1PC12!Switch WS Washer R HL, 1477,289
gauge24=F1PC12!Switch Cooling Vent, 1477,543
gauge25=F1PC12!Switch Ignition, 286,666
gauge26=F1PC12!Switch Inertial Separator, 1685,190
gauge27=F1PC12!Switch No Smoking, 1685,420
gauge28=F1PC12!Switch Probe Heat, 1685,289
gauge29=F1PC12!Switch Prop Deice, 1685,88
gauge30=F1PC12!Switch Seatbelt, 1685,543
gauge31=F1PC12!Switch Pusher, 67,186
gauge32=F1PC12!Switch AV1, 624,664
gauge33=F1PC12!Switch AV2, 518,664
gauge34=F1PC12!Switch Battery 1, 624,374
gauge35=F1PC12!Switch External Power, 729,374
gauge36=F1PC12!Switch Gen 1, 520,374
gauge37=F1PC12!Switch Gen 2, 1185,370
gauge38=F1PC12!Switch Inv Gen 1, 1078,662
gauge39=F1PC12!Switch Non Essential, 730,664
gauge40=F1PC12!Switch Standby Bus, 1184,662
gauge41=F1PC12!Switch Overhead Test, 67,90
gauge42=F1PC12!Light Gen 1, 533,472
gauge43=F1PC12!Light Gen 2, 1199,472
gauge44=F1PC12!Light Battery 1, 638,472
gauge45=F1PC12!Light Avionics, 638,638
gauge46=F1PC12!Light External Power, 743,472
gauge47=F1PC12!Light Standby Bus, 1247,640
gauge48=F1PC12!Light Avionics, 532,637
//------END OF WINDOW CODE--- DO NOT COPY BELOW THIS LINE----
If that still doesn't get the window sized properly for you, return to the previous code, then try commenting out the window_size= line, and try to scale things down using the window_size_ratio= value. Naturally, this will shrink things down in *all* directions, instead of allowing you to define a specific size for width and height independantly of each other, but it may be the 'last resort' to try and get that stubborn panel to cooperate. If I had the PC-12, I'm sure I could be more help to you, but since I don't, all I can do is try and post the things that I would try, and hopefully one will work out for you.
On an unrelated note, I've found that main panel windows that cause the VC to shift upwards a bit (leaving a black bar on the bottom quarter of the screen while the main panel is being displayed) can be worked around by including an alpha_blend value.
For example, if you have an aircraft that is displaying this 'shifting' behavior when the main panel window is opened and closed, edit the window section that corresponds to the main panel window of that aircraft (usually [Window00],) and add the following line:
alpha_blend=0.99
This has fixed the shifting vc issue that I've had with a few aircraft when opening and closing the main panel windows.
Hope this info is helpful, and hope to hear back from you with good news on getting that panel sized. :)
-George
in the gauge definitions, the first two numbers correspond to placement based on a scale that is defined in size_mm. Any numbers following the placement coordinates are used to define the gauge's size relative to the size of the panel window. For example, in the line:
gauge08=F1PC12!Switch Fuel Pump L, 175,534,70,70
gauge08=F1PC12!Switch Fuel Pump L, (This part of the line defines the gauge to use)
175,534 (These first two values define the coordinates to position the gauge in relation to the panel's size_mm definition)
,70,70 (These values define the size of the gauge in relation to the panel's size_mm definition)
In most cases, the sizes defined for individual gauges do not have a negative impact, however I have encountered one plane where the panel window wouldn't resize until I had removed the size entries from that particular panel window.
Here's a modified version of the window code you posted above for you to try. I can't guarantee that this will or won't work for you, so as always, make a backup of your panel.cfg file before making any changes. Then try replacing the [window03] entry with the one from below:
[Window03]
file=PC-12_overhead.bmp
file_1024=PC-12_overhead.bmp
size_mm=1828,813
window_size_ratio=1.000
position=0
visible=0
ident=70
window_size= 0.810, 0.472
window_pos= 0.105, 0.000
gauge00=F1PC12!Overhead VoltAmps, 585,167
gauge01=F1PC12!Engine Start, 177,667
gauge02=F1PC12!Switch Beacon Lights, 287,286
gauge03=F1PC12!Switch Taxi Lights, 175,87
gauge04=F1PC12!Switch Master Power, 1203,73
gauge05=F1PC12!Switch Nav Lights, 287,185
gauge06=F1PC12!Switch Strobe Lights, 175,288
gauge07=F1PC12!Switch Landing Lights, 287,87
gauge08=F1PC12!Switch Fuel Pump L, 175,534
gauge09=F1PC12!Switch Fuel Pump R, 287,534
gauge10=F1PC12!Switch Logo Lights, 287,386
gauge11=F1PC12!Switch Recognition Lights, 175,386
gauge12=F1PC12!Switch Wing Lights, 175,185
gauge13=F1PC12!Switch Fire, 67,287
gauge14=F1PC12!Switch Boots, 1580, 88
gauge15=F1PC12!Switch Boots 3min 1min, 1477,88
gauge16=F1PC12!Switch Cabin Heat, 1477,687
gauge17=F1PC12!Switch Cooling Fan, 1580,543
gauge18=F1PC12!Switch Cooling Recirc, 1477,420
gauge19=F1PC12!Switch Cooling System, 1580,420
gauge20=F1PC12!Switch WS Washer L, 1580,190
gauge21=F1PC12!Switch WS Washer L HL, 1477,190
gauge22=F1PC12!Switch WS Washer R, 1580,289
gauge23=F1PC12!Switch WS Washer R HL, 1477,289
gauge24=F1PC12!Switch Cooling Vent, 1477,543
gauge25=F1PC12!Switch Ignition, 286,666
gauge26=F1PC12!Switch Inertial Separator, 1685,190
gauge27=F1PC12!Switch No Smoking, 1685,420
gauge28=F1PC12!Switch Probe Heat, 1685,289
gauge29=F1PC12!Switch Prop Deice, 1685,88
gauge30=F1PC12!Switch Seatbelt, 1685,543
gauge31=F1PC12!Switch Pusher, 67,186
gauge32=F1PC12!Switch AV1, 624,664
gauge33=F1PC12!Switch AV2, 518,664
gauge34=F1PC12!Switch Battery 1, 624,374
gauge35=F1PC12!Switch External Power, 729,374
gauge36=F1PC12!Switch Gen 1, 520,374
gauge37=F1PC12!Switch Gen 2, 1185,370
gauge38=F1PC12!Switch Inv Gen 1, 1078,662
gauge39=F1PC12!Switch Non Essential, 730,664
gauge40=F1PC12!Switch Standby Bus, 1184,662
gauge41=F1PC12!Switch Overhead Test, 67,90
gauge42=F1PC12!Light Gen 1, 533,472
gauge43=F1PC12!Light Gen 2, 1199,472
gauge44=F1PC12!Light Battery 1, 638,472
gauge45=F1PC12!Light Avionics, 638,638
gauge46=F1PC12!Light External Power, 743,472
gauge47=F1PC12!Light Standby Bus, 1247,640
gauge48=F1PC12!Light Avionics, 532,637
//------END OF WINDOW CODE--- DO NOT COPY BELOW THIS LINE----
If that still doesn't get the window sized properly for you, return to the previous code, then try commenting out the window_size= line, and try to scale things down using the window_size_ratio= value. Naturally, this will shrink things down in *all* directions, instead of allowing you to define a specific size for width and height independantly of each other, but it may be the 'last resort' to try and get that stubborn panel to cooperate. If I had the PC-12, I'm sure I could be more help to you, but since I don't, all I can do is try and post the things that I would try, and hopefully one will work out for you.
On an unrelated note, I've found that main panel windows that cause the VC to shift upwards a bit (leaving a black bar on the bottom quarter of the screen while the main panel is being displayed) can be worked around by including an alpha_blend value.
For example, if you have an aircraft that is displaying this 'shifting' behavior when the main panel window is opened and closed, edit the window section that corresponds to the main panel window of that aircraft (usually [Window00],) and add the following line:
alpha_blend=0.99
This has fixed the shifting vc issue that I've had with a few aircraft when opening and closing the main panel windows.
Hope this info is helpful, and hope to hear back from you with good news on getting that panel sized. :)
-George
Problem With TripleHead2Go and FSX 2D View
Wow,
Thanks for taking the time to do that to the file, George. :D I'll let you know how it works out as soon as I get a chance to try it. Regards, Tom
Thanks for taking the time to do that to the file, George. :D I'll let you know how it works out as soon as I get a chance to try it. Regards, Tom
-
petercaurora
- Posts: 1
- Joined: 09 Feb 2010, 09:03
Re: Problem With TripleHead2Go and FSX 2D View
Hey guys
I am new to this forum and i created an account specifically to answer this this thread.
I have 2 sperate machines both running the TH2Go in 1680x1050 and have encountered the same issue on both.
Here is how I solved the problem on both (excuse the nubeness).
Load up FSX. go to settings > graphics > customize and reduce the resolution to the TH2Go default before any firmware upgrade (3840x1024)
Click Fly Now.
At this point you should be able to see a 2d panel without the cursor acting crazy. If not, reduce the resolution even more.
Click on the panel (still in 2d cockpit mode) and resize it to a very small size (about a quarter of 1 screen)
Now click on file, save flight (check the default flight checkbox).
exit FSX. When you go back in, go back to settings and set your resolution to be whatever you want.
Fly Now. Once back in, you should see your new resolution but the 2d panel window is still small. you can now resize (full screen or whatever) it and save flight again (default checkbox checked)
That should do it, every time you bring up your 2d panel, it should behave normally.
Note, you will have to do this for all flights (planes) you fly and save them.
Hope this helps....
peter.
I am new to this forum and i created an account specifically to answer this this thread.
I have 2 sperate machines both running the TH2Go in 1680x1050 and have encountered the same issue on both.
Here is how I solved the problem on both (excuse the nubeness).
Load up FSX. go to settings > graphics > customize and reduce the resolution to the TH2Go default before any firmware upgrade (3840x1024)
Click Fly Now.
At this point you should be able to see a 2d panel without the cursor acting crazy. If not, reduce the resolution even more.
Click on the panel (still in 2d cockpit mode) and resize it to a very small size (about a quarter of 1 screen)
Now click on file, save flight (check the default flight checkbox).
exit FSX. When you go back in, go back to settings and set your resolution to be whatever you want.
Fly Now. Once back in, you should see your new resolution but the 2d panel window is still small. you can now resize (full screen or whatever) it and save flight again (default checkbox checked)
That should do it, every time you bring up your 2d panel, it should behave normally.
Note, you will have to do this for all flights (planes) you fly and save them.
Hope this helps....
peter.
Re: Problem With TripleHead2Go and FSX 2D View
Hi guys.
I was wondering if anybody is running Level-D 767 and got it working properly with triple wide? In my case 5760x1080.
I have the penel.cfg all figured out correctly and I have saved a default flight that which WORKS, unless for the missions that comes with the level-d 767.
Anybody figured out how to edit the missions so that they use my working panel config? Because they just don´t.
I was wondering if anybody is running Level-D 767 and got it working properly with triple wide? In my case 5760x1080.
I have the penel.cfg all figured out correctly and I have saved a default flight that which WORKS, unless for the missions that comes with the level-d 767.
Anybody figured out how to edit the missions so that they use my working panel config? Because they just don´t.
Asus maximus V gene, Intel 3570k @4,5 GHz, Samsung 830 256 GB, Samsung 1TB, Kingston HyperX Beast 2133 MHz 2x8GB, Gainward GTX TITAN, Corsair HX 750W, Antec 920, Fractal Design R2, Benq XL2411T + 2x Benq G2420HD + Samsung 50"
Can't Fully Grasp This Concept
In most part, this thread has been a great help .... I've managed to get most of my panels configured properly for the DA Fokker 100. At least most are sized to not not be lost with the pulsing cursor from hell. They can not be easily resized using the handles, and moved around.
But I am having problems with two panels in particular. The overhead panels.
Unlike the other panels, I can't find it when selected, and I get the blinking cursor.
While toying around, I changed the window_size for Window03 (size_mm=641,517) but this resulted in the panel image being cropped, but was accessible.
Here is the code for the main panel, which once edited is workable after having once exhibited the same problem as the overheads.
The main panel is in the centre monitor of my spanned display and looks a bit out of place. the other two monitors have the black bars.
But I am having problems with two panels in particular. The overhead panels.
Code: Select all
[Window03]
file=MM_F70100_OVHL.bmp
//size_mm=641,517
size_mm=1280
window_size=0.333, 1.21875
position=1
visible=0
ident=5010
zorder=6
gauge00=F70100_XML_IF!ELEC, 341, 116, 297, 524
gauge01=F70100_XML_IF!BLEED, 952, 11, 300, 437
gauge02=F70100_XML_IF!PRESS, 650, 650, 299, 315
gauge03=F70100_XML_IF!ANTIICE, 345, 657, 300, 112
gauge04=F70100_XML_IF!HYDR, 33, 200, 300, 459
gauge05=F70100_XML_IF!APU, 954, 447, 298, 522
gauge06=F70100_XML_IF!FUEL, 647, 105, 297, 376
gauge07=F70100_XML_IF!ENG, 649, 482, 301, 164
gauge08=F70100_XML_IF!LIGHTS, 344, 770, 300, 200
gauge09=F70100_XML_IF!CALLS, 39, 658, 297, 309
gauge10=F70100_XML_IF!FAC, 34, 52, 298, 144
gauge11=F70100_XML_IF!PVO_OVHL_Close, 1220, 115, 50, 50
gauge12=F70100_XML_IF!PVO_OVHL_Close, 0, 115, 50, 50
gauge13=F70100_XML_IF!PVO_OVHL_Close, 0, 1025, 50, 50
gauge14=F70100_XML_IF!PVO_OVHL_Close, 1220, 1025, 50, 50
gauge15=F70100_XML_IF!PVO_OVHL_Top, 47, 110, 1160, 21
gauge16=F70100_XML_IF!PVO_OVHL_Bottom, 47, 1039, 1160, 21
[Window04]
file=MM_F70100_OVHU.bmp
size_mm=1280
window_size_ratio=1.000
position=7
visible=0
ident=5011
window_size= 0.333, 1.000
zorder=7
gauge00=F70100_XML_IF!MSU, 647, 245, 298, 107
gauge01=F70100_XML_IF!HYDR, 33, 686, 300, 459
gauge02=F70100_XML_IF!ELEC, 341, 599, 297, 524
gauge03=F70100_XML_IF!BLEED, 952, 494, 300, 437
gauge04=F70100_XML_IF!FUEL, 647, 591, 297, 376
gauge05=F70100_XML_IF!FAC, 34, 537, 298, 144
gauge06=F70100_XML_IF!AVP, 35, 359, 297, 172
gauge07=F70100_XML_IF!FIRE, 341, 431, 606, 158
gauge08=F70100_XML_IF!APU_FIRE, 954, 358, 298, 133
gauge09=F70100_XML_IF!CVR, 339, 56, 302, 117
gauge10=F70100_XML_IF!ELT, 341, 354, 301, 76
gauge11=F70100_XML_IF!OXYGEN, 644, 355, 303, 74
gauge12=F70100_XML_IF!TEST, 342, 174, 301, 177
gauge13=F70100_XML_IF!PVO_OVHU_Close, 1220, 5, 50, 50
gauge14=F70100_XML_IF!PVO_OVHU_Close, 0, 5, 50, 50
gauge15=F70100_XML_IF!PVO_OVHU_Close, 0, 915, 50, 50
gauge16=F70100_XML_IF!PVO_OVHU_Close, 1220, 915, 50, 50
gauge17=F70100_XML_IF!PVO_OVHU_Bottom, 47, 930, 1160, 21Unlike the other panels, I can't find it when selected, and I get the blinking cursor.
While toying around, I changed the window_size for Window03 (size_mm=641,517) but this resulted in the panel image being cropped, but was accessible.
Here is the code for the main panel, which once edited is workable after having once exhibited the same problem as the overheads.
Code: Select all
[Window00]
file=MM_F70100_MPNL.bmp
size_mm=1280
window_size_ratio=1.000
position=4
visible=1
//no_luminous=1
ident=MAIN_PANEL
window_size= 0.333, 1.000
//window_pos= 0.000, 0.000
zorder=0
gauge00=F70100_XML_IF!ABS, 1108, 558, 92, 104
gauge01=F70100_XML_IF!EFIS, 378, 348, 304, 92
gauge02=F70100_XML_IF!GIAS, 654, 622, 119, 119
gauge03=F70100_XML_IF!GATI, 720, 483, 128, 103
gauge04=F70100_XML_IF!GATI_Knob, 820, 585, 40, 40
gauge05=F70100_XML_IF!AFCAS, 689, 314, 592, 121
gauge06=F70100_XML_IF!FWS, 326, 370, 32, 63
gauge07=F70100_XML_IF!SRC_SEL, 86, 763, 63, 190
gauge08=F70100_XML_IF!SRC_SEL_CPT, 47, 754, 33, 183
gauge09=F70100_XML_IF!SRC_SEL_ADF, 155, 845, 30, 63
gauge10=F70100_XML_IF!LDG_Lever, 1261, 446, 19, 268
gauge11=F70100_XML_IF!CLK, 174, 590, 131, 131
gauge12=F70100_XML_IF!STBY_ALT, 786, 619, 127, 125
gauge13=F70100_XML_IF!RMI, 719, 753, 129, 158
gauge14=F70100_XML_IF!GPWS_LIGHTS, 653, 480, 62, 129
gauge15=AOG_F70100!MASTER, 0, 0, 1, 1, 1102
gauge16=AOG_F70100!MFDU_L_DISP, 958, 702, 239, 205, 1
gauge17=AOG_F70100!TRP, 977, 483, 112, 129
gauge18=AOG_F70100!ADS, 101000, 0, 1, 1
gauge19=AOG_F70100!DU_U_DISP, 366, 495, 239, 205, 1
gauge20=AOG_F70100!DU_L_DISP, 366, 747, 239, 205, 4
gauge21=AOG_F70100!WINDOW, 0, 0, 1280, 304
gauge22=F70100_XML_IF!PVO_MAIN_Top, 25, 0, 550, 21
gauge23=F70100_XML_IF!PVO_MAIN_Right, 1200, 680, 21, 243
gauge24=F70100_XML_IF!PVO_PEDESTAL_Forward, 619, 930, 625, 21
gauge25=F70100_XML_IF!ALAND, 233, 402, 30, 23
gauge26=F70100_XML_IF!PVO_RADIO, 1055, 284, 200, 21
gauge27=F70100_XML_IF!GPWS_GS_INH, 679, 873, 35, 37
gauge28=F70100_XML_IF!SPDBRK, 278, 562, 20, 17
gauge29=F70100_XML_IF!STBY_COMP, 1075, 82, 78, 40
gauge30=F70100_XML_IF!STBY_COMP_LIGHT, 1144, 65, 21, 17
gauge31=F70100_XML_IF!PVO_MAIN_Gear, 1231, 746, 54, 129
gauge33=F70100_XML_IF!PVO_MAIN_Util, 5, 884, 40, 50
gauge34=F70100_XML_IF!PVO_MAIN_FMC, 1229, 884, 40, 50
gauge35=F70100_XML_IF!LETTER, 867, 481, 91, 27
gauge36=F70100_XML_IF!PVO_System, 2, 2, 1, 1
gauge37=F70100_XML_IF!OVHD_MAIN, 600, 0, 679, 36
gauge38=F70100_XML_IF!LDG_Left_Light, 1259, 812, 17, 10The main panel is in the centre monitor of my spanned display and looks a bit out of place. the other two monitors have the black bars.
Re: Problem With TripleHead2Go and FSX 2D View
I to have been trying to set up 3 monitors using th2g digital edition and have had no luck with it I am at present talking to matrox to solve my probs but not very fourth coming yet I have linked the 3 monitors together on a nvidia 650ti sorted the resolutions out and vow working fine except I to have half a black screen has anyone found a work around for this any help appreciated thanks
Re: Problem With TripleHead2Go and FSX 2D View
Thanks
I've edited a few of my panel.cfg files, and I can confirm that it works. For some panels you do need to edit more than the MAIN section, for example the PMDG ones. Also, you can eit other sections to give you the look/position you want for the panels now that you have the luxury of 3 screens.
So I joined the Forum to be able to thank you guys,
Thanks!
I've edited a few of my panel.cfg files, and I can confirm that it works. For some panels you do need to edit more than the MAIN section, for example the PMDG ones. Also, you can eit other sections to give you the look/position you want for the panels now that you have the luxury of 3 screens.
So I joined the Forum to be able to thank you guys,
Thanks!
Who is online
Users browsing this forum: No registered users and 3 guests