investigating Slave All to SPI fails most of the time

[LeCuvier]

When I use the APKWS rockets I like to designate the target from the TVV. I use these steps:

From TVV (Total Velocity Vector), with TGP on Right MFCD   Set HUD as SOI Throttle Coolie Hat Up Short Slave TDC to TVV Throttle China Hat Aft Short Manoeuvre TVV near Target         Ground-stabilize the TDC Stick TMS Forward Short Make SPI Stick TMS Forward Long Slave All to SPI Throttle China Hat Forward Long After these steps, I set the TGP (right MFCD) as SOI etc. I have been using this process for a long time without problems. But several updates ago I started seeing this failing. When I push the China Hat Forward Long, the SPI simply disappears. Note: It doesn't fail every time, but now most of the time. As a work-around, I set the TGP to boresight and create the SPI from there. But I would really like to use the TVV. I attach a track.

A-10CII cannot SLAVE ALL TO SPI.trk

[f-18hornet]

Thank you, reported for analysis.

[LeCuvier]

I posted this in January. See https://forum.dcs.world/topic/368442-slave-all-to-spi-fails-most-of-the-time/#elControls_5595989_menu

 @f-18hornet Replied that this issue was "reported for analysis" and the thread was locked for replies.
I have not seen the bug confirmed, and there is still no statement whether and when this will be fixed.
In my opinion this is important functionality for designating ground targets. I have successfully used it for a long time, and then an update destroyed it.
Not an indication of good software configuration management!

The bug fix should be a priority item!
ED, please provide an answer!

[BIGNEWY]

Hi, 

as mentioned above the issue has been reported, as soon as there is free dev time for the issue it will be addressed but I can not say when that will be yet, we do not have infinite resources and tasks are assigned by the project managers. 

I have bumped the report internally. 

but please check your hardware, also check your long press is long enough. 

thank you  

[BIGNEWY]

We have reviewed the issue again, it seems you may be missing a step. 

you seems to never set the SPI to the HUD/TDC in the track replay, and in turn the TGP then slaves to the STPT, which was his INIT POSIT some 4 NM behind. 

Here is a track when we set up the correct second waypoint with BMPs SPI to the HUD/TDC.

 

A-10CII-slave to SPI.trk

[LeCuvier]

wrong. I always set the the SOI (not SPI) to the HUD first. But I don't trust the tracks.
Why are you talking about waypoints? When the target is at a waypoint I don't need to go through the process I have described in my original post.

Edited Friday at 09:47 AM by LeCuvier

[BIGNEWY]

Please add a fresh track replay example that is as short as possible, I will ask the team to check it again 

 

[LeCuvier]

1 hour ago, BIGNEWY said:

Please add a fresh track replay example that is as short as possible, I will ask the team to check it again 

 

Here is a new track. I replayed it and it showed the real sequence:

1. set HUD as SOI
2. Slave TDC to TVV
3. Manoeuvre the TVV to the target
4. Ground-stabilize the TDC
5. Make SPI
6. Slave all to SPI

Up to and including step 5. all was fine. But when I did "China hat forward long" to "slave all to SPI", the little square pointing to the SPI disappears.

A-10CII cannot SLAVE ALL TO SPI.trk

[Yurgon]

3 hours ago, LeCuvier said:

Here is a new track. I replayed it and it showed the real sequence:

1. set HUD as SOI
2. Slave TDC to TVV
3. Manoeuvre the TVV to the target
4. Ground-stabilize the TDC
5. Make SPI
6. Slave all to SPI

Up to and including step 5. all was fine. But when I did "China hat forward long" to "slave all to SPI", the little square pointing to the SPI disappears.

Thanks for the new track! I ran both the original track and the new one, and both of them show exactly the same when I play them.

In each case, step 5 from the above list is missing. Here's a screenshot circa 1 second before the "Slave all to SPI":

Note how the HUD reads STPT in the lower left corner.

Since you describe that the SPI indicator disappears, I'm going to assume my track replay and your mission are showing the same thing: the HUD was never set as SPI, and the "Slave all to SPI" HOTAS command diligently slaved all your sensors to the steer point, which is the INIT POSIT some 3.4 NM behind you.

Can you double- and triple-check that setting the HUD as SPI is working as advertised for you, and can you send a screenshot with the SPI indicator showing "TDC" from the track replay?

SPI handling being one of the most focal functions of the entire A-10C, I'm not aware of any open issues in the module in this regard and also haven't heard any questions or complaints from the various A-10C communities I'm friends with.

Edited Friday at 02:52 PM by Yurgon

[LeCuvier]

I'm a bit puzzled.

You say "the HUD was never set as SPI". Shouldn't it be "SOI" rather than "SPI"?
In step 1. I use Coolie switch up short to set the HUD as SOI. Is that the wrong thing to do?
 

[LeCuvier]

I think I have found the culprit. The joystick button I use as TMS seems to be a bit capricious especially when I use it for "TMS Forward Long", so sometimes it works and sometimes it doesn't. Thanks to your post I know now that i need to watch for the ""TDC" indication in the bottom left of the HUD.

I apologize for reporting a bug while it was poor precision of my VRP stick.

[Yurgon]

3 hours ago, LeCuvier said:

You say "the HUD was never set as SPI". Shouldn't it be "SOI" rather than "SPI"?
In step 1. I use Coolie switch up short to set the HUD as SOI. Is that the wrong thing to do?

It's been SOI all along, as indicated by the asterisk * on the left side.

The SPI (or SPI generator) is always the sensor shown in the lower left corner of the HUD. In your case, this was always STPT or steerpoint.

SOI and SPI don't need to be the same sensor. You can SOI and slew the TGP while the SPI remains STPT, for example. Or vice versa, you can make the TGP SPI, then SOI the HUD and slew the TDC around, or half a million similar combinations. "Slave all to SPI" as well as CCRP solutions will always work on the SPI regardless of SOI. 

3 hours ago, LeCuvier said:

The joystick button I use as TMS seems to be a bit capricious especially when I use it for "TMS Forward Long", so sometimes it works and sometimes it doesn't.

Yeah, I ran the track a few more times and zoomed in on stick and throttle. Other button presses like MMCB or China Hat were easily visible, but I could hardly see DMS or TMS move. I used to have a Virpil grip, and while I didn't really like the feel of the buttons, I never noticed this kind of issue on mine. Fingers crossed it'll be an easy fix for you.