Jump to content

Recommended Posts

Posted

I'm trying to set a waypoint exactly where a target is so my AUTO bomb mode in my F-18 will drop it on the ground target.

 

Problem is, my waypoint can not go lower than 98 feet. As a result, when I turn my waypoint into a TGT, the target is 98 below where my bomb are expecting to impact, thus over shooting with AUTO mode.

 

Anyway to force my bombs to be at 0 feet? The waypoint is set to AGL.

 

Thanks!

Posted

Such is life. The mission editor assumes this is a flight plan so it's preventing you from setting heights above datum that are inconsistent with actually flying there.

 

Many actual aircraft store their flight plan waypoints with the ground surface at location instead of planned altitude. I think F/A-18 is one of them. So DCS should be programmed that it takes the ground surface elevation instead of the planned flight altitude for all "y" values. In this case every waypoint would be on the ground.

 

Failing that you have to memorize the target elevation and manually edit the waypoint's height above datum through the cockpit interface.

  • 9 months later...
Posted

Using AGL in the waypoint properties dialog, it is no longer possible to set 0 ft AGL.

 

The minimum value accepted is now 30 m (98 ft) and if a value below this is entered, the 30 m minimum is enforced.

 

Switching to MSL you are able to enter 0 ft AGL i.e. if the terrain is at 4580 ft, you can enter 4580 ft MSL.

 

This particularly effects the creation of target waypoints where setting 0 ft AGL is a quick way to designate a ground target.

 

Tested in Nevada and Caucasus using Open Beta 2.5.5.39003

 

Example mission is in this F/A-18C post :

 

https://forums.eagle.ru/showpost.php?p=4103489&postcount=1

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

Posted
I just enter 0 MSL and let the ME set the 0 AGL equivalent in MSL.

Works perfectly for the A-10C (unsure though about other modules)

It's not module specific, using MSL is a work around, I always thought setting 0 ft AGL was possible but checking my legacy installs of 1.5.6 and 1.2.16, I see the same AGL bug with 30m (98ft) being the minimum accepted AGL value.

 

It's really surprising to find this bug dates from 2015.

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

  • 3 years later...
Posted

Hi, 

Just like the title says. If you put a 0 in the AGL, the game will automatically add 98ft to it (to verify, change to MSL after you've put AGL 0 and see how it gets actual MSL height + 98ft). The MSL on its own work fine. If you initially enter a 0 - the ME will change it to the actual MSL with out adding anything.

For those who build missions and use steer points for JDAM attacks - this will cause the bombs to miss (I GUESS, the addition of the 98ft was done to prevent mistakenly dividing by 0 somewhere in the code...) it's an annoying bug causing bombs miss. Please fix it. 

Posted

if the ground level is 98 feet above sea level, then zero AGL will be 98 feet.  Hence the default.

Your ground targets AGL will be 98 feet, not zero.

Posted
On 6/27/2023 at 3:17 AM, nickos86 said:

Hi, 

Just like the title says. If you put a 0 in the AGL, the game will automatically add 98ft to it (to verify, change to MSL after you've put AGL 0 and see how it gets actual MSL height + 98ft). The MSL on its own work fine. If you initially enter a 0 - the ME will change it to the actual MSL with out adding anything.

For those who build missions and use steer points for JDAM attacks - this will cause the bombs to miss (I GUESS, the addition of the 98ft was done to prevent mistakenly dividing by 0 somewhere in the code...) it's an annoying bug causing bombs miss. Please fix it. 

This is how it's always been

Posted (edited)

I'll try again.

AGL= above ground level (height). In ME if you put 0 AGL - it should always stay zero. Doesn't matter if it is below sea level or on the Everest. 

MSL= mean sea level (altitude). If in ME you put 0 MSL - it should become the altitude above the sea level. if you set the WP on top mount Everest and dial 0 at MSL in the ME it should become 29029ft (but AGL should be 0!)

In DCS (and I've attached a screenshot) - if you set MSL 0 - it automatically become the correct altitude. BUT if you set AGL=0 then it become 98ft instead! You can verify by moving the ALT back to MSL and you'll get MSL+98ft. 

This is WRONG. If you set a JDAM attack on a WP and in the ME you set the alt to 0 while in AGL - you'll probably miss the target because the alt becomes 98ft above the actual target.

@BIGNEWY and @NineLine please take a look.

Thanks.  

AGL_MSL.png

ME_AGL_MSL.png

Edited by nickos86
  • Recently Browsing   0 members

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