cannot repoduce and missing track file A10C-II Mavericks not firing in Mark Point mode.

[Faelwolf]

Issued resolved. Thank you to everyone for your help!

Simple practice mission, tested in both MT and standard versions, MP mission being played offline.

Mavericks work fine when given a SPI from the TGP or using seeker in either mission or flight plan mode.  But when I use the TGP to make mark points on targets and switch to Mark Point mode, Maverick will slew to target and lock when commanded, like normal, but then not fire. Check of DSMS shows maverick status as standby, even though currently locked on a target. Creating a SPI with the TGP while in Mark Point mode gets same result. Also getting same result by manually locking target with the Maverick seeker off-SPI.

Verified that the Mark Point is showing as SPI, and that other SPI guided weapons, such as JDAM and APKWs, are working as normal.

Tested switching to MP mode by CDU switch, and UFC, same result.

Ran a full repair, and re-saved the mission in the ME, no change.

AMD 5800x CPU, 6800XT GPU, 32GB 3200 RAM

Windows 10, Sim, BIOS, and driver files all up to date

Edit to add: Mav screen is verified to be SOI in all cases.

Edited July 15, 2023 by Faelwolf

[Yurgon]

Are you sure you've actually selected the Maverick as the active weapon profile in all test cases? Does the MAV screen show "SEEKER" "SENSOR" in any of the test cases?

Please record a short track of the problem and share it with us.

Which version of DCS do you run (Stable or OpenBeta)? You'll find the full version number in the lower right corner of the DCS main screen.

Edited July 14, 2023 by Yurgon
"SENSOR", not "SEEKER", my bad

[jaylw314]

16 minutes ago, Yurgon said:

Are you sure you've actually selected the Maverick as the active weapon profile in all test cases? Does the MAV screen show "SEEKER" in any of the test cases?

If you don't have the Mavericks profile active, the MAV page will say "SENSOR" to warn you, IIRC

A track or video would be nice, especially one demonstrating that when you switch the STEER switch on the AAP to all the positions other than MARK, that the problem immediately goes away like you're implying

[Yurgon]

4 minutes ago, jaylw314 said:

If you don't have the Mavericks profile active, the MAV page will say "SENSOR" to warn you, IIRC

Starts with S and ends in R, almost nailed that su...r.

[jaylw314]

Just now, Yurgon said:

Starts with S and ends in R, almost nailed that su...r.

 That's a good one!

Edited July 14, 2023 by jaylw314

[Faelwolf]

Yes, as I added to the post originally, the Mav is SOI.  Also, active in DSMS, also works just fine if I'm not in Mark Point mode. As I said it slews, locks, just won't come out of standby if I'm in Mark Point mode. Full procedure is correct, I even reviewed some tutorials to make sure I hadn't forgotten anything or if something had changed in the upgrade before posting here.

[Yurgon]

47 minutes ago, Faelwolf said:

Yes, as I added to the post originally, the Mav is SOI.

What's that in reference to? I don't think anyone asked about the Mav being SOI or not.

47 minutes ago, Faelwolf said:

As I said it slews, locks, just won't come out of standby if I'm in Mark Point mode.

What do you mean by "standby" in this regard? Not sure I understand the description.

Please record a short track of the problem and share it with us.

Which version of DCS do you run (Stable or OpenBeta)? You'll find the full version number in the lower right corner of the DCS main screen.

Edited July 14, 2023 by Yurgon

[Faelwolf]

On the DSMS page the Maverick status is "STBY", they are in standby mode, though they are operating as though they are not, up until it comes time to fire. I have the latest patches, etc. Tested in both MT and standard beta. I don't run release, it takes up enough HD space as it is. Despite this being a MP mission, (though I'm running it offline) it's not saving a track, I'll look into it.

[jaylw314]

4 minutes ago, Faelwolf said:

On the DSMS page the Maverick status is "STBY", they are in standby mode, though they are operating as though they are not, up until it comes time to fire. I have the latest patches, etc. Tested in both MT and standard beta. I don't run release, it takes up enough HD space as it is. Despite this being a MP mission, (though I'm running it offline) it's not saving a track, I'll look into it.

IIRC, 'STBY' just means you don't have a Maverick profile selected.  I also noticed you have not mentioned the magic word 'profile' that @Yurgon mentioned?  Can you confirm you had a Maverick profile selected?

[Yurgon]

9 minutes ago, Faelwolf said:

Despite this being a MP mission, (though I'm running it offline) it's not saving a track, I'll look into it.

Can't you just hit "Save Track" after ending the mission, in the Debrief screen?

Alternatively, you'll find the latest single player track here:

C:\Users\{Your Windows Username}\AppData\Local\Temp\DCS.openbeta\LastMissionTrack.trk

[Faelwolf]

Yep, but the last mission was from me moving on to something else. I'll run a quick mission later tonight if I can dodge the wife long enough and save a track file for you.  Tracks are something I've never messed with, had enough trouble with it hogging HD space over the years saving MP tracks whether I wanted it to or not.  But I guess it's true, you learn more when something goes wrong than when it goes right!

[jaylw314]

I just gave it a try and could not reproduce this.  Made TGP SOI and SPI, made a mark point with TMS right short, changed the STEER knob on the AAP to MARK, then slaved the MAV page to the TGP with China Hat forward long.  Had to wait to get to about 8 nm slant range before the MAV would lock with TMS up short, then launched as usual.

Aside from the possibility of some bug impossible to reproduce without the same exact set of circumstances nobody can know without a track file, some possibilities come to mind:

• Forgetting to set a MAV profile.  This fits everything you've described and you still haven't confirmed this was done.  Results in "SENSOR" on the left edge of the MAV page.
• Forgetting TMS up short to lock the MAV.  This is not required when MAV is slewed, but required when slaved.  Also could be too far away or have insufficient contrast to lock.  Results in "No Track Launch Inhibit" warning
• Accidentally pressing TMS right long.  This makes your most recent markpoint SPI, so if you had to fiddle with the TGP to get on target, slaving will slave MAV at the markpoint, not the TGP.  Results in "MARK" in the SPI indicator, lower left of HUD, and "No track launch inhibit" if there's nothing at the markpoint
• Forgetting to make TGP SPI.  Then slaving the MAV will point it at the wrong location, usually the current steerpoint.  
• Forgetting to turn on Master Arm.  I've never done this

But, of course, all this is just guessing.

Edited July 15, 2023 by jaylw314

[Faelwolf]

Issue resolved.

Talking with you folks showed this was specific to my setup, and not a bug. So I took a deep dive into my mods folder and discovered my old Helios entries had somehow found their way back in. Entries deleted, this issue and some other oddities immediately disappeared. (And this sort of thing is why I stopped using Helios in the first place. More time fixing it after sim updates than flying seemed.)

I greatly appreciate the time and effort given to this issue for me, and apologize if I have been a bother. But you did point me in the right direction! Thank you!

Edited July 15, 2023 by Faelwolf

[jaylw314]

3 hours ago, Faelwolf said:

Issue resolved.

Talking with you folks showed this was specific to my setup, and not a bug. So I took a deep dive into my mods folder and discovered my old Helios entries had somehow found their way back in. Entries deleted, this issue and some other oddities immediately disappeared. (And this sort of thing is why I stopped using Helios in the first place. More time fixing it after sim updates than flying seemed.)

I greatly appreciate the time and effort given to this issue for me, and apologize if I have been a bother. But you did point me in the right direction! Thank you!

 

Thanks for the follow up on that!

[Yurgon]

Good to know it's working as intended now.