bojote

What resolution does DCS show?

Problem is related to higher resolution being used (not viewports) when you have Winwing or any other viewports that require you to extend your resolution. For some reason this updated version freezes and goes black screen when you use a non-standard resolution. This is EASY to replicate, simply requires you set a resolution (at least in my case) of 3840x2104 (I use ultrawide). If I keep the same viewports (MFDs and RWR for example) in the hornet but change the resolution to 3840x1024 (standard) then everything works fine. So, this IS a bug and clearly the QA team did not catch it as they are all probably using standard resolutions

I rolled back to 2.9.13.6818.2 and everything went back to normal. Computer freezes intermitently after loading DCS. Without doing anything, it will freeze/unfreeze and if you activate the frame counter you will see it spiking like crazy. No track file as this is in the MAIN MENU. Only fix I was able to test was to stop HELIOS. For some reason when Helios Control Center is running in my setup I see the erratic behavior. There is clearly some kind of issue with the new version.

Loving Raven One: Dominant Fury so far—fantastic campaign! But I ran into something weird in Mission 10 and wanted to ask if it’s intended behavior or a possible bug. After launching from the carrier, I head straight to WP1 at 12,000 ft as briefed. Since I’m one of the last jets off the deck, I expected my SA page to show all package aircraft immediately—but here’s what happened instead: Before WP1: My SA page only showed Rickshaw 03 (E-6B AWACS), even though the entire package should have been airborne. I saw no other flights (not even my lead, Sluggo). After reaching WP1: Sluggo and Squeegee suddenly appeared on the SA page. Sluggo (Raven 61) showed up as a plain green circle instead of "A" (flight lead). Spartan (F-14s) and Cutlass (F/A-18s) never appeared on the SA page at all during the entire mission. I was expecting: Rickshaw 03 (E-6B AWACS) as a circle with a dot in the center (which worked fine) Sluggo as "A" (since he’s my lead) (instead, he was just a plain green circle) Squeegee (Rickshaw SEAD) as a plain green circle (but only appeared at WP1) Spartan & Cutlass as plain green circles (but they never showed up at all!) So my question is—is this all intended? Are Sluggo & Squeegee scripted to trigger their datalinks at WP1 and thats why they don't show up? Is Sluggo missing his "A" designation a bug or just a DCS quirk? or the result of me turning ON datalink before Sluggo? Are Spartan & Cutlass flights supposed to be hidden on the SA page? that doesn't sound right. The whole package should be visible. If this is all by design, I’ll roll with it—but if not, maybe something broke. Just wanted to check before assuming it’s a bug! Thanks for the hard work on this campaign—absolutely loving it!

If you are interested in the functionality of this tool I suggest you search for WhisperAttack, another user took over what I started and made it much better!

No online, whisper is a downloadable module, completely stand alone. It relies on your PC power

VoiceAttack uses the microsoft SAPI which uses whatever speech engine is installed, so it will use the new speech model now, keep in mind I dont use voiceattack voice model or microsoft’s for that matter, im using whisper AI exclusively. The use of voiceattack is merely for the key assigments!

Correct! Simplicity and convenience as you need to trigger the scripts with a button press/release. But any program that does this will work, it does NOT have to be VoiceAttack you can actually test the scripts stand alone and check how they perform

Hi Fabio, The AI component of this utility (Whisper AI) is meant to 'transcribe' (convert speech to text) as accurately as possible what YOU say into the micropone and convert it to plaint text. Once its coverted to text its pasted to your in-game kneeboard on the fly. As you are probably aware, one of the most challenging aspects of speech recognition is doing it accurately. Whisper is *THE* most accurate Speech recogniton program in the market, its abiliy to translate your speech to text is remarkable and the accuracy is almost 100%. My program is NOT an AI assistant or chat with AI, it uses AI simply to translate what you say into text as accurately as possible. Let me give you an example: Imagine you are returning from a mission,you are flying back to your carrier at night and contact marshall for the inbound. The reply you get is usually a long list of vectors, radials, distances and time to commence your approach, every single value you receive is important. So, in this case while you are receiving the transmission, insteading of getting a pen and writing it all down you simply press a HOTAS/controller button and make a memo.. something like. Final Bearing 170, Mother's Radial 350, DME 22, Angels 7, Comence 48. That 'speech' is converted to 'text' and pasted (automatically) to your kneedboard for you to check later as many times as you want. Not a lot people know that you can 'paste' plain text to your kneeboard, so my application simply transcribes your speech into text, copies it to the clipboard and then does a "paste" to the kneeboard in DCS. null

Do I need to run again after each update?

I tried, and in fact implemented a solution using dictation in VoiceAttack, but its so bad and the buffers so small that it was highly inconsistent. Got so frustrated that ended creating this as I needed 99.9% accuracy. OpenAI's Whisper is simply in another league

Hello everyone, I’m excited to share a tool I’ve been working on that integrates real-time voice transcription directly into your DCS kneeboard using Whisper AI and VoiceAttack. As you know, flying in DCS can require managing tons of information on the fly — coordinates, radio frequencies, headings, or even just reminders. This tool is designed to make that easier by letting you speak and then automatically transcribe that information into your kneeboard in real time. How it Works: Two Python scripts, combined with VoiceAttack, let you record up to 10 seconds (or more if you edit the script) of audio by pressing a button on your HOTAS or joystick. Once you release the button, the recording is automatically processed using OpenAI’s Whisper model, transcribed into text, and pasted directly into your DCS kneeboard (automatically) — no manual typing required. Voice Recording with a Safety Mechanism: When you press a designated button in VoiceAttack, the first script (recorder) starts capturing audio. It records up to 10 seconds (configurable), ensuring that even if you forget to stop the recording, it won’t continue indefinitely. Automatic Transcription and Paste to Kneeboard: Once you release the button, VoiceAttack triggers the second script (transcriber). This script sends a signal to stop the recording, processes the recorded audio using OpenAI's Whisper, and transcribes it into text. The transcription is then automatically copied and pasted into your DCS kneeboard using a simulated keyboard shortcut (Ctrl + Alt + P) assuming you have it assigned on your DCS controls UI Controls screen. Whisper AI for Accurate Transcription: Whisper is one of the best AI models out there for real-time speech recognition, handling aviation terms, and numbers with remarkable accuracy. Whether you're calling out coordinates, frequencies, or instructions, it catches most of it pretty well. Even if you speak a different language, it will translate the instruction to the kneeboard in plain english. Why Use This Tool? Hands-Free: You don’t need to pause the game or type anything. Simply speak into your mic while flying and it will AUTOMATICALLY paste the transcribed version of your speech to your DCS Kneeboard on the fly! Coordinates, instructions, 9-Lines, reminders. anything. Customizable: You can adjust the recording length, transcription settings, and trigger buttons based on your needs. Robust Performance: Both scripts are designed to be reliable under various conditions, with built-in safety mechanisms to avoid race conditions or interruptions. What do you need? (Requirements) VoiceAttack: To trigger the recording and transcription scripts with a button press. Python Installed: The scripts are written in Python, so you’ll need to have Python installed on your system. Detailed instructions will be provided to set this up. Whisper (OpenAI): Whisper is the AI model used to process and transcribe the audio. The model can run on both CPU and GPU (CUDA-supported), but a GPU will significantly speed up transcription. How to Set It Up: Download it from here and check the README file included Feel free to reach out if you have questions, or if you need help getting it set up! Fly safe, Jesus "Bojote" Altuve

having the same problem.. using the recent update from Sep 30. Will revert back to 2.9.5.x and test. Problem seems to be the E2 stuck not letting the flow on the flight deck progress

