Tinkickef

Bumped back up the thread because it seems that a new batch of reverb and potential reverb owners are not aware of this essential mod.

It has its own thread.. I will bump it back up from page two for those that missed it. It is absolutely essential to avoid disconnects. https://forums.eagle.ru/showthread.php?t=242827

For the sake of clarity for those with flickering problems. I fitted two inantek expansion cards to my PC for Rift. Reason for two is that I wanted three separate usb controllers, one on MB, and one on each card. Rift plugged into expansion card one, Sensors plugged into card two and Hog HOTAS plugged into MB via a self powered hub with its own 36w power supply. Other peripherals such as fingerprint reader, laser printer ect, pretty much shared between the two cards as they are not in constant use. The cards are separately connected directly to the 5v rail on my PSU. The cards I have and not had any problems with flickering / grey out are these: https://www.amazon.co.uk/gp/product/B00B6ZCNGM/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

:cry: If you have the F14, take a look at the climb indicator. Lean forward may be 20cm from your normal seated position and read the "climb x1000" text on the dial. This is the resolution Reverb is giving. You cannot quite read that small text from seated normally, but you can if you lean forward slightly. All the placards in the cockpit, including landing checklist are perfectly clear, apart from the caution panel lights. They are problematic.

Agreed. I have not noticed any diminished 3D effect in the Reverb. Everything is still just as gnarly in the verb as in the rift and it was something I deliberately looked for once I got it running. Either the reports are false, or they have not got their IPD set up correctly. I measured my IPD very carefully on Sunday and repeatedly got 65mm. Rift IPD adjustment with green cross always reported that my IPD was 63.5mm. Clearly using Rift values cannot be trusted. The Reverb was set at 64mm and once set at 65mm, things seemed surprisingly better somehow. It is nothing to put ones finger on, but it just seemed more comfortable viewing. Just as well, because peering at my Shrek like visage in the mirror for a good while was distinctly not comfortable viewing.

This. The cameras need contrast to lock onto. Blank walls ect do not provide the same contrast as say a wall with patterned wallpaper. Same with dark rooms. I noticed a drop off in tracking performance last night and it was only dusk. It still tracked, but the odd glitch started creeping in.

I already have 1903.... This is an update for it. Edit....However you have given me pause. I just got everything working, so I stopped the download and am doing a full system image backup onto a removable drive. Thanks for making me think again. Windows updates are a pain for breaking things.

Got a rather large update coming in for Windows 1903, something about Microsoft holographic among other stuff. Wonder if this is the patch for the WMR blurry issues? Well, I spent all day just about in that headset, just setting up control binds ect. Not one real glitch, no flickers and no disconnects. Burned 10,000lbs of fuel off in the Tomcat, got hypoxia because I forgot the Oxygen...tunnel vision and everything going grey round the edges. Wondered what the hell it was at first, I thought I was about to see my third 2080TI go up in smoke. The latest DCS patch really makes things butter smooth with the reverb, so much so I have banged the resolution back up to 180%. Only real fly in the ointment is the WMR portal. The mouse cursor sometimes tends to still think it is confined to window after DCS is shut down and the only way to clear it is a restart. Overall I'm happy now, I was getting worried and was seriously thinking about sending it back yesterday. Glad I persevered with it a bit longer.

It Works!!!! Very early days yet, but.... Finally up and running. 1 hr with no flickers and no disconnects. With my revised cable mod, the cable is no longer an issue and you cannot tell it is there at all, albeit my mast and retractable dog lead is taking the weight, but you can no longer feel any stiffness when you turn the head and the cable does not catch on the headset. It almost feels like a wireless setup. Been setting up my control preferences in the F14 mainly, but making other alterations. Main ones are: Steam VR: Custom resolution set to 155% - I did not think the small performance hit running 188 was worth the small increase in clarity. DCS settings mainly high, all shadows flat only, traffic low, mirrors off, MSAA off. Once again, running 2x MSAA did not make enough of a difference to shimmers to warrant the performance hit. Quite happy now, but still a lot of work to be done. I have to find a way to get Voicemeeter to supply my buttkicker yet. I have no idea why it is not working as before. As for WMR, since Steam VR updated, everything seems to work much more smoothly. No janky starts and dropped cursors. I think Oculus running automatically was a big cause of those issues too.

Bend the cable back and zip tie it between the other two ties, but at 45 degrees. It's not perfect science, it's suck it and see. Disconnects are cable issues, flickers are power issues.

HP Reverb techs have acknowledged that the cable connector is the source of the disconnects due to flexing in the joint. They are now starting to supply clips to hold the connector rigid and are working on a new cable with more secure latching and better fitting connections. I have added a further mod to the cable tie trick as I was still getting the odd disconnect. Figured even with two cable ties holding the cable at the exit end, it could possibly still twist past the cable ties slightly due to the ridiculous rigidity of the cable. So I made an inch loop and brought it back on itself, then added another cable tie so it now exits starboard rear. The loop should take care of any slight twisting that gets past the new tie and stabilise the connector further. Added bonus is it no longer appears to occasionally catch on the right earphone assembly when you turn the head to the right.

We lost a good man when PL was fired from Oculus.

Really sorry to hear that Imacken. I have been thinking on these lines and feared for the hardware failing. I have run out of time because I fly out to Greece early on Monday morning and my 14 days is up on Thursday. What's buggered me up is the crappy, living out on the sticks internet connection I have. Fibre optical broadband got within 3 miles of the house and stopped dead. I have to live with copper and 8 miles from the nearest main telephone exchange with a few signal boosters along the way. With all the updates, new installs and now switching to open beta to take advantage of the reported VR improvement in 2.55 over my present 2.54 stable branch; I have pretty much been downloading stuff constantly since I got the Reverb. Over 130GB of data so far at 3.5Mbs. Switched to OB and downloaded 33GBof DCS World during the week and was asked if I wanted my modules transferring over to the new install. Said yes and sat back. DCS finished and in the "Rubiks cube" I had 12 notifications to install modules. Great, checked install all and was presented with another 70 or so GBs to download.....:mad: !!! I had the sodding things on my hard drive already. That really is poor. I had to delete my stable version as there was not enough room for both. Note to myself: use the command line method next time dummy. PC has been downloading since yesterday teatime and is currently at 50%. All this snail pace downloading as I uncover yet another problem that needs a download to fix it has caused me to run out of time. Of course I can't test it out when a download is in progress, I don't want to do anything to destabilise it. A week and a half of ownership and I have yet to actually fly a mission. However, I have become convinced that all the problems are USB related. I also believe the heavy double cable is a late replacement for a single type, as it connects to a single cable in the headset. I would guess that as people submit tickets regarding disconnects ect, they will eventually be sent a revised cable. I'm betting on the original lightweight cable being found to be insufficiently durable was the cause of the launch delay. But you are right, WMR software sucks big time. In the little testing and tweaking I have managed between the marathon downloading sessions, things are improving. Stopping Oculus starting helped a lot. Correct way of starting is to put headset on, allow wmr portal to auto start, wake up your snoozing desktop in cliff house and start steam wmr and dcs from there. No mouse issues doing it that way.

Possibility of Rift Earphones Fitting Reverb Rift Headphones fitting Reverb. That idea crashed and burned. I had a set replaced under warranty by oculus, so I took the faulty spare and tried it on the Reverb. Everything is the same fitting, with the exception of the length of the center screw. The oculus one is too short to start. In the name of science and the DCS Community. I disassembled the earphone to see if the screw could be changed for a longer one. It looks just like an ordinary PC case screw. However the screw is moulded into the headphone base and cannot be removed, despite ragging at it with a pair of pliers. I drew the line at trying to remove the headphone threaded collars on my Reverb...

Now wondering if cable issues were what held back the original launch. The cable on the headset side of the connector is a single barrel, lightweight cable firmly held in place. The other side of the connector to the PC is a heavy, double barrel design. This seem stupid. UNLESS the original was a lightweight cable and they were finding durability or supply issues..... The cable was already built into the headset, but the extension cables could be taken out of the boxes and swapped for an heavier version.

That certainly seems easiest. I will give it a go once my PC has stopped downloading 34GB of Open Beta 2.55 on my lightning fast 3.5Mbs internet connection. It has been on overnight and probably will be all today too. Hoping that 2.55, Oculus disabled, motion reprojection on auto, setting shadows to flat and backing off some static ground objects populating my airfields will give me better performance on the ground. In the air was not a problem. Then to try some audio suggestions to get Buttkicker running again (thanks to that poster). Buttkicker is a bit like VR, once you have had it, you can't go back.

I have the Butkicker gamer 2. You will need to put your chair on a platform and rubber mount it as it shakes the floorboards. I removed the wheels from my chair, screwed in metalastic exhaust mountings in their place and constructed a wheeled wooden platform to mount it all on. It toned the house shaking down a lot.

Glad to hear it. I have just come back into the OB fold after about six months on stable. I left OB after the Hornet radar kept breaking with every patch. Downloading OB 2.55 as I speak. After assessing my Reverb performance over everyone else's it seems a major factor is that many of those seeing better frames are on 2.55 and I was still on the old version on stable.

Link works ok for me. Shame Oculus dumped high end VR, however I can see their point of view. We buy the Mercedes end of VR, whereas most people will buy Ford.

Firstly, thanks for all the replies regarding Oculus, I did go down the rabbit hole last night using file explorer , Oculus and services, then several sub folders and finally properties. Googling advised that I should open compatibility and tick a checkbox, but the compatability tab was no longer present. Further Googling revealed that method was no longer doable as Oculus had got wise to it. I will give your suggestions a go.... Break. To OP. HP UK have been sold out for quite a while now. It's odd that we got them first as it is usually the U.S. that gets stuff out before Europe. We didn't even get a chance to buy the Odyssey.

Great news about enabling motion reprojection in the settings files. I did just that last night while still tinkering with audio. BTW, I removed the headphones and they look at first glance to be identical fittings to the Rift. Might be possible to swap them over if the dimensions are the same.. I did not have time to test the motion reprojection settings, just enabled them and set to auto. What I did find, despite whatever settings you put in sound as default, WMR overrides them, just like Rift did at release, even analogue stuff won't work. Disappointlng since I just bought some new earbuds for it. Only way to run my buttkicker, so far as I can see is to run a splitter directly off the headset 3.5mm Jack, one to my buds, the other to the buttkicker amp. I will try tonight. More crap cable tied to the back of my headset. However if Rift headphones fit and the Jack still works with them fitted, happy days other than the addition buttkicker cable. A bit concerned about current running the larger drivers and sending the signal to the amp though. I hate USB audio, God knows why headset manufacturers always insist on it. Cheaper to use one plug and cable I suppose. However it limits what you can do with audio. BTW. Has anyone found a way to stop Oculus opening when DCS starts yet? It is a pain in the arse.

I have 3.5Mbs on a good day..... yes that is a small b.

Thanks Froggy. That clears a lot of things up, I am indeed seeing smooth headturning, but on the ground and looking at right angles to the taxiway, that's when the judders start. Also stuff like looking forward and the taxiway signs are approaching, they start juddering too. All my airfields are heavily populated by static ground objects, probably more than 100 of them each, so maybe I will try a new mission with reprojection on in the file, no objects and some settings like shadows turned off. NTTR performs far better than PG so I guess whatever is different in NTTR will likely form part of the new VR optimisation.

Be careful. That could almost be construed as an unboxing post. Some people, actually not that many are against such posts. To pass the new Reverb Posting (Quality Commission Reform) Regulations 2019, you need at least two pages of factual bullet points. Note: Any references to emotion, either expressed, implied or construed are to removed from such posts as these are unhelpful and wasteful. The Quality Commission reserves the right to adjudicate as to whether any particular bullet point is valid, helpful or fit for purpose. As for me, thanks for your post, it helps make a sometimes dry forum a little more vibrant.

I think I can see why my ground Taxy experience is suffering but want to make sure. When Steam VR comes online with the small panel and I hit the hamburger and go to settings, it shows reprojection, just above motion smoothing as "On". Is this not the case, do I have to manually input the line in the thread detailing switching it on to actually switch it on? It has to be said, I like the Reverb, but I hate the software it needs. While I am here, if you are tempted to update to 1903, be aware that the stupid bug is back, the one that makes apps disappear from the start menu. To run DCS I had to make a shortcut on the desktop to the actual DCS folder. No idea yet how to run a repair.