rubbra

Oh, that's odd! You have hit apply, and then restarted DCS? You could also try Adaptive vsync, half refresh rate?

Good advice - I’ve been using the same mindset since I got my oculus. For those of us with hmds that don’t have 80 or 90hz refresh rate (quest 1, for me, sadly, though it was under £100), you can just turn ASW off and then use Nvidia or amd control panel to limit max FPS to the appropriate factor of your refresh rate. I set mine to 36fps, half of the 72hz. And that’s just perfect. With my current settings, on a 1060, I get about 50fps in single player over Syria and slightly more in Caucasus. So I limit to 36fps and rarely if ever dip below, and it’s solid, no artefacts, no weird shimmering/melting trees etc, even at 650kts and 100ft in the hornet. The only things I haven’t decided on are whether to have vsync off or on (or fast, set in NCP) and the best choice for low latency mode. Sent from my iPhone using Tapatalk

The problem with your desire for status updates is that an overhaul of a code base/Significant library and architecture change is a very complex beast and the various steps along the way will be largely meaningless to anyone who doesn’t have access and knowledge of the DCS codebase. It’s rather different with a new plane - get it flying, and add some functionality (trivialising it, I know, but hopefully you get what I mean). That can be translated into meaningful progress reports that we all understand. We don’t expect Microsoft to tell us how their progress towards their next OS is going until it’s nearly ready, do we? That’s kinda what we’re talking about here - the operating system underneath all the modules. Sent from my iPhone using Tapatalk

I second the image quality comments - get the best you can (which is g2 at the moment I believe), and then tweak it to balance performance vs image quality. I have a Quest 1, which I bought because I was flying on an underspecced laptop. It’s a little bit like flying minecraft :-) I would definitely like to upgrade it. Still prefer minecraft DCS in VR to flying on higher settings with head tracking though! Sent from my iPhone using Tapatalk

Is that because runways have got longer? :-) Sent from my iPhone using Tapatalk

