nickos86

if you got something in PB17 - it will use it. Else - UFC

Note, there is not digital ALT map correlated to the RDR for the 15E. If you designate a target while the waypoint you fly to (via UFC) or picked up in the RDR is far from the designation - you'll get a large ALT error because the plane will try to interpolate the ALT.

In general DCS got quite a gap in all related to ground unit damage modeling and the effects caused by a weapon onto a specific unit. Just as you've pointed out, IRL you won't see a "DCS style" explosion when a charge hits a unit. It's not a GBU12 The "explosion effect" simply showed when the unit get destructed. You can argue that currently the damage effect and units damage models not modeled well... I'll be the first to agree with that.

So it should have been: "Fixed: TGP+GPS guided weapons = 15-20m Miss. Note: 3 Second laser or AGR required before release for increased accuracy." There should be nothing special about the GBU-38 in comparison to the rest of the GPS weapons.

Why would the GBU38 procedure be different vs the GBU31? Is the 38 a test bed for JDAM FM and features?

Hi, The increased accuracy followed by 3sec of lasing or AGR - is it a weapon thing? Is it relevant to all modules? Or is it a platform thing? In this case, what mechanism was flawed and now is modeled correctly? ED, could you please share some info regarding this fix? Thanks. Fixed: TGP+GBU38 = 15-20m Miss. Note: 3 Second laser or AGR required before release for increased accuracy.

An interesting feature. If you designate a target via the RDR while the waypoint selected in the UFC is in the target area, the TPOD cues automatically to the designation and the elevation is quite close to the actual one (comparing to the F10 map). If you des a target via the RDR while the waypoint selected in the UFC is FAR from the target area- the delta between the RDR des and a TPOD will drastically vary. Attached two pictures. The target area is at waypoint 2. The target coordinated from the F10 map are: N 30°21.066' E 34°50.382' and alt of 1385ft For the first picture ,I've entered waypoint 2.A into the UFC and designated a TGT . The coordinates are very accurate. Same for elevation - 1380 vs 1385 ft. As for the second picture, I've entered waypoint 1A to the UFC and designated the target. Note that now the elev is 1900 ft! Something to consider and take into account when designating targets using the radar. After seeing the following thread: KlarSnow important input: "The Air to ground radar pulls the elevation from the steerpoint you have input at PB 17 in the upper right of the radar display. If you do not have a steerpoint up there, it pulls from the closest steerpoint. This is why your targetting pod is pointing in the air. It has no way to generate elevation off of an HRM map, only coordinates." So it's a good habit to set the steerpoint closest to target into PB17. But, seems like the "if you don't have a steerpoint up there, it pulls from the closest steerpoint" - doesn't work as intended. Rather, it pull data from the waypoint set in the UFC.

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.

Thanks for the responses! I would be cool if there was this kind of option in the stock version without using mods (perhaps even copy coordinates to the built in kneeboard).

Hi, When trying to create/edit a waypoint from the F10 map to the aircraft you need to remember the coordinates and sometime go F10>F1 and back a ffew times. That would be very cool if by pressing a keybind, the coordinates will be displayed in a message window for 30-40 seconds. Allowing enough time to get back to the F1 view and enter the coordinates into the UFC/ICP/whatever. Thanks!

Use the visor, same keybind as the NVG. It fix the visibility problem.

Much better than only a 4 way keybind for those who doesn't have axis for it. Thanks

@BIGNEWYWhen you share a roadmap, change it along the way and inform the community when doing so - you don't get slammed. Communication is KEY. You get slammed when you don't communicate... For instance, up until not so long ago every one was upset because you haven't updated the SC module. You showed pics of the ready room but months later - nothing happened. Only AFTER you've explained that you must have VULKAN working for it to be implemented properly - people understood what's going on. Keep us in the loop with changes you’ve making... We're getting that things might change along the way. It much more frustrating to be kept in the dark.

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.

Roger, thanks!