Faelwolf

Thanks! I've gone through everything on my end, Pene is looking at the files. I know they recently made some changes to adjust for the ARC-210, may just need a little more work. I suspect a bug due to every single other thing working properly that I've used so far. All in all, I think they've done a great job not only keeping this going, but adding new features etc. I'm sure it will get fixed.

Appreciate it! At this point I have a keybind workaround, so I'm getting by. If it helps, experimentation shows it will change frequency in the ARC210, but not channel, channel in the UHF but not frequency, and nothing in the third radio or in either radio in the Hornet. Tested in both normal and multithread versions of DCS Beta (I don't keep release on my drive), and with all mods, including SRS, removed. Clean verified install.

I've had VA+VP for quite a few years, but honestly never messed with it other than tanker calls. Recently decided to step it up a bit, and move to a full TX setup on a separate switch (not a fan of the SRS integration). So far, so good, got it all set according to the manual and every command so far is working, except changing the preset channels on the radios. Set frequency works well, but other than the UHF radio in the A10C-II, no radios in either the Hog or the Hornet will change preset channels. So it does not appear to be module specific. I have done a full clean re-install to include cleanup of any registry entries, etc, verified settings, .lua, no conflicting mods, etc. Using the latest editions of both VA and VP. I get the acknowledgement beep, the log also shows it understood the command, just nothing happening in the cockpit. Same in both single and multiplayer. I'm sure I've missed something, as I'm not hearing of others having this issue, but have exhausted my resources. Anyone have any ideas? Log File.txt

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!

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!

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.

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.

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.

It's been posted on another forum that if you have Viacom, you can just use it to say "platform" to skip the AI ATC if you are using a human controller. I have no way of testing it, but you might want to check into it if you have the need.

I believe a FLIR update is coming in the next patch, along with the Apache, etc.

Wow the original time limit for that has long expired. Surprised the old A10C has still been available for so long.

I will add when doing the slow (full) repair, also select the option to search for and remove extra files. Some of the old mods went directly into the game folders, and can lurk there, forgotten over time, to come up and bite you later on.

That is correct, non-polarized lenses will reduce, but not remove glare, more for reduced eyestrain and improved overall vision. I have a pair of polarized sunglasses in my prescription for driving, but I can pretty much forget using my phone while wearing them.

As explained to me in a similar discussion years ago, the FLIR in DCS isn't actually "looking at IR", it is displaying, as best I can think to describe it, baked-in images, that get borked almost every time there is an update to the maps or the map system, as it is part of the map coding itself. This is like what, the third time the FLIR has been crippled by changes in the maps? This is also why it seems to be hit-or-miss with some maps having an issue but not others, and takes so long to fix. There was one time that vehicles were simply invisible to the TGP no matter what map/mode you were in, and in 1.1 you could see vehicles through even the heaviest cloud cover, as clouds did not show up on the TGP at all in IR. Currently, the FLIR is not a separate autonomous sub system in the sim, it's just a graphics display receiving map data and hard coded visuals/animations for objects. I am hoping they are working on a true subsystem for FLIR that will work accurately in all aircraft. I don't know programming to know if or how they could get away from translating map data in some ways, but it should be it's own system enough to avoid bugging out when there are map changes, at least.

I'm the same. I tired hard to like the F-18, but it just feels sterile to fly in comparison to the A10, and not as much fun as skimming the trees, popping up and winging over for an attack run, and BRRRRRRRT!