eaglecash867

Your machine should have more than 1 display port connector on it. The RTX3070s I have seen so far usually have at least two of them, along with HDMI ports. The video card itself usually will have 4 ports on it in some combination of DP and HDMI. Can you post a picture of the back of your computer?

The difference between a Rift S and a Reverb G2 for visual quality is huge. As for the relative importance of visual quality and performance, both are equally important, so its all going to be about balance and what looks good to you. Try not to get caught up in chasing the frame counter dragon and just tweak and experiment based on visual "feel". Sure you could get 5 more FPS out of it by sacrificing something in visual quality, but why? If your eyes don't notice the benefit of that extra 5 FPS, then it has no benefit. On my rig, with a G2, I have DCS PD set for 0.6 and SteamVR Super-Sampling set for 128%. That gives me the best experience according to my eyes, but you may find a different combination to be more suitable to you. That's all very subjective. Between the RiftS and Reverb G2, definitely go for the G2 if you can afford it. You can easily "dumb down" a G2 and sacrifice a little visual quality for better performance. But, with a Rift S, no matter what you do, you'll never be able to get it to look as good as a G2. In order to attempt that, you have to crank up DCS PD (pixel density) and/or Oculus Pixel Density, and that actually has a more detrimental effect on performance than it would if you had a headset that could produce the same effective resolution natively. I went from a Rift CV1 to a Reverb G1 (which has the same specs as the G2 I now have...the G2 is just a lot more reliable), and not only did I get MUCH better visuals, but I got better performance as well. I know that seems counter-intuitive, but that comes back to what I said about having to crank up DCS PD and SteamVR SS (which is sort of like Oculus Pixel Density). The extra up and down conversion done by super-sampling eats up a lot of extra CPU and GPU cycles. A higher resolution headset won't be as dependent on those performance-robbing technologies. Just make sure your processor meets the minimum specs recommended by HP. You'll need to know the model number of the processor. The i7 series came in a lot of different models, some of which might not be up to the task. My i7, the 8700K, does just fine with it.

Just to help you with making a decision about which VR headset to get, I would recommend getting the best headset that your budget will allow for. You can get an HP Reverb G2 and make it run acceptably on your system because there is nothing saying that you have to run it at its native resolution. You can dial the resolution down or up with supersampling to match what your current rig is capable of. Then, you'll have a VR headset that has the ability to grow with whatever upgrades you may do on your rig in the future.

No need to even worry about it, Chief. Just plug in your G2, wait for WMR to automatically recognize the HMD and boot up, then just start DCS like you normally would. Everything that needs to run will run automatically from that point forward. You'll see an exploding orb of triangles in your G2 when WMR and SteamVR link up, and next thing you know you'll be in the DCS hangar screen.

That's why I have specifically been saying "Motion Vector" to force it on in my last two posts...for basic troubleshooting purposes to make sure its actually getting activated when he's telling it to. No way to know that for sure if its set to "Auto".

If you're getting anything for FPS other than 45, your Motion Reprojection is not turned on. "Motion Vector" is a setting for Motion Reprojection that tells WMR to run Motion Reprojection all the time. That should give you a solid 45 FPS. It may go lower at times, but if its turned on, you'll never see it go above 45...it isn't possible for it to do that if its turned on.

I still have one of those too, with a 24" touchscreen monitor mounted on an inverted ceiling mount so I could use Helios profiles. Spent countless hours designing and building the thing. I think I easily spent 2 to 3 times what the G2 cost...and then VR came along. Oh well, it still makes a great, solid mounting platform for my HOTAS and rudder pedals.

Yup. VR is the "poor man's sim pit".

Try changing the Motion Reprojection setting on the OpenXR Development Tools page to "Motion Vector" and see what that does for you.

I have typically seen between 40 and 50% with an engine that isn't lighting...could be 52%...which is why I asked. Its the same IRL too, although IRL it would be a really bad (and potentially expensive) thing to let the RPM get that high without ignition. Just trying to start with the basics, and I don't see it specifically mentioned as to which engine he's trying to start. In fact, he says "engines", so maybe he's trying to start both at the same time? Or one and then the other before the first one is done? That would definitely not work. Like you said, a track would be a good thing.

I think you probably misunderstood my post. I'm just making sure he's looking at the ITT gauges during engine start. If he doesn't see that rise in ITT, the engine is never going to start. Your advice is the best though. I'll bet we could figure this out really quickly if he posted a track file. Pretty easy to see what's not set up right in the cockpit with that.

Make sure you have your main and wing boost pumps turned on on the fuel control panel. During engine start, watch not only your RPM gauge, but your ITT gauge as well. When you reach about 20% RPM, you should see a sudden spike in ITT. If you don't see that, your engine isn't lighting off for some reason.

A couple of decades ago, when I was just learning on real aircraft, I was also driving a car with a manual transmission. It took me a little while to not want to try to mash the left pedal to the firewall when I was bringing the aircraft to a stop (pushing in the clutch pedal). Luckily I wasn't yet past learning to taxi before breaking myself of that habit.

Performance is also going to depend a great deal on how high you currently have your DCS PD set to sort of "church up" the visuals in your Vive Pro. With a G2 or VP2, you'll find that you can run DCS PD to a much lower number which will help to offset the performance loss from higher resolution. When I had my Oculus Rift CV1, I was running a DCS PD of 2.0 to make it look decent. With my G2 and the hardware in my sig, I'm running DCS PD at 0.6 and SteamVR SS at 128%. I get good performance with Motion Reprojection turned on, and the visuals are leaps and bounds better than what I had with my CV1 that, honestly, suffered in performance from having to run DCS PD at 2.0 to make it look good. As for GPU, when I had the Reverb G1, I upgraded from a 1080ti to a 2080ti and didn't notice much difference at all in performance.

Wow. You sure do get offended easily. As with any conversation (which is what forums are), context is important. If you don't have that context because you haven't been following the threads, that is your fault, not the fault of the other poster. Nobody here should have to put a manifesto about what their views are on a subject with every post they make, or "correct" anything they post just to make you happy.

Don has actually been posting that information in some form or another since the day he made the decision to give the VP2 a try. Its not his fault if people don't follow the threads here. Just sayin'.

This is a longshot, but have you looked on your Windows Update page to see if your system is caught in a rectal-cranial loop with trying to download an automatic update? I've had that happen to me a couple of times. I found it by accident after having tried all kinds of the usual things you would do to fix performance issues. Nothing else I did revealed anything, and it had just started with the issues out of the blue. Its amazing how much performance it can eat up when it gets caught in an attempted update loop like that.

I remember what it was like going from a CV1 to the Reverb G1. The difference with the G1 was noticeable, but it was weird how I didn't get a "HOLY S***!" reaction to the difference in clarity. What really hit home for me was when, just for giggles, I put the CV1 back on after using the G1 in DCS for a while. DEFINITELY got that reaction, followed by "THIS IS TERRIBLE! HOW DID I DEAL WITH THIS FOR 3 YEARS?!!" LOL

Its just something HP had to add to the G2 to overcome some of the display issues that G1s were having. Instead of using USB power to supply voltage to the display like on the G1, now its the power box that provides display power. Its integrated into the G2s cable, and has an AC to DC converter that you plug into a standard wall outlet. You can just unplug the converter's cord from the power box to remove power from the headset when not using it. I think the main issue they were trying to correct with the power box on the G2 was the G1s tendency to have one or both eyes intermittently get darker. Although I did get used to it on the G1, its been really nice no longer having to deal with that issue on the G2. Also gives you an easy way to shut the headset down when you're done using it.

That's why we have VR. So we don't have to watch the doom and gloom of the news. I'll second what Don said and say welcome to the dark side. Your free cookie will be coming to you shortly. Please allow 6-8 weeks for delivery.

No problem. I was really glad that HP had to put a power box on this one. On my G1, I always left the cable plugged into my video card and plugged it in at the headset when I wanted to use it because I was really hesitant to keep unplugging/plugging in the HDMI cable on my $1700.00 video card. With the power box we don't have to do that anymore.

Another thing you can do is unplug the power box on your G2 after you're done using it. When you want to go back into VR, plug that box back in and WMR will automatically start and link up with your G2. Then, all you have to do is double-click on the DCS exe like you would if you're going to play in 2D. Pull the G2 down over your face and wait for the exploding orb of triangles. SteamVR automatically loads and in a few seconds, you'll be in the DCS hangar in VR. Heh...can't comment on getting all of the other cool stuff you have going though. Unplugging that power box seems to be a pretty reliable way of keeping the HMD from going stupid after sitting idle.

OK, so now you have learned what it means when they tell you the sale ends at 15:00 GMT, so you can plan accordingly next time. I would have loved it if my Oncologist and Radiation Oncologist could have catered to my busy work schedule, but that just isn't how a business operates...even one that gives medical treatments. I adjusted my schedule to fit theirs. It sucked at first, but I sucked it up and got used to it. I realize its not as important as a sale for video games though. Improvise, adapt, and overcome.

Right pedal turns the plane right.

Hi LaCrepe, Take a look at my link in this old thread. Now, bear in mind that the screenshots are really old and a lot of things have changed since then, but the screenshots of my DCS settings are representative of what I still use today...except for the change in DCS PD of course. I made the change to running higher SteamVR SS (the level that SteamVR automatically wants to set for your individual setup) and lower DCS PD after reading about why SteamVR picks what it picks for your rig (barrel distortion). After some experimentation with it, I have found the combination of those two things to be beneficial to how things look while still getting the same performance. I don't spend much time chasing FPS counter dragons. What I do to test performance is to fly low and fast, while maneuvering hard, and look for a minimum of ghosting in ground objects while looking to the side as I fly past them. One DCS setting that I found makes a HUGE difference there is Cockpit Display Resolution. I have mine set to the lowest possible level. The only thing that seems to degrade is the quality of the reflections in your mirrors. I find that I don't spend much time staring at my mirrors, so its not even missed.