• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Hoping to swap (or fix) a gauge

Messages
16
Country
unitedstates
Can someone advise me which of the following in the panel.cfg might be the heading indicator gauge with the heading bug? This freeware plane has a fault in that the heading bug (and the nav arrow) will only turn counterclockwise with left-click and the right-click does not work to turn it clockwise. I want to try to either swap the gauge out with one from another plane that works properly or fix it so that it works properly. Any advise will be helpful. (the layout of this .cfg file is much different that any of the other planes I've dealt with.)

[Vcockpit01]
Background_color=0,0,0
size_mm=512,512
position=7
visible=1
ident=
pixel_size=512,512
texture=$pan1

gauge00=fp_as1_TR!KMA28_Aud_Sel, 12,409,482,102
gauge01=Soloy_TR!Warn, 6,268,494,76
gauge02=Soloy_TR!ATC Reg, 327,366,130,44
gauge03=dsd_fsx_xml_sound_tr!Sound, 1,1,1,1,T206H_sound.ini
gauge04=Soloy_TR!ground_flight_idle, 1,1,1,1
gauge05=Soloy_TR!engine_control, 1,1,1,1
gauge06=Soloy_TR!GPU, 1,1,1,1

[Vcockpit02]
Background_color=0,0,0
size_mm=512,512
position=7
visible=1
ident=
pixel_size=512,512
texture=$pan2

gauge00=FP_M803v8_TR!M803_AK_NoS_TR, 49,77,94,93
gauge01=VA-1A!VA-1A avionics, 104,312,90,89
gauge02=Shadin_FF!Shadin, 215,276,143,142

[Vcockpit03]
Background_color=0,0,0
size_mm=512,512
position=7
visible=1
ident=
pixel_size=512,512
texture=$pan3

gauge00=FP_HOBBS_TR!Hobbs6_tr, 242,149,249,161

[Vcockpit04]
Background_color=0,0,0
size_mm=512,512
position=7
visible=1
ident=
pixel_size=512,512
texture=$pan4

gauge00=Soloy_TR!Annunciator, 122,15,144,483
gauge01=Soloy_TR!DME_Soloy, 304,12,290,127

[Vcockpit05]
Background_color=0,0,0
size_mm=512,512
position=7
visible=1
ident=
pixel_size=512,512
texture=$pan5

gauge00=KR87_ADF_Bill!KR 87 ADF, 21,28,476,94

[Vcockpit06]
Background_color=0,0,0
size_mm=512,512
position=7
visible=1
ident=
pixel_size=512,512
texture=$pan6

gauge00=FS9Garmin530_Basler_tr!GNS530_nc1, 19,0,463,323
gauge01=FS9Garmin430_Basler_tr!GNS430_nc2, 19,321,463,197

[Vcockpit07]
Background_color=0,0,0
size_mm=512,512
position=7
visible=1
ident=
pixel_size=512,512
texture=$pan7

gauge00=FS9Garmin330_TR!GTX330, 8,5,481,122
gauge01=Bendix_King_Radio!Bendix-King Radio AP, 8,138,495,126
gauge02=Soloy_TR!throttleset, 56,279,138,64
gauge03=Soloy_TR!fuelset, 324,282,138,64

[Vcockpit08]
Background_color=0,0,0
size_mm=512,512
position=7
visible=1
ident=
pixel_size=512,512
texture=$pan8

gauge00=F1GTN!GTN750VC, 82,29,323,366,UNIT1

[Vcockpit09]
Background_color=0,0,0
size_mm=512,512
position=7
visible=1
ident=
pixel_size=512,512
texture=$pan9

gauge00=F1GTN!GTN650VC, 108,19,267,108,UNIT1

[Vcockpit10]
Background_color=0,0,0
size_mm=512,512
position=7
visible=1
ident=
pixel_size=512,512
texture=$pan_a

gauge00=kln90b!Kln90B, 25,-5,454,136
gauge01=FP_Radio_Set_Bendix_King!KX155_comnav1, 21,129,463,136
gauge02=FP_Radio_Set_Bendix_King!KX155_comnav2, 21,260,464,136
gauge03=FS9Garmin330_TR!GTX330, 20,393,466,120

[Vcockpit11]
Background_color=0,0,0
size_mm=512,512
position=7
visible=1
ident=
pixel_size=512,512
texture=$pan_b

gauge00=Bendix_King_Radio!Bendix-King Radio AP, 8,5,495,134
gauge01=Soloy_TR!throttleset, 107,281,138,64
gauge02=Soloy_TR!fuelset, 363,280,138,64

[Vcockpit12]
Background_color=0,0,0
size_mm=512,512
position=7
visible=1
ident=
pixel_size=512,512
texture=$pan_c

//gauge00=F1GNS!GNS530, 19,0,463,323,UNIT1.VC
//gauge01=F1GNS!GNS430, 19,316,463,202,UNIT1.VC


[Vcockpit13]
Background_color=0,0,0
size_mm=512,512
position=7
visible=1
ident=
pixel_size=512,512
texture=$pan_d

gauge00=FS9Garmin330_TR!GTX330, 8,5,481,122
gauge01=Bendix_King_Radio!Bendix-King Radio AP, 8,138,495,126
gauge02=Soloy_TR!throttleset, 107,281,138,64
gauge03=Soloy_TR!fuelset, 363,280,138,64

[Vcockpit14]
Background_color=0,0,0
size_mm=512,512
position=7
visible=1
ident=
pixel_size=512,512
texture=$pan_e

gauge00=Bendix_King_Radio!Bendix-King Radio AP, 7,4,492,123
gauge01=Soloy_TR!throttleset, 82,127,154,74
gauge02=Soloy_TR!fuelset, 291,127,158,72

[Vcockpit15]
Background_color=0,0,0
size_mm=1024,1024
position=7
visible=1
ident=
pixel_size=1024,1024
texture=$pan_g

gauge00=F1G600!G600PFD, 95,80,378,469,UNIT1
gauge01=F1G600!G600MFD, 554,80,378,469,UNIT1

[VCockpit16]
Background_color=0,0,0
size_mm=1024,1024
pixel_size=1024,1024
texture=$VCRain
visible=1

gauge00=VCRain!VCRain, 0,0,1024,1024
 

DragonflightDesign

Resource contributor
Messages
1,082
Country
northernireland
You are better off contacting the author and reporting a possible bug. IIRC the Soloy is a relatively recent release.
 

Heretic

Resource contributor
Messages
6,830
Country
germany
I think the knob function is hard coded into the model, so you will have to contact the author to have it fixed.
 
Messages
16
Country
unitedstates
I was afraid of that. I wrote the author quite some time ago (twice) at the email listed in the readme file, but have gotten no response.
 
Top