av8orDave

I agree. Maybe there is something I'm missing, but if they truly mean that force trim won't be available upon early-access release, I'll be holding off until it is available. Seems like a very weird feature to leave out of any type of release. The early-access feature list overall looks a bit too "bare bones" for my taste, which is a shame because I'll definitely buy the Chinook eventually, and I've yet to not purchase a DCS module on day one.

Every now and then I play around with my VR settings just to see what has changed. A few things I figured I'd pass along: System specs: Ryzen 9 7950X, RTX 4090, 64GB DDR, Quest 3 - I've been using: - Oculus set to 72hz, 1.3 in the Quest/Meta app. DCS in-game PD set to 1.3; DLSS Quality; Textures set to high, terrain textures high, shadows medium, water medium - With the recent update of the Quest/Meta app to v66, I decided to try ASW again. Note that I've always hated motion smoothing. - Using 90hz, 1.5 in the Quest/Meta app, PD 1.3 in the Oculus debug tool, and ASW forced on (45 fps), DLAA rather than DLSS, and all settings to "high", I'm getting a crazy-smooth experience with minimal ghosting. I think this will be my new go-to setting. I think Meta must have tweaked something with ASW, because it suddenly works surprisingly well on my system with very few visual artifacts/issues.

Maybe we can get some clarification from @BIGNEWY? The specific verbiage in the newsletter is that the after-early access release features include "DAFCS trim system and force trim." I agree that without force trim, a helicopter is almost useless.

Today's newsletter seems to indicate that force trim is an after-early-access-launch feature. Is this accurate? Seems like kind of a major thing to not have working at launch.

I'm personally glad there is no voiceover, and it would maybe be great if it were an option in settings. I like the walk-through style of training missions, but hate the snail's-pace with which most training mission voiceovers proceed. It's kind of nice to be able to read at your own pace, acknowledge when you're ready to move on, and keep things progressing.

So what am I missing… Sometime after the last Oculus update, it seems like it became impossible to disable ASW while using Quest Link. Whether I try to disable it in Oculus Debug Tool or using Ctrl-Num1 in-game, as soon as the framerate gets stressed my 72 fps immediately turns to 36 fps and the ASW artifacting becomes apparent. In anyone else seeing this? Am I missing something?

I do have hand controllers for the Quest 3, and while they are connected and awake, I don't use them for anything. Could they be conflicting with something?

Yep, I gave that a shot. It makes the yellow mouse indicator disappear / reappear, but doesn't change my inability to move / aim / fire the gun. Interesting, I'll check to see if I have mouse btn 2 bound to anything else this evening.

What is that mapped to in control options? My middle mouse clicker is part of the scrolling wheel and isn’t mapped to anything.

For the life of me, I can’t figure out how to use the M4. I can unstow it, but can’t move it once it is shouldered. I’ve tried L Alt-C to no avail, tried the mouse, etc. I am in VR. (Quest 3). Anyone have any ideas?

Some anecdotal stuff from someone who uses both Quest Link and Virtual Desktop and still can't decide which is better: - If you're using OculusDebugTool, it doesn't seem to save the pixel density / supersampling settings. You have to change it (for example to 1.3) and then leave the ODT program open while playing DCS, then repeat the next time you start your computer or after you close the ODT software. - I've found that to get a true "like-for-like" comparison, you have to use the same pixel density settings in both program. For example, if you were to use a pixel density of 1.3 in OculusDebugTool with Quest Link, you'd need to dial the DCS pixel density in the VR settings tab up to 1.3 when using Virtual Desktop (even if using "godlike" mode). - I'll note that Quest Link seems to have started defaulting to having reprojection on even if you disable it. I say this because sometime around the last update of the Meta software, when stressed, DCS framerates started going from 72 fps straight to 36 fps, even after hitting "Ctrl-1" to disable reprojection/ASW. It used to just drop to whatever framerate was sustainable... now it is straight to 50% of the refresh rate as with reprojection. - I currently think that Virtual Desktop is the better solution, but I'm honestly not totally sure. Probably not much help, but my 2 cents. Good luck sorting it out. I hope for the day where VR hardware / software seamlessly integrates into games, and where it can handle the game at reasonable framerates without jumping through hoops.

Just what I needed @jacobs, greatly appreciated!

Anyone able to share a step-by-step for laydown mode? I'd like to be able to try it for dropping CBUs on an SA-2 site, but I'm finding the manual to be a bit vague. Thanks!

I've struggled in this area as well. I can turn down the HUD on the F-14, dial in on-speed AoA, and catch 3-wires until I'm bored, but as soon as I get an on-speed indication in the F-4, it wants to drop out of the sky. If I add a bit of power, then trim to get back to on-speed AoA, I suddenly find myself climbing for the heavens like a home-sick angel. I'll keep practicing, but I have to say it doesn't feel quite right. I'm a private pilot in real life as well, and I have sworn off going out to the practice area and practicing slow-flight at altitude, so I'll be damned if I'm gonna do it on a simulator.

Sure enough, I didn't have the dcs folders excluded from Windows Defender. And wouldn't you know it... that did the trick! Thanks @MAXsenna for the solution!

Yeah, that's what I'm seeing. Mission load times haven't really changed, but taking longer for the game to load up.

Hmmm.... I think so, but it is worth a double-check. I'll have a look this evening. Fair to assume you're seeing consistently reasonable loading times?

I had the same reaction regarding Crystal vs Q3. Interested to hear your experience at the roadshow with a different headset given that the different lenses don’t seem to make a difference.

Thanks @Silver_Dragon. To be clear, it works fine, just takes forever to load after double clicking the DCS shortcut. I'm using the multi-threaded version. PC spec is Ryzen 9 7950X, RTX 4090, 2TB M2.SSD, 64GB DDR5. It just seems like the loading times for DCS get longer and longer. At one point it was pretty quick / reasonable.

Is it me, or are load times back to historic highs? Seems like since the last couple of updates, it takes FOREVER for the game to load. Load times back around the new year seemed pretty reasonable. Am I the only one seeing this?

Good stuff, and thank you. I use your checklists in all of the DCS modules I fly and find them to be indispensable.

This 100%. After spending nearly 20 years in corporate America, I'll say the unthinkable: a 23 year-old super-green recent college grad consultant from McKinsey would recommend better project management practices than what we regularly see with these patches. Whatever was done didn't work, and that needs evaluated, of course unless they just don't care about hitting dates. It sure sounds like they didn't test the final release candidate and leave enough time to either work through issues or not delay on the day of the planned launch. Yes, I agree with all of the crowd here that says "in the grand scheme, this isn't really a big deal". That's obvious. We're talking about a video game, hobby, whatever. On the other hand, the constant delays get annoying. It is clearly a pattern, and symptomatic of an issue managing product launches. It is not "normal" or "to be expected" to have last-minute delays for complex products, processes, or any other project, regardless of whether it is software, medical devices, brain surgery, aircraft manufacturing, or making orange juice. It's symptomatic of a bad management process.

I'll be more clear: my frustration isn't with this delay. It is with the pattern of constant delays without acknowledgement that anything should change with how they manage projects and launch products. Wouldn't one think that if it were a clear pattern that something would change? Consumer sentiment is like a box of matches; each time you screw up, you burn a few matches out of your box of consumers. Some are harder than others to ignite... they'll stick around even after being struck time and time again. But eventually, even those matches are spent, and if you keep doing it, you run the risk of running out of matches.

Does it matter what is broken? If they have a deliverable to meet today, shouldn’t testing be done on a timeline to accommodate that schedule?

Respectfully, how does that happen? The final check is completed hours before launch even though they announced the date weeks ago?