can not reproduce TGP not targeting correctly

[Hammer1-1]

https://www.dropbox.com/s/9vzb4ti84af4ktz/JTF-13 Caucasus Training Map v3.1-20210123-134846.trk?dl=0

 

First issue - couple of times when I designated a target, the TGP would walk off target. I used the HMD to designate, then used the FLIR to slew the cursor over to the target, then designated. The pod would slowly walk off target.

 

Second issue - using the LMAV, I could designate but couldnt launch. the IRMAV was just fine. Both times I had designated with the TGP and not the HMD, although I DID try to designate with the HMD a few times as well, still couldnt get it to launch for some reason.

 

Third issue - using JDAMs in point track, none of my bombs hit the target, although they DID hit the exact same spot in different attack runs. Everything is in the track file. Im fairly certain I did everything correct, I had someone on comms as well troubleshooting with me while I was training with them. Ive never had this issue before...granted I havent flown in a month, but maybe someone can help me by looking at my track file?

[BIGNEWY]

First issue is reported thanks. 

 

I will take a look at the track but the track is very large so it may not be possible to replay it correctly. 

We do prefer one bug report per thread usually as it can get confusing quickly. 

 

 

[Hammer1-1]

I make it under one thread because Im fairly certain its the pod that caused the issue.

[BIGNEWY]

The track replay makes it difficult to show the issue, the first part of the track replay shows you doing touch and goes, then you rearm and go out to the targets on the coast, put the TGP is looking nowhere near the targets when I replay it. 

 

Would it be possible to catch the issue is a shorter track?

 

thanks

[Hammer1-1]

I can try, I might even be able to get a server side track as this was on multiplayer. Let me get back in a few.

[BIGNEWY]

I dont think the server side track will help in this case. 

[Hammer1-1]

https://www.dropbox.com/s/i4kmbes4774hn5k/tpod.trk?dl=0

 

Also have this one recorded too, Ill post it to youtube if need be.

 

The laser for the mav wasnt firing, so I think I have that one solved. However, the TPOD in HMD was all over the place over a certain altitude, while under that certain altitude it remained pretty much on target. The JDAMs were all over the place, but my LGBs were fine.

Edited January 23, 2021 by Hammer1-1

[Hammer1-1]

Give it time to process; its filed in 1440p and was a big file.

Edited January 24, 2021 by Hammer1-1

[Highwayman-Ed]

Just to add to item 1 with the TGP wandering off, I saw this again tonight, although I haven’t seen it in a long time. I then started another flight to see if I could re-create it, and got the same behaviour after the DCS window loses focus whilst the TGP is displayed on an MFD and is tracking.

[Joni]

On 1/23/2021 at 6:02 PM, BIGNEWY said:

First issue is reported thanks. 

 

 

 

 

 

Yes, it has been reported for a while now. Why isn't it being considered as a high priority? We cannot accurately designate with the HMD beyond 10nm! You need to understand the negative usability impact this bug has.

 

Please don't leave this broken for years, it's a very welcome feature.

Edited January 27, 2021 by Joni

[BIGNEWY]

1 minute ago, Joni said:

 

Yes, it has been reported for a while now. Why isn't it being considered as a high priority? We cannot accurately designate with the HMD beyond 10nm! You need to understand the negative usability impact this bug has.

 

Please don't leave this broken for years, it's a very welcome feature.

 

 

When it is fixed it will be in the change log, you will need to be patient. 

 

thanks

[Tholozor]

As far as I can tell It seems to be fixed now in today's patch. I can easily HMD designate far beyond 10 miles without the TGT position walking.

[Joni]

4 minutes ago, Tholozor said:

As far as I can tell It seems to be fixed now in today's patch. I can easily HMD designate far beyond 10 miles without the TGT position walking.

 

I tried it and it isn't fixed. The thing is that they changed how it works and the bug is no longer the same. Now the bug makes that designating beyond 10nm will put 0ft elevation no matter what the actual elev is. But it won't acquire the real one when crossing the 10nm mark like it did before.

 

