eaglecash867

I'm running 4X MSAA with my Reverb and get very little shimmering, just have to keep my SteamVR SS at 100% to compensate for the performance hit from MSAA. That's OK now though, since 100% SS finally gets us close to native resolution on the Reverb.

I think he's asking about passthrough that will allow us to see our real world surroundings in game when we want to. Could be wrong though. :)

I run 100% SS, 4X MSAA, 16X AF, with shadows off and get good overall results for my liking. :)

I think on the Amazon link, in the questions section, there was somebody who asked if it would fit their Vive Pro. The answer he was given was that it doesn't fit the Vive Pro. Definitely fits the Reverb though. Doesn't have the alignment pegs like the HP facepad does, of course, but the hook-and-loop interface material is enough to hold it securely in place.

It also helped quite a bit with the problem we both have of being able to see the screen edges. It doesn't completely eliminate the problem, but it reduces it to a level where its barely noticeable.

Yup. Fits perfectly, right out of the package. I have my nose piece removed, but I don't think it would make a difference with fit. Just have the nose piece removed to help keep cold screens from fogging up, with the added bonus of being able to easily peek at the keyboard when I need to.

Just go to Amazon and buy the VR Cover facepad replacement for the HTC Vive. It fits the Reverb perfectly, gives slightly more eye relief, and is much more comfortable than the stock HP facepads. They're 29 bucks for 2 of them. https://www.amazon.com/gp/product/B074V7MV1R/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 Heh. Funny that you called it the fake leather face gasket. HP claims that its real leather, but it definitely isn't.

Same thing has happened to me several times recently. I figure it must be an issue with SteamVR, so I try to start it again, and I get an error message in SteamVR telling me its already running. Task Manager shows no SteamVR running. The only way to get it back is to restart my computer. This only started recently, and it happens with VR games other than DCS as well. So, its not a DCS problem. I think something got borked with the version of SteamVR that came out recently.

https://forums.eagle.ru/showpost.php?p=3830595&postcount=2 Just be sure not to forget the most important command at the bottom of the list when you get things adjusted correctly using the commands above it. ;)

Me too. If it looks good to me, I'm happy. If it doesn't look good, I tweak it until it does. No need to go chasing dragons.

No offense taken here. Just adding that for the purposes of bringing a little levity to the thread. For aircraft with real, lifesaving missions, I've seen two extremes there. We have air medical flight crews that squawk everything, and then we have the ones that just "live with" things (sometimes really important systems) and we end up finding them on inspections. When we mention it to the flight crew, one of them always says, "Oh...yeah...its been doing that for as long as I remember." :lol:

Heh. Its often the factory fresh aircraft that are the worst. They make me wonder "How in the hell did this thing get certified?" :D

Yup. Going beyond 1:1 in VR definitely increases the upchuck factor. Just keep working with VR a little bit at a time and you'll increase your flexibility. Looking down at things on the side panels in the cramped cockpit of a military jet is always a little uncomfortable IRL, and I think DCS models that pretty well, except for the fact that you can't really do things by feel and muscle memory in DCS.

I don't have to imagine it, I get to see it almost every day at work. :smilewink:

Not really experiencing performance issues myself with 2.5.6, but some of the other glaring annoyances with it are enough to make me glad I have 2.5.5 stable installed as well. From my experiences with the various versions, I'm starting to think that if the version number ends in an even number, its going to have issues. The odd-numbered versions, on the other hand, seem to have all been reasonably trouble-free from the day of their first release. Heh, not really much into numerology or anything, but I can't deny the observations I've made. :D

VR has the same up-down issue, but that's caused by the default viewing position being just a little bit too far to the rear. Are you able to get the whole thing in view in 2D by adjusting your longitudinal position in the cockpit?

I fly in VR and I can see the whole HUD.

I get this too on my machine, but it only seems to be on the loading screen when first starting DCS in WMR. Once its done loading, the message goes away, and its all back to normal.

That's a WMR thing, and its very annoying. If you do a Google search on it, I think I remember seeing a registry edit that essentially increases the WMR timeout delay to an infinite number. You just have to make sure you don't leave your headset plugged in when you're done with it for the day so you don't get burn-in damage to the Reverb's screens. Edit: Found it. Here is the link to the registry edit. As it says in the link though, edit the registry at your own risk. https://forums.hololens.com/discussion/10152/deactivate-sleep-function-on-windows-mixed-reality-headset

Confirmed that setting oxygen concentration to 100% makes it go away. Also confirmed that with oxygen set to normal, ringing also shows up when in a gentle climb and airspeed falls to 170 knots. Definitely not random, it is reproducible, but the conditions that cause it make no sense at all.

It depends on what I'm trying to accomplish. Once I'm somewhat comfortable with a new jet and its flight/performance characteristics, then I start learning to do cold starts and get deeper with learning its systems. Why bother to spend time learning all of that stuff only to find out you hate flying the plane for one reason or another? I also use quick starts for testing settings, as well as seeing if I can duplicate problems other people are seeing, and trying to find the exact conditions that cause those problems. That being said, when I like what I'm flying and feel semi-competent at flying it, I always do cold starts.:D

That's good to read. With the 2.5.6 update, the accuracy of the GAU-8 seems to have taken a step in the wrong direction, so its good to see they're working on it. :)

:thumbup:

I get the ringing at 410 knots, and its only in the P-51D. The TF-51D doesn't appear to have the issue. I'm usually unloaded, in a shallow dive to pick up speed, so I don't think this particular ringing is caused by negative G.

I have been able to consistently reproduce this when airspeed reaches 410 knots. Not sure what its all about, and it doesn't happen in the TF-51D, just the P-51D. I haven't tried timing it because it seems to start going away the faster I go, and fades completely if I slow back down to 380 knots.