Jump to content

Perform command speedbrake and others


Go to solution Solved by Rudel_chw,

Recommended Posts

Posted (edited)

Hi,

 

I would like to know how to extend/retract speedbrakes under mission editor ? I achieve to do it with "set command" for gears, but I don't achieve for speedbrakes. Could you help me ? thanks

Edited by dureiken
  • Solution
Posted
51 minutes ago, dureiken said:

I would like to know how to extend/retract speedbrakes under mission editor ? I achieve to do it with "set command" for gears, but I don't achieve for speedbrakes. Could you help me ? 

 

Hi,

 

Employ the trigger action:

X:COCKPIT PERFORM CLICkABLE ACTION, device 13, Command 3035, Value: -1 to extend, 1 to close

 

See attached test mission. Keep in mind that this action is meant for Single Player and most likely won't work on Multi Player.

 

Eduardo

F-18C Test Airbrakes (by Rudel_chw).miz

 

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

wow thanks a lot, it works like charm !

 

could I abuse and ask you how to detect that throttle is less than 30%

and more than 70%

 

thanks a lot

  • Like 1
Posted (edited)
12 minutes ago, dureiken said:

...  how to detect that throttle is less than 30% and more than 70%

 

You can use the condition X:COCKPIT PARAM IN RANGE, the parameters would be:

 

BASE_SENSOR_LEFT_THROTTLE_POS

BASE_SENSOR_RIGHT_THROTTLE_POS

 

They return a value where 0 is minimum position and 1 is maximum.

This is a tricky parameter to use, as its value depend to an extent on your physical hardware, so a mission that employs these and works on your DCS, might not work the same on a PC with a different hardware throttle. I believe that checking RPM is safer:

 

BASE_SENSOR_LEFT_ENGINE_FAN_RPM

BASE_SENSOR_RIGHT_ENGINE_FAN_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

Posted

 

 

1 hour ago, Rudel_chw said:

 

You can use the condition X:COCKPIT PARAM IN RANGE, the parameters would be:

 

BASE_SENSOR_LEFT_THROTTLE_POS

BASE_SENSOR_RIGHT_THROTTLE_POS

 

They return a value where 0 is minimum position and 1 is maximum.

This is a tricky parameter to use, as its value depend to an extent on your physical hardware, so a mission that employs these and works on your DCS, might not work the same on a PC with a different hardware throttle. I believe that checking RPM is safer:

 

BASE_SENSOR_LEFT_ENGINE_FAN_RPM

BASE_SENSOR_RIGHT_ENGINE_FAN_RPM

 

BASE_SENSOR_LEFT_THROTTLE_POS works pretty fine

BASE_SENSOR_LEFT_ENGINE_FAN_RPM  I didn't achieve. 70 to, 100 ? 0.7 to 1 ?

 

thanks

Posted (edited)
8 minutes ago, dureiken said:

BASE_SENSOR_LEFT_ENGINE_FAN_RPM  I didn't achieve. 70 to, 100 ? 0.7 to 1 ?


value from 0 to 1, where 1 is 100%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

Posted
15 hours ago, Rudel_chw said:


value from 0 to 1, where 1 is 100%rpm

 

thanks a lot it works perfectly 🙂 I changed topic name as questions are different.

 

I have a strange problem with trim : when I use the perform command 13-3014-1 , it works but it's like 10 click with hat on joystick

 

Is there a way to correct that ? thanks

 

  • dureiken changed the title to Perform command speedbrake and others
Posted
2 hours ago, dureiken said:

thanks a lot it works perfectly 🙂 I changed topic name as questions are different.

 

But the new title does not inform the reader that we are discussing the F/A-18C ... the cockpit commands shown as examples, do not work on any other aircraft. 🙂 

 

2 hours ago, dureiken said:

I have a strange problem with trim : when I use the perform command 13-3014-1 , it works but it's like 10 click with hat on joystick

Is there a way to correct that ? thanks

 

Sorry, can you elaborate? I don't understand what is the exact issue, nor what is your trigger trying to acomplish by manipulating the aircraft's trim.

 

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:

 

But the new title does not inform the reader that we are discussing the F/A-18C ... the cockpit commands shown as examples, do not work on any other aircraft. 🙂 

 

 

Sorry, can you elaborate? I don't understand what is the exact issue, nor what is your trigger trying to acomplish by manipulating the aircraft's trim.

When I use the command to trim the plane via ME, the effect in game is like using it 10 times via the joystick.

Posted
11 minutes ago, dureiken said:

When I use the command to trim the plane via ME, the effect in game is like using it 10 times via the joystick.

 

Sorry, I have no experience manipulating aircraft Trim from within a trigger, so don't know what advice to give, you will need to experiment on your own .. for example try a value of 0.1 instead of 1.

 

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
14 minutes ago, Rudel_chw said:

 

Sorry, I have no experience manipulating aircraft Trim from within a trigger, so don't know what advice to give, you will need to experiment on your own .. for example try a value of 0.1 instead of 1.

yes I tried 0.5 but it does nothing 😞

  • Recently Browsing   0 members

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