Qcumber Posted November 9, 2024 Posted November 9, 2024 11 hours ago, Robi Hobby said: I have the Quest 3 and my Pixel Density is 1.3 With 1.3 I see the Black Squares very sharp and large. With a Pixel Density of 1.0 they look a bit blurrier and smaller. If I set the Pixel Density to 1.1 they look larger and sharper again. Unfortunately still no solution from ED? What are your settings in meta link? Do you have the resolution slider set to 1 or pushed to the right for max resolution? Any other supersampling via Oculus Tray Tool or oculus debug tool? The reason I ask is that it is difficult to compare between headsets without knowing what the final supper sampled-resolution is. For example, someone running a Q3 with an output of 2700 pixels is going to see bigger dots than someone running at 3500 pixels. I run my Quest Pro at 3500 pixels (centre Res equivalent via QVFR) and the dots don't look too bad. PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.
Robi Hobby Posted November 9, 2024 Posted November 9, 2024 vor 45 Minuten schrieb Qcumber: What are your settings in meta link? Do you have the resolution slider set to 1 or pushed to the right for max resolution? Any other supersampling via Oculus Tray Tool or oculus debug tool? The reason I ask is that it is difficult to compare between headsets without knowing what the final supper sampled-resolution is. For example, someone running a Q3 with an output of 2700 pixels is going to see bigger dots than someone running at 3500 pixels. I run my Quest Pro at 3500 pixels (centre Res equivalent via QVFR) and the dots don't look too bad. Yes Resolution slider set to 1 , us Oculus debug tool but not Oculus Tray Tool.
YoYo Posted November 9, 2024 Posted November 9, 2024 (edited) ODT doesnt remember all settings, you have to set it up again and again. OTT remembers, its a lot better tool for this. Also you can have different profiles for each your VR games. Edited November 9, 2024 by YoYo Webmaster of http://www.yoyosims.pl Win 10 64, i9-13900 KF, RTX 5090 32Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro
Qcumber Posted November 9, 2024 Posted November 9, 2024 1 hour ago, Robi Hobby said: Yes Resolution slider set to 1 , us Oculus debug tool but not Oculus Tray Tool. By my reckoning this means that your output resolution will be about 2300. I'm not at my computer but I think the resolution at x1 in meta link is about 1750. So 1750 x PD 1.3 = 2275. Ideally you want to aim for the native resolution of the headset x1.5 for a total of 3312 (2208x1.5). This is the "godlike" setting used in Virtual Desktop. It will make the image look a lot sharper and more detailed and spotting dots should look a better size. You can set the resolution in OTT but leave PD at x1 in DCS. If your base resolution is 1750 you will need to dial in x1.9 in OTT to get 3312 pixels. Have you tried using QVFR? You can use this to set the centre resolution to x1.9 and leave the periphery at x1. This would give you centre clarity without impacting too much on performance. PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.
Bounti30 Posted November 10, 2024 Posted November 10, 2024 And still no news from ED 1 I9 9900k, RTX3090, 64Go, Nvme SDD, X56, pro rudder pedals, Quest2
SWAR1 Posted December 1, 2024 Posted December 1, 2024 On 11/6/2024 at 4:57 PM, BIGNEWY said: I use PD 1.0 in DCS with the PIMAX Crystal and its perfect for me. It is going to be very difficult to make everyone happy no matter what we do, there are way to many variables at play. How is it perfect for you? Do you see dots? I have the crystal, and I'm on 1, and I have absolutely no dots whatsoever. Like , spotting is turned off, no dots. Do I have a bug? Should I see something?
Cab Posted December 1, 2024 Posted December 1, 2024 2 minutes ago, SWAR1 said: How is it perfect for you? Do you see dots? I have the crystal, and I'm on 1, and I have absolutely no dots whatsoever. Like , spotting is turned off, no dots. Do I have a bug? Should I see something? Yeah, we’d need to know what defines “perfect”, in this case. 2
Parkour Posted December 2, 2024 Posted December 2, 2024 "Perfect" is the ability to turn OFF these spotting dots in VR. That would be perfect. For those that want them on, have fun chasing your zero. 3
Cab Posted December 2, 2024 Posted December 2, 2024 (edited) 27 minutes ago, Parkour said: "Perfect" is the ability to turn OFF these spotting dots in VR. That would be perfect. For those that want them on, have fun chasing your zero. We all get that, thanks. But “in this case” obviously referred to Bignewy’s comment. Because him referring to his experience as “perfect” for him is meaningless to us without an understanding of his idea of “perfect”. Edited December 2, 2024 by Cab 1
Bounti30 Posted December 4, 2024 Posted December 4, 2024 Has anyone noticed an improvement before I update for nothing? I9 9900k, RTX3090, 64Go, Nvme SDD, X56, pro rudder pedals, Quest2
YoYo Posted December 4, 2024 Posted December 4, 2024 5 hours ago, Bounti30 said: Has anyone noticed an improvement before I update for nothing? No any changes, also the problem from now is that you see this black box over the fog (ground units), so it looks quite unnatural. 1 1 Webmaster of http://www.yoyosims.pl Win 10 64, i9-13900 KF, RTX 5090 32Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro
Bounti30 Posted December 5, 2024 Posted December 5, 2024 8 hours ago, YoYo said: No any changes, also the problem from now is that you see this black box over the fog (ground units), so it looks quite unnatural. You will need to buy a Pimax headset.... I9 9900k, RTX3090, 64Go, Nvme SDD, X56, pro rudder pedals, Quest2
YoYo Posted December 5, 2024 Posted December 5, 2024 1 hour ago, Bounti30 said: You will need to buy a Pimax headset.... Why? I've tested Pimaxes many times and for me this VR set is overrated. I will never go to Pimax. Besides, the question was whether there are any changes after the last patch, do you think the change would only apply to Pimax? LOL . 1 Webmaster of http://www.yoyosims.pl Win 10 64, i9-13900 KF, RTX 5090 32Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro
Bounti30 Posted December 5, 2024 Posted December 5, 2024 This is probably just an interpretation on my part. But I still ask myself the question We will see I9 9900k, RTX3090, 64Go, Nvme SDD, X56, pro rudder pedals, Quest2
MAXsenna Posted December 5, 2024 Posted December 5, 2024 Why? I've tested Pimaxes many times and for me this VR set is overrated. I will never go to Pimax. Besides, the question was whether there are any changes after the last patch, do you think the change would only apply to Pimax? LOL .He probably suggests that ED and Pimax are in kahoots and DCS is tuned for Pimax. Which we know it isn't as Pimax users have reported the same issues. Sent from my SM-A536B using Tapatalk 1
Bounti30 Posted December 5, 2024 Posted December 5, 2024 (edited) 1 hour ago, MAXsenna said: He probably suggests that ED and Pimax are in kahoots and DCS is tuned for Pimax. Which we know it isn't as Pimax users have reported the same issues. Sent from my SM-A536B using Tapatalk ok I didn't have the information so I take back what I said Edited December 5, 2024 by Bounti30 I9 9900k, RTX3090, 64Go, Nvme SDD, X56, pro rudder pedals, Quest2
MAXsenna Posted December 5, 2024 Posted December 5, 2024 okI didn't have the informationso I take back what I said Well, not the first time I write this. Sent from my SM-A536B using Tapatalk
Bounti30 Posted December 6, 2024 Posted December 6, 2024 (edited) On 12/5/2024 at 12:21 AM, YoYo said: No any changes, also the problem from now is that you see this black box over the fog (ground units), so it looks quite unnatural. The same for me I tried the latest update and it's terrible. Again, revert to an old version. But let's be patient, they worked.... Given the route it takes, we're going to end up with unicorns in the sky Edited December 6, 2024 by Bounti30 2 I9 9900k, RTX3090, 64Go, Nvme SDD, X56, pro rudder pedals, Quest2
Bounti30 Posted December 6, 2024 Posted December 6, 2024 It becomes long and tiring. I'm actually thinking of stopping DCS. I pray for conquering software. For me no money for ED so much investment in equipment and modules. It’s disgusting. 2 I9 9900k, RTX3090, 64Go, Nvme SDD, X56, pro rudder pedals, Quest2
ED Team BIGNEWY Posted December 6, 2024 ED Team Posted December 6, 2024 1 minute ago, Bounti30 said: It becomes long and tiring. I'm actually thinking of stopping DCS. I pray for conquering software. For me no money for ED so much investment in equipment and modules. It’s disgusting. Sorry it is taking so long, it isnt a simple matter. But please do not derail this thread. If you need to take a break no problem I hope you will return when you are happy again. thank you 1 Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
some1 Posted December 6, 2024 Posted December 6, 2024 An OFF switch is not a simple matter? You can still turn the spotting dots off in 2D, you could turn them off in VR before the infamous "rollback" of spotting mechanics 6 months ago. 6 months we're dealing with this! And now with the new fog update it's even more broken that it was before. Seriously ED, this is embarrassing. 2 2 Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil WarBRD, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro
Fisherman82 Posted December 6, 2024 Posted December 6, 2024 2 hours ago, some1 said: An OFF switch is not a simple matter? You can still turn the spotting dots off in 2D, you could turn them off in VR before the infamous "rollback" of spotting mechanics 6 months ago. 6 months we're dealing with this! And now with the new fog update it's even more broken that it was before. Seriously ED, this is embarrassing. +1 2
Parkour Posted December 6, 2024 Posted December 6, 2024 7 hours ago, BIGNEWY said: Sorry it is taking so long, it isnt a simple matter. But please do not derail this thread. If you need to take a break no problem I hope you will return when you are happy again. thank you It's a simple matter to enable VR users to turn OFF the spot dots. Not tune it for every headset. Not take into account every possible pixel density out there. Not get it to your "white paper" design spec. Simply put in a if/then statement that doesn't call the spotting dot rendering function if the VR user doesn't want black squares. It shouldn't take 8,500 hours to figure out. We are just getting frustrated and patience is not running thin, its gone. You wanted our feedback, you asked for it, and you'll keep getting it until you give us back what we used to have. Here is some sample code to cut down on those man hours.. #include <iostream> #define DISABLE_FUNCTION 1 #if !DISABLE_FUNCTION void myFunction() { std::cout << "Function is running!" << std::endl; } #endif int main() { #if !DISABLE_FUNCTION myFunction(); #else std::cout << "Function is disabled." << std::endl; #endif return 0; } 2
ED Team NineLine Posted December 6, 2024 ED Team Posted December 6, 2024 Dear all, I thank your for the feedback on this, and I share your frustration with the lack of quality change for this. We are looking at options to allow players to adjust for their own setup. I agree its moved much too slow and I have taken my frustration up the ladder. I hope to see something new on this soon. Until I will close this until we have something new and more viable to test, and once again I apologize for the time its taken. Thanks! 3 2 Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
Recommended Posts