Share this post

Link to post

Share on other sites

Guest Trevor de S

You have missed the point of this question.I am trying to control the Afterburners in an F-15 Eagle, not trying to control a sound file.FYI I have my own sound control files for XML in FS9 using either ADF or Prop variables.Trevor.

Share this post

Link to post

Share on other sites

Guest bartels

I haven't checked, but one possible point: there is often not a direct response between K: toggle-event and the associated A: variable. It might be necessary to wait a short period before firing the K: event again, but again it might also be something else, I haven't checked.Arne Bartels

Share this post

Link to post

Share on other sites

Hi,Tried it and it works ok.Only in my case i hear only an endless amounts of "Clicks" because i still use the afterburner1 event for a "click" sound using late B. Morad's xml-sound gauge.I enabled afterburner in aircraft.cfg and airfile, but no effect on the 767-300.Jan"Procul Negotiis"

Share this post

Link to post

Share on other sites

Guest Trevor de S

Hi Guys,Thanks for your efforts. I have discovered the source of my problems.The code I posted was part of one section from an omnibus XML gauge which I use to perform initialisations and various calculations which are used in more than one gauge and which presents no visible image on the aircraft panel. (It has a 10x10 pixel transparent image just to make it easy to position using Panel Studio or similar)I have known for some time that there is a limit to how much code can be put in one section and have all the calculations and decisions perform properly, but I can now report that in gauges with a number of different elements it appears that (>K:XXXXXXXXXXX) commands within the code do not (always) perform. The moment I did as you guys had done and created a dedicated gauge for A/B control everthing worked a treat, even when I added the second half of the code to control No 2 engine afterburner.Trevor

Share this post

Link to post

Share on other sites

Hi Trevor,""I have known for some time that there is a limit to how muchcode can be put in one section""Yes, I have also stumbled on that problem once.But are you saying that also the number of ... sections is limited ??Rob

Share this post

Link to post

Share on other sites

Guest Trevor de S

Rob"are you saying that also the number of ... sections is limited ??"No, but it appears that if you embed something of the form(>K:TOGGLE_SOME_CONTROL)in the .... code of 3rd or 4th ... section of an omnibus gauge the event is not triggered!!!This is the only way to explain the problem I encountered with my original Afterburner control logic.Trevor.

AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

Donation Goals

AVSIM's 2018 Fundraising Goal

Donate to our annual general fund. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.