-
Posts
128 -
Joined
-
Last visited
About unltd
- Birthday March 26
Personal Information
-
Flight Simulators
DCS
Iracing
MSFS
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
For those having wanky vr performance after patching, try a fresh full pc shut down and reboot; did wonders for me.
-
Go into controller axis settings for each offending aircraft and clear the conflicts and reset the control you want for the function (in my case throttle) then restart DCS.
-
Good update for me after dealing with the mouse polling issue and the Quest 3 controller binding issue. Definitely freaked me out a bit but a few quick querries brought solutions immediately. Thanks for all the hard work Eagle! Keep moving forward!
-
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.
-
Mike Force Team started following unltd
-
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)
-
Thrusmaster Warthog TDC Issue
unltd replied to KSA Death Force's topic in Controller Questions and Bugs
Also, check through your axis settings and clear all the view controls assigned to various axi if you are using VR or Track IR. -
Thrusmaster Warthog TDC Issue
unltd replied to KSA Death Force's topic in Controller Questions and Bugs
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...