Justin1Ntime

@Bazz_Mulder I have a 13700k with a 3080TI and 6000 DDR5 RAM with a 2TB 980Pro M2 Drive. I was running most everything on medium except Textures, Clouds, Water, on High with MSAA at 4x. I was getting about 35 FPS and using OTT I put that to 30Hz and a RR of 1.4 at 90hz and it was really smooth. I decided to return the headset. I didnt even make it the full 30 days before I had to return it. I played more than a few hours in single sitting, and it became very very uncomfortable to the point it hurt my forehead. That red forehead on youtube reviews is legit. Its not even the fact that its red. I get that from the Q2 around my eyes. The Pro started to hurt after a while. It just wasn't worth it. The color, lenses, and weirdly, the open bottom are all it had going for it as far as DCS is concerned. I never had an issue with the battery life either. I used the link cable. I might try to mod my Q2 to open up the bottom so I can see my body. The visuals really did pop but after a few hours it felt like my forehead was on fire on a long flight. I will hold out for the Q3 and if that fails, I will just suck it up bite the bullet and buy the Aero and steam components to make it work or if the prices of GPUs ever come back down, a next gen GPU to take full advantage of the headset I have now. I would say if you can return it, it cant hurt to try it. You might have a better experience than I did. This is my experience and others have a different opinion than I do. If this headset was 500-600 I would totally keep it and this would be a happy no brainer to scrap my Q2. I put on my Q2 for the first time in 2 weeks and already miss those pancake lenses and the bright colors. I feel like everything is washed out and now. There is a noticeable difference. They are really the way to go for any modern headset going forward.

Agreed on the Overpriced comment for sure but to be fair I am not using half of the capabilities of this headset. This was not designed with SIMs in mind. That was very clear when I bought it.

So, I did it. knowing I have a 30 day return window, I went ahead and purchased the Oculus Pro. Here is my review. One thing to keep in mind is that I have not had any other devices other than the Quest, Quest 2, and now the Pro and I don't play wirelessly as I am trying to get the best visuals. This review is my opinion only for DCS as I don't play anything else in VR or do any kind of VR productivity. Also, I have not used WMR or any other software to get my headset connected to my PC other than Oculus. First let me get the bad things out of the way. Comfort is Meh... Totally subjective so take it with a grain of salt. I knew it was on my head the entire time just like all the other Oculus products. It is half empty half full type of decision. I don't see any advantage over any of the other Oculus products. Surprising I see a bit more of the screen door as I think it might be the added clarity with the new lenses. Not much at all and I have to look for it and only on a white background, but I did seem to notice it more on the Pro than the Quest 2. Not a deal breaker for me coming from the original Quest. I would not let this fact be the sole decision on buying this headset. (See Pros section) Price - yeah even at the discounted price it's still a hard pill to swallow. If this was $300 cheaper It would be a no brainer. Should I just spend another 1500 on top of what I spent already and get the Aero? Its really hard to justify for somebody that is only in the cockpit 3 times a week for a few hours per session and does not own the base stations or valve controllers. Putting on the head set sucks. No swivel or tilt. The side blockers with glasses suck when putting it on. I have to untangle them as they get caught up in my glasses frame when I put on the headset but worth it if you read the PROs section. Just a major annoyance. You will have to use the Oculus Tray tool to get the most out of this headset. You can't just put it on and go. You need to adjust the settings (assuming you have a high-end GPU). When I first started using it, I was like WTF this isn't that great but after some tweaking, it made all the difference in the world. No Display Port - Not much to be said here we all know that this means. Now let's look at the PROs section. OMG the lenses are amazing. Coming from the Oculus family and putting these on I just love the fact I can move my eyes instead of my head now. I am not going to lie. Every headset should have pancake lenses going forward and if they don't it's a firm pass in my book. I love the fact that I can look at my gauges and not have to move my head (within reason that is). The image was really clear (again why I think I could see more screen door as mentioned above), and the colors really seemed to pop. I looked over at the F16 next to me and I was like wow this is cool as hell. Resolution is lacking but the image really looked better than my Quest 2. The internal Speakers are way better than the Quest 2. So much so for DCS I quit using my headset. Are they the best... No. but for sure an improvement. Here is what I think makes this headset. This just wowed me like no tomorrow. I'm still blown away when I am flying. I was on the fence about it letting in so much light. That the headset sits off your face. So, at first, I didn't use the include blockers and it broke the immersion. I could see all the walls around me when making a turn or looking around. it just felt really weird. Here is where things changed for me. So, I have the Winwing F16 stick and throttle and when I put on the blockers, I can't see the walls anymore, but I can see my body and Winwing setup when looking down with my eyes. Being the Winwing works like the real F16 setup, it actually looks like I am in the plane as I see my body and stick where it should be in VR. At first, I laughed because I was in my PJs flying a F16 in my socks but if you take the time and really line it up blending physical and VR, when I move my eyes down, I feel Im in the plane. I see my body on the seat. I had to test this, so I went back to the Quest 2 and sure enough I now feel like I am looking through binoculars with the Quest 2. Prior to the pro I never felt that way. Plus, I can't see my sick, throttle, and body anymore in the Quest2. It just wasn't as much fun. Final Thoughts Personally, I was waiting for the Quest3 and got bored as the Aero was not going to happen any time soon. Now I am in bit of a pickle as If I keep the Pro, because I found that I like it, I am on the hook for 1100 and if I return the Pro, I am having a hard time going back to the Quest 2. Another couple hundred could land me a 4090 instead of a Pro wich is a dilemma in my book. I mean I put the Quest2 on today and did an air-to-air campaign and took them off as I was annoyed by the lack of immersion and the small sweet spot, but I am sure I could get used to Quest 2 again given some time, I guess. And what happens when the Quest3 comes out after making a 1100 dollar purchase? It's all a role of the dice, I guess. TBH, I did not like the Pro at first but after a few tweaks with my physical and virtual setup now I am really struggling on if I should return it or just enjoy the 1100 ride for as long as it lasts. I have one more week to decide and its NOT going to be an easy decision.

Quck update. I just got a boost in FPS and the judder is "almost" gone. I downloaded the oculus tray tool (Quest 2 owner here) and turned off ASW and my game is now running really smooth. I am glad to say 99% of my problems have been fixed without having to upgrade to a 4090. So much of it had to do with the ASW setting and my old CPU. I did try to overclock my CPU and GPU to see what would happen and it just made things worse. My FPS went up by 2 but so did my judder and stability fell drastically. It wasn't worth it. The best settings I found where to not try to overclock. DCS Graphics on "High" 13700 K running at stock 3080TI running at stock Quest Running at RR of 1.6 DDR5 Ram Running at 6000

Just an update. Finally got around to upgrading my PC. I ended up going with 13700, DDR5 6000 and what a difference. My FPS went up, My GPU is a constant 97% utilization. So I guess consider it confirmed @edmuss @M1Combatit was a CPU bottleneck. You where spot on. It was just too old for this type of game.

Didnt even think about that. will give it a try this PM

@VampireNZLove the video what a difference in landing techniques. my newest problem is keeping it straight. I use the pedals/rudder which work great at speed then I hit the nose/wheel button and 70ish and then it looks like have have been drinking since 7AM

Wow thanks for the pics and advice everybody. After a few more runs I am now able to land and have plenty of room. @VampireNZ The pics did help. There was a ton of great info in the thread. Thanks much. I agree with @silverdevil coming from the hornet where you slam it into the ground this was much more of a challenge to try to do it right.

I am using briefing room to create missions. One of the briefing room mission options is to have something else laze targets on the ground for you. I am looking at the way point and I don't see any blue ground forces. I don't see any way point options that have been set. When I go to quick coms I have the option under "other" then select the way point you can ask to designate target with a laser and sure enough they do. What is doing that? When I open it in mission editor I cant find anything lazing the target. I don't see any drones, people, vehicles, nothing. What am I missing here and how are they doing this in mission editor.

I am between 175 and 190 touch down speed. I am aligning the 2.5 deg line with the end of runway and aiming FPM at the threshold and I am holding 13 deg the whole way I think. come to think about it, I point the nose up but not sure what degree it is. I do know many times I hit the tail on the ground trying to hold it up. I will have to pay attention to validate it is 13 though as maybe its 5 and it just seems like 13. Being you guys confirmed the run way is long enough I just need to practice I guess and validate that 13 degrees. I watch my AI wing man stop on a dime and every time I am like WTF as I go blowing past him

empty . Nothing on the wings

I have been practicing landing the F16 at Batumi on the Caucasus map. If I flare (nose up) with air breaks till I get to 100 knots then the nose falls then I hit the breaks hard to stop. I barely stop in time before I run off the run way. I mean its VERY VERY close. Buttttttttt when landing if I flair with air breaks with my foot brakes on full I have all 3 wheels down at 126(ish) knots as the breaks force me to quit pointing my nose up a few seconds after touch down. I stop so much closer to where I need to be on this type of approach. it seems to work out way better if I just slam on my breaks when I touch down and ignore aero braking. My question is, is Batumi runway to short for the F16 or in real life do these guys land with their foot on the breaks. It seems if I land with my foot on the breaks nose up for only a few seconds I have a great landing in DCS. If I try to use aero breaking I need a really really long runway. Thoughts?

That's a really good idea. Yeah I was trying to hold off a few more years until a new X3d or the next gen intel CPU comes out but I cant even fire up liberation without DCS going into slide show mode. Being I have never owned a AMD CPU before any board I should look for that wont break the bank?

Hey guys, I am at an impasse. I have a 3080TI paired with I7 6700 Skylake and I need to upgrade. As you can see I keep my CPUs for quite some time. This system is only used for gaming. I was thinking the 13700 but it might make more sense to go with the X3d, Knowing, I mostly just play DCS in VR (right now). I will play some BF, COD, Squad, Etc from time to time. I see so many people going from 5800 to the 5800X3d but my CPU is so old it all has to be replaced so anything will be a big win for me. Being I only use this for gaming does it make sense just to go down the X3d and if so what mobo should I pair that with? My thought is the X3d is pretty inexpensive right now (assuming I can reuse my 3200 DDR4) so if I need to replace it later that's ok. What would you do? Any help would be really appreciated. I would like to hang on to this CPU for at least 3-5 years. AM5 is not an option at this time.

Question, when I am playing single player I have a wing man and when we engage bandits he can seem to lock them up and shoot them way before I can with our AIM120s. By the time I lock them up with my radar his missiles are hitting or close to hitting the target. I see the bad guys on my radar via the datalink but it seems like as soon as the wing man is about 40 miles out he can fire and will get a hit. it seems like my radar cant lock them up until I am about 20-30 miles away and my wing man seem like he can shoot them at twice that distance some times. Am I doing something wrong here? I am running 3 bars and even gone down to one bar with a focus on a single target pointed my plane right at the bad guy.

I was just practicing finding moving ships with the FCR Radar in sea mode. Then I would move to the targeting pod when my radar would find them. I would push TMS up and get the little box that would lock and follow the moving target so I could drop some LGBs. The first few times this went ok. But on a 3rd try and every try after that, when I am using the TGP, I push up on the TMS and get the box but it no longer follows the target. It just stays in one spot and my ship sales out of the box. Did I push a wrong button because I cannot get it to work any more at all? I can manually slew/and move it with RDR cursor switch to keep my target in the box but it used to do that automatically. I would Push up on the TMS and the little box would stay on top of my moving target and I could focus on just using the laser/dropping the bombs and keeping the TGP pointed in the right direction. What am I doing wrong? This worked the first few times I tried it today. Thanks Much

Hmm... Is anybody else having this problem? I just had my tank do some traveling and I put it on active pause and followed him with the TGP and again, Nothing. TV is the only option. My wing men can find them with 0 problems but when using the TGP, I cant see them on BH or WH. If I have my wing man blow him up the fire is very visible.

I added some soldiers and they show up just fine with BH and WH. I am guessing the vehicles have some special coating and this is supposed to be this way?

I am sure i am doing something wrong. I am setting up missions in Syria using both Mission Editor and Briefing Room. At any rate, when I go to use the TGP, Black hot and white hot doesn't work at all. It makes my target invisible. I can only seem to use TV. I have tried different times of day. I had the enemy tanks move so their motor was hot. I put it on active pause and played with contrast and gain and other settings in the F16. I cant see anything using Black hot and White hot. Is it a map problem, TGP problem, F16 problem, user error? Coming from the F18, I didnt seem to have this problem. Thoughts??????

I agree with edmuss. Not much can be done with the MOBO. Its just too old. Its time for an upgrade. The 6700 has been good but its time

Thanks, I am thinking the same thing, I will just try to be patient and wait till the release of Ryzen7 and then make a decision.

Thanks for the response guys, I will work on getting that done. With that being said, any recommendations on a New CPU? Mine is so old and I was going to replace it anyway so I will start there. Should I be looking at the AMD 5800X3D or Intel 12th Gen I7? I only use this system for gaming. What is the best CPU for VR and DCS. Also is this the toolkit I should be using with Oculus? https://mbucchia.github.io/OpenXR-Toolkit/

Its for sure not a system ram problem as I am not coming even close to maxing that out.

I have 32GB system and 12GB Vram. I am running on a M.2 500GB drive dedicated only to this game. I had it on my M.2 with windows but due to the size of the game, I dedicated a drive just For DCS as I ran out of space.

Yep that was the first thing I did. Regardless of what is open, the settings GPU usage just bounces all over the place. I tried airlink same result. I tried turning down my RR and changed the quest back to 72hrz, while I saw an overall reduction in GPU usage it still bounded all over the place not exceeding 50% with settings this low. I then said well let me crank it up and to 1.7 which is max with 120hrz and same results on GPU utilization except it was more in the 90% then drop to 50%. I did notice that I am using 12.2 GB of Vram and my card only has 12 so I am not sure if that might be a problem. I am thinking its my very old CPU or maybe its just the game and this is the way it behaves. Check out the picture.