Try adding:

 

1 (>L:VAR_CAR_AIR_TEMP , bool)

Try adding:

 

1 (>L:VAR_CAR_AIR_TEMP , bool)

 

Thanks my friend! will do!

Try adding:

 

1 (>L:VAR_CAR_AIR_TEMP , bool)

 

I am sorry but no luck ... also did try "0" for fun ... but no.

Sorry for not clarifying ... I am thinking of the digital OAT gauge which is showing Fahrenheit Degrees under the pilots sidewindow, left of the fuelgauges , after (allways pressing the switchbutton) it shows Celsius which is more common in europe ;-).

Not to mention all of the performance tables are in °C... one less button to push!

 

Thanks gents for your work on this! This thread is a perfect example of why I love this forum! :Hug:

The variable is correct, BUT there is a space behind the variable, just checked the files I got.

 

<!-- Temp in Celcuis -->

	 1 (>L:VAR_CAR_AIR_TEMP ,bool)

 

the variable with the space as above work 100% on my setup.

I hope the owner do not mind me putting the code here.

 

 

The other variables I got is

 

 

-no yoke

1 (>L:Yokepilot,bool)

 

-no yoke CoPilot

1 (>L:YokeCopilot,bool)

 

-no window reflections

1 (>L:WINDOWSTINTBOOL,bool)

 

-no instrument reflections

1 (>L:WINDOWSTINTBOOL2,bool)

 

-Avidene GPS OFF

1 (>L:EX500_PowerOff,bool)

 

-Temp in celcuis

1 (>L:VAR_CAR_AIR_TEMP ,bool)

 

-Armrest up

1 (>L:Perilla10,bool)

 

-Winglet off

1 (>L:VIS_WINGLET_ON,bool)

 

(Sorry these are just what I got in a gauge. not toooo enlightened to quickly check variables myself. Normally take a long time for me via LINDA, because everytime I need to read the instruction manual first.. so if you guys have some more, please post them. Will save me a lot of time - at my age things comes slowly and being old school I sometimes feel like begging to keep asking for help)

The variable is correct, BUT there is a space behind the variable, just checked the files I got...

 

 

This is all good stuff! Really bad programming technique IMHO, to have a significant trailing

blank in a variable name :mellow:

Thanks everyone helping with these lvars ! It works now like a charm and makes this plane even more enjoyable and remember you can use them for the C90B also!!!

....

To turn the Winglets off, you can add one more line

 

1 (>L:VIS_WINGLET_ON,bool)

 

....

 

Dear Bert,

after SP1 this code doesn´t seem to work anymore as they are off as default now :blink: ... any idea how to make that switch work indeed? Thought It would work vice versa ... but no luck!

I am just keen on this switch as you are able to make default winglet and non-winglet models just by different panel.cfgs .

 

Thanks for any help!

Don't know... what happens if you set it to zero?

 

0 (>L:VIS_WINGLET_ON,bool)

here is my gauge that work

<Gauge Name="Control_init_WL" Version="1.0">
<!-- no Winglets -->

<Element>
 <Select>
  <Value>
	  (L:Initwingletb200,bool) 1 != if{
	    0 (>L:VIS_WINGLET_ON,bool)  
	    0 (>L:Initwingletb200,bool)
						 }	 
  </Value>	 
 </Select>
  </Element>
</Gauge>

 

just reversing what they initially did. in the release document they said they reversed the process.

The second line should still be 1, also missing the closing "}"

 

L:Initwingletb200,bool) 1 != if{

0 (>L:VIS_WINGLET_ON,bool)

1 (>L:Initwingletb200,bool) }

 

 

or you assign the value over and over again which becomes a performance drain..

Bert

I tried that initially with the 1 as you show, and it did not work. I dont know why.?

 

for some reason after chnaging the values around and around and playing with the values, I found my code with the two 0's to work.

 

have you tried it that way. would be nice to have definitive answer on this one. I just used this code I got from another guy so I am no programmer and just tampering to try and make it work and do not always grasp the consequences.

 

I would appreciate if you can give us a value that work. Please would you be so kind and just test it for us. I actually sustepect they have added a simmilar gauge to the plane to make the winglets "off" at default as they said in the SP1 documentation and now we try and reverse that again with a simmilar gauge.

 

anyway I appreciate if you can test and clarify

It could be that Carenado changes it, after you set it, and that your code, by continuing to reset it, wins out.. I'll try to test it and see if I can figure out where they set it.

 

It would be nicer to set it once and be done with..

 

Edit: I've tested it, and as long as your gauge call is the very last line in the panel.cfg (at the end of Vcockpit05) you win the game. B)

 

Somewhere in one of the Carenado gauges before it, it gets set to "no winglets"

 

My code:

 

<Element>
 <Select>
 <Value>
	 (L:B200ControlInit,bool) 1 != if{
	 1 (>L:WINDOWSTINTBOOL2,bool)
	 0 (>L:WINDOWSTINTBOOL,bool)
	 0 (>L:VIS_WINGLET_ON,bool)
	 1 (>L:B200ControlInit,bool)	 }	
 </Value>	
 </Select>
</Element>

thanks bert, in the mean time I have found where they set it.

In the gaugeb200 cab file or gaugeb200 folder if you have already got the files into a folder and discarded/renamed the "cab" file

 

Look for file

Gauge_CLOCK_DIG.xml.

open with notepad

scroll down about halfway down it seems here it is being set.

Just changing the value to 0 for the (>L:VIS_WINGLET_ON,bool) variable should also work then I believe

 

<!--
(A:AUTOPILOT MASTER,BOOL) if{ 1 (>K:AP_MASTER) }
(A:AUTOPILOT FLIGHT DIRECTOR ACTIVE , BOOL ) if{ 1 (>K:TOGGLE_FLIGHT_DIRECTOR) }
-->

0 (>L:ASD_KNOB_WINDSHIELD_WIPER_KEYFRAME,number)
0 (>L:WINDSHIELD_WIPER_INCR, number)
0 (>L:WINDSHIELD_WIPER_INIT, number)
0 (>L:WINDSHIELD_WIPER_INIT_SPEED, number)
(P:local time, seconds) (>L:ASD_SWITCH_EFIS_POWER_TIMER, number)
75 (>L:ASD_KNOB_EFIS_DIM,number)

1 (>L:VIS_WINGLET_ON,bool)
1 (>L:ASD_SWITCH_FUEL_QUANTITY,bool)
1 (>K:FUEL_SELECTOR_ALL)

0 (>L:VIS_STROBE_CAR_ON, number)
0 (>L:Time_Cont_car , number)

1 (>L:GAUGE_CLOCK_INIT)

 

 

actually see quite a few things they set here eg dimmer value etc etc..

Bingo! You found it..

 

Yes, changing it there should take care of it :rolleyes: