eaglecash867

Hi TOYKILLA, I've been wanting to try that to see if there are any advantages. What adapter are you using to accomplish that?

It was the Inateck PCIe card that worked for me. I started by trying to use my existing Amazon Basics external, powered hub, and I still had issues. I think my external hub is just short on power when it comes to VR, so I was looking into buying a different one. But, I settled on the Inateck based on information posted on the Oculus site. Worked great with my Rift, and works great with my Reverb. I see some guys even have reliable operation using their MoBo ports, so I guess its another case of everyone's rig being different. Different peripherals attached to USB ports, etc. To sort of echo what Majapahit said, if it ain't broke, don't fix it. But, if it is broken, an external hub seems like the best place to start. I already had one before VR just to keep my HOTAS happy. Had one since the Falcon 4.0 days. :D

This is how I mounted mine in my little roll-away "pit". Black ABS pipe and flanges.

I've had this issue in the A-10C also, so I imagine the F/A-18C's TGP causing lag in VR is for the same reasons. I have my cockpit displays resolution set for 256, which has gotten rid of most of the problem. I don't spend any time looking at my mirrors in the cockpit, and I haven't noticed any quantifiable difference in my ability to acquire targets on the TGP or MAV screens between 256, 512, and 1024. So, 256 works for me, but I still have issues when I have either one (or both) displayed while flying over large cities. My solution to that, so far, has been to just call something else up on the displays that doesn't show a video representation of the outside world. I leave the displays on those non-demanding pages until I get to the IP. Seems to work well that way, as long as the mission doesn't involve striking targets in a large city. :D

The A-10C does that for me too, unless I immediately take my feet off the rudder pedals once I get airborne.

I agree. Sometimes I think the objections to SteamVR might be caused by people following the old, convoluted method of loading DCS in SteamVR. Loading SteamVR, going to the cliff house, pushing a button (not sure what) button, clicking here, then there, etc....All of that still works, but its not even necessary anymore. Now its just a matter of plugging the Reverb in, waiting for WMR to recognize it, and then starting DCS. Everything else happens automatically, so its really not much different than the process was for the Oculus software. I just happened to discover on accident one day that you don't have to do all the other stuff. :)

A good HOTAS is usually enough for the earlier aircraft. They're all pretty simplified, so none of them really have any of the advanced aircraft interfaces like the Mirage 2000C does. The Su-25T was the only one of the bunch that even had an advanced flight model. DCS has come a long way since the LOMAC days. If you like the challenge of everything in the cockpit (except the IFF) being under your control, I highly recommend the A-10C. Its still one of the deepest, most detailed modules, and everything is clickable. It even has a recently-updated cockpit.

I concur with stuarteaston and some1. I don't think WMR headsets have that ability yet, and we know how willing Microsoft is to give users more control of their own equipment. Hopefully, if the DCS team makes native support a reality, they'll make it an option we can select in the VR settings menu.

Hi pbrt, The Su-25T and FC3 planes came before the clickable cockpit, so the mouse pointer won't work with them.

If anyone is planning on using SuperSampling of any kind, I think native support would leave us with just the DCS PD setting. From my experimentation, DCS PD seems to be less efficient for some reason.

Here are some screenshots of the settings I'm running with my Reverb. The only thing that I have changed is the SteamVR SS. Until the F-16 module came along, setting that above 100% didn't seem to yield a noticeable improvement in clarity (flying mostly in the A-10C). But, when the F-16 module came along, I did some experimentation and found that I saw a pretty massive improvement in clarity when I went from 100% SS to 150%. I kept everything else the same as it is in the screenshots, and I get good performance with very rare ghosting or stuttering. https://imageshack.com/a/A7xo/1

DerekSpeare pretty much has it all covered in the thread he linked about VR. I'll just add a quick link to my post about moving and saving your view position. Same information, just presented in a different format. https://forums.eagle.ru/showpost.php?p=3830595&postcount=2 Which VR headset are you using Justin1NTime? One of us on the forum should be able to help you with getting the most out of it in terms of clarity and performance.

Really? Point that thread out to me, please, if you would be so kind. Why make a whole new thread if you were responding to one that already exists? You are taking something said to you in private and editing it to fit your argument, buddy. Putting different statements together without keeping them in their proper context. I'm sorry, but that's not going to fly. Everyone here, including you, has seen my PUBLIC POSTS that say that ghosting is rare or occasional. Your editing something that nobody else has seen themselves isn't a good way to make your case. Another half-truth. You're leaving out the fact that, in that very same chain of PMs, I told you my reasons for not wanting to use FPS VR. I said it appeared as if I would have to use the hand controllers, and didn't want to do that. I also told you that I had thought about trying FPSVR, just out of curiosity to see the actual numbers. As I have said here many times, in many threads, I don't spend much time looking at FPS counters. If I don't see a difference with my eyes, an FPS counter isn't going to change my mind. I also put forth the theory (more like a wild guess) that maybe FPSVR could be using some resources. That's a pretty vague list, but the key thing here (which I also posted a screenshot of in my thread) is that I run my Reverb at 100% super-sampling, not at the 180% you need to hit the native resolution. I've been very clear about that as well, so I'm still not quite sure what's tripping you up, GunSlinger. I have also very clearly explained that I didn't see a need to run things any higher than 100% because I saw no visual benefit to doing so. Sure, we get things slightly clearer in the distance, but to me it wasn't worth the performance hit. I'm coming from a Rift CV1, and again, have made no comparisons between the Reverb and any of the less powerful headsets you mentioned. I started my own thread on the subject because both you and Aurelius asked about what my settings were, and there was so much trolling going on in that thread you both asked me the question in, that it got shut down. I was very clear about my settings, with photographic evidence, for the very reasons you state you were trying to stop by starting this thread. I don't want to waste anybody's time, so if you didn't try the settings I had in those screenshots, the only person you can blame for your wasting time is you. Nothing frustrates me more than eggheads who go on forums, telling people things like "Edit your registry key for this..." simply because they had it work once, so I try my best not to be that guy. Thanks for that, but I don't recall saying that I didn't know why it was happening. I know why its happening, just don't seem to see it mentioned much by anybody. Just trying to be helpful by pointing out my observations. Like I said before, my previous thread was done in the interest of full disclosure. There was nothing left out or churched up to try to convince anybody of anything, and you just told me here that you were refusing to turn your SteamVR down like I did, so again, you're comparing apples to oranges, and telling me I'm wrong. :doh:

Hi YoYo, The FPS fluctuations definitely sound like motion reprojection isn't turned on for some reason. I know you've probably already done this after making the changes to the setup file for WMR, but make sure you exit all of the SteamVR stuff and WMR, and then restart them for the changes to take effect. I only say that because I made that mistake a couple of weeks ago, and forgot to restart everything. Here's a really good resource for information on changing that file to enable reprojection. https://docs.microsoft.com/en-us/windows/mixed-reality/enthusiast-guide/using-steamvr-with-windows-mixed-reality Also, a thread I started a week or two ago. It has screenshots of all the settings I'm using to give me a good experience. Feel free to take a look. https://forums.eagle.ru/showthread.php?t=253988

I couldn't agree more, Toykilla. Before VR, missile and AAA avoidance was a real source of frustration because there is such a disconnect with your natural senses and instincts when you're on a flat screen. Air to air combat was also something I never found to be all that much fun because it was always a non-stop turning fight where you had to visualize how you would defeat an opponent in 3 dimensions, when all you could see was 2. VR has completely changed that for me as well. Its a really awesome experience if you're not looking for reasons to be disappointed in everything. :pilotfly:

Yes, this is true. I'm sorry, but where did I say otherwise? I posted all of my settings in screen shots a week or two ago, and you're just now noticing them? I have also been pretty clear about the fact that ghosting is not gone completely. I have referred to it as "very little" or "rare". Yes, something is wrong with the DCS engine, so I found ways to work with it and make a tolerable experience for myself. I shared my settings for that purpose, to help others who don't simply want to fold their arms and say "it can't be done". It can be done, but we have to deal with reality and make sacrifices until the Holy Grail finally shows up. VR experiences are highly subjective, and I have always encouraged people to buy from authorized distributors with good return policies in case their experience didn't match my own. I'm not here to convince anybody of anything, just to share the settings I'm using for my VR experience. Its very much a "you do you" situation. So, in other words, you were targeting me with your post. I've always given full disclosure about my settings so as NOT to mislead anybody. Unfortunately, we have to deal with the reality of the situation by making sacrifices of things that some of us don't feel are all that important anyway. The Reverb image quality, AND performance is leaps and bounds ahead of my CV1. How it compares to the latest, cheaper offerings, I wouldn't know, and have made no claims to the contrary. As I have said before, I can only see what I see, not what others think I should see. With all due respect to your resume' that you keep feeling the need to mention for some reason, Richard Quest has 18 years of real world experience as CNNs Aviation Correspondent, and even wrote a book on the subject. That doesn't mean that those of us who are hands-on in the aviation world don't roll our eyes every time he speaks. Just sayin'. :smilewink: The problem with your "clearing up misconceptions" and "100% incorrect information" is that you have not disclosed your test conditions like I have. The information was all there, bud. All you had to do was read it. Others have. Some have been happy with the results, other's haven't due to personal preferences for what they want from the experience. Simply saying "it can't be done" when you don't disclose the settings you're using isn't really "clearing up" anything. I'd love it if I could max everything out in DCS in VR, but the reality of the situation is that it just ain't there yet. So, if we pair our settings down a little bit, we can all get the best possible experience. The way I see it is that the technology will improve, and getting a VR headset that has the headroom to grow when that improves just seems like a better investment. But, again, its not correct or incorrect, its a personal preference, and I have been very clear about the settings that I'm using so I don't mislead anybody. :thumbup:

Oh, its not completely gone, but extremely rare. :smilewink: I agree with you about this all being totally subjective, just kind of had a little bit of heartburn with the implication by the OP that I didn't know what ghosting was and was spreading misinformation. The comment was directed at me, based on some PMs I had exchanged with the OP, all of which seemed quite civil to me. Quite frankly, I'm not sure how someone can keep their focus so sharp on an Su-27 passing them with a 700 knot closure rate that they're able to see ghosting so badly that it ruins everything for them. The thing gets extremely small in a mere fraction of a second. :) I don't usually fly air-to-air, but I was able to keep eyes on the best I could for the closure rate and didn't see ghosting. Then I was able to climb, turn, do a lag pursuit and kill him, knowing exactly how I needed to maneuver to get into an advantageous position because I could see him so much better than I ever could on my CV1. That was a really fun experience though. I had no idea that the F-14 was such a beast in BFM, it looks way too huge to be so nimble. What aircraft are you usually flying, Aurelius? Since I fly the A-10C mostly, I may be incorrectly thinking that you're flying it too. When I had my CV1 and was getting really bad ghosting when I went without the shaders mod, I did a lot of experimentation with what the biggest performance killers were. One of the biggest performance killers, as it turns out, doesn't really have anything to do with graphics settings, although the problem is aggravated by one of them. The biggest performance killer is when you have video displayed on your MFCDs from either the TGP, the MAV, or both. Even to this day, just out of habit, I put both screens on a non-video page until I get to the target area. If I have one or both displayed shortly after takeoff in the In The Weeds mission, its stutter/ghost city. Ironically, in the mission, if I trade my A-10C for an F-14B, I actually get better graphical performance, even though my aircraft's speed is a lot higher. The MFCD video problem is also the reason I turned my "cockpit displays" setting down to 256 a long time ago. Haven't really noticed much of a difference in my target-finding abilities between that and 1024, but then again, there's a lot going on and you don't really have time to get fixated on any one item in the cockpit. Something I have not figured out how to get clearer in the cockpit though, is the CMSP panel. Unless I lean in, the text on it is always smudged no matter what my settings are.

Well, what can I say? I posted all of the settings I am using for my Reverb which results in very rare ghosting. If you choose to go higher than those settings that I posted for all to see, right on this very forum, in the interest of full disclosure, then you're going to have problems. Ghosting is the problem that showed up so badly on my Reverb in the beginning that I almost returned it out of frustration with the performance. Then I discovered that the 188% SS thing we were all told in the beginning is a lie. Mine works just fine, with rare ghosting in dense areas, with the settings I am using. If you use higher settings than that, its not a direct comparison, and obviously you're not going to get the same results. Let's try comparing apples to apples before we start accusing each other of spreading FUD. :D

Have a look at my imageshack link in my thread here: https://forums.eagle.ru/showthread.php?t=253988

I really haven't been looking at frame times, but the sudden spinning of the view seemed to happen with the Reverb in the same areas I used to experience brief pauses with the hourglass when I was flying with the Rift CV1. You might be on to something with what you're seeing with frame times. My stable version I still have at 2.5.3 because of all the performance issues and AGM-65 issues that were introduced with 2.5.4. The Beta I've been keeping up-to-date though.

Yup. The cameras only control lateral movement in VR, rotational movement comes from the internal sensors. I tried cleaning mine and so far so good. No smudges on them, but there was some dust. Still early though, the theory hasn't been extensively tested yet.

The only person who seems to be passing judgment on anybody else is you. I don't have a problem with your choosing not to participate in VR. I just think your argument is a self-defeating one. Relax buddy. Try not to get so offended. :D

Just a shot in the dark, but have you tried cleaning the camera lenses with a microfiber cloth? Maybe you inadvertently touched one or both and got a finger smudge on there? I haven't looked at mine yet, gonna go do that now.

Hi Jason, I've had this problem recently too, but it didn't happen at all yesterday. Yesterday was different from my usual weekend routine in DCS though. I was flying a different aircraft, in a different scenario. What aircraft are you flying usually? Have you tried other aircraft, scenarios, terrains? I have seen exactly what you're talking about, and I agree that it was only in the last few updates that this became a problem. mpdugas, so many bad reviews on Amazon are from people who didn't have any basic troubleshooting skills. Most of the problems listed are caused by improper setup and hardware that's not up to the task. Yes, there are legitimate issues, such as the fragile, unreliable nature of having not just 1 cheesy DP connection, but 2 of them. I had those issues myself, and they were fixed with a new cable from HP. I knew this was essentially experimental technology, but the resolution increase made it worth it to me to participate in the development, troubleshooting, and growing pains that were inevitable. Overall, I'm so much happier with the Reverb from both a performance and clarity standpoint.

Would that be called a self-fulfilling prophecy, or a self-defeating one? There's currently not enough interest to sustain advances in VR technology, so the solution is to add to that problem by not participating in it. Got it. :thumbup: