Tinkickef

Pull the review. They are not worth dealing with. I am going to contact my CC company to claw my money back. I can understand delays in production, but I cannot countenance ignoring emails from concerned customers.

Unfortunately that fix only applies to Vive ect.

It must be the update before the last from what you have all said. This is because I declined the first update at the time and the second update appeared later. So I downloaded both at the same time. Bugger. My Reverb was working flawlessly too. Does anyone know if this has been reported?

Since last DCS update. During gameplay, at times the tracking stutters and starts getting worse. Eventually it will flicker back to the steam VR loading screen - the one with the lines, Aurora and mountains for a fraction of a second. Maybe every five minutes or so, usually when moving my head to look somewhere else. Only for a fraction of a second. Eventually the tracking will freeze permanently, so the cockpit follows your head movement. On removing the headset, the message "steam VR has encountered a problem" or some such with the option of exiting steam VR is on the screen. Metashaders and FXO have all been recompiled since last update.

I can't even get the tomcat to Taxy off stand and turn a corner without running on to the grass in track replay.

This. We have had very similar experiences. We have the same IPD, we both wear glasses. We have both taken the trouble to jump through all the hoops. Break. Reverb is not designed to be a peripheral for gamers, it was a tool for designers, architects, low impact training courses ect to view their work in VR. Using it for gaming is pushing it well beyond its original design brief and if you know this and buy it anyway, you have to accept its shortfalls. As I state very, very often. Reverb is not for everyone. Everything must be optimum to get it running at the best performance it has the ability to display - from physical IPD to in game gamma settings. When everything is optimal, then Wow.

As said before. The bulletholes you see are generic. They are applied to an area, they do not depict an actual bullet strike. So far as I know, at this moment, only the later IL2 series have correctly applied damage where ordnance strikes. Cliffs of Dover most certainly has. A bullet strikes the airframe and the correct damage is assigned to that area, taking into account ordnance type, velocity, airframe object material, thickness, the amount of energy remaining in the bullet after penetrating said object and it's ability to penetrate the next object in line, bullet path due to angle of penetration and deflection ect. You may see a single, insignificant looking bullet hole in a wing but the internal damage could be catastrophic. The main spar could be severely damaged and the only time you will find out is when you attempt to pull G. DCS have employed some ex Maddox damage modelling devs to put this shortfall right - they are "working on it". Multiplayer is problematic with such things. I can recall one mission on CLoD where I was avoiding a friend's 109 in my Blenheim on route to target and was flying through a large cell of cloud, twisting and altering course, trying to avoid him. He doggedly followed me through the cloud and shot me down. I praised him for staying visual in cloud and his reply was "what cloud?". In multiplayer, what you are seeing is not always what someone else is experiencing, other than in very broad terms.

Chaff is most certainly modelled. I once took a bit in a Warthog over Tonopah Test Base. I had been pumping chaff, but the SA8 got me. I ejected at low level and landed on the base and decided to have a walk around. Some minutes later, several dark coloured "panels" came fluttering slowly down and disappeared when they touched ground. I wondered what the Hell they were then it came to me - the chaff I had been pumping out on my gun run. That is the only time I have ever seen it. I posted about it at the time, I was amazed at the level of detail modelled.

You need to read through the last 150 pages of this thread. There are diferent versions of Reverb and different software settings. My Reverb Pro settings at full resolution is 188%. Other versions are very much lower. You appear to be setting some very high supersampling with your settings if your software version is the latter. I think.it is Secoda that has the other setting type. It is not the resolution, rather than the scaling that is different.

[TABLE]i[/TABLE] Oh Secoda. You have my commiserations. To be without Reverb for awhile. Disappointing. I'm lucky enough to have sorted all the problems out and have a stable headset. I have had my headset since early June as have you and to see you fall by the wayside now is jarring. Guess it's the luck of the draw with early adopters... Never mind, you will bounce back.

Appears to be issues arising with the new headsets that I never encountered. What is this wmr screen lock of which you speak? I simply put on my headset and cliff house appears. I double click the desktop within cliff house to wake it up. I minimise the desktop and right click DCS, select open, then right click steam wmr and also select open. I then take a quick peep under my headset to ensure that some DCS installer is not waiting for an answer. The white triangles do their thing and I appear in the steam wmr house. Very quickly thereafter, I get the loading screen with the evening sky and the lines, with DCS flickering on and off. DCS loads into UI screen. That's it. Never anything else.

This..

Thanks Karon. It makes sense to fit another GPU in my old rig to get it up, running and fit for DCS. Last time my GPU let out the magic smoke I was without DCS for over two months and had forgotten much of what I had learned. As for the rest. That will require more thought. It will not be worth it just for a couple of one off, ten minute rides for family and friends. Although the idea is very attractive still....

I have one of those niggles that keeps itching and I can't scratch it. Background. So, a few weeks ago I built my new PC, but kept the old one as a backup, in full working order, all apart from the GPU. I intend it as a spare, should something major go wrong with my present rig (I'm on my third 2080TI in less than 12 months and it's getting to failure time again). My Old rig was perfectly adequate for DCS using Rift (and probably for Reverb, however when I started buying my new components, I did not know that). I also still have my Rift packed away in its box. So I'm thinking of buying either a 2070 Super or one of the new 5900XTs to put back in my old PC to get it back into service so I can use Oculus games. All just conjecture at this point. The itch... I should point out I'm a single player mission only type. I enjoy making my own missions and am not much interested in the multiplayer side of things. As I state often, I enjoy the flight, not the fight. I use combat only as a motivation to fly to some place on the map and to add a little excitement mid mission. All my missions are generally full fuel and external tanks. I have a hankering to give rides in the rear seat of the Tomcat in real time, since the track replay is so broken that you cannot Taxy off the stand and turn a corner without running onto the grass. Even the missus thought the idea would be a cool one, esp if we could communicate through the comms system. It would certainly be cool for her to see my head movements from the backseat when looking back at her. Who knows, I may have a prospective RIO... So how would I set it all up? I heard that you could buy a second module from HB at a much reduced price for just this scenario, but have never seen the option. Naturally, I would probably have to buy the PG or NTTR maps again for the second PC. I could connect the two PCs together using an Ethernet cable or via my home WiFi network, but would they talk to each other? Would one of them have to be set up as the server and how do you do this? As said, just conjecture at this point, I would have to save up for the new GPU, but a few pointers would be nice. I really do not have a clue how to set about this and have not seen any threads on it.

Indeed. Unless I am deploying weapons in AA mode, I just keep the HUD in take off mode. I find the rate of climb bar and pitch ladder very useful, but for everything else I use the round gauges. It must be remembered that the HUD was never designated as a flight instrument in this version and should be treated as a convenient guide for wise men and the obfuscator of fools.

You will still need to do the cable mod to stress relieve the cable connections themselves.

I rubbed out auto and replaced it with "motionvector". Butter smooth now, even in PG, an heavily object populated AlDhafra airbase and taxying in the F14. Happy days. To be clear.. strike out the // on the bottom line as detailed earlier, then delete the "auto" part and replace it with "motionvector", save the change and you are good to go. This enables reprojection permanently on and is by far the best setting to use I find. New updates have and probably will change the line back to the default setting again, so if you suddenly have jitters again after an update, this is your first port of call.

Tried the visual range radar. Found the jettison droptanks, selected it after looking at external tank contents and found them to be zero. Asked Jester to drop them and he refused. I had to climb over the seat, cuff him around the head a few times, select the stations for the tanks and hold the jettison switch till I heard the pylon squibs kick em clear. I then climbed back over the seat, kicking Jester in the teeth for good measure, before resuming my role as a steely eyed missile man. I am having doubts as to Jester's overall commitment to the mission.

That is very good news Ironmike. :)

I just got on their site and sent a message to customer support asking what happened to my order. If I get a reply I will let you know. They did state at the time of ordering that delivery would be in the "summer". So it's a bit like groundhog day, F14 release all over again. Astronomical summer ends around 21st Sept, so time yet. Still, they should keep regular updates on their blog.

I've finally got comfortable with the F14 cockpit now and know the switches that I use regularly during the cold start process. The placards are readable using Reverb, but were illegible in Rift, so the new hardware has made a huge difference. However, I agree. The text does need to be more immediately legible as do the caution panel lights. I cannot read those at all without leaning forward a long way. Not something you could do strapped in. I truly appreciate the artistry that went into what is an astoundingly realistic cockpit, but as several aircraft maintainers have stated, both on this thread and others; it is simply not realistic to have this level of wear in the cockpit of an in service aircraft. I can appreciate discoloration due to dust / polish on the text, but the chipped paint around the letters so some are missing/illegible would be recorded as an unserviceable panel placard even in a flying school Cessna. I don't know why HB are being so resistant to this, after all we were promised several different cockpit textures from the start. All I can think of is that since they were taken over, they are having to dance to the new master's tune somewhat, and their hands are tied. Happens all the time, a really great little company with an innovative attitude and brilliant customer service gets absorbed into the corporate world. This is never good news for the existing customers. That aside, HB deserves every penny they can get. They busted their asses and should reap the rewards. I bear them no ill will. Thanks for the great module (I have a notion it may be the last one we see in DCS, but will be delighted to be proved wrong). :)

Thanks Airhunter and Strikeagle... never really get that far into radar menus. Contact...tws.. launch a couple of Phoenix. Suddenly dipping contrails, small fires on the ground, then turn for an hour's flight home looking forward to tea and medals Happy days.

Just get this one.... https://www.amazon.co.uk/gp/product/B073NZZ6TG/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1

As others said and Ironmike stated, it would be nice to see a pilot body for VR, though it is hard. I also would really like the external engine noise to ramp up when the canopy raises. I have begged for this in the past. One other tiny matter... it would be nice to have a place on the Jester wheel for jettisoning droptanks. I fly quite long missions, being mainly into the flight rather than the fight, and those empty droptanks must cut my fuel mileage considerably.

You need to swap your drivers. Pick from a list on your PC and install any ending in (Microsoft). Edit... I see you are now good to go.