nikoel

OpenAI Whisper for VoiceAttack - WhisperAttack This repository provides a single-server approach for using OpenAI Whisper locally with VoiceAttack, replacing Windows Speech Recognition with a fully offline, GPU-accelerated recognition engine via Nvidia Cuda. (For those of you without CUDA, this is still possible with the use of CPU compute. The code automatically uses the CPU as fallback and will work on any processor) This is a fork for further integration of KneeboardWhisper by the amazing creator @bojote A special thank you goes to hradec, whose original script used Google Voice Recognition, and @SeaTechNerd83 for helping combine the two approaches finally @sleighzy for VAICOM implementation and the lengthy list of bug fixes and enhancements that would fill this page In short, @SeaTechNerd83 and I combined the two scripts to run voice commands through Whisper using Bojote's code and then pushed it into VoiceAttack using hradec's code. To speed this up, I unified the codebase into one file and made it run a server to send commands to VoiceAttack. Current average compute for me is between 0.3-0.2s, which can be sped up even more with the use of smaller models (like base.en or tiny.en) by modifying one string (and it can actually understand you, in two days of testing I yet to get it to mis-transcribe anything that I have said) Features: Pushes transcribed text to clipboard - (perfect for voice to text DCS Chat...) Bojote's original vision preserved - DCS Kneeboard integration out of the gate About x10 faster than the original script (from ~2.5s to 0.25ms on a 4090) - and up to 2000% if smaller AI models are utilised - also included with the release (depending on compute available) Has aviation dictionary and bias out of the gate Has phonic alphabet integration and bias Instructions and release download can be found here: https://github.com/nikoelt/WhisperAttack TLDR No more saying Gear Down, and Windows Speech interpreting it as 'Eject, Eject, Eject' VAICOM Support is currently being tested and will be coming shortly! VAICOM is now working. A massive thank you to @sleighzy Additionally, a fixed profile by Bailey for the apache also by Sleighzy is now fully incorporated and working with WhisperAttack https://github.com/nikoelt/WhisperAttack/blob/add-vaicom-integration-instructions/VAICOM PRO/VAICOM_INTEGRATION.md If you want to test, contribute, troubleshoot etc and see latest happenings the development was done in the VR4DCS Discord - https://discord.com/channels/610534461456777257/809527129422430218

It has internet access updates will apply The way to turn off auto updates is via settings -> updates toggle all to off

There was a Hoggit guide...?! Damn - I had to research and build this out from scratch and now I feel stupid for not looking there first as it took me hours of trial and error. Either way you're welcome. Glad it helped and thank you for replying as I was thinking it was too niche for me to bother writing it out and it would get lost in the depths of the forum You already have a few answers. But it comes down to somehow Virtual Desktop is able to do more with less. QuestLink is semi AbandonWare for Meta. They treat it like a bastard child and they have a habit of breaking it, hell they couldn't be bothered renaming it. In theory I agree, USB 3.2 connection it should be better, but it ain't and it's Meta's fault Some people prefer QuestLink, and it might work better for them. The main thing here is that we have options and you're now free to chose between QuestLink WiFi or USB, Virtual Desktop Wifi or Ethernet. More options and more ways to get the experience that you want from an extremely expensive, niche hobby that we all love In regards to one of the above comments, I already had a WiFi 6e Router 30 cm away from my headset that is solely dedicated to running VR. Ethernet was still an upgrade for me personally, and from a handful of people looks like I was not alone. You can read in my first post where the experience became better [for me] and where it didn't

Just finished the campaign a second time. Still the best one I have played in DCS, and I have about a dozen of them Extremely varied and well executed. A few highlights that all campaign makers should implement: Jump to Pushtime. DCS CTD a few times through the 13 missions, and it made it far less tedious and demoralizing. I also replayed a couple that I really wanted to nail down but didn't have much time. With no save state within DCS, this is an amazing feature, and I thank you for it, Sedlo Pre-briefing by lead (aka you) to your wingman on things that you, as a player, really should be paying attention to. Aka of course I set my countermeasures cough – let me just quickly flip a switch, nothing important The way comms are handled is the best out there. Realistic enough to make you use both comms and guard. Understanding enough to just give you the darn channels rather than having you scroll through the kneeboard pages as you try to find your Waldo through 40 lines of frequencies A campaign that uses actual weather. Even if it means that a couple of missions got a little bit broken – thank you Small Nitpicks – and they are tiny because the campaign is so good already QNH is all over the place across the campaign when anything but 1013/2992 is used. Take the last mission as an example: I changed the QNH three times. Once based on the METAR in the PDF, next based on the comms from Magic, and then lastly based on in-game comms, which I believe would be correct. But maybe it's set to change across the map like that? Altitude handoff. As an example you're often cleared to FL200, but the flight plan clearly wants you to climb further; however, the limitation is never lifted 0.5) You've set the weather and time of day to a beautiful dusk in some missions. However, DCS (as I understand) doesn't give you full control over the super carrier. When/if they do, consider turning on the lights, as with the new fog/smog simulation and low sun, the super carrier is a black blob in Virtual Reality The tiny nitpicks show just how high the quality of this campaign is. Sedlo, I've googled but couldn't find your PayPal address anywhere. If you ever consider taking donations, please PM me or leave it at the bottom of your campaigns. I am certain that I won't be the only one P.S. Mission 12 – Not sure what happened. I shot down a couple of F-4s and then got cleared to engage the Su-24s. Found them in TWS, shot the first one with an AMRAAM and the second with an AIM-9. Then two more spawned directly behind me; I was able to shoot one down but got shot down by the last bandit. On my second replay, only two spawned. I shot both down and got cleared to RTB cheetah.trk

Current 'make bookmark/shortcut' key binding of kneeboard within F/A-18C creates bookmarks However if the user accidentally creates an unwanted bookmark, the same key press does not remove that said bookmark. I could not find an additional binding to remove the shortcut/bookmark either Please consider making the 'Make Shortcut/Bookmark' Binding for Kneeboards a toggle function where each press of a button turns the bookmark/shortcut on or off, rather than the current one way implementation Thank you

@bojote - Thank you so much. I have installed it, and run the application (had to reinstall VoiceAttack too) It's leagues ahead of the 1995 Windows Voice Recognition. I pity anyone who is not using this, the days of me saying 'Gear Down' and Voice Attack interpreting this as 'Eject Eject Eject' are over. Good riddance It blows my mind that the developers have not jumped on this and integrated it within VoiceAttack by default since this is by far and away it's biggest weakness bar none Thank you again

I did put this step into the guide. I'll think of a way to make it more clear. Here is the step copied and pasted: "Plug the headset into your computer via any *DATA* USB cable. Put on the headset and allow the incoming connection (popup will appear as soon as the USB connection is being made)" Glad you're enjoying it. May I ask which one of the two code snippets worked for you and what is different to when you tried it first time?

Hey Sedlo, with mission 8 did you mean for the player to shoot down small boats with non precision visual weapons in full IMC or was it an oversight? I was using the FLIR, but in the end my wingman got in the way every time and would shoot the boats until none were left. I didn't get any confirmation or any further radio calls when all boats were killed so I just called winchester and were told to land on the carrier. Did that, but no mission success/fail, got 60% and passed on to the next mission. Unfortunately track file is larger than 50mb so can not be attached

It's easier than what it reads. Much like a certain yesteryear guide from long ago, I tried making the steps user error proof. Which meant writing additional instructions that most users would not need (i.e. Not using a power only USB cable etc...) This entire thing can be summarised as: Connect the headset with developer mode enabled via USB to computer, go to ADB folder and run terminal, input the command, disconnect from computer and finally connect the peripherals to the router and power - done

What is this? A guide on how to connect your quest pro to your router via ethernet instead of WiFi for use with Virtual Desktop Why do I want this? Depending on your router, location, speed etc... a cable connection can result in fewer artifacts, an ability to push higher bandwidth, a more stable connection with fewer micro stutters and tears and much faster eye tracking. The user may have more money to spend on DCS modules as they no longer need to purchase a WiFi 6/e router (I have a WiFi 6e Router - for me no improvements in bandwidth and overall image quality - but I have fewer artifacts, rock solid frame stability and much faster eye tracking) What do I need? A Quest Pro Data USB Cable to connect the Quest Pro to your Computer A fast Ethernet cable from your computer to the router, an equally fast Ethernet cable from your router to your Quest Pro A Router with DHCP A Ethernet to USB-C adapter - I used https://www.unitek-products.com/products/usb-c-to-gigabit-ethernet-5gbps-aluminium-adapter Virtual Desktop Recommended: A high quality USB-C Female/Male *data* extension cable so you can leave the ethernet adapter on the desk and just run one cable to the headset Guide In short, Meta have disabled ethernet by default. To enable it you need to input a command into your headset via something that is called ADB (Android Debug Bridge). To do this you are required to have Developer Mode turned on and the headset connected to your computer to input this command Disconnect QuestPro from computer Put your headset into developer mode (inside the phone app and headset settings). It's actually very simple. Screenshot flow on how to do this is here: https://help.arborxr.com/en/articles/6333136-developer-mode-on-meta-quest-devices Plug the headset into your computer via any *DATA* USB cable. Next, put the headset over your head and inside the headset allow the incoming connection (a Virtual Reality popup will appear as soon as the USB connection is being made) Install Android Studio Navigate to the folder ADB is installed. For me it was in Users/~Username~/AppData/Local/Android/Sdk/platform-tools. AppData folder may be hidden - make sure to view hidden folders in explorer Right click anywhere inside the folder (but not on any of the files) - Open in Terminal Then run the following command to double check that everything is good to go .\adb devices Your quest pro should come up as some bunch of numbers and characters. It should tell you if it's authorised (aka if you performed the above steps correctly) Then run the following command .\adb shell setprop debug.usb.ethernet.enabled 1 Disconnect your quest pro USB cable. Plug in ethernet adapter. Into the ethernet adapter connect PD power source and ethernet cable. Connect the other end of the ethernet cable to the router. (If you, like me forgot to order your USB extension cable, your quest pro should now look like this): Inside your headset settings turn off wifi. If you still have interwebs then she is working gud. The ethernet lights should also be flashing Documentation on ADB within Meta ecosystem: https://developers.meta.com/horizon/documentation/native/android/ts-adb/ Closing Concerns This is not officially supported by Virtual Desktop. I believe this is because Meta could theoretically remove this feature at any time, leaving us at their mercy if they decide to alter the code or delete the feature. (I’ve disabled updates until other guinea pigs update their headsets first and confirm it’s safe.) Nonetheless, it’s not really a risk, since Meta seems hell-bent on bricking everyone’s devices with updates regardless of which features are installed. Frequent User Errors Not using a data delivery USB cable (i.e. the default cable used for charging only) Only enabling the developer mode inside the headset or inside the iPhone/Android App. Both are required Not putting on the headset and accepting the connection inside VR when connecting QuestPro to PC Not providing power to the ethernet adapter Plugging the ethernet cable directly from computer to the headset. Need a router with DHCP

Hey Sedlo, I was replaying your campaign again and re-downloaded the new version. It’s the best campaign in DCS so far! I'm glad you didn’t forget about DCS players—your brief to have the HSI page up because you’ll likely be getting coordinates is a big help, as are the pre-programmed frequencies with comms that say which channel to push. It might seem like a small point, but having to cycle through pages for frequencies over and over is such a massive pain—I wish others did what you do. Anyway, Mission 5: I chose to refuel and got a reply saying I should dial up Arco on 51Y, but there was nothing from Arco on 51Y. I tried 51X and got the tanker. I flew to it, but something may have broken. I was told to change to channel 4 left, and then all communications stopped. When I got to ARCO, I tried to call him on channel 10 (as outlined on your frequency sheet), but got no reply. I ended up plugging in max range speed and made it with just a few fumes to spare. Not sure if it was something I did wrong. Also, I wanted to confirm I was doing the timing correctly. There's a hold and a push waypoint. I timed it so I was overhead the push waypoint at 00:55. Is that correct, or is your campaign set up so you’re overhead the hold and then fly to the push at 00:55? Many Thanks

