unltd

Meta already sells the Quest systems basically at production cost, and just ignores the development costs, so don’t expect this to result in cheaper VR headsets from other companies with Quest equivalent capabilities. Even if the other companies have greater efficiency, they can’t compete with that. What it CAN do is enable a variety of high end “boutique” headsets, as you get with Varjo / Pimax / Bigscreen on SteamVR. Push on resolution, push on field of view, push on comfort. You could drive the Apple displays from Quest silicon. You could make a headset for people with extremely wide or narrow IPD or unusual head / face shapes. You could add crazy cooling systems and overclock everything. All with full app compatibility, but at higher price points. That would be great! This brings with it a tension, because Meta as a company, as well as the individual engineers, want the shine of making industry leading high-end gear. If Meta cedes those “simple scaling” axes to other headset developers, they will be left leaning in with novel new hardware systems from the research pipeline for their high end systems, which is going to lead to poor decisions. VR is held back more by software than hardware. This initiative will be a drag on software development at Meta. Unquestionably. Preparing the entire system for sharing, then maintaining good communication and trying not to break your partners will steal the focus of key developers that would be better spent improving the system. It is tempting to think this is just a matter of increasing the budget, but that is not the way it works in practice – sharing the system with partners is not a cost that can be cleanly factored out. Just allowing partner access to the full OS build for standard Quest hardware could be done very cheaply, and would open up a lot of specialty applications and location based entertainment systems, but that would be a much lower key announcement.

Great Patch! Love the new grey out before black out effects in the Spit! Everything running smooth here on Quest 3 v63 using oculus software. Hopefully, the inclusion of the Razbam patches is indicative of progress being made toward solving that issue. Thanks team ED!

Great patch. Love the FA18 FLCS improvements! Actually damage a left gear on landing! Bravo Zulu! Kneeboards! Spitfire textures looking fine!

Getting a curl error after downloading patching process crashed. Third time looks like the patch completed successfully with same error but showing new version. 00531.129 ERROR: Got Curl error (6): Couldn't resolve host name 00532.592 STATUS: Curl error (6): Couldn't resolve host name 00560.345 === Log closed. All good now!

2.0 pd is way too high for that configuration...pushing too many pixels for the bandwidth available.

Quick $.02 after 1.5 hours in 2.9: Using my shiny new quest 3 at 72hz on my old 3090 and 5950...your mileage may vary. 1. Love the new screen space shadows! 2. For one-on-one dog fights or intensive head down radar work I still prefer 2x msaa for clarity and no jitters or smearing. 3. I do love the sharpening option with dlss quality and dlaa looks good too. I'm going to have to do more work here. Maybe increase pd and get more mileage. 4. Normandy looks much improved. 5. I look forward to experiments with lod setting and color setting. Great work DCS team! This has been a 20+ year journey for me...thank you.

New driver out from Nvidia may fix this issue for 3000 series Ampere cards. See article: Nvidia's New GeForce Driver Claimed to Fix DPC Latency Issues | Tom's Hardware (tomshardware.com)

Also, check through your axis settings and clear all the view controls assigned to various axi if you are using VR or Track IR.

The TDC knob is an axis controller, not a button push. Program it just like you program the stick. throttle, and rudder.

Nvidia Software QA Manager Says Long-Awaited DPC Latency Fix Is Ready | Tom's Hardware (tomshardware.com) Hopefully, this will be a very positive fix for DCS. Keeping fingers crossed.

Just read about the benefits of directstorage on Tom's Hardware here: Nvidia Driver Boosts GPU Decompression By 17 Percent On PCIe 5.0 SSDs | Tom's Hardware (tomshardware.com) was wondering if DCS is using it.

Maybe we could ask them nicely to do an "Apple" quality version of a VR full fidelity combat simulator on a world scale to go with the pretty headset...

The MT update internalizes OPENXR and SteamVR now. Messing with DCS vr files no longer needed.

+1 lables only in right eye in ST

And that OpenAI is pretty damn good poet...wait 'till they give DCS AI the OpenAI treatment. We'll never win a dogfight again!

In the world of code, there's nothing finer, Than a team of programmers and beta testers, a designer, Working hard to make a program better, For users who demand nothing lesser. They introduced new code, with much elation, And the program now runs at lightning's acceleration, 50% faster than before, A feat worth celebrating, and much more. But alas, there's a catch, a price to pay, For every gain, there's something taken away, The program now lost 50% of its functionality, A bitter pill to swallow, a harsh reality. The programmers and beta testers, in their zeal, Didn't anticipate the impact of this deal, But they can't turn back now, it's too late, They must accept this new fate. They hope that users will still be content, With a program that's speedy, but less potent, They'll have to make do with what they've got, And hope for the best, like it or not. But let us not forget the irony of this tale, A program that's faster, but not quite as well, Hyperbole aside, it's a lesson we should heed, To always consider the consequences of our deeds. So here's to the programmers and beta testers, Who worked hard to make the program better, May their efforts bear fruit, and may they learn, To balance speed and functionality in their next turn. -ChatGPT

No and Flat shadows are fixed along with mountain object shadows but the Low and Medium settings are borked in VR in the MT version.

My .02: Firstly, thanks to everyone involved in continuing to improve DCS World! This MT advance and other improvements in code efficiency translate to a much smoother user experience in my case. However, we've seen in the past that with the addition of large new blocks of code key functional items broken which gave a false sense that the engine was running smoother: path finding was off and broken, object view distances were borked, shadows completely messed up, various ai engines broken, etc...Once these functions were restored, game speed suffered tremendously. In the MT patch, I see broken shadows again, broken EW systems, broken ai formations, broken lighting on supercarriers, and that was just with a few hours of testing. Hopefully, as these items are addressed we won't see the degradation of performance seen in the past. Again thanks for all the hard work!

+1

Isn't DCS currently running essentially paralell processes now and each can be a bottleneck in certain cases? So much depends on mission design. 1. Multiplayer server on one CPU 2. DCS sound on a cpu 3. DCS program on a CPU for logic 4. DCS graphics and maybe some physics on a GPU

I love it when designers open up giving us insights to what lies ahead. Doing a quick search through these forums show early discussions about multi-threading back in 2005 just as dual-processor chips were hitting the streets. Commentors suggested then that it would require a complete re-write of the LOMAC code itself a development of the 1995 SU-27 Flanker product. That's 30 years of commitment to making and supporting an amazing product through all kinds of changing times, people etc. Kindest regards to all those people that have helped along the way! Fantastic news!

Very much enjoying the new 2.8 patch. No significant degradation in VR frametime for me. Had the most marvelous session just setting up a new supercarrier mission with ACLS activated for the FA-18 and all the new weather on the South Atlantic map--super immersive and I love all the great changes to the mission editor! Well done boys and girls at ED. You may have a cookie! AND WE LOVE THE SKELE'S!!! HAPPY HALLOWEEN!!!!

How long from launch? You only get 80 sec of battery time for the 120. See this thread:

Got some VR performance back after the last 2 updates knocked it back some. Still not quite where it was in March.

Tried resetting my nvidia control panel to default today and set all dcs specific settings to default. Results were even smoother and sharper.