Ok, I edited the file as below and nothing in the 2D view except a 2D HUD. Sorry Anthony your idea does not work.//F-35A Panel configuration file[Window Titles]Window00=Main panelWindow01=HMDWindow02=Default Radio StackWindow03=Default GPSVIEW_FORWARD_DIR=-1.000, 0.000, 0.000//--------------------------------------------------------[Window00]Background_color=0,0,0 visible=1ident=MAIN_PANELalpha_blend=0.95position=8window_size= 1.000, 1.000size_mm=1024,1024 // Uncomment one of the lines below depending on your "WideViewAspect" setting in your fsx.CFG file.gauge00=F-35_HUD_VC!F-35_HUD_VC, 317, 211, 388, 691 // <--- F-35 2D HUD, conformal at zoom 0.9, aspect ratio 16:9 and WideViewAspect=False//gauge00=F-35_HUD_VC!F-35_HUD_VC, 330, 230, 364, 647 // <--- F-35 2D HUD, conformal at zoom 1.5, aspect ratio 16:9 and WideViewAspect=True//--------------------------------------------------------[Window01]Background_color=0,0,0 visible=1ident=MAIN_PANELalpha_blend=0.90position=5window_size= 1.000, 1.000size_mm=1024,1024 gauge00=F35!F35HMD, 0, 0, 1024, 1024 //--------------------------------------------------------// Default FSX Radio stack[Window02]BACKGROUND_COLOR=2,2,2size_mm=156,308position=8visible=0ident=RADIO_STACK_PANELzorder=3gauge00=Bendix_King_Radio!Bendix-King Radio Audio, 0, 0,156,31gauge01=Bendix_King_Radio!Bendix-King Radio Nav-Comm 1, 0, 29,156,59gauge02=Bendix_King_Radio!Bendix-King Radio Nav-Comm 2, 0, 86,156,59gauge03=Bendix_King_Radio!Bendix-King Radio ADF, 0,142,156,41gauge04=Bendix_King_Radio!Bendix-King Radio DME, 0,180,156,41gauge05=Bendix_King_Radio!Bendix-King Radio Xpndr, 0,217,156,49gauge06=Bendix_King_Radio!Bendix-King Radio AP, 0,262,156,48windowsize_ratio=1.000window_pos=0.756,0.358window_size=0.243,0.641//--------------------------------------------------------//DEFAULT FSX GPS//--------------------------------------------------------[Window03]Background_color=0,0,0 size_mm=456,378position=8visible=0ident=GPS_PANELwindow_size= 0.500no_luminous=1gauge00=fs9gps!gps_500, 0,0//--------------------------------------------------------[Window04] BACKGROUND_COLOR=2,2,2 size_mm=1024,512 position=7 visible=1 ident=12000 gauge00=f35!mfd1, 0,0,512,512 gauge01=f35!mfd2, 512,0,512,512//--------------------------------------------------------[Vcockpit01]Background_color=0,0,0 size_mm=1024,1024visible=1pixel_size=512,512texture=$F351gauge00=f35!pfd, 10,100,1024,1050//--------------------------------------------------------[Vcockpit02]Background_color=0,0,0 size_mm=1024,512visible=1pixel_size=2048,1024texture=$F35MFD1gauge01=f35!mfd1, 0,0,1024,512//--------------------------------------------------------[Vcockpit03]Background_color=0,0,0 size_mm=1024,512visible=1pixel_size=2048,1024texture=$F35MFD2gauge01=f35!mfd2, 0,0,1024,512//--------------------------------------------------------Day=255,255,255Night=223,255,255Luminous=246,115,119//--------------------------------------------------------[Vcockpit06]Background_color=0,0,0 size_mm=1024,1024visible=1pixel_size=1024,1024texture=$F353gauge00=f35!autopilot, 0,10,512,90gauge01=F35!flightdata, 0, 934, 425, 90gauge02=f35!mfdhsi3, 15,140,200,200gauge03=F35!MFDcontrol,406,941,143,76gauge04=F35!MFDSwap,555, 941,159,76//--------------------------------------------------------[Vcockpit07]Background_color=0,0,0 size_mm=128,128visible=1pixel_size=128,128texture=$F354gauge00=f35!HMDToggle, 0,10,512,90//--------------------------------------------------------[Vcockpit08]Background_color=0,0,0 size_mm=1024,1024visible=1pixel_size=1024,1024texture=$HMD3d2gauge00=F-35_HUD_VC!F-35_HUD_VC, 222, 267, 549, 549 //// <--- F-35 VC HUD//--------------------------------------------------------[Default View]X=0Y=0SIZE_X=8192SIZE_Y=8192