Just had the same thing happen to me. It might be a DCS issue in the recent updates. What you describe is EXACTLY what happened to me. and I too ended up shooting the outermost left engine. I did escort the plane all the way to the landing this time! full flaps and gear down to match its speed

@baltic_dragon what an amazing experience. As you probably remember I had some issues with Mission 2 and I did not want to skip it. So simply waited on it and played OCN in the meantime. While playing OCN I noticed extreme performance degradation and got so frustrated that ended up reverting to DCS 2.9.5.x, which solved the perfornance issue but also helped solve the problem with mission 2 as I was finally able to complete it. Of all the campaigns I've completed this has to be the most fun and engaging. It helps that I was also reading the book along the way. I did NOT have any problems with the complexity or briefings, the ONLY issues I encountered was in mission 14, first for some weird reason TRONs we not pushing. I tried getting closer and after 2 tries I believe they finally did. Tron 51 never shows in my SA page so I was following the moonshadows flight 52. The other issue I found was with the GBU-10s laser codes. If I change them (both in the SMS page for both GBUs and ALSO in my atflir) the bombs will NOT hit. They only work if I keep the default laser codes, not sure if this a DCS bug when using different laser codes despite changing them everywhere correctly. I did in fact try a custom solo mission and when using custom codes they were NOT hitting the target so this might be a DCS issue. Finally... and SPOILER ALERT stop reading here if you have not played mission 14 Here's the video: https://www.youtube.com/watch?v=344qL__9ee4

When I posted this on Aug 25, I felt something was off, it just felt different to what I was used to but could not figure out exactly what it was. Then (as other users had reported) there was the issue with performance when a lot of AI ground and AI units were present and that ED acknowledged. Since I was so frustrated with the performance (of the sim, not just the radar) I deciced to ROLL BACK to 2.9.5.55918 so that I could again enjoy complex SP missions (Operation Cerberus North). Whats interesting is that after the ROLL BACK, the radar performance is now again outstanding, NIGHT AND DAY, as if something was introduced after 2.9.5.x that makes the radar 'drop' contacts randomly. This is not placebo, there is no way others haven't noticed this. I know you asked for a track file but before doing so I'll wait for the next patch as I believe there might be a relationship of the performance problems introduced with AI Ground and Air units and radar behavior and if its fixed then there's no need for a track file... will report back after the patch.

I do in my main DCS computer, but since troubleshooting this problem I installed DCS in my (other civilian sim) computer, which NEVER had DCS installed. Meaning no mods AT ALL. Zero. Only Hornet, Cerberus North and Syria. Thats it. As I said, I've tried (on my own) to isolate the problem (as others here are doing) and what I did, was to roll back my DCS version to 2.9.5.x. which works great. My next step is using process monitor (the sysinternals tool) and compare what DCS.exe is doing in 2.9.5.x different from > 2.9.6.x that might help. Also, if anyone is familiar with process monitor (NOT THE WINDOWS process monitor) but the specialized tool you download you'll see how helpful that can be. I don't thinking bashing ED will help, thats why I rather take a proactive approach and see if I can spot something obvious that will help the devs figure out what the problem is.

Its limited to 120. The 250-280 number is the theoretical you see in the frame counter and simply used for reference

Do you own Operation Cerberus North? A consistent way to test and see the problem inmediatly is to load Mission 16 (Part 2).. that SAME mission in 2.9.5 works FLAWLESLY, not a single stutter and consistent 250-280 fps. If you load the exact same mission with > 2.9.6.x you'll inmediatly spot the problem, FPS will wildy go from 40-150 and frame time (which is the time it takes to render a single frame) will go up and down erratically. If you edit that mission and remove either ALL AIR AI units or GROUND/STATIC units (there are > 2000 units aprox) then everything works fine. The attached image shows what changed after 2.9.5.x. Thats why you see people suggesting that the problem has some relation to the logic/interactions between Air AI and Ground units. ED also MOVED the logic to a different thread, so there is a thread syncronization matter that could potentially affect the MAIN thread. If the main thread is 'expecting' something to happen and/or needs to wait for it you'll have a condition in which the CPU will consume cycles, go 100% and stall the entire simulation. As discusses before, this is a complex programming issue that requires specific conditions in order to be triggered and that condition is simply lots of units (not sure if ground, static, blue or red) thats for ED to investigate (which they are) null

