nikoel

Was so excited as I was looking for a replacement for my aging QuestPro; but alas in the typical VR fashion they must kneecap the thing In this case, no eye tracking on a headset that pushes 28 megapixels (with two panels that do not add to 7k - with the headset named aptly 8K) The wait continues

Hahaha the infamous 10min, 2hr install due to instruction skimming. Happens to the best of us

That’s the windows counterpart (not the app within the headset/meta eco system)? in regards to your controller issue I don’t have that message so it’s definitely possible. However I have no idea how as this is not something I’ve ever had

Hey Team I've also ran into issues with the new executable. It's still under development However, I have just pushed an update that addresses the issues that some users have reported. For instance, when user double clicks the file the window closes itself. I also updated the VA Profile so it now runs the plugin by default Please let me know if it works (or doesn't) - for now the executable works, but in some cases doesn't. Sleighzy will have a fix in two shakes of a lamb's tail. However here is the new version which runs the script as it did originally https://github.com/nikoelt/WhisperAttack/releases/tag/v0.4.1-beta All the best

Hey mate. We are about to release an executable, However if you want to get it going straight away put the following into the command prompt run as admin: winget install --id=ffmpeg.ffmpeg -e

My views on Pimax are known so I wont write them again. Other than to say in addition to all the points, the Pimax costs *a lot* more in aggregate because it's a Land Rover when it comes to resale value. No one wants to buy one off you because everyone assumes that you're selling because your unit is somehow faulty. So you get shafted from both ends To some this is a good time; and I do not kinkshame them

Not sure if what I wrote came across correctly. I was on 2400mbit WiFI connection, now I am using the stock Mobo Ethernet port and it is too restricted to 1000mbit. This upgrade is a theoretical mathematical downgrade in that regard, but has been an upgrade

I have a 2400mbit WiFi6e connection (and I have technically downgraded to 1000 ethernet) and it was an upgrade for me; but this is kind of the reason I put this guide up, so I would encourage you to ask others

Wait-a-second. Those two things are not that improbable. Hollywood has been reviving corpses of all the old titles and the gaming industry is taking notes, and Musky boi is raiding the US treasury. Besides getting to mars is not *that* hard, its staying alive there for an extended period of time that seems to be a problem See you in 2026

WhisperAttack - New Release! We’re excited to bring you the latest version of Whisper Server with major improvements, enhanced accuracy, and better configurability! What’s New? Improved Installation & Dependencies Replaced whisper with openai-whisper for better compatibility. torch now installs with CUDA support automatically for optimized GPU performance. Added text2digits to improve number recognition in transcriptions. New Configuration System! Added settings.cfg for easier customization! You can now define key settings (e.g., Whisper model, device selection, and VoiceAttack path) in a simple config file. 🏎 Faster & More Accurate Transcriptions New text processing enhancements: Automatically converts spoken numbers into actual digits (e.g., "five thousand two hundred" → 5200). Better word normalization – reduces errors and improves accuracy. More refined regex processing to clean up text input. Addition of ability to push fine tuned future whisper models -> 🛠 VoiceAttack Integration Enhancements VoiceAttack path is now configurable instead of hardcoded. If VoiceAttack is not found, a clear error message is displayed. Trigger phrase change: Instead of saying "copy", now use "note " to send transcriptions to the DCS kneeboard. Other Fixes & Improvements Fixed issues with hyphenated words in transcriptions. Improved phonetic alphabet handling (e.g., "X-ray" is now properly recognized). Enhanced logging for easier debugging. ️ This update brings smoother, faster, and more accurate voice recognition with better configurability. Let us know if you have any feedback! Happy flying and commanding Massive thank you to @sleighzy who did most of the heavy lifting for this release and @Seatechnerd83 for the awesome new plugin! Get it here! https://github.com/nikoelt/WhisperAttack/releases

If it walks like a duck… ¯\_(ツ)_/¯ give it a go

Can ya screenshot The folder should look like this and ADB should be around 6ish MB

AppData folder is hidden by default. Make sure that you can see hidden folders in explorer P.S. Confirming you have installed Android Studio as per the step prior https://developer.android.com/studio

yeah exactly, then it makes the middle one redundant

Basically nothing really changes; you want to run ethernet cable from whichever router you connected via WiFi with Virtual Desktop What you want to avoid is double NAT, or connecting to the upstream router which will then send signal to the downstream router which will then send the signal to the PC. The fewer links between your PC to the headset the better

He is running 12.5 Megapixels [final resolution] brochachi

Well crap. I've tried the 2x supersample with ASW with Link from the thread next door and now I have the same thing. It's obviously network related, but I literally changed nothing Have you figured it out?

Don't want to assume anything as it's still on the front page, but in case you didn't see it, did you mean this?

Good for you. I have tried it and this is how I formed my opinion. It looks like you have yours and I am glad you are getting a superior experience with compromises that work best for you

Yeah boys, I concur. You’re better off going into the Quadview Log (the one inside the AppData folder) and quoting end resolutions. This “multiply by 2, divide by 3, and then square” BS gets old very quickly, not to mention that big elephant in the room of encoding image you're actually sending to the headset (or think you're sending to the headset, more on this in a second) @gonvise, I’m just going to state this bluntly—if you think you’re running a 2x supersample by showing the Oculus settings page but not showing the end resolution in the quadviews log, it’s easier to say that you’re not and this is not how resolution and encoding works I strongly believe it’s a matter of taste, and both have their place depending on what the end user wants and what they are sensitive to. Additionally, no two systems are the same, and you can indeed have better experiences with one or the other. The min/max setup you’re running and whatever absurd supersampling you’re pushing is honestly hilarious. I’m a firm believer that friends don’t let friends use reprojection, but at that stage, I don’t care how much supersampling you’re cranking up—your fake frame injection is absolutely wrecking your image. It’s like splurging on the latest Sony A7 with top-tier lenses and then smearing Vaseline all over the sensor—an iPhone would give you a better result. ASW, in my view, makes fake frame injection so jarring and distracting that I’d gladly take a full 1.0 native image with everything set to medium over that mess. It almost completely nullifies any meaningful discussions about DLSS 4, ghosting, or image quality because of how much it butchers the visual experience. If I had to put it in perspective, sure, having a pimple and some dark circles might hurt your self-esteem, but maybe deal with the black eye and missing teeth first. That said, I’ll admit this is a strong personal preference, and you might see things differently As others have pointed out, while the numbers in Oculus settings do go higher, for some, the end image is no better and is often worse. This has led people in other forums to hypothesize that larger numbers do not always properly apply—but they do give you a nice fuzzy feeling because you see a higher number in the settings. For many the difference between HVEC @150 and Cable Link at almost 1K is so minuscule that it makes me believe those people have a point To me running higher DCS settings (everything to the right) brings more meaningful increases in fidelity that are undeniable compared to supersampling beyond ~1.3 due to lens effects Either way, we know for certain that some settings inside the debug tool are ignored by the Oculus Runtime. As an example, set it to ignore the proximity sensor and see what happens Good luck with your quest

Sign me up to the .96 team Just updated from the “leaked” version to the newest and had massive performance issues that some reported Went back to .96 with Profile J and all the issues went away. Duno ¯\_(ツ)_/¯ P.S. neither had the NVIDIA app installed. As lean and mean of an installation as it gets

Thank you mate. I might take a page out of Ironmexxs book and disable updates via ADB to be extra safe. Glad it's a software bug and nothing to do with your hardware - did the ethernet mod cause the issue or was it just the update?

Version 71. I do have Meta asking me to update. But so far I have not

<profanity> photo. But you get the idea

adb shell setprop debug.usb.ethernet.enabled 0 Reboot. Then run the following: adb shell getprop debug.usb.ethernet.enabled It should return a 0 or N/A etc... to tell you that it's off P.S. I just saw your eye tracking thread. I am sorry to see it. I have seen a thread months ago where a gentleman had a similar issue, one of the comments said that the condensation from sweat etc... got into the eye tracking circuit and wrecked havoc. One way to check is to take a photo and you should see the Quest Pro eye tracking stack light up. I hope it's just software related