Perhaps, but that's a bit too high-brow for one who mostly sweeps up the dirt and dusts the furniture... :(

You missed a spot...

You forgot to add the Window04 entry into the [Window Titles] section at the top. FSX needs that to know that there is a new window available. Something like this may work:[Window Titles]Window00=Main panelWindow01=HMDWindow02=Default Radio StackWindow03=Default GPSWindow04=PFDBy the way. Here is a tip for you.If you run FSX in windows mode you can open up the panel.cfg file, make some changes and save it and then using the reload aircraft command (I think it is crtl+shift+r but you should check this in the key assignments in FSX 'cause I use a lot of non-standard key assignments so I may have changed it) you can check how your changes work. You can then go back and tweak the panel.cfg and then reload the aircraft. It is a hell of a lot quicker than having to restart FSX every time.

Thanks Anthony, that is a lot quicker. The main avionics glass panel is made up of 2 gauges. The strip along the top (autopilot) is a separate gauge that I can't seem to convert. I have converted the main part ok though. I am also having problems with the 3D Hud.I am going to try panel designer and see if that may do the trick.

Looks like this one is the AP:gauge00=f35!autopilot, 0,10,512,90Hope this helps,

Hi Tom. Yes, I thought that too. I added the script (below) which gave me the main part of the avionics display in 2D and then I added the gauge that you mentioned (bottom) but it never showed up. I am baffled I have to say.[Window04] BACKGROUND_COLOR=2,2,2 size_mm=1024,512 position=7 visible=1 ident=12000 gauge00=f35!mfd1, 0,0,512,512 gauge01=f35!mfd2, 512,0,512,512[Window04] BACKGROUND_COLOR=2,2,2 size_mm=1024,512 position=7 visible=1 ident=12000 gauge00=f35!mfd1, 0,0,512,512 gauge00=f35!autopilot, 0,10,512,90gauge01=f35!mfd2, 512,0,512,512

Hi Tom. Yes, I thought that too. I added the script (below) which gave me the main part of the avionics display in 2D and then I added the gauge that you mentioned (bottom) but it never showed up. I am baffled I have to say.[Window04] BACKGROUND_COLOR=2,2,2 size_mm=1024,512 position=7 visible=1 ident=12000 gauge00=f35!mfd1, 0,0,512,512 gauge01=f35!mfd2, 512,0,512,512[Window04] BACKGROUND_COLOR=2,2,2 size_mm=1024,512 position=7 visible=1 ident=12000 gauge00=f35!mfd1, 0,0,512,512 gauge00=f35!autopilot, 0,10,512,90gauge01=f35!mfd2, 512,0,512,512

I'm not baffled... mfd1 settings: x=0,y=0,width=512,height=512autopilot settings: x=0,y=10,width=512,height=90Those settings place the autopilot 10 pixels down from the top of mfd1... which means it's probably hidden behind mfd1. It's important to actually understand what you're doing to be able to know what's wrong.

Do you understand what Ed is saying? You need to:1 Make the size of the panel taller to make room for the 90 pixels of AP at the top (512 + 90).2. Move the two other gauges down by 90 pixels to avoid the AP sitting at the top.3. Make the gauge listing numerical (1, 2, 3, etc.)Something like:[Window04]BACKGROUND_COLOR=2,2,2size_mm=1024,602position=7visible=1ident=12000gauge00=f35!autopilot, 0,10,512,90gauge01=f35!mfd1, 0,90,512,512gauge02=f35!mfd2, 512,90,512,512Hope this helps,

Ok,, but why then do the coordinates match up exactly in the VC? That's why I assumed that no size and location editing was required.Thank's anyway Tom, Ed. appreciated.

Ok,, but why then do the coordinates match up exactly in the VC? That's why I assumed that no size and location editing was required.Thank's anyway Tom, Ed. appreciated.

The location and sizes in the VC have absolutely no bearing on any other panel or sub-panel.The other reason your AP didn't show up was because you used the same gaugenn= entry. Each gaugenn= must be unique.

Roger that Bill, fully understood, now. Thanks.May I ask the difference between 'pixel size' and 'size mm'? gauge00=F-35_HUD_VC!F-35_HUD_VC, 222, 267, 549, 549 //// <--- F-35 VC HUD

Hi,Those two values are the size of the panel in mm and the size of the panel in pixels. I don't know how those two relate to each other, but I set the pixel value to the size of my VC texture, and the mm value in FS Panel Studio (I think?).You cannot relate gauge placement values in these two cases, since each of those three gauges are present in *separate* VC sections, while we are combining them into a single 2D panel. Two completely different situations.Hope this helps,

Roger that Bill, fully understood, now. Thanks.May I ask the difference between 'pixel size' and 'size mm'?

The best description of "mm" is found in the FSX SDK:size_mm

A definition of the unit size used for placing and sizing gauges on this panel. For example, if the size_mm is 200 x 200 and a gauge’s size is 50, 50, it will take up 1/16th ( ¼ x ¼) of the panel window. If no size_mm is defined, the size of the panel’s background bitmap (not the gauge’s background bitmap) will be used. If no background bitmap is defined (as is often the case with popup panels that contain only one gauge), a default size of 100 x 100 is used. If window_size is not specified, the size of the window on screen will be size_mm divided by the size_mm for the first window specified in the panel.cfg. For example, if the size_mm for a given panel is 200, 200 and the size_mm for the first panel in the panel.cfg is 1024 x 768, the given panel would occupy 19% of the screen in the x dimension and 26% in the y dimension, or a total of 5% of the total screen area.

The whole concept of "mm" as a whole is related to the issue of "scalability." With such a wide range of monitor sizes and pixel dimensions, and resolutions......it would be impossible to use any system that wasn't "agnostic" with regards to an absolute measurement scale.

Do you understand what Ed is saying? You need to:1 Make the size of the panel taller to make room for the 90 pixels of AP at the top (512 + 90).2. Move the two other gauges down by 90 pixels to avoid the AP sitting at the top.3. Make the gauge listing numerical (1, 2, 3, etc.)Something like:[Window04]BACKGROUND_COLOR=2,2,2size_mm=1024,602position=7visible=1ident=12000gauge00=f35!autopilot, 0,10,512,90gauge01=f35!mfd1, 0,90,512,512gauge02=f35!mfd2, 512,90,512,512Hope this helps,

Thanks again. I searched the SDK and found nothing relating to size. It all makes sense now. Tom, the above proved to be correct. I now have all 3 gauges present in the correct location. (autopilot is slightly over to the left.)The only issue for me now is to find a way of converting the VC collimated HUD so that it also shows up in the 2D view. You will see from the attached image that I have the outside view rendered in 3D, but with a 2D HUD. The VC HUD renders in 3D. [Vcockpit08] references the VC HUD.//F-35A Panel configuration file[Window Titles]Window00=Main panelWindow01=HMDWindow02=Default Radio StackWindow03=Default GPSVIEW_FORWARD_DIR=-1.000, 0.000, 0.000//--------------------------------------------------------[Window00]Background_color=0,0,0 visible=1ident=MAIN_PANELalpha_blend=0.95position=8window_size= 1.000, 1.000size_mm=1024,1024 // Uncomment one of the lines below depending on your "WideViewAspect" setting in your fsx.CFG file.gauge00=F-35_HUD_VC!F-35_HUD_VC, 317, 211, 388, 691 // <--- F-35 2D HUD, conformal at zoom 0.9, aspect ratio 16:9 and WideViewAspect=False//gauge00=F-35_HUD_VC!F-35_HUD_VC, 330, 230, 364, 647 // <--- F-35 2D HUD, conformal at zoom 1.5, aspect ratio 16:9 and WideViewAspect=True//--------------------------------------------------------[Window01]Background_color=0,0,0 visible=1ident=MAIN_PANELalpha_blend=0.90position=5window_size= 1.000, 1.000size_mm=1024,1024 gauge00=F35!F35HMD, 0, 0, 1024, 1024 //--------------------------------------------------------// Default FSX Radio stack[Window02]BACKGROUND_COLOR=2,2,2size_mm=156,308position=8visible=0ident=RADIO_STACK_PANELzorder=3gauge00=Bendix_King_Radio!Bendix-King Radio Audio, 0, 0,156,31gauge01=Bendix_King_Radio!Bendix-King Radio Nav-Comm 1, 0, 29,156,59gauge02=Bendix_King_Radio!Bendix-King Radio Nav-Comm 2, 0, 86,156,59gauge03=Bendix_King_Radio!Bendix-King Radio ADF, 0,142,156,41gauge04=Bendix_King_Radio!Bendix-King Radio DME, 0,180,156,41gauge05=Bendix_King_Radio!Bendix-King Radio Xpndr, 0,217,156,49gauge06=Bendix_King_Radio!Bendix-King Radio AP, 0,262,156,48windowsize_ratio=1.000window_pos=0.756,0.358window_size=0.243,0.641//--------------------------------------------------------//DEFAULT FSX GPS//--------------------------------------------------------[Window03]Background_color=0,0,0 size_mm=456,378position=8visible=0ident=GPS_PANELwindow_size= 0.500no_luminous=1gauge00=fs9gps!gps_500, 0,0//--------------------------------------------------------[Window04]BACKGROUND_COLOR=2,2,2size_mm=1024,602position=7visible=1ident=12000gauge00=f35!autopilot, 0,10,512,90gauge01=f35!mfd1, 0,90,512,512gauge02=f35!mfd2, 512,90,512,512//--------------------------------------------------------[Vcockpit01]Background_color=0,0,0 size_mm=1024,1024visible=1pixel_size=512,512texture=$F351gauge00=f35!pfd, 10,100,1024,1050//--------------------------------------------------------[Vcockpit02]Background_color=0,0,0 size_mm=1024,512visible=1pixel_size=2048,1024texture=$F35MFD1gauge01=f35!mfd1, 0,0,1024,512//--------------------------------------------------------[Vcockpit03]Background_color=0,0,0 size_mm=1024,512visible=1pixel_size=2048,1024texture=$F35MFD2gauge01=f35!mfd2, 0,0,1024,512//--------------------------------------------------------Day=255,255,255Night=223,255,255Luminous=246,115,119//--------------------------------------------------------[Vcockpit06]Background_color=0,0,0 size_mm=1024,1024visible=1pixel_size=1024,1024texture=$F353gauge00=f35!autopilot, 0,10,512,90gauge01=F35!flightdata, 0, 934, 425, 90gauge02=f35!mfdhsi3, 15,140,200,200gauge03=F35!MFDcontrol,406,941,143,76gauge04=F35!MFDSwap,555, 941,159,76//--------------------------------------------------------[Vcockpit07]Background_color=0,0,0 size_mm=128,128visible=1pixel_size=128,128texture=$F354gauge00=f35!HMDToggle, 0,10,512,90//--------------------------------------------------------[Vcockpit08]Background_color=0,0,0 size_mm=1024,1024visible=1pixel_size=1024,1024texture=$HMD3d2gauge00=F-35_HUD_VC!F-35_HUD_VC, 222, 267, 549, 549 //// <--- F-35 VC HUD//--------------------------------------------------------[Default View]X=0Y=0SIZE_X=8192SIZE_Y=8192

Hi,You have to remember - you are in a 2D cockpit! You cannot get a 3D object to render (inside the cockpit) in a 2D cockpit. That's one reason why the VC was invented. AFAIK you are getting all you will ever get - the HUD gauge displaying over the outside view. The 3D part of the HUD is probably created in the aircraft model.Hope this helps,