moving gauges in or out on the panel

[jterr]

Looking at these numbers what do I change to move the gauges in or out?
//--------------------------------------------------------
[Vcockpit01]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$VC_01

//gauge00=B50!Main, 0,0,1,1
gauge15=B50!LightInTrans, 87,727,22,22
gauge16=B50!LightsReverse121GVC, 91,653,100,22
gauge17=B50!LightAutoFeather, 123,727,22,22
gauge18=B50!RadioCOMM1, 678,378,109,63
gauge19=B50!RadioNAV1, 787,378,109,63
gauge20=B50!RadioNAV2, 896,378,109,63
gauge21=B50!LightFire, 214,649,26,26
gauge22=B50!AirTempVC, 518,350,137,137
gauge23=B50!Call_SignVC, 678,452,100,18
gauge24=B50!Light_hyd_press1, 67,762,22,22
gauge25=B50!Light_hyd_press2, 97,762,22,22
gauge26=B50!Light_hyd_press3, 127,762,22,22
gauge27=B50!Light_hyd_press4, 157,762,22,22
gauge28=B50!ManPress1649AFE_1, 197,20,150,150
gauge29=B50!ManPress1649AFE_2, 360,20,150,150
gauge30=B50!Tachometer1649AFE_1, 524,20,150,150
gauge31=B50!Tachometer1649AFE_2, 687,20,150,150
gauge32=B50!ManPress1649AFE_3, 197,696,150,150
gauge33=B50!ManPress1649AFE_4, 360,696,150,150
gauge34=B50!Tachometer1649AFE_3, 524,696,150,150
gauge35=B50!Tachometer1649AFE_4, 687,696,150,150
gauge41=B50!RadioAltimeterVC, 338,485,183,183
gauge42=B50!Airspeed1649AFE, 20,20,150,150

 

[WarpD]

What do you mean "in or out"?

 

[jterr]

I was trying something I thought I read where some of the gauges(FSX exported to MSFS) are behind a texture and if they are moved forward then you could see them.

 

[WarpD]

Only XML gauges from FSX stand a chance of working in MSFS.

I know of no way of changing the gauge size and position values to make them "move forward".

 

[jterr]

Only XML gauges from FSX stand a chance of working in MSFS.

I know of no way of changing the gauge size and position values to make them "move forward".

Can different gauges from another plane be copied over??

 

[kalong]

panel.cfg only for gauge placement / include , not animation.
use xml gauge for any movement.

 

[B21-soaring]

Here's the explanation of why you can't move XML gauges 'in/out':

The $VC_01 texture is a bitmap area defined in the aircraft 3D model (i.e. the <aircraft>/model/***.mdl), and the XML (and html/js) gauges are 'painted' onto that texture.

So if the $texture is bigger than your single gauge (as in this case) you can choose the x,y coordinates *where* on that texture your gauge is going to appear. But you CANNOT change the position of the $texture (unless you edit the 3D model) so you can't bring the whole texture forwards or backwards.

The bad news: FSX cockpits with '2D' xml gauges don't really 'migrate' to MSFS. The 'conversion tool' will attempt to convert them to html/js (actually as a 'livery', not a 'vcockpit' because the FSX mdl needs that). For anything other than a very simple gauge you have to rewrite it in html/js. Not great, but that does allow you to re-use an excellent FSX 3D model.

The best example I have of an FSX conversion from no XML gauges working to a replacement html/js panel is the Ka6E glider on Paul Falke's page here. I appreciate this is zero help unless you're a gauge programmer.

 

[lao.kurt]

I use MSK MUSHSHAK T-17 and use VR , will it be possible to make some panel ( like Cessna) and lay it in to T-17 and use it in P3D V5.?

 

[B21-soaring]

To edit a 3D panel you need an aircraft model you can edit in the Blender 3D modelling tool, expertise in Blender, and a good understanding of the panel and gauges SDK. You cannot cut-and-paste a 3D panel or even individual 3D instruments from one aircraft to another by editting text config files.

TBH it's about time flight simulators had better support for 3D instruments as plug-in 'sim objects' but there's no sign of that yet (YHIHF). Some instruments are more complex than some aircraft.

 

[n4gix]

The $VC_01 texture is a bitmap area defined in the aircraft 3D model (i.e. the <aircraft>/model/***.mdl), and the XML (and html/js) gauges are 'painted' onto that texture.

Another way to describe this is that the $VC_01 dynamic bitmap acts like a movie screen. The gauges are projected onto the movie screen...

...however, just like a movie screen the bitmap is two-dimensional; it has no depth.