GunSlingerAUS

Toykilla, your nuggets of wisdom are priceless. It's comments like yours that cause people to waste time. Just to scratch my curiosity, would you be ever so kind as to tell me what fps you're seeing when running the Reverb at its native resolution of 2160 x 2160? Here's a guide to show you how to set the correct resolution in case you're not aware of how to run your Reverb correctly - you'll need to up the SS% if you're running SteamVR, or install the SteamVR beta for the software to correctly recognise the Reverb's native resolution: https://vr4dcs.com/2019/09/10/reverb-settings-for-dcs/

Lol, I sure did! It's pretty obvious this guy is doing promotional work for Xtal. It's a shame that they go about it in such a shady way, as it does nothing but make the brand look weak. And from all accounts, the Xtal is a huge disappointment, at least when it comes to games and simming. You're much better off buying a Reverb, which is a fraction of the cost. It's a bummer, as the Xtal promised some interesting technology, but the end product is more a proof of concept than an actually desirable consumer product. Better luck next time, though if they're now skulking around forums, I hate to say that I don't think there will be a next time...

Eaglecrash, if you want to deny stating clearly in your messages that you solved ghosting, that's up to you. It’s there in writing, so I'd kindly ask you to check your messages again. If other people ask for it, I’m happy to show them in their entirety, but it seems rather pedantic. The thread I was referring to that sparked my OP is just below this one (https://forums.eagle.ru/showthread.php?t=220815), but there are also dozens of posts on these forums saying that it can be resolved (there's even some in this very thread that suggest user error is the issue). Please don’t ask me to spend more time finding them, as I'm sure you can do so using the forum's search feature. You'll also see that this had led to great confusion in the forums, which is why the work of Thud is so appreciated. I just wish I'd stuck to his info before going down the ghost-free rabbit hole! :) Also, you’re running 100% SS in what seems to be the SteamVR release version (based on the low resolution you use). Please note that you need to update this to the SteamVR beta release for it to correctly identify the Reverb – set the beta SS to 100% and it will then run at the Reverb’s native resolution. UPDATE - IT NEEDS THE STEAM WMR BETA TO ENABLE THE REVERB'S NATIVE RESOLUTIONAgain, Thud has done all the hard work here if you want to see. Or you can manually change it in the release SteamVR slider to correctly reflect the resolution. Or you can run at the same resolution as the Index or Cosmos, like you do, but that defeats the purpose of the Reverb - you're better of with a wide FOV in the other HMDs at this lower resolution. My descriptions of my settings aren’t vague – they’re concise. Anybody can easily replicate them exactly except for the last one which was a mixture of high/low. Finally, I don’t need to take a screenshot – run everything at low (but keep the Reverb at its native resolution, and don’t disable shadows entirely). Run the F-14 dogfight quickstart, then watch the Su-27 warp on by as you make the knife fight. In fact, try any mission where you’re flying close to aircraft moving near you at a decent velocity at a different heading, and you’ll see huge double projections of their model. Feel free to post another essay, but please don’t muddy the waters – it’s impossible to run the Reverb at native resolution and not experience ghosting. Can you agree on this? I’m sure it might run much better with the resolution dropped 35%, which is also why lesser HMDs don’t experience this issue as much.

Eagecrash, chill buddy! My post was actually in response to another thread with the title stating that they had solved ghosting. This kind of misinformation wastes people's valuable time and money, so I wanted a clear thread for those trying to solve ghosting on the Reverb (which many have thanks to the misinformation on these forums) telling them not to bother. This came after I spent days and days trying to solve the issue, only to find it's impossible. Certain other people on these forums don't help the matter, claiming it's other users' computers at fault, and that their game runs perfectly with no ghosting issues. You did actually claim that you had solved ghosting when messaging me, stating things like: "This could very well be why you're having ghosting on yours. I haven't found this to be the case...Its only the nature of reprojection if you're over-taxing the processor...the Su-27 looks just fine in the merge when I'm in the F-14... I'm very familiar with what ghosting looks like...Doesn't happen with the Reverb" This is why I asked you to run VRfps so I could verify your subjective observations with objective facts. Unfortunately you didn't, so I spent considerable time trying to replicate your non-ghosting. Turns out this is impossible, at least when running the Reverb at its native resolution - I'm not going to try lower, as I could have stuck with my Vive Cosmos to run at those resolutions. I totally understand if you don't perceive ghosting like many of us do. Perhaps some of us have higher-attuned visual systems due to long-term gaming that makes us more sensitive to this? (I know gamers are indeed susceptible to noticing visual flaws more than non-gamers, as I did an experiment on the LCD projector rainbow effect with a test-group, but I digress). Regardless, I envy you for not being bothered by this - but it could also be due to the fact that you don't fly fighters and don't dogfight, making you less prone to being in situations where it's extremely obvious. I can say that for those of us who dogfight at WVR, the ghosting is pretty damn atrocious. Nothing like seeing an Su-27 warp right on by, with a ghost-like second aircraft a metre behind it! I don't think it's overly critical to point out such a fundamental issue. As for what settings I ran my tests in, I used the F-14 in numerous places - the F-14 carrier take-off training mission, the F-14 runway takeoff quick mission, and F-14 dogfight quick mission - and using the following test settings, other than running the Reverb at its native resolution via SteamVR's setting panel: All in-game settings low, but I didn't disable shadows (kept them at low) All in-game settings high A mixture of high and low, lowering those that had the biggest impact on frametime (not fps) Turns out the difference between low and high is about 45fps in low to 36fps in high - and even at 45fps, reprojection is enabled automatically (remember, the game must hit 90fps to match the 90Hz of the HMD to disable reprojection). I also tried the F-16 and F-18 in various scenarios to see if their less detailed models would still cause terrible performance - they do. I'm not sure about the A-10 though; given it's a decade old old model, I'd wager that it has slightly better performance, but would still suffer from performance issues. The reason I mention my experience is to show that I'm used to testing these things scientifically, with results that can be replicated and terminology that everyone can understand. I know the importance of sharing factual, correct information, as people read it and then use it to make decisions on how they spend their time and money. When people spread incorrect information, it can lead to others wasting their time, or becoming frustrated trying to solve an impossible problem. Anyway, as I said, your inability to see ghosting is fantastic. Unfortunately, ghosting is a real problem for Reverb users, whether the player is one of the few who doesn't see it or not, and existing owners and potential buyers of the Reverb shouldn't chase a rainbow trying to fix it. (bolded so that those looking for a Reverb ghosting fix don't get caught up in all the guff on this thread!). While this is a problem, DCS VR remains a fantastic way to fly around scenery at altitude, but falls apart in the nitty gritty of dog-fighting. Oh, btw, the reason the game slows down when you have external video feeds on your HMDs is that it has to re-render each of those zoomed in areas , thus massively increasing the geometry load on your PC. Hope that helps.

@eaglecash867 Please note that I wasn't specifically 'targeting' you with my comment - it was a general response to the multiple users on here who are claiming they have removed ghosting on the Reverb. These claims mean other users are wasting countless hours trying to solve this issue, and yet others will buy a Reverb expecting there to be no ghosting issues. As I've pointed out, and numerous other people have discovered, this is impossible. It's fantastic that you don't notice ghosting. That doesn't mean it's not a real issue that is 100% currently the norm on the Reverb. Ghosting is a vague term to discuss a very real artifact of reprojection, which is why I asked you to run VRfps so I could see what your hard, scientific numbers are. Unfortunately you decided not to, but I'm sure you'd have then seen just how many frames you're dropping. Looking at the fps counter and being happy with 45fps shows that some people just don't understand what reprojection is - you should always see 45fps locked with reprojection turned on, but I won't write an essay explaining why, as there are other guides on the Internet explaining this. Also, eaglecash, you're running at extremely low settings - specifically, much lower than the native resolution of the Reverb. This will introduce a huge amount of aliasing/pixelisation, which many users simply can't stomach. You're also disabling all shadows, which has a HUGE effect on VR fps, and suggests there's something very wrong with the DCS engine in VR. In summary it's great that some are happy with the experience. But I wanted to shine a light on 100% incorrect information that will lead to higher expectations from other users. As a technology writer specialising in PC gaming hardware and performance, I've got over 20 years of real world, full time experience looking at these issues, so will always try to share the correct information and clear up misconceptions. Now, just because ghosting (which should more accurately be called something like reprojection double-frame artifacting) is currently an issue, does this mean that VR is not worth enjoying? Absolutely not, especially in less demanding scenarios where fps is better. But, and it's a big but, does it compare well to the experience of a high-end PC on a huge, crisp display? That's the million dollar question - I'm leaning towards enjoying both. VR for 'fun', immersive sessions, 2D for serious, lengthy and complex missions.

Hey guys There's a heck of a lot of FUD on here about getting rid of ghosting/stuttering while using the Reverb. To be blunt, after weeks of testing, I've discovered it's impossible to remove this with today's top hardware (I run a 5GHz i9 with GTX 2080 Ti). While some might claim they don't see ghosting, they're simply unfamiliar with the phenomenon, or don't fly fast-jets (slow moving aircraft are less prone to it, such as choppers or prop-planes, as they don't update the scenery/objects as quickly, and thus reprojection looks better). The only way to remove this is to run at the Reverb's native refresh rate of 60HZ or 90Hz (and thus 60fps or 90fps), depending on what refresh rate you set in the WMR software. From what I can see, this framerate is currently impossible with the DCS engine in its current iteration unless you run at a very low resolution, and thus have a horribly pixelated image. I hate being the bearer of bad news, but this is something people need to be aware of if they're spending US$600 or more on a Reverb. Personally, I'm not sure if I'm going to continue to use the Reverb and live with the ghosting, as the rest of the VR experience is so damn good, or switch back to my ultrawide 3440 x 1440 display - even this is problematic, as it's a 144Hz display and thus causes massive stuttering issues with TrackIR. Here's hoping ED can make huge improvements with DCS in VR. I'm not betting on it though, as they harped on about multithreading/multi-core CPU improvements for at least a decade and still haven't implemented it well.

wju, as far as I can tell, there is NO WAY TO DISABLE PROJECTION ON WMR DEVICES. It is not as simple as ending a process...

I'm sorry to say that this initial post is actually incorrect, as it is based from information from early 2018. Motion reprojection is enabled by default in SteamVR/WMR as of November 2019 - the fix mentioned here just enables a new experimental version of it, which some feel looks better than the default reprojection mode. You can see Thud's excellent VR guide for more information: https://vr4dcs.com/2019/09/10/reverb-settings-for-dcs/ TO REITERATE, IF YOU CAN'T MAINTAIN 90FPS OR ABOVE IN VR ON A 90HZ HMD, REPROJECTION IS AUTOMATICALLY ENABLED, AND YOU WILL INDEED SEE GHOSTING (also referred to as stuttering, juddering and a bunch of other vague terms) Now, there is a way to get around this apparently - disable reprojection entirely. However, while this should remove ghosting, there are a few issues: 1.) I'm not sure it's possible to disable ghosting with WMR/SteamVR devices. Would love somebody point me in the direction of how to do this with the latest versions of SteamVR and WMR. 2.) If you do disable it, which apparently is possible on the Oculus HMDs and older versions of SteamVR, you will experience massive smoothness issues when turning your head or watching the displays. Expect it to jump around and stutter heaps. One thing that does seem to help for WMR owners is to run at 60Hz, and then lower your graphics details and resolution until you can hit 60fps solid. Unfortunately DCS looks terrible as a result. I'm getting a bit tired of the misinformation about VR these days, with non-technical people giving out incorrect information that leads to others wasting hours of their time. I understand their heart is in the right place, but as a former technology journalist I always ensure that the information I put out is correct. And if it's not, I'm happy to be corrected. TLDR: If you can't run the game at the HMD's refresh rate, you're going to see ghosting from reprojection. And you need a PC from the year 2030 to be able to do so on the Reverb.

What LeonRedbone said. There's a lot of misinformation on here about ghosting, as many people don't actually know what it means. But it's basically impossible to have a smooth, crisp experience AND remove reprojection ghosting.

Sorry, it's impossible to run with no ghosting and those settings. I'm running the fastest hardware money can buy, and have tried all various options. As Thud has surmised, SteamVR SS is much better than MSAA in the game. If somebody is not seeing that, they're changing it in the wrong area.

Interesting - so I don't need to faff about with any resolution settings in WMR or SteamVR, correct? I left everything at 1x and it's perfect.

Hey guys Ok, so the floor thing wasn't an issue - way too obvious my friends! It turns out that the problem appeared to be OpenVR Advanced Settings plugin for Steam. Somebody on the WMR Reddit forum suggested this, so I uninstalled it, then uninstalled SteamVR and WMR for Steam. Then I reinstalled SteamVR beta, WMR beta, and ran the game. Now it's all working perfectly, with the VR Center button doing its job. And now I get the added bonus of running at the Reverb's default resolution for added crispy benefits! Thanks for your suggestions though guys, much appreciated. Now to play with async reprojection!

I've just followed the excellent DCS VR guide here to fix my HP Reverb resolution issues in DCS, as the Reverb requires the new SteamVR beta and WMR Portal beta to enable the correct native resolution. However, doing so has broken my DCS menu and cockpit views, so that both are now set approximately 7 feet below my actual, real word view position. This makes the game totally unusable (can barely navigate menus, and can't move the in-game camera back into the cockpit). I have attached screenshots of the problem. I've tried the following to solve the problem, to no avail: 1.) Deleted my WMR room setup configuration, and recalibrated via WMR. 2.) Rebound the DCS VR center key and hit it - this causes my menu/cockpit to flash in the correct position for about 0.2 seconds, but it then goes straight back to the broken view. 3.) Used SteamVR Reset Seated Position button in the SteamVR menu, but this does the same thing as solution #2. 4.) I can just barely navigate into the first quick start flight, but then I can't move the camera down and into the cockpit using the ctrl+shift+numpad keys far enough. It seems to stop moving about 4 feet above the cockpit. 5.) Hit numpad 5 to recenter in-game view. Note, this problem only occurs with DCS. Every other game is fine, as the Steam Reset Seated View button works in every other title I've tested, including IL2. I need to use the SteamVR latest beta to enable the true resolution of the Reverb for every game, and it also has a better reprojection method. Anybody know how I can fix this issue? Or will ED need to patch the game to get it working?

Just a quick update until I have time to post in detail. I've swapped to the Reverb, and it's by far superior to the Cosmos for DCS. The resolution increase can't be understated, and DCS is now actually playable in VR for me. There simply isn't any competition if you're looking for a seated VR simming experience. I am having some issues though, but will make a separate post about these.

Mate, you've convinced me! I've just purchased a Reverb, and will be returning my Cosmos ASAP. Thanks for prompting me to head in the HP direction.

Oops, you're correct, so I've corrected my post. I've read mostly negative feedback though regarding the Reverb - small sweet spot, bad mura and other issues - which is why I didn't go for this product. I'd love to hear your thoughts though, as I'd kill to have a super high-res HMD. This review in particular guided my decision, as the Road To VR guys know their HMDs well: https://www.roadtovr.com/hp-reverb-review-vr-headset/

Hey guys, to answer your questions and thoughts: Firstly, thanks for the suggested solutions, but I'd already tried all of these to no avail. However, I think doing a clean reboot and then making sure I don't alt-tab out of the game is a temporary fix for the mouse issues. Still working on the FPS issue, but I think ED will have to patch the game to get around the V-sync being stuck on. Flameout, as for your questions: I am wondering if the lower FPS is just due to having to push more pixels due to the higher resolution and not a software issue. When you say other games purr in comparison, are you talking about with VR or on the monitor? I'm talking about other games and DCS when it's running properly. The increase in resolution is tiny for my RTX 2080 Ti when compared to my 2860 x 1440 monitor, as I've tested my PC running at 4K resolution, where it still hits over 60fps minimum in DCS. So it's definitely some issue with the game itself. Can you clarify - you say the cockpits look great - but also say other objects look clunky. The cockpit is very readable, while the environment looks good - basically anything large is nice and clear, but when it has to render smaller objects such as other aircraft, buildings, pilons, etc, the limitation in resolution is obvious. However, if you're coming from a Rift CV1, the increase in resolution is absolutely massive - I could never play DCS with my original Rift as I hated the decrease. But I think I'll try DCS more with the Cosmos. As for whether it's worth buying, that's totally up to you, but it is indeed a huge upgrade over the Rift. At the same time, I miss the razor sharp quality of my monitor.

Hey guys So my Cosmos has finally arrived! I used the original Vive and Rift, so the Cosmos is a big step up. My first impressions in DCS are: 1.) It's very comfortable for extended periods of time once you've mounted it correctly. Finding just the right spot on your head takes quite a bit of trial and error, but it's easy to take on and off once you have done so. It also doesn't get too hot, and I was running it in a room with the heater cranked to 25C. 2.) The "Sweet Spot" isn't as bad as I'd heard. You still get a bit of blurring outside of the center point, but it's easy to adjust to - simply look moving your head rather than your eyes. 3.) The image quality is great for a HMD. Compared to the other headsets I've tried, it's light years ahead. I can basically read all instruments in the pit of my F-14, and easily keep track of a bogey in a knife-fight. 4.) The tracking is absolutely fine for DCS, and most other games. It uses in-out tracking, so there's no hassle of setting up external peripherals. Being able to look around my pit is simply amazing, as is the 1:1 movement of my head. It absolutely smashes my TrackIR out of the ballpark. The tracking of the hand controllers is actually surprisingly good, and I can easily hit buttons in the pit. 5.) Setup is an absolute breeze, taking about 10 minutes the first time, and then a minute or two thereafter when I want to change from seated gaming to room-sized gaming. However, it's not without issues: 1.) Despite being the 2nd highest res HMD on the consumer market (Reverb takes that crown), it's still very low resolution compared to my 2560 x 1440p display. There aren't too many jaggies, and the screendoor effect is minimal, but it's still got a long way to go to beat a monitor. Even with the game rendering at 3840 x 2160, distant aircraft look like rather large dots at range, which morph into blobs, before becoming distinguishable as aircraft. 2.) It's super buggy with DCS. For some reason I'm currently unable to fly, as I've done something (not sure what) that has caused me to be unable to hit the FLY button on the starting briefing. I also can't hit the green OK button in menus - but everything else is fine. I think this may be a common VR issue though, as I recall having this happen with my Rift - I'D LOVE ANY SUGGESTIONS ON A FIX! 3.) I'm stuck at 30fps, sometimes 45fps. This is very surprising given I'm running a top-of-the-line system (i9 9700K @ 5GHz,m 32GB DDR4 @ 3200MHz, Aorus GeForce RTX 2080 Ti overclocked by around 10% in both core and memory, ADATA NVMe M.2 SSD). 45fps seems nice and smooth, but 30fps is a jerk-fest. I think it's simply a software issue though, as every other game absolutely purrs in comparison (btw, I get around 70-120fps when running at 2560 x 1440p, so should be able to get close to that). The display has a refresh rate of 90Hz, but for some reason I can't disable the v-sync, which is why it's stuck at a maximum of 45Hz or 30Hz. This is despite all v-sync settings in game and Windows being turned off. 4.) The integrated headphone sounds good, but the mounting clips are absolute rubbish, as they keep flipping up when they're not supposed to. Luckily I can remove these entirely and use my beyerdynamic MMX 300 headphones instead, which are vastly superior. 5.) Nearly every single VR game for Vive or Rift doesn't currently work with the Cosmos, as they don't support the Cosmos controllers. This should be an easy fix for developers though, so I expect this to change in the near future. I paid AU$1300 for this HMD, primarily to fly DCS. Was it worth it? To be frank, probably not - the chunky graphics are going to take some getting used to. I think it may suit WWI and WWII sims better, so I'll be checking these out soon. However, the sense of immersion is absolutely second to none. The cockpits of the F-14 and F-16 look absolutely superb, as does most of the terrain. It's really only when looking at other objects, such as aircraft, vehicles, or buildings, that the low resolution becomes quite noticeable. I'm probably going to use it quite a lot for DCS, but also go back to my lovely 32" 1440p display, which also has a variable refresh rate. So, there you go. Hopefully somebody can help with my weird UI issues, and ED can fix the fps problems. If you've got any questions, fire away!

Hey guys I'm very new to the advanced A2A radars in the DCS modules, and am now focusing on learning the F-14. I can get Jester to lock up targets, and switch between targets by number, but I was wondering if there is a command to tell Jester to read out what each target is? Ie "Jester, identify TWS Lock number one" or something similar? If not, what's the best way to: a) identify if a target track is friend or foe (I *think* I might be able to use the radar symbology to do so?) b) figure out what each contact on the radar scope is Thanks in advance!

Ok, so I was on the Grim Reapers Discord, and somebody recommended disabling MSAA, and just using SSAA. I set it to 2X SSAA 0XMSAA, and BINGO! I could now spot targets at a range of around 10 miles, or 14 or so km. Phew!

Yes please. Can't play the game right now as I don't use a monitor from 2003 :(

zhukov032186, seriously, I'd love to hear your thoughts on how to fairly spot targets on monitors that now sell for approximately US$200 - ie what most people are now buying because they're so darned cheap, and make game look so much better.

Can I ask what resolution you're playing on zhukov032186? If you're on a modern rig, you'd be dismayed at this issue too. If you are on 1440p or above, can I ask what your resolution to this resolution problem is? (pun TOTES intended)

Hey guys, just wanted to add my two cents to this, as I've recently started playing DCS more often now that the F-14 is out. I even upgraded my entire rig and simming gear for this beautiful plane, only to find that my gorgeous new 32 inch 2650 x 1440 monitor makes it simply impossible to spot anything, even at extremely close range, such as 5nm or so. I first realised this while doing the sidewinder training for the F-14 module, where I would get seeker lock much sooner than my Mk1 eyeballs. After more research, I discovered that this is a fundamental flaw with DCS, which is becoming more prominent among my flying friends now that 1440p monitors are so cheap. With 4K monitors plunging in price, this is going to be a HUGE issue for DCS' playerbase. As simmers, much of us pour money into high-end rigs, yet A2A is nigh on impossible on current mid-range rigs that run a lowly 1440p. Heck, even the console games being made now have 4K resolutions in mind. There are other solutions for other sims that currently exist that deal with this issue, so why hasn't ED implemented them? If one community modder can come up with a solution for this exact issue for another sim, I fail to see why ED's team of paid experts can't. Until this is fixed I'm going to have to really consider which sims I play. Sadly this means I'll be giving the F-16 module a miss, which is a real shame as it would have been great to get into a knife-fight with that acrobatic wonder. This problem is not going to go away,and will only increase in the near future as higher resolution monitors plunge in price. Hopefully my inbound Valve Cosmos offers a better experience, but I'm not holding my breath as it too is higher res than the 1080p displays that ED appears to develop on. In the meantime I'm going back to IL2 and RoF for my A2A fix. ED, please hear our concerns - this issue appears to be longstanding, and it's in your best interests to get it fixed. Would love to hear you acknowledge the issue, and give me some insight into any action being taken to solve it for this otherwise outstanding simulation.

CALLING VAICOM PRO EXPERTS! I'm willing to donate a new aircraft, campaign or map to anybody who can spend s0me time with me on VOIP to get VAICOM Pro and its modules all working smoothly Hey folks So I've just spent a rather large sum of money on a new High End rig so I can run DCS F14, but I'm very new to the advanced aircraft in DCS, including how to operate the radios, and also how to operate VAICOM with them. I've read the VAICOM manuals, and there are several steps that aren't clear to a noobie - such as: - Which radios communicate with which AI entities such as wingmen, Jester, ATC, etc - How do I map my Thrustmaster Warthog HOTAS to the correct PTT buttons, including which DCS keymaps do I need to change - how do I get AIRIO to work properly (NFI what "Follow the regular FINISH steps (see page 30) to update your VA profile with the new keyword" means, even after reading the manual.) I've already spent hours trying to configure this to no avail, but I think I could get it all going smoothly if somebody spent an hour or so with me on VOIP talking me through the setup process. I think I've installed the three VAICOM modules correctly, and registered the licenses, so it's just a matter of changing the settings. As mentioned, I'm willing to donate a new aircraft, campaign or map to anybody who can spend some time with me on VOIP to get this all working smoothly. I think this would be far more efficient than trying to muddle my way through it all. If you're keen to help this beginner out, please PM me. Note that I live in Melbourne, Australia, so it would have to be at a suitable AEST time (I can do it any day of the week between 11am and 11pm. Fingers crossed somebody wants a new module for DCS and can take the time to help me. Thanks in advance for anybody who can expertly guide me through configuring VAICOM and DCS so I can sink my teeth into learning the F14 and reliving my Top Gun glory days!