No problem. It *is* pretty damn good. There are "things" about VR that mean everything is a compromise, but as a flying experience, once you've done it, it's hard to go back to 2D. Some things - image quality; VR image quality is like going back 15 years compared to 2D mode. Think more Minecraft than DCS on Ultra (that's harsh - it's not as bad as that, but it's the best I could up with). Speed vs Image Quality - expect to spend a lot of time chasing this dream of having amazing IQ AND FPS. Never gonna happen. Keybinds - expect to either use VoiceAttack or have like a gazillion keybinds on your HOTAS and then forget which one is which and accidentally lower your gear at 450 knots, or jettison stores on take off once in a while! You know that moment when you look at your watch after a flight and go "where did the last 2 hours go" ? Double it with VR. Questions like "when did it get dark?" or "when did my wife and kids leave home?" will need answering once you live in the enclosed world of your VR headset. I think your decision to hold off until you can sort out hardware is probably the right one. I didn't do the same - probably should - but got offered a Quest for a song, so thought it was worth a shot. Was expecting to have the worst performance ever, and then give it to my son. But have managed to tweak and tweak and tweak and have got it pretty stable and reliable with "good enough" image quality. I *will* buy a desktop. But not until I can get one with a decent GPU without selling any of my vital organs.

Your GPU is below the minimum specs for a Quest I believe. Not a Quest 2, a Quest 1. I am flying in VR with a Quest 1 on an unsupported GPU. It’s… satisfactory. Good enough that I keep doing it and don’t want to go back to pancake mode ever. But… this is single player, simple missions. I play multiplayer with one other person and that’s fine, but joining any bigger server with more complex missions and the whole thing grinds to a halt. I would say if you’re going to try it either go for a lower resolution headset such as the original Quest, or get a better GPU first. Sent from my iPhone using Tapatalk

I use bodnar boards. They are quite literally plug and play, easy to wire up (if you get the one with the push connector header soldered on, it’s just strip end of wire, push in) and no programming required. My only beef is that DCS doesn’t have a “on release” option in keybinds. So if you have a 2 way switch, most modules will only let you bind the “On” whereas what you want is “off unless On” or “on release of DX4, trigger Master Arm Off”. Hornet is a bit better than most module as there are some On/Off binds. You can achieve the desired effect in Lua though. Sent from my iPhone using Tapatalk

Ah yes, I see what you mean. Very awkward to use! I stand by my hybrid feature request ! Sent from my iPhone using Tapatalk

If I have use mouse on, nothing moves with my head. It’s completely binary. Blue cross = move with head, White dot = move with mouse. Nothing in the middle… Is this not “normal” ? (Am on OpenBeta, most recent update - 2.7.3.something)

Interesting! So do you have “Use Mouse” on or off? If on, I wasn’t aware there was a way to move the cursor vertical; is not fixed to the centre of your view?

I really like using the “Blue Cross” option in VR - i.e. mouse cursor follows my head, in the middle of the screen, and using HOTAS as LMB and RMB. Except for the switches that are down and to the side - the switches that IRL you could glance at and stick your hand on easily, but in VR you have to contort your neck to get the cursor on to. What would be totally awesome would be a hybrid of Use Mouse and the Blue Cross - i.e. it behaves like the VR blue cross in the middle of the screen, unless the mouse is moved, then after N (configurable, perhaps?) seconds of mouse inactivity, snaps back to the centre. That would give the best of both. That would be be “Gold Standard” version - “Silver Standard” would be to have a keybind/HOTAS control to switch between mouse and no mouse input… (And now I’m expecting someone to reply and say, “Oh, there is a keybind for this!”)

Ah, I think ‘cos I read this forum and others through Tapatalk, it’s pretty hard to know that this is a bug thread. I just see the topic title of “should TGP be this hard?” Sent from my iPhone using Tapatalk

Ah, apologies NineLine! I am completely happy with that post being moderated - though it really wasn't meant to be a DCS bash at all more a "look what will be coming"! (And if I wasn't happy with it, also so what - this is ED's forum, their rules!)

I'm towards the bottom end of any specs, especially for VR, but can get a solid 35-45 fps in VR depending on what I'm flying over for Syria, solid 60 (vsynced) in flatscreen mode. Same settings for Marianas... 16-18fps. Flatscreen mode, also 18fps. That doesn't make much sense to me! More specifically, if it helps anyone: Marianas at 2000ft: flying over open sea at in the FA/18, I get 24fps, solidly, until I pull a high-g turn, at which point it drops to 9. Flying over one of the small towns beginning with A, 14-18fps. Syria map at 2000ft - flying over open sea inbound to Akrotiri, 42fps, pretty solidly, slight dip below 40 for high g turn, then 36 when flying over Akrotiri.

It’s an instant action for the module under Caucasus map

You can use the stores config switch to help you reduce the chances of over G, can’t you? I believe it doesn’t limit G, but does reduce roll and pitch rate and AoA which all helps.

MSAA does make (at least on my system) a huge impact on FPS. I’d set it to off to start with.

[quote post="4701204" Only thing left to try is the batch file. Good luck. I’d be surprised, unless you’re on a laptop too, if it makes that much difference :-( I tried 1v1 multiplayer over the weekend and lost many fps Sent from my iPhone using Tapatalk

I have it now also crystal sharp via Quest 2 Air Link, it costed me several hours to get to the sweet spot (see attached). I can see the texts on the panels very clearly If I turn the bitrate higher, like 200 then I get lag and stuttering images, while the rendering on my screen is just fine. Seems to be to Quest 2 Air Link can't handle bitrate >200 very well. Encode resolution to anything lower than 3600 gives blurry panels. You’ll likely find that is a limitation of your wifi not AirLink, but that’s just me guessing. Sent from my iPhone using Tapatalk

Unlikely, but possible, I guess. The high performance/idle state disabling is only done by Oculus to reduce latency for a few FPS games that were having problems. My son’s desktop doesn’t perform any worse with the idle state disabled, but it does maintain a significantly higher fan speed as a result.

Clogger - exactly, as I say above, "I suspect it won’t have much effect on desktop performance but it makes a vast difference for me on a laptop. "

VR shaders patch - works with current latest beta and stable. But will not pass MP integrity check. There is a version that does but I’ve not tested it. Batch file - on your desktop, create a new file with the extension .bat, eg “power.bat”. Copy and paste my simple code above into that file. You will need to change the long guid (unique identifier for the balanced power plan on your system) to match your balanced power plan’s id- open command prompt, run “powercfg /list” and copy/paste that guid to replace my one. Save the file. Then double click on it And it should open a command prompt window and change power plan every 60 seconds. It’s not clever but it does work. I suspect it won’t have much effect on desktop performance but it makes a vast difference for me on a laptop. Sent from my iPhone using Tapatalk

Hopefully the last updates from me. I've just made two more tweaks which may be relevant to you - I added Kegety's VR shaders patch. Gained roughly 10-15fps depending on the scenario. Disabled TacView, gained another 5-7 fps on average. My 3 test instant action missions now give: A10C-II - Georgia, Easy mission, averages 45fps F5 - Takeoff, Batumi, between 48 and 60fps, depending on where I am in the cloud cover. MB339A - Batumi Air Show (don't know why, I love this one!), 55fps pretty much consistently, unless flying in the middle of the coloured smoke, drops to 45, then 38 with mirrors open.

:loop PowerCfg /SETACTIVE 381b4222-f694-41f0-9685-ff5bb260df2e PowerCfg /SETACVALUEINDEX SCHEME_CURRENT SUB_PROCESSOR IDLEDISABLE 000 timeout /t 60 goto loop if it's any help, the above is my simple batch file. The guid for the power plan you will need to find for your own system by doing powercfg /list from the command line, then copy and paste that above (replacing the long guid after /setactive)