Jump to content

Recommended Posts

Posted

Does the "X: COCKPIT ARGUMENT IN RANGE" cockpit trigger work with the FC3/Su25-T aircraft?
If so, do the argument numbers to be used in the Mission Editor match the "3D Model Viewer" arguments numbers for that item (for example Engine RPM's = 16 & 17)?

CPU = Intel i7-6700K

Motherboard = ASUS ROG Maximus VIII Hero Alpha, w/ the Intel Z170 Chipset,

RAM = 64 Gigs of Ripjaws V F4-3400C16Q.

GPU = Zotac GTX980ti Amp Extreme

Hard-drive = Samsung V-NAD SSD 950 PRO M.2

  • 2 months later...
Posted (edited)
On 6/8/2024 at 10:27 PM, DigitalEngine said:

Does the "X: COCKPIT ARGUMENT IN RANGE" cockpit trigger work with the FC3/Su25-T aircraft?
If so, do the argument numbers to be used in the Mission Editor match the "3D Model Viewer" arguments numbers for that item (for example Engine RPM's = 16 & 17)?

 

Hi,

 

Sorry for the late response, but I just found this thread while looking for something else. Regarding your questions:

a) yes, the "X: COCKPIT ARGUMENT IN RANGE" works with non-clickable aircraft too.

b) Yes, the argument for the Tach needles can be used that way, however for RPM it is probably better to use the parameters BASE_SENSOR_LEFT_ENGINE_RPM and BASE_SENSOR_RIGHT_ENGINE_RPM with the X:COCKPIT PARAM IN RANGE instead. A value of 0.5 is 50% rpm.

Edited by Rudel_chw

 

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...