Jump to content

Recommended Posts

Posted (edited)

Hi, just tested and all still worked ok - direct hit with both JDAMS  Obviously coords haven't changed at all since the mission was built so they're all good.  I did this with both JDAMs set to PP, using the coords supplied in the kneeboard for the command track and attacking the target as briefed.  If you can provide more detail on how you're setting the aircraft/weapons up and how you're executing the attack, me or another knowledgeable user might be able to offer some more insight.

Thanks

Edited by ChillNG

 

 

Posted

Confirm the JDAM's hit, but, it takes a little trust, and make sure it is giving in zone rather than in range before pickling.

 

On a side matter, the secondary target is not always recorded as a kill, this seems to happen if you attack before 4, i spotted them on the road, and after i was given the order to attack i circled round and dropped bombs (though i steep didn't give a bomb release message, as i have in the past), missed the target and strafed the target not shooting at me; killing it... but it was not recorded as a kill by Poodle, even though it was in the logs.

 

  

Screen_220605_103845.png

SYSTEM SPECS: Hardware AMD 9800X3D, 64Gb RAM, 4090 FE, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero
SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO

YOUTUBE CHANNEL: @speed-of-heat

1569924735_WildcardsBadgerFAASig.jpg.dbb8c2a337e37c2bfb12855f86d70fd5.jpg

Posted
1 hour ago, speed-of-heat said:

Confirm the JDAM's hit, but, it takes a little trust, and make sure it is giving in zone rather than in range before pickling.

 

On a side matter, the secondary target is not always recorded as a kill, this seems to happen if you attack before 4, i spotted them on the road, and after i was given the order to attack i circled round and dropped bombs (though i steep didn't give a bomb release message, as i have in the past), missed the target and strafed the target not shooting at me; killing it... but it was not recorded as a kill by Poodle, even though it was in the logs.

 

  

Screen_220605_103845.png

Thanks for the report, found a minor vulnerability in one of the triggers that records the kill so have fixed for the next update.

  • Thanks 1

 

 

Posted

Thanks, they really are very well put together!

  • Thanks 1

SYSTEM SPECS: Hardware AMD 9800X3D, 64Gb RAM, 4090 FE, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero
SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO

YOUTUBE CHANNEL: @speed-of-heat

1569924735_WildcardsBadgerFAASig.jpg.dbb8c2a337e37c2bfb12855f86d70fd5.jpg

Posted

Hi - sorry have searched for the answer and I can find any loft tutorials that cover it but on my run in to the target I keep getting ‘DUD’ 

the bombs then don’t release 😞

any idea what I’m missing?

 

Posted

I didnt use the loft profile, i couldn't get the release queues. 

Spoiler

what i did was use the  manual release 520 knots on the deck, pull up at the IP (15 degrees or so) , wait for the in zone  and then give it a couple of Mississippi's and then pop both off in a paired release.  seems to work consistently well ... 


 

  • Thanks 1

SYSTEM SPECS: Hardware AMD 9800X3D, 64Gb RAM, 4090 FE, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero
SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO

YOUTUBE CHANNEL: @speed-of-heat

1569924735_WildcardsBadgerFAASig.jpg.dbb8c2a337e37c2bfb12855f86d70fd5.jpg

Posted (edited)
3 hours ago, L4key said:

Hi - sorry have searched for the answer and I can find any loft tutorials that cover it but on my run in to the target I keep getting ‘DUD’ 

the bombs then don’t release 😞

any idea what I’m missing?

 

Dud can be down to incorrect fusing as well I think?  No need for a loft profile as such, just pulling up the aircraft will suffice so the JDAM release zone gets bigger.

Edited by ChillNG
  • Thanks 1

 

 

Posted
3 hours ago, L4key said:

Hi - sorry have searched for the answer and I can find any loft tutorials that cover it but on my run in to the target I keep getting ‘DUD’ 

the bombs then don’t release 😞

any idea what I’m missing?

 

DUD should be either from not having fuse set correctly (or just not set at all) -- most common -- OR being outside release parameters (typically too low).

  • Thanks 1
Posted
5 hours ago, ChillNG said:

Dud can be down to incorrect fusing as well I think?  No need for a loft profile as such, just pulling up the aircraft will suffice so the JDAM release zone gets bigger.

 

This worked - thanks Chris, and all who answered! 

  • Thanks 2
  • 5 months later...
Posted
On 5/29/2022 at 12:26 PM, liojet said:

Good afternoon 

during this mission impossible to hit primary target 

is the coordinates good ??

I am flying this campaign atm and discovered coordinates are NOT correct INGAME (they are right on Syria map though).

Mission 5 i missed the GPS (!) bomb. In mission 6 same stuff. They cannot miss basically.

I found out in a test setup on mission 5 location that the coordinate of mission 5 was way in the field south of Raqqa. And i noticed that the real target has a unpossible coordinate consisting of "98(?) seconds . Seconds can only be up to 60. So in other words, the coordinate grid is wrong ingame for some reason. It does seems to be right when i look up briefing coordinate on the map. This (program?) error must be the cause that all mission fail that us GPS coordinates imo.

Wanted to place this bug in the bug section but it seems its locked for new bugs??

Posted
3 hours ago, Michel0079 said:

I am flying this campaign atm and discovered coordinates are NOT correct INGAME (they are right on Syria map though).

Mission 5 i missed the GPS (!) bomb. In mission 6 same stuff. They cannot miss basically.

I found out in a test setup on mission 5 location that the coordinate of mission 5 was way in the field south of Raqqa. And i noticed that the real target has a unpossible coordinate consisting of "98(?) seconds . Seconds can only be up to 60. So in other words, the coordinate grid is wrong ingame for some reason. It does seems to be right when i look up briefing coordinate on the map. This (program?) error must be the cause that all mission fail that us GPS coordinates imo.

Wanted to place this bug in the bug section but it seems its locked for new bugs??

I'm not sure what you mean here, a bug with the campaign or with DCS/Syria itself?  Not sure what you're referring to with 98 seconds.

Just for clarity I've just retested M6 and my previous comment below still applies.

On 5/29/2022 at 2:25 PM, ChillNG said:

Hi, just tested and all still worked ok - direct hit with both JDAMS  Obviously coords haven't changed at all since the mission was built so they're all good.  I did this with both JDAMs set to PP, using the coords supplied in the kneeboard for the command track and attacking the target as briefed. 

If you set your JDAMs up in PP mode the coordinates are correct.  There was a long standing Hornet bug where the TGP doesn't quite lineup when adding way points manually, not sure if this is still the case or not.

 

 

Posted

1) I see that the target building in mission 5 has a different coördinate when i select it with FLIR then in mission briefing. The strange thing it says 35 degrees 56 minutes 98 seconds North and 39 degrees 02 minutes 00 seconds. I dont think it is possible that minutes and seconds can be higher than 60. (you also notice this when enter a coordinate in the map in mission editor / it does not accept it). So my conclusion is there is something strange going on (at least) Syria map when playing (not in map editor itself).

2) When i enter the mission-coordinate from briefing in the Datapage via HSI i get a different area when i look on FLIR via WPDSG (not the building next to mosque, but some rural field).

I would think this also is the case in other missions like 6 and i just did 7 (and noticed that the coordinate was not exactly on the bunker target).

Maybe its part of my Beta version but it aint right here.

 

PS. i would say that PP would need to give same target as using some coordinates from WPDSG, or not?

 

Unfortunetaly i cant place pictures easily for some illustrations here.

Regards.

Posted
4 minutes ago, Michel0079 said:

1) I see that the target building in mission 5 has a different coördinate when i select it with FLIR then in mission briefing. The strange thing it says 35 degrees 56 minutes 98 seconds North and 39 degrees 02 minutes 00 seconds. I dont think it is possible that minutes and seconds can be higher than 60. (you also notice this when enter a coordinate in the map in mission editor / it does not accept it). So my conclusion is there is something strange going on (at least) Syria map when playing (not in map editor itself).

2) When i enter the mission-coordinate from briefing in the Datapage via HSI i get a different area when i look on FLIR via WPDSG (not the building next to mosque, but some rural field).

I would think this also is the case in other missions like 6 and i just did 7 (and noticed that the coordinate was not exactly on the bunker target).

Maybe its part of my Beta version but it aint right here.

 

PS. i would say that PP would need to give same target as using some coordinates from WPDSG, or not?

 

Unfortunetaly i cant place pictures easily for some illustrations here.

Regards.

Ok thanks I get what you're saying.  The FLIR coords are always a little off in the Hornet, this is an old bug with the Hornet.  They're close enough to allow you to still get the pod looking close but it is a bit of a pain.  Not sure about the 98 seconds, could be part of the same bug, or perhaps a new one.  Same issue you're seeing on mission 5 and 7 I think.  Any JDAM mission where you have pre-briefed coords I would just use PP mode, the weapons should still hit as long as you set it up and drop it right.

 

 

 

 

Posted
1 hour ago, Michel0079 said:

35 degrees 56 minutes 98 seconds North and 39 degrees 02 minutes 00 seconds.

You're confusing coordinates in Degrees Decimal Minutes whereas the briefing gives the targets in Degrees Minutes *Seconds.Decimals* . 

Default F18 setup is in decimal minutes, I think. See below:
(I activated the fine precision, in low precision it would read N42°14.64'. That's 0.64 minutes, so not 64s but 60*0.64 = 38.4s)

 image.png

You can change the coordinate system in the A/C tab, there are seveal options. With degrees/minutes/seconds.decimals, we get what we expected with 14'38s (exercise to the reader : why is there a slight discrepancy 38.96 vs 38.4 ? 😉

image.png

 

HTH,
Buzz

  • Like 1
  • Thanks 1
  • Recently Browsing   0 members

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