- Messages
- 300
- Country
Hi all,
I have been working on replacing existing xml gauge mouse clicks with Lvars so that they can be operated with external switches. In particular I am modelling a Garmin GCU477 which has a number/keypad to input flight plan data.
I had the keypad and number pad working fine, then I upgraded my aircraft (Carenado Phenom 300) which added a full navigation database. This update came with new gauges which meant that i needed to update my code as the macros were different.
The problem have is this....I started adding my code to the new gauge by starting on the letters of the keypad. I put in the code for the letter "A" then tested it to make sure it worked. It did.
Then i added more letters. All was well until I got to the letter "E" then my FSX wouldn't startup due to lack of virtual memory(the dreaded out of memory error).
My code sits in a new loop which i put into the existing VC gauge.
What is causing this when it worked before the aircraft update? Is there a size limit on xml gauges?
Would the update have brought FSX close to its virtual memory limit?
Is there a way i can get around this problem?
Would including my code into one of the gauges existing update loops make a difference?
Would it be better to create a new gauge with my code in and if so would i also have to put the macros in my gauge or would it cross reference to the macros in the carenado gauge?
Sorry, lots of questions there!
Thanks for looking
Stinger
Sent from my SM-T813 using Tapatalk
I have been working on replacing existing xml gauge mouse clicks with Lvars so that they can be operated with external switches. In particular I am modelling a Garmin GCU477 which has a number/keypad to input flight plan data.
I had the keypad and number pad working fine, then I upgraded my aircraft (Carenado Phenom 300) which added a full navigation database. This update came with new gauges which meant that i needed to update my code as the macros were different.
The problem have is this....I started adding my code to the new gauge by starting on the letters of the keypad. I put in the code for the letter "A" then tested it to make sure it worked. It did.
Then i added more letters. All was well until I got to the letter "E" then my FSX wouldn't startup due to lack of virtual memory(the dreaded out of memory error).
My code sits in a new loop which i put into the existing VC gauge.
What is causing this when it worked before the aircraft update? Is there a size limit on xml gauges?
Would the update have brought FSX close to its virtual memory limit?
Is there a way i can get around this problem?
Would including my code into one of the gauges existing update loops make a difference?
Would it be better to create a new gauge with my code in and if so would i also have to put the macros in my gauge or would it cross reference to the macros in the carenado gauge?
Sorry, lots of questions there!
Thanks for looking
Stinger
Sent from my SM-T813 using Tapatalk
Code:
<Update id="GCU477">
<Script>
(L:GCU477_A,bool) 1 == if{ @G1000INPUT(65) 0 (>L:GCU477_A,bool) }
(L:GCU477_B,bool) 1 == if{ @G1000INPUT(66) 0 (>L:GCU477_B,bool) }
(L:GCU477_C,bool) 1 == if{ @G1000INPUT(67) 0 (>L:GCU477_C,bool) }
(L:GCU477_D,bool) 1 == if{ @G1000INPUT(68) 0 (>L:GCU477_D,bool) }
(L:GCU477_E,bool) 1 == if{ @G1000INPUT(69) 0 (>L:GCU477_E,bool) }
</Script>
</Update>
Last edited: