[REPORTED] X: COCKPIT PARAM IN RANGE only accept integer values

[Rudel_chw]

When using these Trigger conditions, I found that while I can enter fractional values like 0.013 as parameters on the X:COCKPIT PARAM EQUAL TO condition; on the very similar X:COCKPIT PARAM IN RANGE condition it only accepts integer values:

 

 

This seems odd to me, and it makes impossible to check parameters that range in value only from 0 to 1, like the MiG-21 gunsight Span Ring.

 

Hopefully it is an easy fix, best regards,

 

 

Eduardo.

[Rudel_chw]

Come on ED, I realize that a bug can take time to fix, but at the very least please acknowledge the report :(

 

I'm now editing another mission and the Flaps indicator D_FLAPS_IND varies between 0 and 1, and this bug makes it impossible to detect the half-flaps position.

[Rudel_chw]

Hi,

 

Just wanted to report that on the latest OpenBeta (DCS 2.5.6.55363) this bug still persists :(

Hopefully it will get fixed soon, as it is very useful to edit training-type missions.

[Grimes]

Can you add a sample of a param from a non 3rd party aircraft? Or better yet, where I can I look to get these values? As described in the manual the console isn't exactly enabled. This is also one of the few areas that I have little experience with in the editor.

[Rudel_chw]

Can you add a sample of a param from a non 3rd party aircraft? ...

 

OK, I will prepare a good example .. just need a bit of time as there was a power outage on my area and I'm just now updating DCS to today's version. I promise I wont forget :thumbup:

[Rudel_chw]

Can you add a sample of a param from a non 3rd party aircraft?

 

Hi,

Here is a sample from the A-10C:

 

Parameters A-10C:

"EJECTION_BLOCKED_0:0.000000\
EJECTION_INITIATED_0:-1.000000\
MAV_VIDEO:\"OFF\"\
MAV_FOV:\"OFF\"\
TGP_VIDEO_MODE:\"NONE\"\
TGP_TRACK_MODE:\"NONE\"\
MFCD_RIGHT_PAGE:\"TGP\"\
SOI:\"HUD\"\
MAV_STATUS:0.000000\
TGP_ZOOM:0.000000\
TGP_FOV:\"NONE\"\
TGP_DESIGNATOR:\"NONE\"\
ACCELERATION_X_W:-0.364018\
ACCELERATION_Y_W:0.078486\
ACCELERATION_Z_W:-0.088020\
DTS_UPLOAD:\"NO_UPLOAD\"\
HUD_MODE:\"NAV\"\
VHF_FM_FREQ:30.000000\
STEERPOINT:\"INIT POSIT\"\
MFCD_LEFT_PAGE:\"TAD\"\
CDU_PAGE:\"CDU_WAYPT1\"\
UHF_FREQ:251.000000\
VHF_AM_FREQ:124.000000\
"

 

and this is a sample from the Hornet:

 

Parameters F/A-18C:

"HMD_IN_AA_MSL_RAERO:0.000000\
HMD_IN_SIDEWINDER_SEEKER_X:0.000000\
HMD_IN_REQUIRED_GRD_SPEED_SHOW:0.000000\
RWR_BAKE_MATERIAL:\"RWR_Bake\"\
HMD_IN_RDR_WEAPON_COUNT:0.000000\
HMD_IN_NORM_ACCELERATION:0.000000\
EJECTION_BLOCKED_0:0.000000\
EJECTION_INITIATED_0:-1.000000\
HMD_IN_WINDOW_3_MAN_VALUE:0.000000\
RMDI_INDICATOR_INDEX:3.000000\
bakeIndicators:1.000000\
LMDI_BAKE_MATERIAL:\"LMDI_Bake\"\
bakeHUD:0.000000\
HMD_IN_AA_RDR_TD_BOX_KIND:0.000000\
HMD_IN_AA_TARGET_RANGE_RATE:0.000000\
HMD_IN_BIT_REQUEST:0.000000\
HMD_IN_TOF_WINDOW_DISPLAY:0.000000\
HMD_IN_EYE_OPTION:1.000000\
AMPCD_BAKE_MATERIAL:\"AMPCD_Bake\"\
HMD_OUT_LOS_HEADING_EARTH:0.000000\
HMD_IN_CURR_REJ_LEVEL:0.000000\
HMD_IN_FORMAT:0.000000\
HUD_BAKE_MATERIAL:\"HUD_Bake\"\
RMDI_BAKE_MATERIAL:\"RMDI_Bake\"\
MDG_init_DEFAULT_LEVEL:24.000000\
HMD_IN_WINDOW_2_FLASHING:0.000000\
HUD_INDICATOR_INDEX:1.000000\
ACCELERATION_Y_W:0.000000\
LMDI_INDICATOR_INDEX:2.000000\
HMD_IN_AC_PITCH:0.000000\
HMD_IN_AA_TARGET_RANGE_FLOOD_STATUS:0.000000\
MAV_FOV:\"OFF\"\
AMPCD_INDICATOR_INDEX:4.000000\
RWR_INDICATOR_INDEX:7.000000\
ACCELERATION_X_W:0.000000\
ACCELERATION_Z_W:0.000000\
MAV_VIDEO:\"OFF\"\
HMD_IN_RWR_THREAT_VALID_3:0.000000\
HMD_IN_AIRSPEED:0.000000\
MAV_STATUS:0.000000\
HMD_IN_AG_BOMB_AUTO_TTG:0.000000\
MDG_init_specifics:\"./Mods/aircraft/FA-18C/Cockpit/Scripts/HMD/indicator/HMD_specifics.lua\"\
COMM1_FREQ:305.000000\
HMD_IN_ALTITUDE_WARNING:0.000000\
COMM2_FREQ:305.000000\
HMD_IN_AA_MSL_RMAX:0.000000\
HMD_IN_EU_POWER:0.000000\
HMD_OUT_IBIT_OK:0.000000\
HMD_IN_DISP_POWER:0.000000\
HMD_IN_WINDOW_7_DISPLAY:0.000000\
HMD_IN_BRIGHTNESS:0.000000\
HMD_IN_AC_ROLL:0.000000\
HMD_IN_AC_YAW:0.000000\
HMD_IN_AC_ATTITUDE_VALID:0.000000\
HMD_IN_HDG_SCALE_HEADING:0.000000\
HMD_IN_MANUAL_BLANKING:0.000000\
HMD_IN_VERTICAL_VELOCITY_SHOW:0.000000\
HMD_IN_AUTO_BLANKING:0.000000\
HMD_IN_ALTITUDE:0.000000\
HMD_IN_RWR_THREAT_SYMBOL_2_6:0.000000\
HMD_IN_ALTITUDE_LABEL:0.000000\
HMD_IN_VERTICAL_VELOCITY:0.000000\
HMD_IN_AA_TARGET_RANGE:0.000000\
HMD_IN_AOA:0.000000\
HMD_IN_MACH:0.000000\
HMD_IN_WINDOW_2_DISPLAY:0.000000\
HMD_IN_MAX_NORM_ACCELERATION:0.000000\
HMD_IN_BREAKAWAY_X_AA:0.000000\
HMD_IN_BREAKAWAY_X_AG:0.000000\
HMD_IN_REQUIRED_GRD_SPEED_CARET:0.000000\
HMD_IN_WINDOW_3_DISPLAY:0.000000\
HMD_IN_FCR_RANGE_SCALE:0.000000\
HMD_IN_WINDOW_4_DISPLAY:0.000000\
HMD_IN_AA_TARGET_RANGE_RATE_SHOW:0.000000\
HMD_IN_SELECTED_WEAPON_CODE:0.000000\
HMD_IN_SELECTED_WEAPON_COUNT:0.000000\
HMD_IN_AA_SELECTED_WEAPON_VIS:0.000000\
HMD_IN_SIDEWINDER_SEEKER_Y:0.000000\
HMD_IN_SIDEWINDER_TRACKING:0.000000\
HMD_IN_AA_ASE_STATUS:0.000000\
HMD_IN_AA_TGT_RNG:0.000000\
HMD_IN_AA_MSL_RMIN:0.000000\
HMD_IN_AA_MSL_RNE:0.000000\
HMD_IN_AA_MSL_RAERO_CUE_SHOW:0.000000\
HMD_IN_WINDOW15_BULLSEYE_RANGE:0.000000\
HMD_IN_AA_RETICLE_RMAX:0.000000\
HMD_IN_AA_TARGET_ASPECT_CUE_SHOW:0.000000\
HMD_IN_AA_TARGET_ASPECT_CUE_ROT:0.000000\
HMD_IN_AIM9_SEEKER_STATUS:0.000000\
HMD_IN_AIM120_SEEKER_SHOW:0.000000\
HMD_IN_RWR_THREAT_SYMBOL_2_3:0.000000\
HMD_IN_AIM7_SEEKER_SHOW:0.000000\
HMD_IN_FCR_AA_MSL_RMIN:0.000000\
HMD_IN_AA_RDR_ACM_FOV_KIND:0.000000\
HMD_IN_AA_RDR_TD_BOX_POS_X:0.000000\
HMD_IN_AA_RDR_TD_BOX_POS_Y:0.000000\
HMD_IN_WINDOW11_WARN:0.000000\
HMD_IN_RDR_ANTENNA_POSITION_AZIMUTH:0.000000\
HMD_IN_WINDOW15_HOME_BINGO:0.000000\
HMD_IN_RDR_ANTENNA_POSITION_ELEVATION:0.000000\
HMD_IN_RDR_ANTENNA_POSITION_ON_LIMIT:0.000000\
HMD_IN_UPLOOK_RETICLE_ENABLED:0.000000\
HMD_IN_ARM_STATUS:0.000000\
HMD_IN_SUB_MODE:0.000000\
HMD_IN_RWR_THREAT_SYMBOL_2_1:0.000000\
HMD_IN_SLANT_RANGE_SHOW:0.000000\
HMD_IN_SLANT_RANGE_SHOW_NM:0.000000\
HMD_IN_SLANT_RANGE_LITERA:0.000000\
HMD_IN_SLANT_RANGE:0.000000\
HMD_IN_WINDOW12_FUEL_ADVISORY:0.000000\
HMD_IN_STPT_SYM_TYPE:0.000000\
HMD_IN_STP_RANGE:0.000000\
HMD_IN_STP_NUM:0.000000\
HMD_IN_TGT_RANGE:0.000000\
HMD_IN_FCR_SHOW_DLZ:0.000000\
HMD_IN_TGT_BEARING:0.000000\
HMD_IN_WINDOW15_TYPE:0.000000\
HMD_IN_WINDOW15_BULLSEYE_BEARING:0.000000\
HMD_IN_NO_RAD:0.000000\
HMD_IN_AA_TD_ALTITUDE:0.000000\
HMD_IN_FCR_RANGE_SCALE_SHOW:0.000000\
HMD_IN_FCR_AA_TGT_RNG:0.000000\
HMD_IN_FCR_AA_CLOSURE_RATE:0.000000\
HMD_IN_FCR_AA_MSL_RNE:0.000000\
HMD_IN_FCR_AA_MSL_RMAX:0.000000\
HMD_IN_FCR_AA_MSL_RAERO:0.000000\
HMD_IN_FCR_AA_AIM120_ACT:0.000000\
HMD_IN_FCR_AA_AIM120_ACT_RANGE:0.000000\
HMD_IN_FCR_AA_MSL_ACT0:0.000000\
HMD_IN_FCR_AA_MSL_TOF0:0.000000\
HMD_IN_FCR_AA_MSL_TTG:0.000000\
HMD_IN_AA_Aim9DiamondFlash:0.000000\
HMD_IN_RWR_THREAT_AZIMUTH_4:0.000000\
HMD_IN_AA_Aim9Uncaged:0.000000\
HMD_IN_AA_Aim9Locked:0.000000\
HMD_IN_AA_Aim120LosFixed:0.000000\
HMD_IN_AA_Aim120LosPos_X:0.000000\
HMD_IN_RWR_THREAT_SYMBOL_1_1:0.000000\
HMD_IN_AA_Aim120LosPos_Y:0.000000\
HMD_IN_RWR_SHOW_NUM:0.000000\
HMD_IN_RWR_THREAT_VALID_1:0.000000\
HMD_IN_RWR_THREAT_VALID_2:0.000000\
HMD_IN_RWR_THREAT_VALID_4:0.000000\
HMD_IN_RWR_THREAT_VALID_5:0.000000\
HMD_IN_RWR_THREAT_VALID_6:0.000000\
HMD_OUT_SIDEWINDER_SEEKER_Y:0.000000\
HMD_IN_RWR_THREAT_AZIMUTH_1:0.000000\
HMD_IN_RWR_THREAT_AZIMUTH_2:0.000000\
HMD_IN_RWR_THREAT_AZIMUTH_3:0.000000\
HMD_IN_RWR_THREAT_AZIMUTH_5:0.000000\
HMD_IN_RWR_THREAT_AZIMUTH_6:0.000000\
HMD_OUT_STATE:0.000000\
HMD_IN_RWR_THREAT_SYMBOL_1_2:0.000000\
HMD_IN_RWR_THREAT_SYMBOL_2_2:0.000000\
HMD_IN_RWR_THREAT_SYMBOL_1_3:0.000000\
HMD_IN_RWR_THREAT_SYMBOL_1_4:0.000000\
HMD_IN_RWR_THREAT_SYMBOL_2_4:0.000000\
HMD_IN_RWR_THREAT_SYMBOL_1_5:0.000000\
HMD_IN_RWR_THREAT_SYMBOL_2_5:0.000000\
HMD_IN_RWR_THREAT_SYMBOL_1_6:0.000000\
HMD_IN_RWR_THREAT_LEVEL_1:0.000000\
HMD_IN_RWR_THREAT_LEVEL_2:0.000000\
HMD_IN_RWR_THREAT_LEVEL_3:0.000000\
HMD_IN_RWR_THREAT_LEVEL_4:0.000000\
HMD_IN_RWR_THREAT_LEVEL_5:0.000000\
HMD_IN_RWR_THREAT_LEVEL_6:0.000000\
HMD_STR_IN_REJECT_STATUS:\"\"\
HMD_OUT_BIT_IN_TEST:0.000000\
HMD_OUT_SET_NO_GO:0.000000\
HMD_OUT_LOS_ELEVATION_EARTH:0.000000\
HMD_OUT_HDU_ROLL:0.000000\
HMD_OUT_LOS_HEADING_BODY:0.000000\
HMD_OUT_LOS_ELEVATION_BODY:0.000000\
HMD_OUT_DAC_HEADING_BODY:0.000000\
HMD_OUT_DAC_ELEVATION_BODY:0.000000\
HMD_OUT_DAC_SLAVING_ON:0.000000\
HMD_OUT_SIDEWINDER_SEEKER_X:0.000000\
"

 

Please note that I don't know the meaning of each parameter, I usually find what they represent by flying the aircraft while updating the Parameter display.

 

Or better yet, where I can I look to get these values? As described in the manual the console isn't exactly enabled.

 

The DCS Console is only enabled on developer's versions of DCS, so we can't really use it. However, the DCS-BIOS software includes a LUA Console. This software is no longer being supported, but it still works.

 

When I load it, it places an Icon on the status bar that allows us to enable its Lua Console and open a Browser windows to interact with it, like this:

 

 

The software includes some documentation, this is the command that one can use on its Lua Console to get a Parameter listing:

 

 

This is the format that the parameters display:

 

 

This is also one of the few areas that I have little experience with in the editor.

 

I started to use this tool because I wanted to edit some training missions, it was very challenging and that was what hooked me into this type of mission editing :) .. here are videos of some of my missions:

 

https://forums.eagle.ru/showthread.php?t=260933

 

Here there is more info on DCS-BIOS:

 

https://forums.eagle.ru/showthread.php?t=141095

 

Best regards,

 

 

Eduardo

[Grimes]

Thanks for the info. It is reported.

[Rudel_chw]

... It is reported.

 

Thanks a lot for that, I do hope that ED will take note and fix this.

 

I'm currently editing another training mission (for a non-ED aircraft, but this trigger can also be used for ED's aircraft training missions).

 

