eaglecash867

If you want to get a little detail on how these systems work, civilian aircraft have a similar system that has evolved over the years from analog to digital. The analog systems were called flux detectors/flux gates, and the digital systems they have now are called magnetometers. Some systems even have other sensors, such as OAT and GPS all contained in the same "antenna" and those are called Remote Sensor Modules. They all have the same purpose of providing more accurate navigation info to systems like the AHRS.

Yup. Many "individuals" have "suspected" Elvis may still be alive as well. Must be true.

I pre-ordered mine in February to take advantage of the discount that was being offered, and then moved on with life, knowing it would be several months just like it was with every other EA that I pre-ordered in the past. Lots of other things going on, and never enough hours in the day to worry too much about this one thing. No worries.

Yup. Been saying this for years in those threads with people bagging on VR because "I should be able to spot targets at XX.X nautical miles, and I can't do that in VR like I can on my monitor" The truth is, it is unrealistically easy to spot other aircraft, as well as ground targets, on a 2D monitor, and the current generation of VR is a little worse than reality...but not as much as people sometimes think. Not a pilot myself, but I fly pretty regularly in the right seat during avionics test flights, and many of those test flights involve functional checks of TCAS, TIS-A, or TIS-B systems. All of them tell me exactly where to look in the sky, but just like it is for you, I'm not spotting anything at DCS 2D monitor ranges.

I know I'm late to the party on this, but randomly switching to F-key views sounds like maybe the G2s microphone is picking up a noise that it is interpreting as a voice command maybe?

When I had my Reverb Pro G1, I used a 14mm VR Cover replacement pad that was actually designed for an HTC Vive. With the G1, for some of us, there was a problem with not having enough eye relief inside the headset, which made the edges of the lenses visible. That 14mm pad (which replaced the HP pad) worked really well for me. Not sure there was much impact to FOV in that case, since before I installed the pad I could see those lens edges.

Get the best VR HMD that you can afford. You want one that is capable of the highest possible native resolution your money can buy because you can always "de-tune" the graphics settings to match your hardware. If you get one with a lower native resolution, you end up having to use more and more supersampling to make it look decent, and the whole supersampling process is the biggest performance killer for any headset/GPU/CPU combination.

Me too. In all of my years of flying in various aircraft, including some fighters, IRL, I can honestly say that I have never once put my head against a window or canopy. Because of that, I have never done it in VR either. I think you, me, and several others here have tried to explain on several occasions why having your head stop in the game, while your real head keeps going isn't a good thing to do in VR because of how it would induce motion sickness in most people. But, I guess some are just determined to focus on things they don't like. I just enjoy the hell out of DCS and although there are lots of things that could be better, I just avoid focusing on those things. There really isn't anything currently available that does everything well, and DCS just does well with the things that matter to me. Heh...not big fan of clear air turbulence anyway after being knocked unconscious by it once because I didn't have my harness cinched down tight enough. Also kinda hate wind sheer for even worse reasons. Cab summed everything else up with just a few words about expectation management. Its kinda what I've been harping on for all these years when it comes to posts that all seem to go "I should be able to do [fill in the blank]." Well, there's always going to be the sim we want...but this is the one we have, we have to work within the limitations of it and our equipment.

I still have the old G2 cable so I don't know for sure, but the Reverb still has a pretty high power requirement on its USB connection. I haven't found powered, external USB hubs to make any difference with that. They still don't supply enough juice to run everything reliably. But, what I did find, way back in the Oculus Rift days, was that a powered USB card that plugs into your motherboard's PCIex4 port as well as an SATA power cable from your power supply overcomes USB power consumption issues with VR headsets. Its a problem that all VR headsets have to one degree or another, and who it causes problems for depends on your rig, as well as how many things you're already running on your motherboard USB ports. This is what I bought that solved my Oculus Rift issues, as well as solving my Reverb G2 issues when I installed an RTX3090 that no longer has the built-in, powered USB-C port like the 2080s did. https://www.amazon.com/gp/product/B00FPIMJEW/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 If you get one of these, just make sure you remember to plug an unused SATA power plug for your rig's power supply into it, and DO NOT install the drivers the instructions tell you to download. The card actually works with the default drivers that Windows will install for it...it doesn't work with the card manufacturer's drivers. Also, forgive me if you have already said so, but does the G2 only have problems with DCS? Or does it have problems with other VR titles as well? Are you going through SteamVR for WMR to use the G2? If you are, there is a possibility something got borked in your SteamVR installation. I had that happen one time, and that also would cause random crashes and blue screens. I reinstalled SteamVR and it fixed all of those issues when I had them. Just look up how to do it on Steam's support site. They walk you through how to reinstall it, while retaining all of your library titles and game settings.

From my observations, increasing pixel density does very little to correct shimmering effects and comes with a major performance hit. I run MSAA of 4X on my machine, with DCS PD set at 0.7, and Steam VR set to whatever it defaults to for supersampling (haven't been on it in a while, but I think it was defaulting to around 150% last time I looked). Runs well and looks as good as it possibly can on my Reverb G2. If I push anything higher, it starts to impact performance, and I don't see any visual benefit from it.

Move View Left: Rshift+Rctrl+Num4 Move View Right: Rshift+Rctrl+Num6 Move View Up: Rshift+Rctrl+Num8 Move View Down: Rshift+Rctrl+Num2 Move View Backward Rshift+Rctrl+Num/ Move View Forward: Rshift+Rctrl+Num* Save Position: Ralt+Num0

Heh...I pulled up next to a Tesla S this past Friday night when I had just been to a concert that put me in a nostalgic mood for my teenage drag racing days in the 80s, but me and the guy in the Tesla had a brief drag race (I'm driving a Dodge Durango R/T with a 5.7 liter Hemi). Well...he not only smoked me...but smoked me BAD. I guess the 0-60 spec for that car is 2 seconds flat! YIKES! But, I didn't feel all that bad about it. Afterall, he spent over $150,000 for his car...mine cost me 40. No hatred for Pimax here either. MAXSenna said it better than I could have, no other manufacturer represents their resolution that way...because its not correct to do so. That's what I have a problem with. Not trying to rationalize anything or change anyone's minds.

Just giving a very simple explanation of my viewpoint, which is getting misinterpreted over and over. Its just habit from my career. If I have a salesman come into my office with a new avionics product he wants me to buy into and promote, and during his presentation, everything he says doesn't align with industry standards of terminology? I'm going to take his business card and say "Thanks for stopping by.", and that's going to be it. I won't be buying into his product. I understand that its a different situation though, because that scenario is literally life and death. But, that's why it matters to me, just hard-coded into my brain...that's all. If it doesn't matter to you, I'm good with that.

The same image is being displayed in both eyes essentially, so yes, it is a misrepresentation. I don't get to call my 4K television an 8K television because I'm watching it with both eyes.

Yup. Right there with ya. It makes me doubt their actual knowledge and abilities when it comes to display technology...and I sure wouldn't ever trust any future claims they make about anything. We would have no way of knowing what terms like "eye tracking" and "foveated rendering" mean to them, but it probably won't have anything to do with what those two things actually are. Kinda reminds me of all of those cosmetics commercials they have on TV where every few months there's some made up buzzword "chemical" that everybody just has to have...only to have it all disappear from advertising just as quickly. LOL

Its really not even that complicated. When you're in VR, the image isn't spread between two eyes (with one half in one eye, and the other half in the other eye)...it is the same image on each screen, offset a little bit for a 3D image. Even if 1 panel in the headset is a true 4K panel, the headset is still going to be a 4K headset (or possibly a 4.8k like you said), not an 8K like Pimax claims. That's all I was trying to say.

By the logic of Pimax, if I watch TV with both eyes open, I actually have an 8K television.

I have my cable secured with Ty-Raps in a couple of spots on the strap, and I have never gotten in the habit of flipping it up. I just take it straight off, or push the whole thing up onto my forehead if I need to see something in the real world.

We'll just have to agree to disagree on that one.

Heh...I guess it all depends on how much ambient noise you have in the room and how much hearing loss you have. When I had the volume turned all the way up for the G2, I could barely hear it, and there was definitely no depth or dynamic range for me. Anyway, just putting that out there as a possible drawback to off-ear audio for people in similar circumstances.

Off-ear audio was the main reason for my removing the off-ear speakers from my G2 and just using my Bose QC35s and a Avantree Bluetooth audio dongle. Don't know if its the same for the system in the link, but I couldn't deal with off-ear audio...I couldn't hear anything with it.

To keep the Oculus app from running automatically, you can set the Oculus executable file to "Run as administrator". Once you have it set tht way, any time you do actually want to run the Oculus software, you just run it manually, and now it will pop up a window asking if you want to allow it to run. I read your other thread as well, and I feel your pain. I almost sent my Reverb back for the same reason. As it turns out, the main performance killer was the Pixel Density setting in DCS. With your Oculus, you were probably running a higher PD setting like I was with mine...I think I was running mine at 2.0. With my Reverb G2, I am currently running DCS PD at 0.7, with the SteamVR rendering factor set to 150% (I think...not home at the moment to confirm that). Checking those settings and getting them to something similar on your rig should take care of a major part of the problem. The other problem is that WMR headsets don't use ASW like Oculus headsets do. WMR headsets, through the SteamVR app, use Motion Reprojection. For dealing with that, have a look at my post here: Once you get those things squared away, you shouldn't have to ever mess with them again...except if you want to experiment with getting more eye candy. At that point, you'll find yourself much happier than you were initially. Mine runs great now.

Thanks for the info, RackMonkey. I'm not using OpenXR at the moment, so I haven't seen what Motion Reprojection does with that. I just read in another thread, however, that it may be an issue with AMD cards.

Performance and quality in VR are also very subjective things. Try not to get too wrapped up in what other guys are saying about their performance and quality with a Pimax versus what you're seeing with your G2. You say you're getting 40 FPS on your G2. Is there a reason you're not running Motion Reprojection on yours? You might try turning that on and seeing what that gets you for a performance gain. Your frame counter will lock at 45, but remember that Motion Reprojection's interpolated frames aren't visible to the counter, so the frame rate your eyes perceive will actually be between that 45 FPS and 90FPS.