Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

Hi all,

I am adding lines to an existing gauge so that i can replace mouse click spots with lua triggered lvars. I am currently adding lines to have external buttons input alphabet letters into a flight plan. I managed to do it for the entire alphabet and all was working ok. I have since upgraded my aircraft (Carenados Phenom 300) to include a full navigation database. This upgrade has changed the xml gauges in the aircraft.

Now when i add the lines to the new gauge i can get as far as the letter E working and then the dreaded o.o.m limit seems to be reached. It seems the new VC gauge which i am working with uses a lot more virtual memory.

My question is this....is there a way i can mitigate this to get it working . Would creating a new xml gauge to have just my new <Update> code in it make any difference? I have been putting my new code in a new  <update> section in the existing VC gauge. Would intergrating my code into an existing <update> section make any difference?

My new code wraps an existing macro call in an Lvar then switches off the Lvar after the macro has operated. As i say, i think the code is fine because it was working ok prior to the aircraft update although i had to change the code slightly as Carenado changed the macro which is called.

Thanks for looking

Stinger

 

 

  • Moderator

In FSX/FSX:SE and Prepar3Dv1 through v3 each XML 'gauge' can have only one <Update> section.

I would suggest creating a new 'gauge' with only one <Update> section and all of your custom scripts, instead of potentially screwing up any working XML 'gauges'. At the very least if your new 'gauge' doesn't work you stand a better chance of finding/fixing the bad script more easily.

I can tell you from bitter experience that trying to 'unscrewup' a large XML 'gauge script' is a nightmare!

Fr. Bill    

AOPA Member: 07141481 AARP Member: 3209010556


     Avsim Board of Directors | Avsim Forums Moderator
  • 7 months later...
On 5/4/2019 at 2:00 AM, n4gix said:

I would suggest creating a new 'gauge' with only one <Update> section and all of your custom scripts,

How to include such 'gauge' in your aircraft?

  • Moderator
9 minutes ago, jonny said:

How to include such 'gauge' in your aircraft?

Simply add it to the [Vcockpit01] section of the panel.cfg file:

gauge05=C310_XMLGauges!C310_Logic,  0,0,1,1

Fr. Bill    

AOPA Member: 07141481 AARP Member: 3209010556


     Avsim Board of Directors | Avsim Forums Moderator

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.