So you feel it works ok, but if you use it for weapon delivery it will always miss (unless obviously the TGT is at sea level).

Edited January 27, 2021 by Joni

[Tholozor]

Yep, seeing that now.

[evilnate]

Darn. I came to this thread because I didn’t see any mentions in the change log.

 

Is the elevation still 0ft beyond 10mi if you take over TGP from HMD on a point higher than sea level?

[Joni]

2 minutes ago, evilnate said:

Darn. I came to this thread because I didn’t see any mentions in the change log.

 

Is the elevation still 0ft beyond 10mi if you take over TGP from HMD on a point higher than sea level?

 

Unfortunately yes, it remains bugged. 

 

That's why I said this is a critical one.

[BIGNEWY]

2 minutes ago, Joni said:

 

Unfortunately yes, it remains bugged. 

 

That's why I said this is a critical one.

Again unless it is in the change log it is not fixed. 

 

you will have to continue to be patient 

 

thanks

[Joni]

1 minute ago, BIGNEWY said:

Again unless it is in the change log it is not fixed. 

 

you will have to continue to be patient 

 

thanks

 

I wasn't pushing anything, I got you the first time. This was just a reply to a different user with a clarification on why I stated what I had stated before.

 

Thanks anyway, I know it was a huge patch and a lot of work.

[Hammer1-1]

can we get a status update please? tgp still walks off target from time to time and its been a while since I originally posted this.

[BIGNEWY]

On 1/15/2022 at 12:41 AM, Hammer1-1 said:

can we get a status update please? tgp still walks off target from time to time and its been a while since I originally posted this.

The report has gone stale sorry, I have tried to reproduce today and have been unable, it looks fixed to me. 

If you do have a short track replay showing it please attach it as the old tracks no longer show the issue. 

Thanks

[Harker]

The report has gone stale sorry, I have tried to reproduce today and have been unable, it looks fixed to me. 
If you do have a short track replay showing it please attach it as the old tracks no longer show the issue. 
Thanks

BN, follow these steps and you should be able to reproduce the first issue (FLIR walking off target upon TDC Depress after designating with WPDSG):
1. In the ME, place a WP at ground elevation (just so the problem is clearer).
2. Start the mission. Air start is fine, but also happens with cold start.
3. Select that WP, press WPDSG. The FLIR is slaved to the designation, as it should. It is not slewable yet.
4. With TDC Priority to the FLIR page, depress the TDC to drive the designation through the FLIR INR mode. The BUG occurs here, as soon as you depress the TDC and the FLIR can be slewed, it wanders off target. It shouldn't.

[Cathnan]

BN, follow these steps and you should be able to reproduce the first issue (FLIR walking off target upon TDC Depress after designating with WPDSG):
1. In the ME, place a WP at ground elevation (just so the problem is clearer).
2. Start the mission. Air start is fine, but also happens with cold start.
3. Select that WP, press WPDSG. The FLIR is slaved to the designation, as it should. It is not slewable yet.
4. With TDC Priority to the FLIR page, depress the TDC to drive the designation through the FLIR INR mode. The BUG occurs here, as soon as you depress the TDC and the FLIR can be slewed, it wanders off target. It shouldn't.

Have you switched to area track at that point? I was always wondering if that was intended or not. If I don't have the tpod in area or pointtrack it's usually only a matter of seconds until it drifts away.

Sent from my Pixel 2 XL using Tapatalk

[Harker]

Have you switched to area track at that point? I was always wondering if that was intended or not. If I don't have the tpod in area or pointtrack it's usually only a matter of seconds until it drifts away.

Sent from my Pixel 2 XL using Tapatalk

If you cycle through SCENE -> AUTO and back to INR, then it doesn't drift anymore, sure.

But that's not correct behavior, INR should be space stabilized from the beginning, since the pod is commanded to designate (the INR crosshairs are a diamond).

[Hammer1-1]

yeah it should never walk off target regardless of submode.