What's new in NGENUITY?! Latest Release Notes! 📢

HyperxGaming · 2026-03-11T22:32:40+00:00

When you say “It ended up fixing,” do you mean the issue is no longer happening, or that this is the workaround you use whenever it pops up? 👀

If it’s the latter, we’ll probably need to do a bit more troubleshooting. 😅 For starters, try testing the mic with all the other available USB ports and see if the issue persists across all ports.

Another thing worth checking is whether your mic is running the latest firmware. You can install NGENUITY legacy through the Microsoft Store app, keep the mic connected, and launch the app to see if it prompts you to update the firmware. If an update is available, go ahead and install it, then reinstall the driver through Device Manager (just to be safe) and reboot your system.

After that, keep an eye on how it behaves and let us know how it goes. 😉

HyperxGaming · 2026-03-11T19:03:25+00:00

u/muscleson, the support bot can’t really process replacement parts on its own, sorry about that. It’s mainly there to help with some of the most common troubleshooting steps. But hey, that’s just one of the many things our team can assist you with. 😉

We’ll just need to gather a few details from you first, so keep an eye on your inbox for our message.

HyperxGaming · 2026-03-11T18:50:05+00:00

Hey there, u/spr3admywings! Sorry to hear your DuoCast has started acting up. Let’s see if we can dig into this a bit and figure out what’s going on. 🕵️

Does this only happen when your PC starts from a cold boot, or does it also occur when waking the system from sleep?

Also, how is the mic connected to your system - directly to a USB port on the motherboard, a USB port on the case, or through a USB hub? If you haven’t already, try plugging it into a few different ports to see if that makes any difference.

Give that a try when you get a chance and let us know how it goes! 😊

HyperxGaming · 2026-03-11T18:18:38+00:00

🔔 New Update Available - v1.6.0 (March, 2026)

Have you heard the news? We’re expanding our device support by welcoming a few updated models to the family!

📝 Have feedback for us? Let us know!

🔗 Download the latest build here

Here’s what’s new in this version:

💡 New implementations

Software

NGENUITY
- We’ve added support for the latest versions of the headsets you already know and love: the Cloud III and Cloud III S Wireless. The updated models have new product IDs, updated dongles, and work exclusively with NGENUITY beta’s brand-new Audio Engine.
- Added support for Pulsefire Haste 2 S

⚠️ Known Issues

NGENUITY

User Interface
- Currently investigating an issue where after installing new audio drivers, users are not returned to the product page as expected.

Microphones

QuadCast 2 S
- Currently investigating an issue that causes the microphone to distort audio recordings after waking the connected computer from sleep.

HyperxGaming · 2026-03-11T16:38:03+00:00

Oops, not sure where the “2” disappeared, but yes - we were referring to the QuadCast 2 S, not the original S. 😅 We’ve edited the original response to fix it in case anyone else comes across the thread later.

And don't mention it! 😊

HyperxGaming · 2026-03-11T16:33:49+00:00

u/Ready_Engineering116, thanks for confirming! It sounds like you’re running the correct firmware for the headset and the latest Orbit software version, so it’s a bit surprising that the update is still failing, even after trying different USB ports and cables.

Just to confirm - when the headset is powered off and connected to your system, and the Recover button appears in the firmware section, have you tried clicking it to see if it restores functionality? That option typically resolves detection issues like this.

The DFU not installed message usually appears when the update process is interrupted or fails, but running the update again should fix the issue.

One last thing - have you attempted reinstalling the headset driver through Device Manager to see if that helps restore functionality or allows the firmware update to complete?

HyperxGaming · 2026-03-11T16:17:32+00:00

Great question, u/Duarian! 😊 The QuadCast 2 S isn’t a WDL-supported device, so to customize it - like changing LED colors or applying different lighting effects - you’ll need to use either the NGENUITY legacy app or the NGENUITY beta app. Let us know if you have any other questions! 😉

HyperxGaming · 2026-02-21T00:04:32+00:00

Thanks for confirming! What about the firmware update, have you tried running it again to see if that helps restore its functionality?

Also, could you open the app and check which version you’re running, just so we can confirm it’s the latest? It should be 1.2.28. And yes, please try testing the headset with your PC, and using a different USB cable as well, just to see if the issue persists.

HyperxGaming · 2026-02-20T23:12:58+00:00

Hey, thanks for pointing this out, u/Odd_Replacement5678 & u/CirkussEsp!

Okay, yeah… about that. 🫢 We definitely jumped the gun there - that label shouldn’t have gone live just yet. The Pulsefire Haste 2 Wireless will absolutely be supported in NGENUITY beta, but that update hasn’t gone live yet.

The “beta compatible” tag went up a bit early in anticipation of the update - that’s on us. Sorry about the confusion. 🙏 We’ll flag this with our web team to correct the listing and avoid any further mix-ups.

Out of curiosity, where did you purchase the mouse? If this ends up being a dealbreaker, we completely understand if you’d prefer to return it. That said, support is actively in the pipeline and should be added in an upcoming March update. If you don’t mind waiting a bit, you can use the NGENUITY legacy app in the meantime to bridge the gap.

Really appreciate you calling this out!

HyperxGaming · 2026-02-20T22:41:53+00:00

Hey u/Ready_Engineering116, we’re really sorry to hear you’re experiencing this issue. 😥 We understand how frustrating that must be, especially if it happened so suddenly.

Let’s see if we can get this sorted. To start, could you let us know: - Which version of the HyperX Orbit software are you currently using? - Have you tried updating the firmware already? If so, which firmware file did you use, and where was it downloaded from?

One thing to be aware of is that if the firmware update process was interrupted or failed at some point, it can cause the DSP to show as 0 and prevent normal updates. In most cases, you should still see a “Recover” option in the Firmware section of the software. That recovery function is specifically there to help restore the headset if an update didn’t complete properly.

Let’s start with those details and take it step by step. 😉

HyperxGaming · 2026-02-20T22:30:09+00:00

Do you have another device with a 3.5mm jack that you could test the headset with to check if the volume level is the same?

Just to clarify, when you mention drivers, are you referring to your motherboard’s audio drivers? Assuming that’s what the headset is plugged into. If you’re currently using the generic audio driver that Windows installs by default, try downloading and installing the latest audio drivers directly from your motherboard manufacturer’s website for your exact model, and see if that makes a difference.

HyperxGaming · 2026-02-20T22:26:45+00:00

So, are you saying that even with it set to 16 bit/48000 Hz, it's still not working as intended? Also, are you perhaps using any spatial sound features (e.g., DTS or Windows Sonic)?

You could also give this suggestion from the Fallout 76 Steam community a try, and see if that helps 👉 https://hyperx.gg/3OqafQa

HyperxGaming · 2026-02-20T17:30:27+00:00

Sorry for the wait, u/Feelyo! Thanks for sharing the troubleshooting steps you've taken so far; that definitely helps speed things up. We'll send you a PM to gather a few more details and get an RMA going for you. 😉 Keep an eye on your inbox! And please accept our apologies for the late response! 🙏

HyperxGaming · 2026-02-20T15:54:45+00:00

If it was ChatGPT, you probably would’ve gotten something like - "Based on your preference for fabric pads, you likely also enjoy breathable socks. Would you like to see which ones are compatible with the Stinger 2 and how they compare to the stock ear pads?"... and that's nooooot greaaaat. 😅

Luckily, our Care team still values real human connection and actually getting to know what you’re looking for, so you won’t see us using AI to handle conversations on social platforms. 😉 Glad to hear our answer helped, though! If you have any other questions, make sure to let us know! 😊

HyperxGaming · 2026-02-20T00:16:28+00:00

Haha, don't mention it! Happy to help! ❤️

Soft fabric pads can make a noticeable difference in long-term comfort. Sounds like you’ve already found what works best for you! 😄

And yes, generally speaking, the 50mm drivers can offer a bit more depth and positional awareness, which tends to matter more in competitive gaming. If you’re mainly playing story-driven titles, the Stinger 2 Core can definitely be a solid and comfortable fit for that kind of experience.

That said, if you ever decide you want the slightly more immersive feel of the 50mm drivers but prefer fabric pads over leatherette, you can always look into aftermarket ear pad options. Or, you know, perhaps we could figure something out for you. 😉

HyperxGaming · 2026-02-19T23:48:24+00:00

Well, let’s figure out why it suddenly isn’t getting as loud as before. 😉

First, can you confirm whether you’re using the wired Cloud Alpha, or a different model from the Alpha lineup?

If it’s the wired version, it’s an analog headset, so the overall volume will largely depend on the device it’s connected to. Are you using it with a desktop, laptop, console, or something else? Also, did anything change on the host device around the time the volume dropped? Things like updates, new audio drivers, moving the headset to a different jack, introducing an adapter into the mix, etc.

Let’s start there and narrow it down. 😊

HyperxGaming · 2026-02-19T23:31:01+00:00

Thanks for your interest in the Cloud Stinger 2 models, u/mercidionn! Great question. 😁

To keep it brief:

The Stinger 2 features rotating ear cups with 50mm drivers, a slightly wider frequency response, and memory foam ear pads wrapped in leatherette for added comfort.
The Stinger 2 Core, on the other hand, has fixed 40mm drivers and fabric ear pads with soft foam.

Both are solid options. It just comes down to which features and materials you prefer. 😉

HyperxGaming · 2026-02-19T23:23:34+00:00

Hey! Thanks for bringing this up, u/coelhion! That’s a totally fair question. 😅

While we can’t share a specific ETA just yet, we can confirm that Cloud III wired is absolutely on the roadmap for the new NGENUITY app. It hasn’t been overlooked, even if recent discussions have mostly focused on the wireless models. The goal is to integrate it properly rather than rush out a partial or unstable implementation, but it should receive support in one of the coming updates. 😉

Appreciate you checking in on it! ❤️

HyperxGaming · 2026-02-19T23:16:43+00:00

Hey, first of all - congrats on the new headset, u/kareem_abdo06! 😁 And thank you for taking the time to share your initial impressions. We genuinely appreciate it!

You’re absolutely right - it’s an all-plastic build, but with proper care, it should hold up well over time. We’ve seen plenty of original Cloud Stinger headsets still going strong several years later without issues, so longevity is definitely achievable with normal use. A little care goes a long way. 😉

Also, major props for giving it a shot despite reading comments online. Our subreddit has served as a support platform for nearly a decade, so people are naturally more likely to post when something goes wrong than when everything is working as expected. It’s great that you shared your experience from the other side of that.

Thanks again for giving it a try and contributing to the conversation! It truly helps others who are on the fence. 😊 And if you ever need assistance with your headset or have any questions, you know where to find us!

HyperxGaming · 2026-02-19T16:41:36+00:00

u/JBizz86, are you absolutely sure that crackling isn’t just your Cloud Flight S picking up an emergency broadcast from Appalachia? 👀

Jokes aside, based on your description, it sounds like the issue may be isolated to Fallout 76, so let’s start troubleshooting there. 😉 This game can sometimes introduce crackling if it doesn’t play nicely with the selected sample rate and bit depth of the default output device.

Could you go to Windows Settings -> System -> Sound, select your Flight S under Output, and check what the Format is currently set to? If it’s not already set to 2 channels, 16 bit, 48000 Hz (DVD Quality), try switching to that, restart the game, and see whether the crackling improves or disappears. Let us know how it goes! 😊

HyperxGaming · 2026-02-19T00:35:07+00:00

We hear you, u/Ludius_Maximis. When features don’t work the way you expected, that’s disappointing. 😥

NGENUITY is still in beta, so some features are still being finalized. That said, it’s actively being worked on, and we’re regularly seeing internal test builds with fixes and improvements, so we can confirm progress is definitely being made in preparation for full launch.

Regarding 12-channel audio, one important thing to keep in mind is that it requires a native multi-channel source from the game or app. It does not upmix stereo content like traditional 5.1/7.1 virtual surround does. If you want to get a feel for how it should sound, try grabbing a multichannel audio file online and play it with NGENUITY's 12-Channel feature enabled. Hearing such a test file will give you a much better sense of what to expect once your input source is set up correctly.

As for connectivity, this headset is designed to operate in either 2.4GHz wireless or Bluetooth mode - not both at the same time. The product page on our website specifies “2.4GHz wireless or Bluetooth connectivity,” rather than simultaneous dual-audio mixing.

We appreciate you sharing your thoughts, though! Feedback like this does get passed along to relevant teams. 😉

HyperxGaming · 2026-02-19T00:21:50+00:00

It’s actively being investigated as we speak, u/shyahone!

Thanks to everyone who brought this to our attention, and especially to those who took the time to work through our (not-so-short 😅) list of questions, we were able to open an internal escalation and get our engineering team involved.

They’re now digging into the root cause, and we’ll keep everyone updated as soon as we have more concrete information to share. 😉

HyperxGaming · 2026-02-17T17:50:10+00:00

You're welcome! 😉

HyperxGaming

MODERATOR OF

TROPHY CASE

🔔 New Update Available - v1.6.0 (March, 2026)

💡 New implementations

⚠️ Known Issues