You know what my Oculus Quest 2 setup needs? More weird controller attachments

When I think of controller attachments, I instantly imagine the crappy Wii remote add-ons I had as a kid. 

At first, I loved them – I wouldn’t touch Wii Sports unless my controller looked like a tennis racket or golf club – but over time, I came to despise them. The cheap plastic constructions would always break after a few uses, and they objectively made playing games harder because they’d block the sensor on the end of the remote.

I’ve recently had the chance to try out the HelloReal Grip-to-putter with my Oculus Quest 2 and Meta Quest Pro VR headsets, and it’s reopened my eyes to the immersion that accessories can bring to virtual reality – whether it’s gaming, working out, or just plain working.

My Grip-to-putter thoughts 

The HelloReal Grip-to-putter is a golf club controller attachment and the perfect companion for Walkabout Mini Golf – one of my favorite VR experiences

The HelloReal Grip-to-putter with an oculus quest 2 on one end and a colorful grip at the other

(Image credit: Future)

You slot your Quest 2 or Quest Pro controller into the open end where it sits snuggly – for additional assurance that your handset won’t fly off when you swing the club HelloReal has included instructions on securing it using the controller’s wrist straps. Once it’s in place you can boot up your favorite VR golfing app and enjoy swinging a club that feels much more like the real thing than your controller ever did.

The Grip-to-putter gets its name from the grip-to-putt feature in Walkabout Mini Golf. When this setting is switched on in the app’s menu your club’s end will vanish until you hold down the side grip button on the controller. This lets you get a few practice swings without the risk of accidentally hitting your virtual ball before you’re ready. 

HelloReal’s attachment includes a contraption that will hold down the controller’s grip button when you press the trigger that sits just above the padded end. While playing Walkabout with the putter took a little getting used to – because the mechanics are a bit different with the add-on – I found that it made the whole experience significantly more immersive.

Have to feel to believe 

As you can see from the images included above, the HelloReal putter looks nothing like a golf club beyond the fact it’s vaguely pole shaped. But it doesn’t matter what the add-on looks like, just what it feels like – and HelloReal has got the golf club feeling down to a tee. The padded grip and weight distribution of the putter are perfect. 

A closeup of the HelloReal Grip-to-putter with an Oculus Quest 2 attached and a black claw pressing down the grip button

(Image credit: Future)

Once I slipped my headset on, I fully believed I was holding a real golf club. And this got me thinking – I need more realistic feeling VR accessories to use at home.

Inspired by the Wii’s heyday, I can already imagine some of the VR gaming accessories I could get, such as attachments that mimic the feel of swords and axes or sporting-inspired add-ons for VR fishing and tennis.

For the VR fitness fans out there, wouldn’t it be great to get a weighted club attachment that makes your Supernatural workout a little tougher? Maybe someday, we could get a boxing glove-inspired accessory that brings Litesport VR and other boxing workouts to life.

While working in the metaverse, perhaps we could use blank slates and styluses that make us believe we’re writing on paper when taking virtual notes. OK, this add-on is a little bleak, but if metaverse working is inevitable, it might make it more enjoyable than I found it before – I much prefer traditional pen and paper to using a keyboard. It would also feel more real than the controller styluses Meta includes in the Quest Pro’s box, which enable you to write in VR, albeit clunkily. If you didn’t realize the styluses were in the box, it might be because they’re tiny and exceptionally easy to lose.

Cost and effect 

These sorts of realism-boosting accessories are already deployed by commercial VR experiences you can find in some malls and theme parks to great effect – but they do admittedly have a downside if you want to bring them home. Cost.

A VR playter running around on an Omni One VR treadmill

The Omni One VR treadmill is a next-level VR accessory (Image credit: Virtuix)

Different add-ons have different prices, with gadgets like the Omni One VR treadmill at the ‘ridiculous’ (over $ 2,500, around £2,000 / AU$ 3,900) end, and accessories like the Grip-to-putter at a more reasonable $ 58.99 (around £46 / AU$ 91). Admittedly, $ 58.99 still isn’t ‘cheap’, but if you plan to use your VR accessory a lot, you'll likely feel it offers solid bang for your buck. 

So if you are a VR power user – or even just pick it up once a week – and have been weighing up buying a few accessories for it, then I’d say go for it (provided they’re good quality). Burnt by the Wii, I’d been instantly dismissing every add-on as a gimmick, but after trying the HelloReal putter, I’ve been scouring the internet for other weird goodies I could pick up to improve my VR setup.

You might also like

TechRadar – All the latest technology news

Read More

Windows 11 suffers from a weird bug that messes with SATA SSDs and hard drives

Microsoft has confirmed that Windows 11 users are also experiencing an odd bug with SATA hard drives that has already been witnessed plaguing Windows 10 (and indeed Windows 8.1 and 7).

