sohei

The shell_table.lua script referenced earlier in this thread appears to have disappeared now, presumably replaced with a similar file. I'm not having much luck finding what that might be. Does anyone have any idea where this data is now located?

My motherboard is probably a bit older with lower bandwidth ports. I'll check that. The card has 10Gbps ports so that's probably what's helped, along with the dedicated power from the PSU. It's definitely made a significant improvement.

TO ANYONE HAVING RANDOM ISSUES WITH FLICKERING, TRACKING DISCONNECTS, performance issues : I've just connected the headset to a powered StarTech PCI-E USB 3.1 card and it has made a very significant improvement in terms of stability. For the first time the headset tracks in every direction smoothly (before it was basically a matter of luck as to whether it would work fully), the disconnects and flickering seem to be totally eliminated based on the last 30 minutes of flying. overall performance is much better now. I can't recommend this addition highly enough. For the sake of another £30 or $30 I think you'll have a MUCH more enjoyable VR experience.

It's already in my library so it must have been a black ops install when I installed steamVR.

I suspect the SteamVR wmr app is probably not required tbh. Just native wmr and steamvr is most likely adequate.

Yeah I've got steamvr, but not wmr for steamvr, just the version that comes with Windows. Seems to run OK.

Well I've got steamvr and wmr installed and dcs runs on the reverb fine. I just want to clarify if 'steamvr wmr' is necessary and offers any improvement?

I haven't installed steamVR WMR up to this point? Does it make a significant difference to just using steam VR and the standard WMR? Do I need to do anything specific to set it up?

Noooooo! I've just ordered the startech card! :( To be fair it's also a 3.1 card with direct SATA connection from the PSU so it will probably do just fine.

Thanks, I'll consider that!

Perhaps it would work to use a 3rd party USB card to offload all the OTHER USB devices and hopefully free up juice (technical term) for the Reverb. Would you mind giving that a go at some point if you haven't already? I totes agree about the cable. It's a lot more stable now I've captured the connector in a loop secured to the headset strap.

@hansangb and @tinkickef Yes, I think you're right about this. I've experimented with having my main light on and it seems to coincide with an improvement in tracking. I was hoping the LED lights in front of me around my window might be enough for the Reverb to be able to track but I guess not.

I still have quite a lot of trouble with getting the Reverb to track my head movements in the cockpit. Rotating (looking around) works fine, but tracking backwards and forwards, laterally etc seems to be really finicky. Most times I start up DCS it just won't work but springs into life later on, usually propelling my ten feet above my cockpit so I have to recentre myself. It's very frustrating. Does anyone have any insight as to the nature of this problem?

Hi Everyone I'm in the process of setting up VAICOM and it's been a smooth process up the point where I assign my joysticks in the options for VoiceAttack. For some reason VoiceAttack doesn't want to recognise any input from my Thrustmaster Warthog Throttle. If I click on the 'test' button it just shows 'waiting' if I have the throttle assigned, regardless of what I press. The Thrustmaster joystick, and my Xbox controller are recognised and work just fine. However if I assign the throttle along with any other input device then VoiceAttack once again fails to recognise any input. The throttle has given me no problems in its normal operation. I've tried moving it to a different port, and I've tried with my HP Reverb disconnected as well, with no luck. Does anyone have any suggestions as to what the problem might be? Many thanks in advance. EDIT : Ha, fixed it already. If anyone has a similar problem, please consider the following tip to resolve : "Trouble is likely that some of the toggle switches on the Warthog throttle is set to on! Go to "Game Controllers > Properties" and ensure that none of the buttons are lit up. I imagine it's neccesary to do that for all controllers connected, or VA gets confused." https://forum.voiceattack.com/SMF?topic=1949.0

You'll need steamVR, but you DON'T need DCS purchased within Steam. I run the DCS openBeta and it's fine. You just need to make sure that steamVR is running.

According to my measurements : W = 165 mm D = 93 mm H = 80 mm

I think you may have a point about the cable connector. I noticed that just a slight pressure on that connector causes flickering, so it could well also cause a reconnect. I'll do the same. Also I moved my various devices around so that the USB 3.0 ports were freed up as much as possible other than for the headset. It's a bit early to be certain but it does seem to be more stable now.

Yeah it's puzzling. If anything I've been pretty thrilled how much better the performance is with the Reverb than it was with the Rift, although the 2.5.5 update could be a significant factor here as well.

No, I'm on a i7-4790K. Seems to work ok overall. Yes there has been the occasional blip but I also improved things quite a lot by making this change to the ASMedia USB 3.0 extensible host controller (where they change to an MS driver). Perhaps that could help. https://forums.hololens.com/discussion/9650/mixed-reality-will-not-recognize-my-usb-3-0-or-3-1-ports

The headphones are the weakest component by a mile tbh. I removed them after half an hour. I'm puzzled that you're experiencing issues at ground level. I've been really pleased with it. Could just be that I have lower standards.

Thanks for the input everyone. I'll play around with USB connections to see if it helps.

Hi everyone I've noticed with both the Rift CV1 and the Reverb that occasionally when I fire up DCS the head tracking isn't working fully for VR. What I mean is that I can look around and tilt my head but I can't move laterally, up/down or forwards and backwards. If I make any of these movements the cockpit just moves with me. Fixing it seems to be a bit trial and error. A restart of the PC can work, and on one occasion in the F14 it just randomly fixed itself. I've also experienced this in the A10 Does anyone have any idea what causes this and what can fix it? It's a bit frustrating to fire up a mission only to find I can't move fully in my cockpit. This doesn't happen huge amount but it spoils the experience when it does occur, especially when I'm all primed for a larger mission! Any help appreciated. Thanks in advance!

Might be best to stick to your guns and wait it out at this stage. Who knows what stock is going where right now. I ordered the consumer edition but they shipped the pro version, and that was ordering direct from hp

Yeah the performance with the reverb is absolutely fine. Low level flying over the caucasus map with dense forest in the f14 is really smooth. I have no complaints

I'm 1803 version of Windows and quite happy with the clarity of the image. For the first time in VR spotting an aircraft without relying on a labels patch is now actually possible. Makes A/A combat sooo much more enjoyable!