Hardcard

Could we just have ALL Jester wheel commands added to the bindings list (under Jester AI)? Jester wheel changing dynamically is kind of a nightmare for voice command users like myself. Also, I second everything @mattag08 said above.

@Beirut If you can't figure it out, try VoiceMacro, it's free, it has no profile / macro limit and it works quite well (as long as your mic is configured properly and you make command tests before alt tabbing back to DCS) Here's the tomcat B profile I'm currently using (40 commands so far), you can import it: Tomcat B.xml PS: You'll need to modify some of the commands in that profile, since they rely on custom bindings I made (under Jester AI). Also, the six communication commands at the bottom of the list use the "ç" key ( OEM_2 (? /) ), which your keyboard might not have... they're pretty specific to the server I usually fly in, so you can just ignore / delete them.

@Home Fries Are all commands in the Jester wheel included in that plugin? I'm using VoiceMacro here and I'm pretty happy with it, the only real problem I'm encountering is what you mentioned about the dynamic Jester wheel, which changes depending of whether your radar is on / off, whether you have an STT lock, etc. I was about to start a thread asking HB to duplicate ALL Jester wheel commands in the bindings list (under Jester AI), so we can set all macros independently of the damned wheel.

Now, after the last patch, it's the opposite situation again: F-15C (without bags) struggles to reach the mach 2+ speeds at altitude that it's known for. You can consider yourself lucky if you reach mach 1.7, almost feels like accelerating a hornet, tbh. It's either too much drag or too little... we don't seem to get it right

@HoldmyBeer @Jimi08 Please, read previous posts and attach the required files @Jimi08 IIRC, there are cosmetic differences between static and AI replacements, but, beyond that, I don't think there's anything I can do about it, script wise.

@TrikeFighter Your dcs.log is still showing DCS/2.7.7.14727, this isn't the latest OB. If you were using the latest OB, it would be showing DCS/2.7.7.15038, like it does in my case. I'd force a manual update by running the command DCS_updater.exe update I'd also make a backup of important stuff in my DCS.openbeta Saved Games folder (like mappings, missions, liveries, loadouts, etc.), then delete it and let DCS create a new one.

Well, I'm delighted to say that, during this last week, I've been able to do GCI / F10 map stuff for several hours without ever losing my icons. It really looks like the issue has been fixed and I couldn't be happier about it Thanks to @JayRoc for reporting the issue, to @Flappie and @[ED]Obi for looking into it and to @Tholozor for finding the key.

@Flappie Much appreciated, mate Btw, I wasn't sure about the F-5, but I'm pretty sure about the tomcat, since a teammate who flew tomcat got hit by the Moskva without warning in a MP session as well.

@Tippis Moskva and Piotr Velikiy don't give any kind of radar warning, not even in the terminal SARH phase. Also, hornet gets warning (I haven't tried with the viper yet), just like all DCS aircraft with RWR have always done. Also, it makes no sense that all ships equipped with anti-air missiles in DCS give warning to the affected aircraft, except for these four (Kuznetsov 2017 gives warning, while old Kuznetsov doesn't) It all points to a bug.

@Flappie Thanks for looking into it I've performed testing with F-15C and pretty much all ships with anti-air capability. The following ships don't give me warning: - Moskva - Piotr Velikiy - Kuznetsov old (the new model gives warning, though) - Neustrashimy

@Flappie Well, you're a luckier man than me and other players who are experiencing the same issue with F-15C, F-5 and tomcat (hornet seems to get the warning just fine). Here's proof that I'm not making it up : https://streamable.com/v3t3wf I've also attached the test mission I'm using. It doesn't seem to be coalition related, since changing the coalitions of both Moskva and Eagle makes no difference. I don't know what's going on, but it's affecting a bunch of players, not just me. Btw, I've also tested with the Pyotr Velikiy and get no warning either, so it's not just limited to the Moskva. F-15C Moskva test.miz PS: Using the latest OB, btw. DCS 2.7.7.15038 Open Beta - 28.10.2021 Also, I'm using a cockpit texture mod for the eagle, but it's not related to the issue (problem appears with the default cockpit as well) I'll perform further testing with all kinds of ships, see the results I get.

Slava class cruiser (Moskva) doesn't give missile warning to F-15C (I think F-5, tomcat and other modules are also affected by this issue) Other ships might have the same issue, haven't had the chance to test it yet.

This thread has several posts by people who jumped the gun after AMD and DCS OB releases, getting it wrong each time. I'll give it a week of proper testing, then we can draw conclusions. So far so good on my end, we'll see if it holds.

30 minutes of testing is not nearly enough to determine whether the bug has actually been fixed. We'll need to conduct tests during entire BF sessions in order to be sure. I'll start tomorrow.

I can also reproduce the issue by setting polygon thickness to 1 (or changing it to any other value after restarting DCS and reopening the mission). Nice catch, @Tholozor

@Flappie Nice to know Could someone tag the thread as "investigating", though?

6 months later, the issue is still around and this thread isn't even tagged... is it funny or sad?

I didn't ask the Nvidia user to provide a log because it's not my job... but apparently I'll have to end up doing it anyway. Here's the thread (same issue, loss of UI icons / buttons across the board): The user is @G.J.S Like you, I also suspected the issue was AMD related, but then he replied that he was also experiencing the issue with an Nvidia card, so that put 2.7 back at the front of the suspect list. Anyway, blaming it on AMD won't solve anything, since AMD employees will say that everything worked fine before DCS OB 2.7 (and they'll be right about that), returning the ball to ED's side of the court.

Nvidia card users have reported this issue as well, the "blame it on AMD" card can't be played here. This is clearly a 2.7 issue.

Same problem here.

Another relevant thing that I haven't seen mentioned so far in this thread is the bar setting. Before the hornet's radar rework, I remember that 4 bar & 40º azimuth in TWS was good enough. After the rework, though, 4 bar was no good anymore, even with the narrowest azimuth setting, the radar struggled to pick up targets and maintain locks. I found that the 2 bar setting yielded much better results. If you're experiencing this kind of issues and using the 4 bar setting, try with 2 bar instead. (Perhaps the brick timeout workaround will be enough to make the 4 bar setting reliable, but in case it doesn't improve things, try 2 bar)

Unfortunately, dcs.log has never recorded anything that could be linked to this issue (afaik). I get that you're looking for clues, but I don't think there are any to be found in dcs.log, sadly. The one thing we know for sure is that the issue was introduced in 2.7, along with new UI features such as the ability to see other client / unit waypoint paths displayed on F10 map. Perhaps it's just me, but it has always seemed to me that this issue is related to UI changes introduced in 2.7 ... As for "Smart Access Memory", let's not start chasing rabbits here, guys. My hardware doesn't even support that tech, it has nothing to do with this issue. Also, the AMD CPU + AMD GPU setup hypothesis isn't valid either, I'm running an intel chip as well. If we have to look for possible hardware culprits, maybe we should consider memory issues instead (since both AMD and Intel users are experiencing this issue). Drives and paging files?. I'm using Samsung 840 EVO 120GB SSD as system drive (with a paging file) + Samsung 860 EVO 1TB SSD for DCS + OCZ Vector SSD (with another paging file) . I'm also using a 144Hz AOC monitor and have DCS capped at 72FPS (I think) I also used a symlink for the DCS Saved Games folder, since it got too heavy for my system SSD.

@Tomy10 Unfortunately, I can't check your mission, since I don't own the WW2 asset pack or any warbird module. I haven't tested SWAPR in Syria map either, there might be bugs related to parking spot IDs and stuff like that. As for the rest of things you mentioned, some of those are explained in the videos and previous comments in this thread. For instance, AI replacements are removed after ~3 minutes (no idea why), this is a known issue, you can use static replacements as a workaround, since they don't seem to be affected. Also, spawn offsets are intentional, I had to reintroduce them in order to avoid collision problems in version 2.7 As for having several replacements spawning in the same spot, something is clearly not working as it should. Btw, you didn't provide your dcs.log, it might contain some clues.

Sounds like a new issue, but, tbh, I don't think I can do anything about it, script wise. DCS spawning has been screwed for a long time and looks like they're finding new ways of screwing it with every new build

@pacastro Capture logic was only implemented in an experimental 1.3 version, 1.4 doesn't support it. The reason being that DCS automatically removes airbase replacements and prevents them from spawning upon capture (at least sometimes). It was a mess, so I removed the related code.