av8orDave

I have no idea of the actual facts behind the disagreement between Razbam and ED. I'd wager that no one on this forum knows all the facts, particularly not Razbam's SMEs who seem to constantly chime in with their beliefs of the reality of the situation. I also will say I am regularly very critical of ED, at least when they deserve it, which a search of my post and comment history would show. Having said that: I can almost promise you that any reputable legal counsel would be advising ED to absolutely not comment publicly about the situation any more than they already have, and would likely also advise them not to remove Razbam's modules from their digital store, as for all we know, that may put ED in breach of whatever agreement they have with Razbam or could be interpreted poorly in legal proceedings. If you are expecting some kind of update or change on the store, I think you may be waiting a while. If the situation has entered the legal realm, legal proceedings take significant amounts of time, and I would think there would be little to no public communications about the situation until significant progress has been made.

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?

I agree. The situation highlights an interesting conundrum, however. The nature of these early-access modules is that a number of features promised have no timeline associated with them when the module goes into early-access sale; as such, even if development and updates are slow, or if the developer stops working on the module entirely, even if for an extended period of time, it isn't really behind schedule because one was never created or communicated. This is something I really have to factor in before buying early-access products in the future. Even though the price of the module is largely inconsequential for me, I'd still rather not shell out a few bucks for something that really may never been finished as it was advertised. All that to say yes, I believe they should put an indicator on the e-store indicating that development on the module is paused, even if temporarily.

I'll state the obvious and say "man, I wish it were an F-4B or F-4J", but absent that, this looks incredible! Reflected's campaigns are an automatic purchase as soon as they release. I'm sure this will live up to the standard he's set with his other campaigns. I don't want to derail the thread, and I'm sure it has been answered and I've missed it, but does anyone know if Heatblur had a reason for choosing to model the -E over the -B or -J? Phantom carrier ops would be phenomenal. I know they've mentioned doing a Navy Phantom down the road, but given DCS development timelines I hope it happens before the expansion of the sun encapsulates Earth.

@Qcumber is correct. Quad View Foveated Rendering does not require a Pimax headset, eye tracking, etc. If you have a Quest 3, for example, it works in fixed foveated mode. I used to use it on my old system that had a 3080 and it worked wonders for improving the framerate (I don’t feel I need it now with a 4090 or id still be using it).

Nice work, I'd give you about a 90% on the test, not bad for a first try! Seriously though, you've got it mostly correct. Some notes: 1) You can use Virtual Desktop, Oculus Link, or AirLink. As a general rule, Link refers to the cabled setup, while AirLink refers to Oculus's wireless option. 2) If you are using the Multithread version of DCS, OpenXR is native, and you don't need to use an argument. OpenXR Toolkit is a seperate software that gives additional options in-game. Your only other option is SteamVR. 3) With a Quest, you'll be using Oculus unless you use Virtual Desktop. OpenXR Toolkit is just additional software that adds additional features / options. 4) Correct.

Not only confusing, but I can’t say that I’ve seen a meaningful improvement in framerates since the last update. The newsletter suggests scenery rendering improvements in orders of magnitude, yet I’ve seen no real difference. What am I missing? system: Ryzen 7950x, RTX 4090, 64GB DDR 5, 1TB SSD