Vakari

Thank you for reporting this, Igrok_kun! You are right about the default frequencies. Luckily it was only a display error with the GUI, so the preset files are unaffected. Regarding being unable to "Set SRS settings to this preset," I was unable to replicate your problem. The only thing I can think of is that you may be clicking the button while EAM is connected. To load a preset, you have to disconnect EAM and reconnect EAM after clicking the button for the new values to show up. You don't have to disconnect/reconnect to the server, however, just EAM. Updated to version 6, available in User Files GUI: Fixed GUI bug that caused default radio frequencies to be shown instead of the actual values saved by the user in the preset file.

Updated to version 5, available in User Files File modified is now "(SRS Folder)\awacs-radios-custom.json" instead of "(SRS Folder)\awacs-radios.json" SRS updates could overwrite the original file. GUI: Moved volume slider up. GUI: Changed order of the Modulation types in their dropdown box. GUI: Window position is saved. Delete the "SRS AWACS-GCI Radio Presets.ini" file to reset all options, or delete the "AppPosition" lines in it to only reset window position. MIDS: When selecting MIDS as the modulation type, the frequency fields will be disabled and will automatically be calculated when you enter the desired MIDS channel Even though the .json file contains the data, SRS does not currently load the saved MIDS channel when enabling EAM mode. You will have to manually select the proper MIDS channel in SRS after connecting to EAM mode. If SRS is updated to load these values, this program should already support that update.

Yeah it would be great to have with many possibilities. It could present news, sales, allow mod management, etc. I'm glad it's planned, just hoping it isn't required everty time you run the game.

Short and sweet wish regarding the launcher mentioned in the 2024.01.12 newsletter: I like that ED hopes to improve accessibility and the new-user experience! Having more options is great, however, please don't do it at the expense of requiring everyone to interact with a launcher before entering the game. Battle.net kills me, hah. 7 Days to Die has a good launcher. It's helpful and is made in such a way that you don't have to use it if you don't want to.

Referencing the following thread where it was mentioned previously and I uploaded a video where I happened to capture the effect: Problems: Intermittently, when landing the A-10C2 it will pitch up heavily just after crossing the runway threshold. After today's patch (2.9.2.49629) when performing my tests, my aircraft would pitch down heavily a few thousand feet before the runway threshold, then pitch up again after crossing the threshold. I had encountered the pitch up behavior maybe a dozen times prior to sitting down today to test it, and I only experienced the pitch down behavior after updating today. Maybe it's just a coincidence and the patch is unrelated. I created a new mission to help me try and find the source of this problem. In the attached mission, 5 of my first 9 landings triggered this behavior. When triggered it applied both the pitch-down behavior followed by the pitch-up behavior. I was starting to think it had something to do with the position of the speedbrake, but my 9th attempt had these problems without using it. Setup: Caucasus, Sochi-Adler, no wind, aircraft in-air, lined up for runway 06, 1500ft ASL, 200kts. Upon entering the aircraft I would immediately throttle to idle, lower landing gear, set full flaps, trim for approach then land. I would also tweak HUD settings and waypoint out of habit. I tend to intentionally land very early on runways. Some details I've noticed so far: The pitch down behavior consistently occurs at the first line I've drawn in the attached image, roughly 3800ft before the runway starts. The pitch up behavior consistently occurs just after the start of the runway. When landing long (touch-down between the end of the tire marks and the center of the runway) I could not reproduce the issue. When landing steeply (5-degree glide slope) I could not reproduce the issue. When landing shallow (1-degree glide slope) I could reproduce the issue. The best way I could describe the feeling is that all pitch trim is removed on approach then re-applied once over the runway. If I react quickly enough, I can pull back on the stick and hold it to maintain glide slope when the pitch-down occurs, then when the pitch-up occurs I can quickly release the stick to neutral to continue the last few feet before flaring onto the runway. I've included multiple tracks that include this 'bug' and also tracks where I expected the bug to occur but it didn't. Let me know if there is any other information I can provide. Thank you for your time! A-10C2 Landing Pitch No Bug 3 - Very Shallow.trk A-10C2 Landing Pitch No Bug 2 - Standard Landing.trk A-10C2 Landing Pitch No Bug 1 - Standard Landing.trk A-10C2 Landing Pitch Bug 7 - Shallow with Rapid User Response.trk A-10C2 Landing Pitch Bug 6 - Very Shallow Failed Landing.trk A-10C2 Landing Pitch Bug 5 - Standard Landing No Speedbrake.trk A-10C2 Landing Pitch Bug 4 - Standard Landing.trk A-10C2 Landing Pitch Bug 3 - Standard Landing.trk A-10C2 Landing Pitch Bug 2 - Standard Landing.trk A-10C2 Landing Pitch Bug 1 - Standard Landing.trk A-10C2 Landing Pitch No Bug 4 - Landing Long.trk A-10C2 Landing Pitch - Bug Hunt.miz

I would appreciate it, but I don't want you to have to go through any sort of painful process on my behalf. I've only written a few small programs and none of them look as involved as what you have built

They have a community thread where people regularly update their status or whine about their impatience https://forum.virpil.com/index.php?/topic/1946-new-ordering-process-live-community-discussion/

Alt+Enter Click the "Help" button at the top then select "Controls List." In that menu, you'll see all of the shortcuts.

Looks fancy! I have disabled/removed a lot of Microsoft stuff on my system, including the MS Store. Is this the only possible way to acquire your program?

Updated to version 4, links in original post "Clear Input" button resets all radio volumes to 100% instead of 0% Minor adjustment to UI alignment Added links to this post and YouTube tutorial Version 4 has been uploaded to User Files

Sorry for no track, but I encountered this again a couple of weeks ago while trying to record a water glitch I was experiencing. I was just starting a gentle flare on my crap landing when the nose pitched up violently, requiring a lot of forward stick to get it back down. This has happened to me maybe 4 times so far in the last month. Now that I see it isn't just me, I'll pay closer attention and try to get a track uploaded.

MT Version:<Install Location>\DCS World OpenBeta\bin-mt\DCS.exe ST Version: <Install Location>\DCS World OpenBeta\bin\DCS.exe Just run whichever you prefer.

My Mic-Test just spews noise when I try and configure my mic, so I can't use the new VOIP. I've attached my dcs.log, dxdiag, and this 6-second video comparing how my mic sounds normally vs. in the DCS Mic Test. I've also recently completed a repair of my DCS installation and removed SRS temporarily. Hopefully I'm not missing something obvious. I'm just now configuring the new VOIP as I'm worried some servers might begin to migrate away from SRS. I've been using a Razer Ifrit headset for a few years now with no issues. Regarding the dxdiag and all of the audio devices, I use Voicemeter Potato as follows: Razer Mic -> Voicemeter -> (any game/software). The new VoiceChat is the only program I've noticed that doesn't work properly. All other software/games I run operate normally with my setup, including SRS. I tested disabling Voicemeter and setting my DCS mic as the Razer device but the issue persists. Thank you for your time! dcs.log DxDiag.txt

Just thought I'd update this with a list of my attempts to fix it to no avail. I did a slow repair which doesn't seem to have affected much. For some reason I did have to redefine all of my key modifiers for the A-10CII. Odd Still looking out for anything broken by the repair. Anyway, I still can't get my external camera views to cooperate like it used to in 2.8. When I make my own mission and fly single-player I can't move the external cameras on any of the modules I've used. I did get 'lucky' once and instead of entering a module I just didn't enter any or choose a coalition and ended up spectating an AWACS I put in the mission. I could manipulate the camera then with both my mouse and head-tracking. Thinking the problem went away, I chose a module and tried again, but neither worked. So I reloaded the mission, did the same steps to spectate the AWACS, but it didn't work this time. I couldn't control the camera. Boo, intermittency! After deciding there was nothing I could do, I gave up and joined a multiplayer server. On the server I had no problems using both systems at the same time! Yes! I joined a different server earlier today and found that I couldn't use my mouse, but I could use my head-tracking. I left the server to disable the "TrackIR external views" option and rejoined, which gave me the ability to use my mouse again. Heck. Further tests to continue as a discover more patience Last step is a fresh installation I think.

Getting back into DCS after a few months away and I have this issue now. I used to be able to use both my head-tracking and mouse to manipulate my external views. I've followed suggestions by Flappie and others in this thread with no luck. I've read a gazillion other threads and Reddit threads. Most are quite old, so I don't think there is a bug so much as I'm missing something stupid. I've tested it in the only modules I've really flown so far: A-10CII, F-18, F-16, and can't move the camera with my mouse in any view. I've verified my mouse binds in each module are properly bound to "Axis Commands" -> "Camera Horizonal/Vertical/Zoom View". I've tried toggling on and off the "Misc. Setting" -> "Track IR external views." I've removed my "Config" and "MissionEditor" folders like Flappie suggested. I can click everything fine in the cockpit and press LAlt+C to hide the cursor while both in and out of the cockpit. I've also launched DCS without my headtracking hardware/software connected/running. I have yet to repair as I'm afraid it's going to break some kind of customization I may have made a long time ago that I'll never figure out again That will be the next step if I can't figure it out otherwise.