@slient 50nm is about right for the SDB 1 that we have. 70+nm is the SDB2 which is not in BMS AFAIK
Best posts made by obsidianuk
-
RE: SDB and jsow max range
-
RE: Quest 2 great results on moderate system specs
Just to clarify - your running 90hz in oculus - i assume that’s at max resolution on the slider?
Also in Nvidia control panel… It’s the falconBMS.exe in the 64 bit bin folder.
For NVCP AA;
Only FXAA works.
Multisample AA / Transparency if set to enhance or override doesn’t have an effect (tested in 2D at 1440p) and no noticeable different in VR.I’d personally set environment mapping and water env mapping to 0 as it add (IIRC) 8 more renders to the scene, especially if your running “set g_fVRResolution 1.4”.
What I don’t get is I have perfectly readable MFDs at max oculus render res and g_fVRResolution at 1 (default). I get the feeling people are increasing that before oculus render res. Should always maximise oculus res and encode width to at least 3664 before fiddling with other things to increase readability otherwise your just working against yourself.
Latest posts made by obsidianuk
-
RE: SDB and jsow max range
@CheckPoint I wonder if it’s just the same flight model as the SDB 1
-
RE: SDB and jsow max range
@slient 50nm is about right for the SDB 1 that we have. 70+nm is the SDB2 which is not in BMS AFAIK
-
RE: Balkans issues……?
@cougar56th
Small doc issue I noticed on the airfield charts for Galatina- both parking charts (RW14 & 32) have a large black polygon blocking the view. Installed latest Balkans 4.37.2 -
RE: Optimizing Quest 2
@danster From what I gather latency will be the delay between when the image rendered to it being displayed in headset. I don’t use airlink or VD, but believe a latency of 40ms is typical for non wired. I think to get 20 you may need cable.
But if the picture is smooth then don’t worry about the numbers!
-
RE: Optimizing Quest 2
@DanWolo probably, but I usually avoid WVR combat.
-
RE: Optimizing Quest 2
@DanWolo no, normally run 80hz, but with AWS forced on, so stable 40
-
RE: Optimizing Quest 2
@DanWolo I run a 3070 and have everything at 1.0 except quest 2 render slider, which is maxed. This will give the best possible 1:1 clarity with no supersampling.
-
RE: Optimizing Quest 2
@danster all resolution sliders will be multiple of each other.
-
RE: Tacview – Understand what happened during your last flight! (alternative ACMI viewer)
@BuzyBee I note in your changelog;
“IMPROVED Korea database and terrain for BMS 4.36
IMPROVED Israel database and terrain for BMS 4.36”We’re on 4.37 now - I don’t know if the database has changed, but maybe it’s worth looking into updating?
-
RE: Quest 2 great results on moderate system specs
Just to clarify - your running 90hz in oculus - i assume that’s at max resolution on the slider?
Also in Nvidia control panel… It’s the falconBMS.exe in the 64 bit bin folder.
For NVCP AA;
Only FXAA works.
Multisample AA / Transparency if set to enhance or override doesn’t have an effect (tested in 2D at 1440p) and no noticeable different in VR.I’d personally set environment mapping and water env mapping to 0 as it add (IIRC) 8 more renders to the scene, especially if your running “set g_fVRResolution 1.4”.
What I don’t get is I have perfectly readable MFDs at max oculus render res and g_fVRResolution at 1 (default). I get the feeling people are increasing that before oculus render res. Should always maximise oculus res and encode width to at least 3664 before fiddling with other things to increase readability otherwise your just working against yourself.