RoGaR Posted December 29, 2022 Posted December 29, 2022 (edited) Hello guys, I try to set an altitude dependent trigger. I Found it, set it, it works, but I obviously missing something because the trigger is not activating at 5000 but at 7750. The temperature is 15C and altimeter 2992. Any hints what I'm missing? Thanks null Edited December 29, 2022 by RoGaR
Rudel_chw Posted December 29, 2022 Posted December 29, 2022 Have you tried the UNIT'S ALTITUDE HIGHER THAN trigger condition? Its arguments is in meters, so for 5,000 feet use 1524 meters. 2 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
RoGaR Posted December 30, 2022 Author Posted December 30, 2022 9 hours ago, Rudel_chw said: Have you tried the UNIT'S ALTITUDE HIGHER THAN trigger condition? Its arguments is in meters, so for 5,000 feet use 1524 meters. Thank you for that hint, but I want to have the value of the altitude value will be connected with the pilot not with the game. What I want, is a simple read from the altimeter in the cockpit. I tried you method. E.g. I set this value to 1600m = 5249ft . The trigger starts at the 5249ft but you need to check this via the F2 view (Game altitude). In cockpit @32C and 2992inHG you will see 5180ft or @32C and 3001inHG=5260ft. So this trigger "UNIT'S ALTITUDE HIGHER THA" is weather independent and I need the opposite. I want that the outcome will depend on how you set your altimeter. I twitched the coefficient (0.117) to match my altitude but it still something happening behind. The trigger above is not simple reading the altimeter. If you increase the altitude value by increasing the altimeter pressure, the trigger will not start in the desired altitude and it's moved by the altimeter setting. BTW I was surprised that the function between (0-0.117)is not even linear. Eg. For 3000ft @15C and 2992inHG you would expect 0.045ish but it's 2700ft=0.0065 and 3300ft=0.0187 I still try to figure it out, how it's work
Rudel_chw Posted December 30, 2022 Posted December 30, 2022 2 hours ago, RoGaR said: What I want, is a simple read from the altimeter in the cockpit. I understand, you need the altitude value that is seen by the pilot, not the actual altitude of the aircraft .. I'm afraid that I don't know how to do that. The F-18 has a parameter "BASE_SENSOR_BAROALT" that is supposed to give you the baro altitude of the aircraft, but it still won't match the value that the Hornet shows on the HUD .. close, but not a match 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
RoGaR Posted December 30, 2022 Author Posted December 30, 2022 1 hour ago, Rudel_chw said: I understand, you need the altitude value that is seen by the pilot, not the actual altitude of the aircraft .. I'm afraid that I don't know how to do that. The F-18 has a parameter "BASE_SENSOR_BAROALT" that is supposed to give you the baro altitude of the aircraft, but it still won't match the value that the Hornet shows on the HUD .. close, but not a match Solved it via "X: COCKPIT INDICATION TEXT IS EQUAL TO ", but if the change is so fast, the indication (HUD) cannot catch your value (u can use more values). However, in the racetrack precision flying practice (that was the original purpose) do not expect such a big deviations. And the trigger react to the altimeter setting too. 1
Sedlo Posted December 30, 2022 Posted December 30, 2022 (edited) 13 minutes ago, RoGaR said: Solved it via "X: COCKPIT INDICATION TEXT IS EQUAL TO ", but if the change is so fast, the indication (HUD) cannot catch your value (u can use more values). However, in the racetrack precision flying practice (that was the original purpose) do not expect such a big deviations. And the trigger react to the altimeter setting too. You could use the standby altimeter with a cockpit argument in range trigger... It could be a little more lenient to altitude variables... Try Cockpit Argument In Range 219 and the Range like 0.690 to 0.710... That will trigger it from about 6900 ft to 7100 ft. Add argument range 220 from -1 to 0 to ensure this only fires at 7000ft and not 17,000, 27,000, etc. So yeah, two conditions Cockpit Arguement in Range 219 0.690-0.710 and Cockpit Argument in Range 220 -1 to 0 Edited December 30, 2022 by Sedlo 1 1 My Youtube Channel MY DCS MISSIONS
RoGaR Posted December 30, 2022 Author Posted December 30, 2022 21 minutes ago, Sedlo said: You could use the standby altimeter with a cockpit argument in range trigger... It could be a little more lenient to altitude variables... Try Cockpit Argument In Range 219 and the Range like 0.690 to 0.710... That will trigger it from about 6900 ft to 7100 ft. Thank you. I will try it. Any idea why the argument 285 is so tricky?
Sedlo Posted December 30, 2022 Posted December 30, 2022 2 hours ago, RoGaR said: Thank you. I will try it. Any idea why the argument 285 is so tricky? Argument 285 is the cabin altitude gauge.... null 1 1 My Youtube Channel MY DCS MISSIONS
RoGaR Posted December 30, 2022 Author Posted December 30, 2022 46 minutes ago, Sedlo said: Argument 285 is the cabin altitude gauge.... null LOL OK, it makes sense now. Thank you so much. You are legend I feel like a , but at least learned something new. 1
Sedlo Posted December 30, 2022 Posted December 30, 2022 No worries at all! 1 My Youtube Channel MY DCS MISSIONS
Recommended Posts