Grodin

Cockpit texture size is one issue, 11 gb vram is really pushing it for any module and default apache textures its a no go, thats why the taz texture mod helps alot. DCS VR with 2080ti will require lots of balancing in the settings, MSAA or high pixel density are purely 4080/4090 territory i'm afraid, even 4080 struggles with PD 1.0 and 2x MSAA. Motion reprojection and DLSS surely help with FPS but they totally ruin the image quality so for now anyone who doesnt have 4090 has to deal with either low fps or avarage visuals. I have 4080 and i use 2x MSAA and PD 1.0 and usually get around 60-80 fps which i would call tolerable for some but i know many players would need 90+ to consider it smooth.

Yes please, a toggle to unlink mouse cursor from head movement in VR. Annoying to try and hold my head absolutely still while hitting buttons.

Depends on the headset fov and what you are looking at with it. I only lose the cursor in DCS, not other games. White cursor against white clouds (comms window open) or yellow cursor against a sunset at the edge of your peripheral vision can be quite tricky to notice, atleast with high fov when you can't see the whole picture without moving your eyes. Yes i know its easy to find the cursor when you move it around a lot, but thats not the point here.

Simulators usually are a bit frustrating at first, they are not just plug and play console games. iRacing does not have auto-pit, Arma does not have auto-aim. Certain amount of learning curve is to be expected. Target audience often invests so much time and money to this hobby that when someone wants more hand holding aids you start wondering what they need next when they get to the more challenging parts of the game - someone wants autoland, someone auto takeoff, someone wants dumb bombs to auto hit because they are hard to hit etc etc, it never ends. Well you could look at a track of someone doing AAR within DCS to see what it looks like and you can even take control during any part of the replay to practice keeping the probe in after connection if you want to.

Player planes only fly themselves to the extent their autopilot is modeled. AFAIK while some of the autopilots can follow a tacan none of the autopilots in the game can automatically match the speed of another plane - you would need to model a new system for the plane to do that. Switching to the AI flight model and letting AI completely control the plane might be easier, but if AI was to take control of the player plane the cockpit would go haywire because the AI flight model doesnt use any of the sensors or inputs from the player cockpit, currently you cant look inside a cockpit of a plane that is flown by AI so there is propably a lot more to code than you would first think.

My point is even that kind of system would take some serious coding.Having autopilot fly the players plane to the boom or well any specific position other than what the module is already programmed to do is some serious work and every module would have to implement it differently. Its very unlikely the player plane could be autopiloted like an AI plane because the AI flight model that is used for the AI planes to refuel is 100% different to how player planes are controlled. They would have to write a completely new mode to every planes autopilot system. Weeks or months of coding i would guess. Slightly more plausable system would be a trigger zone near the tanker that would refuel the plane when you fly close enough to the tanker, would require some additions to mission editor. But even then my point is if the devs made a poll "What should we code for the next month?" and the poll has options like "Add undo feature to mission editor", "add f16 sniper pod", "finish supercarrier briefing room", "make dedicated server multi threaded", "implement vulcan", "code a smarted sam/iads system", "make a dynamic campaign" etc i would imagine option "easy AAR feature" would not be on top of the poll. Yeah sure some of the backlash you get could be about "only worthy pilots can join my "wohoo i can AAR" club" but i'm sure most people would just like the devs to focus on what they think is most important at the moment and frankly easy AAR is not very high on that list for vast majority of DCS players.

I'm not saying it would be bad if they could just magically make that kind of option appear without spending time to code it. But they cant and i want devs to focus on things like fixing bugs, adding missing features to the modules, implementing vulcan, improving the AI etc etc which i consider more important. Now the question is how big part of the customers want this or that. There are more pressing matters that affect 99% of players or 70% of players etc and then there are things that maybe 0,5% of players consider important. We can only guess which features are which.

It has nothing to do with the "sweet spot" - that has not been a thing since like Reverb G2 or such, current headsets are 100% clear all the way from edge to edge, thats not the problem. To get an idea go and touch your monitor with your nose and then move the mouse around when you are inside the cockpit, its tricky to find no matter how clear and hi-res your monitor is. The issue is that VR users have so much larger area to look for the mouse while on motor you are looking at a post stamp in comparison, ofcourse its easy to find because you can see your whole game thru a straw. PointCtrl makes mouse sort of obsolete in dcs but yeah instead of a keybind i would prefer the cursor to auto center when you havent touched the mouse for a few seconds.

Just don't do it or spend a few hours training for it, jeez, its not hard. Devs have much more important things to do. If you want to pretend its WT just turn on unlimited fuel and go full afterburner everywhere.

ASW causes ghosting in external views (its motion reprojection) try unchecking that from the VD options. Disabling it will lower fps tho because it essentially creates fake frames, thats why you noticed such a huge performance jump.

But for VD you connect headset to router with wifi and router to your computer with a cable. Quest 3 cable support seems pretty much abandoned, doesnt work very well for many people compared to VD. You can't use virtual desktop with a cable, only by wifi to the router.

Because the headset is recommended to connect to the router with Wifi 6.

You can do augmented reality with openkneeboard and VD to see the real world on part of the screen yes. It works by creating a blank page that is pink or some other good greenscreen colour, open that in openkneeboard and then put the same color to VD passthrough settings, then when you open that pink page on your kneeboard VD will use passthrough camera over that pink page. Switch to a router will propably work yes but the recommended setup is computer directly to a wifi6 router via cable.

Not sure i understand your question but the way i do it is i press com 1 -> 1 -> ENTR on mission start and then i can just cycle through all the channels with the up/down arrows (have them bound to a rotary on my hotas). I've never had to enter a manual freq, all the needed channels are on preset channels.

I find all reprojection methods unbearable, but give the latest update a try, they made it so much better few weeks ago than it was with VD. Gauges, hud and ground objects dont ghost anymore. I mean yeah AH64 is still unplayable because of the reprojection cant deal with the rotor and hmd and fast moving planes in external views still ghost, but other than that it is now quite good - no more ghosting on HUD, gauges or radar screen and flying low the ground objects dont ghost anymore either, they seem to have completely revamped it.

Virtual Desktop works fine so if you are itching to fly thats a solution, pretty good one actually, thats all i use anymore with q3.

It's not a performance issue, it's a maintenance issue. The plane can do 9G just fine, land based air forces have their hornets rated for 9G because they don't have to endure the stress of carrier landings so using a paddle is fine if you operate from an airfield and pretend it's a swiss, finnish or some other land based air force.

Yeah this bug has been around pretty much since the burble was implemented, it's impossible to keep the nose up with it turned on, even full aft stick wont do - so just keep the burble off until its fixed :)

Not aware of such websites but ive seen most people avarage around 60-65 when they start to get a hang of it, say around 100 landings or so - it's easy to get 75 every now and then but the occational 60 drops the avarage. More active players with thousands of landings seem to avarage around 70. I have 814 carrier landings (F14 and F18 combined) and last 20 landings i wrote down avaraged 66 with F14 and 69 with F18. Really depends on the squadrons you fly with, some take landings quite seriously and avarage much higher than some more relaxed squadrons. Also taking a break seems to hurt the scores, if i dont fly for a month i will struggle to get even 60 on the first 2-3 landings.

I strongly recommend to make sure it won't come off accidentally, because when DCS thinks you took off your headset your flight will be done, the game will freeze and you have to restart. Once you get all the settings dialed in the only advantage G2 has is the center spot is ever so slightly more clear - i'd say like 10% or so. However with quest 3 you have that same clarity for all of your FOV, i don't have to turn my head at all or zoom in to read the texts in F16 MFD, all text is clearly visible from default head position for example (unless you use DLSS/DLAA which makes everything a blurry mess). FPS is same or better with Q3. Tracking is very much better on Q3. I'm on RTX 4080, 13900KS and 64gb DDR4 4400mhz CL18. Both - i max the settings in Oculus but also increase PD in DCS, because i can't use 2x MSAA, costs too much performance, but 1.2 PD is a good middle ground for image quality/performance. I didn't notice much difference in jitters or quality on Wireless desktop AV1 vs Oculus link on cable, but few random crashes on VD made me go back to cable - nothing like losing your progress after landing on 3 hour mission..

Any news on DCS MT OpenXR with Reshade? Is it working?

Thank you so much, you totally made me enjoy VR again! By default i felt like flying in a snow storm on my Quest 3, everything was blinding white from the ridiculous amount of haze. Now it is perfect, i think i'm going with 0.3 or 0.4. This should absolutely be a slider in the options!

Can anyone confirm if current drivers fixed the vr issues and increased fps to 4080 levels where it should be?

You can just tick the option from settings to override mission settings with your own i think.

Considering that the landings work perfectly fine for the rest of us the only logical conclusion is that either a) Something wrong with the technique or b) something wrong with the game. I'm unable to reproduce a situation where the nose wont stay up no matter how heavy i load the plane if i have the correct AoA and glide path.