Unsolved JASSM is missing targets
-
@I-Hawk said in JASSM is missing targets:
@Hubert3000 said in JASSM is missing targets:
@I-Hawk said in JASSM is missing targets:
@Hubert3000 said in JASSM is missing targets:
@I-Hawk said in JASSM is missing targets:
@Hubert3000 said in JASSM is missing targets:
@I-Hawk said in JASSM is missing targets:
Hi,
Are you guys launching the weapon always when it’s in “RDY alignment” state?
Yes. As stated in OP other GPS guided weapons working and JASSM was working in previous bms versions, that rules a few things out. Clearly a bug IMO but if no one else is seeing it then it’s a weird one.
And I tried stock CPU settings as I have OCed CPU as I suspected same result so it’s not that if that is next question lol. Ram, GPU on stock.
Anyway not a huge issue if no one else is seeing it just thought I’d mention it.I’ll try to test myself later thanx.
Some more questions - When you say other weapons are working, does that include other similar weapons - i.e GPS guided with motor? or maybe only gliding weapons like JSOW or SDB?
Yes everything working right except JASSM.
In fact no, I’m testing on Dev version but I assume the same goes on on 4.37, I got both JSSMs and SDBs missing the control tower at Kalma airport, but hitting same spot exactly, means it’s not anything random. Targeting is messed up so it seems
Edit for you above. Having issues with GPS guided powered munitions. JASSM, Stormshadow, Taurus, Apache, Scalp.
That’s weird because I’ve done a few campaigns in 4.37.2 and had no trouble with JDAM, JSOW, SDB.
This is getting complicated… it’s been long time since I flew “operational”, so I apparently I messed up targeting. I set Control tower as target but apparently forgot to assigned it to the STPT, so anyway after that I’m sorry but I cannot reproduce, JSSMs are hitting perfectly time after time here in a self-made TE on Kalma Airport control tower. Will need a way to reproduce your issue.
OK then. Well that’s not weird at all… lol.
Probably not worth worrying about if only 2 people are seeing it. I never use JASSM anyway.
-
@Hubert3000 @I-Hawk Seifer found and fixed a bug recently re JSOWs missing, when approach azimuth was exactly 270 or 360. (Maybe other cardinal compass directions? or any azimuth between 270 and 360? not sure)
If that same codepath is used for JASSM… something to consider.
-
@airtex2019 said in JASSM is missing targets:
@Hubert3000 @I-Hawk Seifer found and fixed a bug recently re JSOWs missing, when approach azimuth was exactly 270 or 360. (Maybe other cardinal compass directions? or any azimuth between 270 and 360? not sure)
If that same codepath is used for JASSM… something to consider.
Thanx I thought about it but in that case it was an original bug in the azimuth calculation which caused one of the missiles or both to go wrong position, but here there is no azimuth calculation at all, it’s a direct SPI position fed to the missile target position and that’s it.
-
Update: Got new nvidia drivers 531.68 WIn10 and seems a lot better. Still slightly off target but only a few meters not like 50m off. Didn’t expect that to have an effect but with this game you never know.
-
@Hubert3000 That’s strange, what system are you running ?
-
@jayb said in JASSM is missing targets:
@Hubert3000 That’s strange, what system are you running ?
i7 4770K
Asrock Z97 Killer
Patriot Viper DDR3 1600 16GB
Galax GTX 1060 3 GB
Sandisk Ultra 2 480GB
Crucial MX500 500GB
WD Black 1TB
Thermaltake 750w
CH fighterstick
Philips 32" 1440p 60Hz
WIn10
Might upgrade soon. Still does 1080p 60Hz gaming Ok. -
Hello @Hubert3000 ,
As mentioned earlier in this post, the JASSM is a GPS guided weapon. The weapon is launched towards the active steerpoint selected in the DED. It means that the location of the steerpoint must be at the GPS location of the target. So, if you carry a target pod, you can point and designate a ground target in order to get the exact GPS coordinates of the ground target. Enter the GPS coordinates in the UFC using the ICP: open the DEST page in the DED by depressing LIST followed by the numerical keys 1. Toggle the DEST page to STPT of the target location and enter the LAT and the LNG coordinates and the elevation of the target location. Repeat these steps for other targets at other steerpoints. On the HSD page on the MFD, you will see that the modified GPS coordinates in the DEST page will move the waypoints onto the target(s) location(s).
To release the weapon, select the steerpoint from the HSD page of the MFD where the ground target is located. Fly towards the waypoint and release the weapon when the target is in range (JLZ). I can hit all the ground targets with the JASSM by doing that way.
This procedure is identical as the one for the JDAM described in the 4.36 manual. I agree with you that something has changed between with the update to 4.37.2. With the previous version, I could designate the target with the target pod and enter the GPS coordinates in the weapon using the MARK key (key 7 of the ICP).
Let me know if it helps.
Best regards and good flight! -
@Magnum1964 said in JASSM is missing targets:
Hello @Hubert3000 ,
As mentioned earlier in this post, the JASSM is a GPS guided weapon. The weapon is launched towards the active steerpoint selected in the DED. It means that the location of the steerpoint must be at the GPS location of the target. So, if you carry a target pod, you can point and designate a ground target in order to get the exact GPS coordinates of the ground target. Enter the GPS coordinates in the UFC using the ICP: open the DEST page in the DED by depressing LIST followed by the numerical keys 1. Toggle the DEST page to STPT of the target location and enter the LAT and the LNG coordinates and the elevation of the target location. Repeat these steps for other targets at other steerpoints. On the HSD page on the MFD, you will see that the modified GPS coordinates in the DEST page will move the waypoints onto the target(s) location(s).
To release the weapon, select the steerpoint from the HSD page of the MFD where the ground target is located. Fly towards the waypoint and release the weapon when the target is in range (JLZ). I can hit all the ground targets with the JASSM by doing that way.
This procedure is identical as the one for the JDAM described in the 4.36 manual. I agree with you that something has changed between with the update to 4.37.2. With the previous version, I could designate the target with the target pod and enter the GPS coordinates in the weapon using the MARK key (key 7 of the ICP).
Let me know if it helps.
Best regards and good flight!I set targets in recon and save in DTC (which should work shouldn’t it?), or use radar or TGP, which works for all other weapons. Other GPS guided weapons are working fine except JASSM, anyway I rarely use it as it’s not in most campaigns but I will check it out.
-
@Hubert3000 were you assigning target to an existing waypoint, or PPT steer point, or defining a new precision steer point?
I was defining a new steerpoint, 99, in the recon screen.
Didn’t think that could make a difference but you never know.
I’ll try the other variations and see what happens…
-
@airtex2019 said in JASSM is missing targets:
@Hubert3000 were you assigning target to an existing waypoint, or PPT steer point, or defining a new precision steer point?
I was defining a new steerpoint, 99, in the recon screen.
Didn’t think that could make a difference but you never know.
I’ll try the other variations and see what happens…
Usually waypoint 3 or 4
Meh I wouldn’t worry about it. Could be issue with PC or game who knows. No problems with other games/programs though at all. Older CPU maybe.
I might get 13700K Z790 RTX 3080 soon that will be full reinstall OS you know the drill -
PC specs please just for curiosity.
-
@Hubert3000 said in JASSM is missing targets:
Usually waypoint 3 or 4Do you see your Target in DTC?
I also thought a time ago it would be sufficient to assign the specific target to waypoint 7 of aircraft 1. But it isn’t, waypoint 7 is always just the general installation steerpoint.You alsways have to set a Target Steerpoint (the manual tells which ones are suitable somewhere, but I don’t find it now. Could be 20-30 and 80-99 or so).
Manual says:
The steerpoint is not usually placed perfectly on your DMPI (Desired Mean Point of Impact) but will be in the general vicinity of the target. To set a precision steerpoint for your DMPI select it in the target list, as we just did, and click on the ► arrow to the right of the DESIGNATE AS TRG STPT # box to increase the number to the same as the target steerpoint (7). Click on the ACCEPT button and target Steerpoint 7 will be placed exactly on your DMPI. This will ensure your sensors are looking at this point when STPT 7 becomes active.
But I have made the experience that STPT 7 is still misaligned even if DESIGNATE AS TRG STPT. You see that right away in the TGP.
But since other GPS-weapons work, that may not be the issue. But could you try to set the Control Tower to TRG STPT 99?
-
In general @Atze-0 is right. Target steerpoint (6,7) is NOT ‘precision steerpoint’ (IF not made as one… you can make it yourself).
So placing target triangle on objective does not make it target specific feature in objective, you must do so via Recon -> Targeting.
For GPS (precision steerpoint) you can use any of 1-24 , 81-90 , 91-99. , those can be defined via map. Others, Markpoints, DL-points, can be used as ‘precision steerpoints’ but can’t assign them via map/DTC.
Everything is in the manual, suggest read some.
Cheers
-
Guys… GPS weapons will go to SPI. So when you have a STPT, the GPS weapons will go there, if you move the SPI via any AG sensor (GM, TGP, HUD, whatever) then the SPI become the position of the sensor controlling it (In order to understand please read the relevant chapter in the 3-4 manual) and when you launch a GPS weapon it’ll go to the SPI, always.
-
@Atze-0 said in JASSM is missing targets:
But could you try to set the Control Tower to TRG STPT 99?
I did try to repro in TR#13 using waypoint 4 target set to the control tower of nearby airbase … both my JASSMs hit perfectly.
So, still a mystery what is going wrong, and why, for some folks. Probably need a short video, to identify the repro conditions.
-
@Hubert3000 said in JASSM is missing targets:
Update: Got new nvidia drivers 531.68 WIn10 and seems a lot better. Still slightly off target but only a few meters not like 50m off. Didn’t expect that to have an effect but with this game you never know.
No idea (really, not even foggiest) how a Graphics driver update can even be involved with GPS targeting. I’m sure there is something else here.
-
@Hubert3000 My specs are:
i7-9700K
RTX 2070
32 Gb RAM
1440p widescreenI am quite happy with my fps, not using VR though
-
I did few tests. My conclusion so far is that JASSM is wind sensitive.
Reprocase Details
Setup:
- TE / 1 x F-16CM-52 / 2 x JASSM
- Targeting with Markpoint through Sniper (ICP 7 - TGP - TMS Up - ICP 0 - CZ)
- No change on CTRL Page
- Changing Wind Direction on every test (0°, 90°, 180°)
Process for each tests :
- Power ON and wait for RDY
- Arriving on Kotar from West, with a bearing of 90° (IP on Delta)
- Drop 1 x JASSM
- Change direction for quarter circle to arrive on Kotar from South, with bearing 180° (IP on Charlie)
- Drop 1 x JASSM
Results :
- With a significant wind (20-30 kts) the JASSMs drift from target on the side opposite to the wind.
Confirming on the same scenario with SDB: Right on Targets
Video of one of the tests (wind from the east, missiles drift west)
-
@CheckPoint said in JASSM is missing targets:
With a significant wind (20-30 kts) the JASSMs drift from target on the side opposite to the wind.
Confirming on the same scenario with SDB: Right on Targets
This sounds like maybe 2 bugs?
What range (distance/altitude) were you releasing?
At 50nm and 25k ft, with ~20 kt headwind or crosswind, I wasn’t able to get jassm to miss.
I haven’t tried stretching the range out to max-jiz … because then I would expect the possibility for it to miss or fall short.
-
@airtex2019 said in JASSM is missing targets:
@CheckPoint said in JASSM is missing targets:
With a significant wind (20-30 kts) the JASSMs drift from target on the side opposite to the wind.
Confirming on the same scenario with SDB: Right on Targets
This sounds like maybe 2 bugs?
What range (distance/altitude) were you releasing?
From 25 to 14 nm, 20 000 ft
EDIT : Add wind settings
EDIT : Add one video of the tests (wind from the east, missiles drift west)
EDIT : Graphical results of Tests (Aim was the central target)