AlpineGTA

Yes, I use only the trim hat, I don't move the stick. I manage to use autopilot levelling and the stick to get the probe aligned close enough that I only need small adjustments with the trim to catch the basket. I do not have the rudder mapped to the trim hat. I think I saw someone mention that they use the rudder to align horizontally because rolling also causes a change in altitude. I think that's true and I've noticed this when using the trim, because if I tap it just once horizontally I usually also have to tap it once or twice up to keep the same altitude.

Yes, that's the exact one I have.

No, it's still not working. I've just heard from my friend who tested it on his brand new system running a Ryzen 7 and Nvidia 3060 ti and it doesn't work for him either. So my next step is to collect my headset and send it back to HP for testing.

Yes, actually, thinking about it, I'll have to go back and check, but by the time I was at the basket I think the autopilot had disengaged anyway, it was just helping me to initially get steady and level with the tanker, but once I was there it was just tiny movements of trim and throttle, rather than the stick, to guide the probe into the basket. I also should also take another look at my curves, that's a good point.

I haven't tried refueling for months, I could never do it, but I thought I'd give it a quick try in the Hornet last night. I only fly in VR and I've always tried by using the often suggested method of not looking at the basket but at a fixed point in space and simply flying in formation with the tanker. But I discovered last night that actually in VR it's much easier to look at the basket, because you can see exactly where it is in 3D space. I used autopilot and RALT mode to fly formation with the tanker and use tiny movements of throttle and trim hat (no rudder) to hook the basket, all the while looking at the basket whilst making the adjustments. To my surprise I found it relatively easy to hook the basket using this method. I would say, if your control inputs are good enough, you can definitely refuel by looking at the basket if you're using VR. My biggest problems remain flying smoothly enough where I can even get close to the tanker to fly formation and staying in the basket once I am hooked. And I can't do it if the tanker is banking, only if it's flying straight and level.

Battle of Britain era Spitfire, Hurricane, Bf 109, Ju 87, Ju 88 and He 111, to make cohesive campaigns and missions. We already have the maps.

I can't even get WMR and SteamVR to run anymore because it just won't connect, I get constant USB errors.

Yes, that's definitely puzzling then. It just seemed to make sense, in my case, what the guy was telling me, but that doesn't mean it's the solution for everyone. As I said, I've lent my G2 to a friend to test and if he also has problems then it would seem to indicate it's an issue with the headset. It's frustrating not knowing what the exact problem is, I hope you find the issue and get it working. If you haven't already done so, it might be worth phoning HP support as I did. 1-800-334-5144 (for the US) They do seem to genuinely try to help you fix the problem. Edit: As a side note, my Quest 2 works perfectly at 90Hz on the same system, which surprised the HP guy, so maybe there's still the possibility it is the headset. I'll report back as soon as I hear my friend's tested it.

I had a lengthy phone conversation with HP support at the weekend (very helpful guy actually) and although on paper my PC specs appear to tick all the boxes - fairly new, powerful GPU, i7 CPU, USB 3.0 etc., in reality my PC is actually built upon an older Dell workstation that I upgraded. That means my i7 is only third gen, my Windows 10 is a free upgrade from Windows 7 and most importantly, the support guy reckoned, my motherboard is pretty old and is only booting a legacy BIOS, not UEFI and the last available update for it was 2018. Basically, this all means that my PC is only capable of running old USB protocols that just aren't up to what the G2 requires. It was working up to a point when I received a recent Windows update that meant it would no longer run on the old protocols and it's just not getting the speed of communication that it needs through the USB. He said that the G2 is really designed to run on the latest and newest hardware and USB protocols, preferably USB 3.1. He said that maybe changing my BIOS from legacy to UEFI might help but he didn't sound too confident. In the meantime, I've lent my G2 to a friend who's just bought a rand new Gaming PC, so if it works on that I can be pretty confident that my headset isn't defective and my problems are likely due to running on an older PC architecture. If that's the case, I'll be ok with that, just to know that my headset isn't defective, as I plan to upgrade anyway. So I would say to anyone who may be experiencing similar issues with black screens, problems connecting your headset and USB error codes, it might be something to consider. Even if you have a new GPU and USB 3.0, how old are the rest of your components? I'm sure it won't be the solution for everyone obviously, but something else to bear in mind. I hope this information might help others.

I don't know then, sorry.

I'm sure there are lots of people using the G2 very happily without any issues but I'm not one of them. From my experience I would find it hard to recommend the G2. After working perfectly, after a couple of weeks, without changing anything on my PC, it just stopped. I'm not sure it's specifically an AMD problem (I have an AMD GPU), because I've also seen reports of people with Nvidia GPUs having problems, I think it's more something to do with the USB connection. I've tried everything recommended on the internet, including a powered USB hub and add on PCI-E card but nothing has worked. I'm currently waiting on another PCI-E USB card that I've ordered, hoping that will finally fix it...

Have you got DCS as your window of focus? Alt+Tab and make sure you're on your DCS window, sometimes it's something as simple as that. Also Windows Mixed Reality can sort of hog the desktop and you have to Windows key+Y to regain desktop mouse control. Maybe it's that?

I think you'd be better off just buying a new SSD and transferring everything onto that. It made a big difference for me, not just in how the modules ran but everything is better, the boot up time of your PC and DCS loading times are dramatically faster. It you get a Samsung SSD, for example, they come with their own software that makes data transfer from your old drive really easy. Other brands might do also but I know the Samsung one I got definitely did.

So I spoke too soon. My G2 is not working at all now. I had it running for a few days in 60Hz mode, (it would no longer run in 90Hz mode at all), but I started getting the black screen again even in 60Hz until eventually it stopped working completely. I tried uninstalling and reinstalling Windows mixed reality again, a couple of times, but now when it runs through the initial setup and detects my hardware I get a tick mark next to everything except for USB 3.0+, that has a cross next to it and there's a message, "Can't run mixed reality". It's exactly the same hardware and USB ports as when I first got the G2 and it worked. Doing an internet search some people say using a powered USB hub or a USB PCI-E expansion card fixed their issues. I've bought and tried both a powered USB 3.0 hub and a PCI-E USB 3.0 expansion card, that includes a USB type C connection. I've tried them all, including every USB port already on my PC and I still get the cross next to the USB 3.0+ and "Can't run mixed reality" message. It seems to be a USB issue of some kind, or the headset is faulty. As soon as I plug in and power up the headset Windows Mixed Reality automatically starts up, so it knows the headset is there. Also, sometimes when I unplug and plug the headset into a USB port it crashes my PC. I'm all out of options and ideas to try now, if anyone has any suggestions? At this point I'm pretty cheesed off with it. I have a $650 door stop. All of the USB ports work perfectly fine with my Quest 2 btw. I plug that in and it just works!

A useful review, thanks.

Well it's less of an immersion killer than lifting your headset. And if one clickable kneeboard (sorry I originally read keyboard) could be designed that can be used on all aircraft, much like the current kneeboard is, then surely that's easier and less work than re-engineering all the different FC3 cockpits and it has the added bonus (as I've already said) of also being useful on aircraft that already have clickable cockpits. After all, real aircraft don't have F2, F3, F4, F10 or Esc etc. buttons so maybe it would be useful on all aircraft for accessing functions like those. It also seems to me to be less unrealistic than talking to your aircraft like it's KITT or something. I imagine some people are either uncomfortable with, don't like to, or are simply unable to use voice commands, so what's wrong, if it's feasible, with offering another alternative and giving people more choice and options? So it's not something I would call a waste of time immersion killer but something that's seriously worth considering and if the idea's to be dismissed it should be dismissed with sound reasoning.

Sounds like a good idea to me. It would actually also be useful for full clickable cockpits, being able to quickly pull up a virtual keyboard to click those odd keys that you don't have bound to your HOTAS, instead of having to lift your headset or fumble around for the keyboard.

I'm happy to say I have it working again. I tried uninstalling Windows Mixed Reality for Steam VR, which it doesn't seem to let you do but I clicked on the uninstall button in Windows apps anyway, then disconnected and reconnected the headset power. I then got an error that the headset couldn't run in 90Hz mode, I went into Window mixed reality settings changed the headset to optimized for performance, changed it to 60Hz then back to 90Hz. I put the headset back on and the picture was perfect, no more snowy flickering or screen blacking out and I've just done a couple of hours in DCS with no issues. So basically I just messed around with the Windows mixed reality software. Whether it was the messing with the settings or trying to uninstall and restart it that fixed it, I don't know, but it seems it was to do with the software being a bit glitchy.

I tried those suggestions but it didn't work unfortunately. And the issue seems to be getting worse. Maybe I have a faulty headset.

I'll take a look at it, thanks.

After working fine until now, my G2 has started to randomly go black inside the headset. There's no light coming from the lenses at all, like the screen is completely turned off. I can still see DCS running on the desktop and responding to movements from the headset and I can still hear sound but no image at all inside the headset. Sometimes it'll come back on again, but then randomly go black again but sometimes it just won't come on at all. I've also noticed that when I do have a display I can see tiny snowy specs of light and horizontal lines, like a snowy tv interference but very subtle. I never used to see that, the picture used to be perfectly clear. It only started this week after the latest DCS patch but also about the same time I installed an AMD GPU driver update for my 5700 XT. At first I wondered if it was the DCS update but I'm also getting a black screen in MSFS2020 and the snowy interference even when I'm just in the Windows mixed reality house or Steam VR lodge. A quick internet search revealed other people with the black screen issue over the last couple of months (no mention of the snowy specs) and they all seemed to be using AMD GPUs but an AMD update seemed to have fixed it looking at the notes for one of their past driver updates. I'm wondering if the issue has returned with the latest AMD driver. I'm hoping AMD will quickly release another update that will fix it and my headset hasn't suddenly gone faulty. I'm thinking of lending it to a friend who's running an Nvidia 3060 Ti to see if it runs fine for him. At least then I'll know the headset isn't defective. I'm just curious, is anyone else running an AMD card with their G2 and experiencing similar issues? As soon as graphics cards are back in stock I want to upgrade to Nvidia. People seem to haver fewer issues with those.

Nice tip, thanks. I'll give that a try too.

I was just going to post... does anyone else think the scroll wheel on their trackball mouse very slow when using it to rotate knobs, especially compared to when using the thumb stick on a VR controller? For example, with a VR thumb stick I can spin a lighting knob very fast but it takes an age with the mouse wheel... But then I look down at my mouse and for the first time notice there's a 'Low/High' switch above the wheel! mmm... I wonder if the high setting will make it spin faster - immediately goes off to try...

I hadn't thought about the hand position not changing when using a rail before, I think it's a very good point. I'm currently used to using a TWS rail throttle so I think I will be holding out for the VKB rail version too. As for modern jets using tilt throttles, not all do, I believe the upcoming Eurofighter Typhoon uses a rail, to name but one?

I have a trackball mouse next to my throttle. I can easy find it when I'm in VR. It takes a bit of getting used to, especially if you're right handed, but it works pretty well and having a left handed one next to the throttle means you can keep your hand on the stick.