Jump to content

Recommended Posts

Posted

Hello all,

 

I'm editing a Viggen mission where I would like to be able to detect if the FR.22 radio is tuned to a specific preset:

 

wVoW2pP.jpg}

 

On the clickabledata.lua the following lines refer to this cockpit element:

 

iq4jUiY.jpg

 

I have tried to use the trigger condition X:COCKPIT ARGUMENT IN RANGE, using argument 361 and 3230, and neither seem to work 😞  Does anyone know how to properly read this preset number?

Does anyone know what means the -666 argument?

 

Thanks a lot for any help with this, and best regards.

 

Eduardo

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted (edited)

The thumb is a control (clickable device), the indication is an indication.
I think you should not focus on the thumb, but on the indication by using trigger condition X: COCKPIT INDICATION TEXT IS EQUAL TO.

See DCS Manual page 156.
I think the FR22 "indicator ID" might be 30, but I don't know the name for the indication (e.g. "data" or something else).

Edited by TOViper

Visit https://www.viggen.training
...Viggen... what more can you ask for?

my computer:
AMD Ryzen 5600G 4.4 GHz | NVIDIA RTX 3080 10GB | 32 GB 3.2 GHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TRP | Rift CV1

 

Posted
52 minutes ago, TOViper said:

The thumb is a control (clickable device), the indication is an indication.
I think you should not focus on the thumb, but on the indication by using trigger condition X: COCKPIT INDICATION TEXT IS EQUAL TO.

See DCS Manual page 156.
I think the FR22 "indicator ID" might be 30, but I don't know the name for the indication (e.g. "data" or something else).

 

 

Hi,

Thanks for the input, unfortunately the device 30 has no indications that I could find (using the Lua Console of DCS-BIOS).  😞

With other knobs, like Master Mode, or the Computer Data Selector, I have no problem reading their position, but this radio knob seems to work differently, pity, seems I will have to trust the student pilot to dial the correct preset 🙂 

Best regards,

 

Eduardo

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted
42 minutes ago, Rudel_chw said:

 

Hi,

Thanks for the input, unfortunately the device 30 has no indications that I could find (using the Lua Console of DCS-BIOS).  😞

With other knobs, like Master Mode, or the Computer Data Selector, I have no problem reading their position, but this radio knob seems to work differently, pity, seems I will have to trust the student pilot to dial the correct preset 🙂 

Best regards,

 

Eduardo

What about using Argument 491 to detect the channel it is in? Every 0.01 is a Channel, starting from 0 with Channel "-".

Argument 490 is for the left channel selector number and 491 for the right one.

Posted
40 minutes ago, razo+r said:

What about using Argument 491 to detect the channel it is in? Every 0.01 is a Channel, starting from 0 with Channel "-".

Argument 490 is for the left channel selector number and 491 for the right one.

 

works perfect 🙏 just tried it, a value of 0.20 corresponds to Preset 17 of the radio, thank you so much 👍

May I ask how did you knew which arguments corresponds to that visor? 🙂 

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted
2 minutes ago, Rudel_chw said:

 

works perfect 🙏 just tried it, a value of 0.20 corresponds to Preset 17 of the radio, thank you so much 👍

May I ask how did you knew which arguments corresponds to that visor? 🙂 

I checked it in the model viewer which argument moves what and after finding the correct one I checked how far it moves with which value of the argument.

It can be tedious sometimes but it works.

  • Thanks 1
Posted
3 minutes ago, razo+r said:

I checked it in the model viewer which argument moves what and after finding the correct one I checked how far it moves with which value of the argument.

It can be tedious sometimes but it works.

 

Thanks a lot for sharing this tip 👍

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...