Neowin reports that Microsoft let us know this problem affects Windows 11 via a support document that discusses the glitch, and advises users what can be done about it.

The bug causes an internal SATA drive – this can affect both hard drives and SSDs that are installed inside your PC via a SATA connection – to be detected as removable media in the Windows taskbar, as opposed to a permanently attached drive (which, of course, it very much is).

Microsoft explains: “Whether or not a device is considered removable is determined by your system’s BIOS and how it marks the various SATA ports on the motherboard.

“The inbox driver directly inspects SATA ports and considers devices connected to those ports marked ‘external’ as removable devices. Not all storage drivers do this, which can be a potential cause for corruption or data loss.”


Analysis: A fix is available, fortunately

The good news here is that many modern systems won’t be affected by the bug, as most SSDs these days aren’t SATA – and hard drives are a piece of tech that’s on the way out, and very much doing a vanishing act.

Still, that’s not to say that there aren’t plenty of PCs out there with a SATA drive in them, even if only an old hard drive recruited into the mix for media storage duties, say.

The good news is that Microsoft provides the details of a fix in the support document. As Microsoft advises, the first thing to do is to check for a BIOS update for your motherboard. If you haven’t got the latest version, update it, and keep your fingers crossed that this may solve the issue.

If it doesn’t, or you’re already on the newest BIOS – don’t flirt with installing any beta BIOS, by the way, it’s just not worth the risk – then Microsoft outlines instructions for manually dealing with the problem here.

Note that you will have to enter a lengthy command (which pretty much looks like gobbledegook) so make sure you get this right. It’s a touch fiddly, and involves tinkering with the Registry, so a mistyped mistake could be bad news – just be very careful you type in exactly what Microsoft says in the final step (for Windows 8 or later, which obviously includes Windows 11 users).

TechRadar – All the latest technology news

Read More

Nvidia fixes a weird GPU driver bug that tanked CPU performance

Nvidia’s GPU driver was recently found to have a bug that was spiking processor usage after quitting out of a game, but the good news is this problem has been fixed in a freshly released hotfix.

Neowin reports that the affected GeForce driver version, 531.18, now has a hotfix (531.26), and it cures two issues including the gremlin that was eating CPU resources.

This was an odd bug which saw an Nvidia Container process hang around after you’d stopped playing a game and exited. Going into Task Manager, gamers were seeing CPU resources being eaten up to the tune of 10% or even 15%, causing some slowdown to the host gaming PC.

If you didn’t open Task Manager and notice this process, then manually close it, your machine could run rather sluggishly and you’d have no idea why.

Still, the cure has arrived now, and if you were holding off updating to version 531.18 due to the presence of this bug, you can now go ahead.


Analysis: Notebook crashing blues also fixed

This fix has been deployed quickly, which is good to see. Nvidia chose the route of a hotfix because that can be pushed out immediately to those with GeForce graphics cards, rather than having to wait for a cure bundled with the next version of Team Green’s graphics driver.

The hotfix also comes packing a resolution for a second problem. Namely a random crash (stop error) happening with some laptops that have GeForce GTX 10 Series, or MX 250 / MX 350 mobile GPUs.

Both of these are quite nasty little glitches, so it’s good to see them stamped out by Nvidia in a swift manner. Indeed, because there was apparently some noticeable slowdown evident with the persisting Nvidia Container bug, slightly more paranoid types may even have wondered if something had happened malware-wise, as sudden system slowdown or lack of responsiveness can be a symptom of infection – so they may have worried unduly.

TechRadar – All the latest technology news

Read More

Windows 11 updates are failing to install with this weird error

Windows 11 users are reporting some installation failures when trying to update the OS, with an uninformative error not throwing much light on the cause of the apparent problem – although it’s an issue that Microsoft is ‘closely monitoring’.

Windows Latest reports that an error code 0xc1900101 is being produced for some folks when trying to update, and the operating system then rolls back to the previous build with no further details on the cause of the issue being provided.

This is apparently happening mostly with preview builds of Windows 11, and other error codes have been witnessed as well, Windows Latest notes, but the aforementioned one is the most commonly seen and reported on Microsoft’s Feedback Hub.

One user posted to the Hub: “All my physical machines updated ok, but on a virtual machine running either Hyper-V, VMWare, or VirtualBox, it almost gets to the end of the update, and then rolls back. Worse, on VMWare and VirtualBox, the virtual machine software crashes at the end of the update.”

Another observed: “Mine has the same problem. The first time I update the pc to the latest build it showed an error about my graphics driver so it rolled back. I was suspecting that the windows update corrupted my graphic driver as after rolling back my graphics card was not working, it just works after I reinstall driver. I reinstall the update later and it was a success.”

Microsoft has confirmed that it knows about the error which it describes as a ‘generic’ failure and an area that the company is watching closely.

Microsoft advised one affected user: “Thanks for taking the time to report this – error code 0xc1900101 is a generic error displayed when an update fails and rolls back for some reason. This is an area we monitor closely and can have different root causes depending on which build you were attempting to upgrade to and your setup.”

No firm advice was given, then, as to how someone might get around this gremlin in the works, but Microsoft does say that users should try updating to the very latest preview build (if they were attempting to upgrade to a previous version, of course).


Analysis: Some possible workarounds, but the waiting game might be best

There are various theories about the cause of this – and similar – update failure errors, including suggestions of app compatibility or driver issues (as we saw above), or even low disk space. But as Microsoft mentions, this is a ‘generic’ error and one which could have a number of different causes.

If you encounter this problem, aside from making sure you are attempting to install the very latest build, there are a few things you can try. It certainly won’t hurt to ensure that you aren’t running low on drive space, and maybe run a disk clean (it’s a good idea to do this periodically anyway). Also, we’ve seen another user report that disabling their antivirus resolved the installation failure of a recent preview build, and there are some further suggestions of potential action to take in this thread from the Microsoft Tech Community.

What’s also worth noting here is that this error has been a problem in the past, for example with Windows 11 preview build 22504 (back in November 2021). At the time, Microsoft’s advice was that users “may want to pause updates until we release a fix”, although in the past Microsoft has also said that those encountering this error code with Windows 10 should try to install the update again after a clean boot (find instructions here – and interestingly as observed above, another potential mitigation mentioned is to disable your antivirus temporarily).

In short, while you may get some joy from the potential solutions floated in the links above, your best bet might be to simply wait for the issue to resolve itself, providing you don’t have an urgent need to get the update in question up and running.

TechRadar – All the latest technology news

Read More

Windows 11 updates are failing to install with this weird error

Windows 11 users are reporting some installation failures when trying to update the OS, with an uninformative error not throwing much light on the cause of the apparent problem – although it’s an issue that Microsoft is ‘closely monitoring’.

Windows Latest reports that an error code 0xc1900101 is being produced for some folks when trying to update, and the operating system then rolls back to the previous build with no further details on the cause of the issue being provided.

This is apparently happening mostly with preview builds of Windows 11, and other error codes have been witnessed as well, Windows Latest notes, but the aforementioned one is the most commonly seen and reported on Microsoft’s Feedback Hub.

One user posted to the Hub: “All my physical machines updated ok, but on a virtual machine running either Hyper-V, VMWare, or VirtualBox, it almost gets to the end of the update, and then rolls back. Worse, on VMWare and VirtualBox, the virtual machine software crashes at the end of the update.”

Another observed: “Mine has the same problem. The first time I update the pc to the latest build it showed an error about my graphics driver so it rolled back. I was suspecting that the windows update corrupted my graphic driver as after rolling back my graphics card was not working, it just works after I reinstall driver. I reinstall the update later and it was a success.”

Microsoft has confirmed that it knows about the error which it describes as a ‘generic’ failure and an area that the company is watching closely.

Microsoft advised one affected user: “Thanks for taking the time to report this – error code 0xc1900101 is a generic error displayed when an update fails and rolls back for some reason. This is an area we monitor closely and can have different root causes depending on which build you were attempting to upgrade to and your setup.”

No firm advice was given, then, as to how someone might get around this gremlin in the works, but Microsoft does say that users should try updating to the very latest preview build (if they were attempting to upgrade to a previous version, of course).


Analysis: Some possible workarounds, but the waiting game might be best

There are various theories about the cause of this – and similar – update failure errors, including suggestions of app compatibility or driver issues (as we saw above), or even low disk space. But as Microsoft mentions, this is a ‘generic’ error and one which could have a number of different causes.

If you encounter this problem, aside from making sure you are attempting to install the very latest build, there are a few things you can try. It certainly won’t hurt to ensure that you aren’t running low on drive space, and maybe run a disk clean (it’s a good idea to do this periodically anyway). Also, we’ve seen another user report that disabling their antivirus resolved the installation failure of a recent preview build, and there are some further suggestions of potential action to take in this thread from the Microsoft Tech Community.

What’s also worth noting here is that this error has been a problem in the past, for example with Windows 11 preview build 22504 (back in November 2021). At the time, Microsoft’s advice was that users “may want to pause updates until we release a fix”, although in the past Microsoft has also said that those encountering this error code with Windows 10 should try to install the update again after a clean boot (find instructions here – and interestingly as observed above, another potential mitigation mentioned is to disable your antivirus temporarily).

In short, while you may get some joy from the potential solutions floated in the links above, your best bet might be to simply wait for the issue to resolve itself, providing you don’t have an urgent need to get the update in question up and running.

TechRadar – All the latest technology news

Read More