Flying the KA-50 through the rain brought to mind a story a Russian friend of mine once told me. It took place back in the Soviet Union during the 1980s. He was standing on a balcony in Moscow when the weather turned, and raindrops began to fall. Whenever visitors from abroad witnessed what happened next, it always intrigued them: everyone would pull over, stop their cars, open their glove boxes, and take out their windshield wiper inserts. Right there in the pouring rain, they’d quickly attach the blades, jump back into the car, and continue on their way. Once they reached their destinations, they would remove the wipers and stow them away again. This strange ritual was all because hooligans would steal the wiper blades and then try to sell them. Anyway, is ED so committed to realism that the wiper blades on the KA-50 have been swiped by neighborhood kids, or have you simply forgotten to implement them? I’ve tried turning them on, but they seem about as effective as a condom salesman at a monastery. I’ve seen the capitalist pigs in their 64-Ds repel bad weather, with their wipers and this just doesn’t seem fair. With the recent weather patch, everyone seems to have fallen in love with rain, which makes flying the KA-50 quite challenging and unenjoyable Please, consider making these wipers actually wipe

If it makes you feel better; after the last couple updates I have been struggling I have a 4090 with a highly tuned system and even when I reduce the settings to potaetoe quality I get a momentary frame spike every few seconds. Only the bare minimum background services running (I even culled security settings) with overhead of 90%, frametimes for GPU and CPU in low single digits Reverting to older Nvidia Version helped a little bit I just came to a conclusion that there is something wrong with this build of DCS and it was my time to be the collateral and I just need to wait for a fix

In some circumstances, but mostly no. To address this issue, most (if not all) headset manufacturers use a technology called motion reprojection, which involves generating fake frames or motion smoothing. Although these terms used to have specific meanings, they are now often used interchangeably, so it’s simpler to refer to them collectively. For the G2, which is an older headset, OpenXR Reprojection works in stages. At 90Hz, if you can achieve more than 90 FPS, you experience no judder. When you drop to 89 FPS, motion reprojection kicks in, producing one real frame for every fake frame, effectively resulting in 45 FPS with a slight overhead of creating 45 FFPS (fake FPS). It can also step down to 30 FPS. This approach minimizes judder but can introduce artifacts. The quality of these artifacts depends on the headset manufacturer and the specific technique used—some may be more tolerable than others (G2 versus Pimax or Meta). In practice, you are effectively at 90 FPS @ 90Hz (or FPS = Hz if you have a different refresh rate) unless your system drops below 45 FPS (i.e., half the refresh rate), in which case the experience will be less smooth and more like a fast slideshow. What you’re describing is essentially a simplified form of V-Sync, known as reprojection (without the motion part, though the term is often used to describe the overall concept). If your system can handle it, you’re generally better off with the highest refresh rate you can manage divided by 2. For example, at 120 Hz, 60 FPS is preferable. Given your example and figures, your math is correct. However, I would recommend using motion reprojection if available. Keeping the refresh rate at 72 Hz means that if you can maintain 72 FPS or above most of the time, you’ll have true smoothness. During moments when you can’t maintain this, reprojection will activate to maintain 72 FPS with 31 fake frames.

Thanks for the post If you want VDXR over Link Cable, there is a standalone application that has been developed by the himself Limitation is that there is no Body/Eye Tracking and you need to use a OpenXR Picker to make sure you select the correct runtime https://github.com/mbucchia/VirtualDesktop-OpenXR/releases

It is. You replace a file in Quadviews Program Files folder The video has been linked above. Remember what Mbucchia has said, it will break anticheat for OpenXR games. We are under strict instructions to keep our fingers tightly clenched