I believe thats precisely the point everyone here is trying to make. Its not a matter of 'who' is affected, but when will it affect you. If you only fly single player instant missions or simple MP dogfight PvP servers then you'll probably NEVER be affected and you'll post things such as: Everything fine on my end! no performance issues here.. thats fine! but, what is being discussed here is something much more complex. Its a LOGIC/PROGRAMMING FLAW in the way AI Ground and Air units interact. As if an endless loop and/or unnecesary recurring process is trashing the CPU, most likely due to a race condition and/or a scoping issue (my theory is that ALL ground units and actively searching for AI air threats, instead of a selected few within a zone/bubble) The reason you see people frustrated is because they know that 2.9.5.x did NOT have this issue, period. This thread and the problem discussed has been already identified and being worked on by ED, my concern (and this is nothing against Scott) but something that worries me is when he says ED is working on 'Optimizations' and finding ways to make FPS better. We don't need an 'optimization'. This is a BUG, a problem in the code, a LOGIC issue and the way to fix it is to either ROLL back the AI Ground/AIR interaction logic introduced in 2.9.6.x or rework its implementation as its clearly not working.

Yeah thats what I imagined. I believe some people is probably not aware of the specific problem we are discussing (and that has been acknowledged already) so I'll just wait for the new patch. thanks!

Does mist or moose get installed automatically by OCN? I’ve certainly not downloaded them

Thats great to hear Scott! I was concerned that ED would think this was just users complaining with messed up configurations and or mods causing the problem. I do not use ANY mods in my testing PC so I was confident this was something introduced in 2.9.6 in particular with either ground or air AI units as I believe you guys added new AI logic and/or moved functionality to other threads. I'm pretty sure this also affected my A/A radar 'effectiveness' as I was experiencing radar lock drops even in STT mode for contacts in front of me, not maneuvering and both in PRF med/hi. Looking forward to the next update! Thanks!

Pretty sure you must be aware of this as its very easy to replicate in ANY computer. Something after 2.9.5.55918 completely killed performance for complex missions. This is not a problem in simple missions or instant action, but clearly noticeable in the late missions of OCN. For example, Mission 16 Part 2. Check this out: The name of the gif corresponds to the DCS version being used. I can go back and forth between versions and clearly notice how 2.9.5.55918 performs flawlesly. Not a single stutter, incredible smooth performance during the mission. This is 120 FPS limited. Notice how starting with DCS 2.9.6.57650 (which by the way, DCS wont let me revert to, I had to go to 2.9.6.58056) performance is all messed up. I believe the jump from DCS 2.9.5 to 2.9.6 is affecting users with complex SP missions or heavy units MP servers. I'm writing this here hoping that you can raise this concern with DCS as it is very easy to replicate. Just load Mission 16 (Part 2) and compare how DCS versions behave. I tried this in my two computers (one of them NEVER had DCS installed) so it was a fresh install, no mods, Just Syria, OCN and the Hornet, thats it. I understand this is NOT your problem and your campaign is not the issue I'm simply raising this concern with you hoping DCS at least acknowledges there is a problem that will and is affecting users. Thanks!

Fresh install (DCS installed for the first time), no mods, Just Hornet, Syria and Cerberus North. Mission 16 (Part 2) 5 seconds after pressing spacebar: DCS 2.9.5.55918 vs DCS 2.9.6.58056 Needless to say, AFTER 2.9.5.55918 something messed up heavy unit SP missions. Fact, easy to replicate.