On this mission I ask the user to set a Take-Off trim of +/- 7 degrees. The aircraft has a Parameter, appropiately called PITCH_TRIM, but rather than containing the trim value in degrees it is a value between 0 to 1.

 

7º corresponds to a value of 0.55 but I have no means to use this trigger to detect if it is on the range of say 0.54 to 0.56 .. I could use the X:COCKPIT PARAM EQUAL TO trigger to test for 0.55, but then it is really hard for the user to dial that exact pitch value .. it really needs the IN RANGE trigger.

 

On another step of the same mission, I ask the user to extend the flaps to its mid position for take-off .. the Parameter this time is D_FLAPS_IND which corresponds to the cockpit flap indicator dial ... half flaps is about 0.431 while full flaps is 0.98 ... the mid flaps range goes from 0.322 to 0.617 but it is impossible to detect that without the IN RANGE trigger condition.

 

Of course, there are work arounds: I ask the user to extend the flaps to their mid position and then press Space once they are extended ... but I can't verify the user action from within the mission triggers :cry:

 

Anyway ... thanks a lot for bringing this up to the ED team :thumbup:

 

 

Eduardo

Edited October 15, 2020 by Rudel_chw

[Rudel_chw]

Hi,

 

Just wanted to report that this issue is still present on the latest Openbeta, only integer values can be used on the X:COCKPIT PARAM IN RANGE condition, while the very similar X:COCKPIT PARAM EQUAL TO condition accepts decimal values with no problem. Please ED, this should be a very simple fix 

[Rudel_chw]

  another month, another OpenBeta Update, and this bug is still there ... please ED, this seems like a simple input box format issue 

[Olddog]

Just a thought, but would the X:COCKPIT ARGUMENT IN RANGE accomplish what you are wanting to do?

 

Since  X: COCKPIT PARAM IN RANGE (requires  console), and not many folks have access to the console, it could be a while before ED gets around to looking at it.

[Rudel_chw]

36 minutes ago, Olddog said:

Just a thought, but would the X:COCKPIT ARGUMENT IN RANGE accomplish what you are wanting to do?

 

Hi.

 

No it doesn't .. the COCKPIT ARGUMENT tests the position of the knobs and switches that you have on the cockpit. This has nothing to do with a COCKPIT PARAMETER.

 

For example, the cockpit Flaps lever has three positions: UP moves the flaps up, DOWN moves the flaps down, CENTER stops the flaps movement. So, detecting the position of this lever does not tell you what is the current extension of the Flaps, while the "Flaps" Parameter has a value 0 when they are retracted, 1 when they are extended, 0.5 when they are at exactly half travel, etc.

 

However, I can't use X:COCKPIT PARAM EQUAL TO to detect the 0.5 position as that would force the pilot to set the flaps to EXACTLY 0.5000 which is real hard ... while with the X:COCKPIT PARAM IN RANGE I could test for values from 0.45 to 0.55  ... if only it accepted decimal values, currently it is impossible.

 

My current Workaround is a message like this: "Set the Flaps to half extension and press [Spacebar] when done".  This workaround, if used too often results in a poor mission that request a lot of "pressing the spacebar" on the part of the player.

 

Best regards and thanks anyway for bumping this thread .. maybe someone at ED would take notice

 

Eduardo

Edited February 28, 2021 by Rudel_chw

[Jagohu]

Actually, maybe you can use COCKPIT PARAMETER EQUAL TO... ? It seems to work for me on frequencies with a decimal.

Edited March 4, 2021 by Jagohu

[Rudel_chw]

2 minutes ago, Jagohu said:

Actually, maybe you can use COCKPIT PARAMETER EQUAL TO... ? It seems to work for me on frequencies with a decimal.

 

I would use this if I could, but it actually doesn't work reliably as many parameters are not precise and say instead of 1.00000 you can actually have 0.999879  

 

If the EQUAL TO trigger condition can handle decimal values, I don't get it why the very similar IN RANGE can not.

[Rudel_chw]

On 10/5/2020 at 8:01 PM, Grimes said:

Thanks for the info. It is reported.

 

Hello. Just wanted to report that this has been solved on the latest DCS 2.7 released today:

 

 

As the figure shows, now this condition accepts decimal values  thanks a lot ED. @BIGNEWY please, mark as SOLVED 

Best regards,

 

Eduardo