Woah. We have some high rollers in ere' I am also going to constructively say that I really hope that the feedback that you're passing on @BIGNEWY is taken onboard rather than "yes dear; thank you dear" Quadviews is as much of an advancement for VR as Multithreading - this is a big deal to many of us I have fixed this with the patch made by @sandboxcode - so from the bottom of my heart thank you mate. It would be good to have something a little more official from DCS as this fix screws up all other games that rely on anticheat and QuadViews

Just wanted to quickly chime in, I don’t know what happened to the chart in post one. For me the image tries to load but doesnt. For the record I haven’t deleted it The figures I’ve read 19.#’ for Viper at 9.3G’s. @HWasp did your model begin to GLOC? Hornet is 21’ - so that’s close two degrees per second, not 0.5. @HWasp was this at 380, or the spicy 400ish? At 7.5 it gets difficult as the speed can runaway from you but that’s where the max performance is for me when I tested it a few weeks ago Similar to what was mentioned in my post, the video I posted and the graphs by contact light and what other users confirmed too It is true I opened myself up to criticism, some more earned than others. It’s a shame that something that I perceived as obvious and common knowledge took so long to prove. In my defence I wanted to present evidence/arguments without getting anyone in trouble. So what we have to go off are the interviews which mostly say the same thing as Wilbur’s post and the aerobatic videos to late 90’s metal music. My personal conversations with pilots who have flown in the military have concurred all this too, but this “just trust me bro” argument can only go so far especially second hand What we have proven is this is not currently the case in DCS. The only way to get close to this condition is by artificially fattening up the hornet and putting the fighting falcon on a diet Now some do think that F/A-18C can confidently out-rate the Block 50 Viper in real life with equal fuel endurance. I’ve been lead to believe that this is not the case in real life My intention was to see if devs wanted to revisit and continue developing the flight model and present arguments with whatever limited information we had and allowed to disclose Hope that all makes sense

@BIGNEWY - @HWasp has provided the track data that correspond to the graphs. All credit to him I wanted to double check that you also got the GAO document with the performance data in the previous page

Not in front of my main DCS computer, but I had a look at the Tacview Now you did achieve 22-23' but then had to ease off to 18-19' to regain energy. Your average was, somewhere just north of 20' / second Additionally, when fuel quantity is being normalised it's not done by %, lb's is better, but actual endurance is best Otherwise aircraft with large fuel tanks, and efficient engines are penalised and ones with smaller tanks and thirstier engines given an advantage. For instance the F/A-18 has an internal fuel capacity of just under 11,000lbs, whilst the 16 is in the realm of 7,000lbs internally This is why on the aircraft have been fuel loaded for 5-6min on the dogfights server. This is important for your "data" because this is a double whammy - the F-16 consumes more fuel than the F/A-18 so for equal endurance in burner it needs more fuel and then additionally for the same percentage of fuel, it physically carries less All you have proven is that if you make the hornet heavier and the viper lighter their performance converges At least you didn't make it +50 outside

Duplicate post

They were not made by me Newy. They were made by @contactlight - only he can comment on them directly and give you the replays that he may or may not have I do not have any affiliation with him, only mutual respect for the work he puts in and knowledge that his graphs are respected by the users of mob’s dogfighting server

I’m going to put this into ‘you might not understand what context this answer was made in’ rather than, what you have accused of. For your information my real life job directly makes me qualified to read these graphs - what we are discussing with these graphs are not real life, it’s DCS world Now on to the context - I was answering a question in regards to the graph made by contactlight Cab’s question/request was in regards to the use of paddle. We know from the manual that 7.5G is the maximum G’s that the pilot can command All I did was a draw a green and red line outlining that everything below and to the left of that curve for that specific graph was within “non-paddle” parameters if you have a problem with what the graph says you’re welcome to take it up with contactlight - I haven’t touched it or altered it

Hmmm… I have a theory how he got 23 Got the turn part right; sustained, not so much

Interesting question. Interesting because the chart does show this. All you have to do is run up to the 7.5G line. I have done this for you here: