Hoirtel

Yeah, I had one at launch and a G1 before that. I'm in the minority that didn't get on with them. My issue was the tiny sweet spot followed by the quite large image degradation immediately outside of the center. I opted for the Q2 at the time as it was softer in centre but more uniform across the lens. The Q3 is G2 sharp throughout. It's been a while since I wore a G2 but the colours are probably still better on G2. I also hated the wmr/steamvr bridge, I had it way before any openxr support. G2 is much more comfortable out if the box but then it has a proper strap. The Q3 feels similar nice and comfy around the face, and slimmer too. You will want a strap. Sound is improved from q2 but still low end. I will always use a headset as before. As I said my issue is compression but really not spend enough time tinkering. Not compressions issues on G2, but then no wireless either. If you ever do any standing VR game play, once you go wireless you cannot go back.

Had a chance to have a go now. I am so far a little underwelmed but enjoying it. Essentially it's a Q2 with a bump in clarity and comfort. Lenses are quite sharp, but honestly I didn't think the sweet spot of the Q2 was all that bad, and most importantly the degradation towards the edges was gradual. These lenses are better. I do notice a minor hue change at the very edges, not really a problem. Edge to edge clarity? Yeah... I suppose it is.. My current issue is compression (running on 4090). I can really see it and tried bitrates of 0 (auto) 200 and 450 (my q2 setting) on link cable. I also tried upto 200 and 200 fixed on airlink. Still there, and all looked the same. Either I haven't figured this out yet or meta hasn't implemented the proper controls yet... or my worst fear is that the new clarity shows it up more. I had a similar thing with the rift s to q2. The q2's loss of screendoor showed up some other problems. The lenses do have glare, but it's well improved. Night time is still dark gray but the visible lights in buildings/airfields etc look much much better, and aircraft lights in daytime much more natural looking. This is a nice update. Alasing about the same, I run 2x msaa. However I did add mfaa and change anisotropic filter to clamp in NVC and this actually made a difference. I will play around with supersampling, never did this on q2 but I feel there is a little more to get out of the Q3. I am running max Res in software. I think DCS is just alasing prone, I hope dlaa will replace all above tweaks. Passthrough looks a bit pants. I think a bit if standard YouTube over hype. Quick early impressions, not actually done full sortie yet, just run tracks and some cockpit hopping.

Its arrived, unboxed already and wow feels slimmer and much more comfortable!! On charge now and will try it later. Got to work today..

My Q3 has been dispatched, so hopefully able to post some initial thoughts quite soon. However I suppose there is a chance that we will get DCS 2.9 this week too, so potential big changes.

I know we are not getting 3.0 frame gen DLSS, I am wondering about the upscaling. If the GPU is upscaling frames that are already "guesstimated" by the VR software that might be a recipe for problems. Considering reprojection already causes artifacts AI upscaling would probably make these a bit worse. I think the future of VR is probably a version of DLSS and move away from reprojection, but maybe not with current versions of DLSS. I do have a good bit of faith that ED is working hard to support VR these days so I expect what is possible they will do. Interesting to see what that is.

I wonder if the issues with DLSS and VR are caused when reprojection is also working. It would make sense that these two would not be compatible. Give the additional hardware requirements for DLSS it should do a better job than reproduction technology? However one of the main reasons I still use meta is because their reprojection is just so good. 90% of the time I can't tell if its on or not in DCS.

VR headsets aren't as simple as pixel count, the type of lenses, type of screens and the positioning of screens to the lenses make massive differences to the actual clarity experienced. There are a few good videos that cover different aspects of this, its quite a complicated science. Well, playing DCS will be possible in it so what else is there to change. It obviously affects performance as with any display device (more needs more power). Can't see what it would be expected to change? Improvements over older headsets? - yes. Trade-offs with other headsets? - yes. Is it compatible with PCVR? - yes.

I have two Dayton audio BST-1s which I love, so much extra immersion. I have a homemade simpit with a sim racing seat mounted on plywood which is attached to the frame via rubber anti vibration mounts. They help reduce any of the noise through the house and ensure that I get the full effect through the seat. The main challenge I had is choosing the amp. I went for a nobsound mini (hmm) seems quite widely used at the time and does run these well although they are 50w and the amp only does 30 per channel with the current power supply. It can do 50 with more volts. I found it really hard to figure out what amp rating is ok as I know there can be mis matches. On 80% volume it feels fine, I don't use sim shaker, really didn't like it. I use game sound only (EQ'd) and it feels great, sonic booms feel like I have been hit with a bomb though! The game sound option is so much less hassle and to me feels so much more natural with the game, perfect sync and as much variety as the game sounds effects have. One thing I have noticed is that not all modules have the same amount of low frequency sounds. For example the F15 feels quite weak all the time, but the apache is amazing - nice subtle thud when the door closes and the gun rattle it nicely, in the front you feel it even more, like it was actually under my seat. Helis in general are great as the rotor whirl works nicely.

I have pre-ordered so will happily post my beta testing . I currently use a Q2 so it will be a direct comparison as a DCS headset. I do like oculus/meta's ASW, so that is a big selling point for me. I decided to go Q3 over QPro because of the increased res and new version XR2 chip. Downsides are no local dimming or DFR. I don't use fixed FR currently with ASW so that helped me with the trade-off. I run a strong system and have been quite happy with my Q2, I have had both HP headsets in the past and didn't get on with them but that was back in the early days. My hopes for the Q3 are really about less aliasing as this is my main issue. I feel I can read everything in cockpits that is realistically readable, extra sharpness is always nice though. The pancake lenses more or less guaranteed to be great, and I also hope for better colors, particularly black levels although I may not get this with this headset. I still want to buy a DP super high res headset and will do one day. Don't want that massive pimax thing and the aero is now tempting but I don't own base stations, have tax to pay and I hear the reprojection isn't great. The Q3 will hopefully give me an upgrade until something new comes out and although I pre-ordered the Q3 as it feels a safe bet, any new high end headsets I will need to wait until they are well tested before buying. So a year or two from now at least.

I have found the same thing. Is this just broken currently?

Yeah, well it happened to me twice today a few hours apart. Both times after PC boot. Did a slow repair in between too. Just now I did disk cleanup, SFC scannow and removed some mods. Rebooted and it authorized properly, now I am not sure. Did too many things in one go. I would like to know what the 400 error is.

First time I go to load DCS today I get an authorization failure code 400, I have done a repair and it has happened twice. Closing DCS and restarting seems to fix it although I get my wall paper reset. Everything else seems OK, but may not have found what else went wrong. What could be causing this? never had an issue like this before. Thanks for any help.

The lack of good reprojection does bother me about the aero. Even at this new price, it's one of the reasons why I have stayed with meta (hate incoming...). Really tempted to buy an aero but was planning on Q3, yeah big difference but I am in the minority of people that actually like the meta headsets.

Download the example livery you have, see what textures they have included in their pack, see what the description.lua has in it. Use that to create your own using original blade DDS files from the core game directory.

Although the above works I have found that I really need the camera to go through the body of the tanker to get the perfect angle, which it doesn't unless the view is locked to the jet and then it looks a bit odd. GoPro style on the fuselage is the best we can do. The view system is so convoluted, they need a single spectators drone-style option with bookmarks. The rest can be done away with.

This has been discussed a lot. Think it's just a part of the current mt preview. It's not really fixable with settings, turbo mode appears to mask it. https://forum.dcs.world/topic/322124-constant-terrain-stutter-on-mt/page/4/#comment-5286294

Hmm, ok thanks for the replies. It was the F18 BFM Red Flag campaign, I did get miles when I bought it for myself, and then didn't when I purchased it as a gift... I double checked this in my profile. Maybe the policy changed as there was quite a while between. Never mind.

This is the way! Thanks, I knew I was missing something! Dedicated server racks don't corrupt, but have no F1 view.

I recently bought a campaign for a friend, but I didn't get the miles from it. Was I supposed to?

I also tried changing fps limits. I set it to my VR refresh (80fps) in graphics lua alongside the 80fps I already had set in the NVCP. I can't force change the refresh rate of my monitor to 80hz as its only an 60hz screen. Not sure if that is an essential part of this tweak or not. I saw no difference, but actually did observe something odd. When in the DCS menu I could see that the stats total CPU use would flicker quickly between 0.4-0.6 ish. However, every 3-4 seconds it would build to 11.X which then would peak and show on the frametime graph as a wobbly line. At this time it would flick from CPU bound (main thread) to very briefly CPU bound (render thread), shown in yellow, then the whole thing would settle and do it again. Using the open XR tools to throttle at 80fps reduced this behaviour massively, but opening up all framerate throttling stopped it completely and returned to a flat uninterrupted 0.X total use. For me, I cannot get rid of the minor stutter but I can reduce it with vsync=fast and low latency mode on ultra, pre-rendered frames to 1. Its not fully consistent as this will be great in some of my low flying test tracks, but then I will get bigger stutters in actual missions when things are a bit more dynamic. @Rapierarch What you say makes a lot of sense. I don't know much about render pipelines but the general point of current MT preview being a sort of stop gap before the Vulkan integration makes a lot of sense, and the devs are just focusing on the next stage rather than a repair of what we have now. Having seen the videos of this same terrain stutter in 2D (although less obvious) just means it is a current part of the MT preview. As will all DCS tweaks, different things will work for different people to reduce this. It will depend on what your system is and where its bottlenecks are. I run a 7800X3D and found it to actually work a bit smoother with CPU intensive settings increased, like view distance and cockpit shadows (This is along with the latency setting above) I assume this is reducing my top FPS at the same time, but as I mostly run to 40fps with reprojection I can't tell, and haven't done any proper testing to find out. Thanks to everyone posting in this thread, its quite interesting to follow.

I have a track replay from a server and I would like to record the refuel footage as if its from the tanker boom operator view. I know this isn't a specific view available (please ED..) so I wondered how to do it myself. Seems harder than I first thought. F2 view on the refuelling aircraft did make this work but as camera is fixed to the wrong aircraft you don't see the fine movements and the view goes out of position quickly, I did try messing around with F2/F4/F11 views on the tanker but couldn't get it to go through the body of the tanker? I have seen this on YT so I believe it is possible. Does anyone know how best to do this? Thanks

Just had a flight on the Sinai map, in daytime. Went to put the sun visor down and got NVGs instead. Not sure if this was my fault or not, perhaps I should have changed an option somewhere when I set the mission. However I thought for a long time during the flight the UFC looked different and it wasn't until near the end I realised that it had a clear cover attached over the top, must be some sort of night vision filter... but I never knew this cockpit had dynamic internal features. Is the availablity of this controlled by a setting somewhere?

It's the digital age we live in. I mean if you buy a digital product it only exist digitally so that relies on equipment to have any existence. It's all just electricity...

I think ED should buy the static mods that meet thier specs from the modders that make them and include them in the game. Or allow modders to sell asset packs as a third party, just need to ensure that people without these packs can still join a server with them on otherwise it's a pain to try and do MP.

Assuming you have to press the modifier along with any other button, and keep it held. This will work but the tutorials show using an always on switch as a modifier state, which does not work. Or might for a bit then not.