FoxTwo

TL;DR Ground and building textures in syria in VR have a very, very short distance LOD? I think. I'm not sure but even at > 30m altitude, the roads are just a blurry mess, and buildings at more than a few hundred yards look worse than buildings in SU-27 Flanker. Road example:

There's no reason they shouldn't be able to make this work, the HMQS is one eye only in VR unless you enable special options to make it less realistic.

Several parts of the UI including the server browser coming out of a multiplayer mission, the ground crew stores interface, and the F10 map loading routinely cause a SteamVR crash. Sometimes exiting DCS causes the same issue. Draw calls stop because the some part of the UI takes 100% cpu and steam interprets this as a game crash. I don't overclock. My system is otherwise stable. I opened a ticket and support said it was a problem with the pimax driver. I think this is case of buck passing, because I had the exact same problems with my HP Reverb G2 and WindowsMR. With both beta SteamVR and release versions. This mostly only happens in multiplayer. The single player experience is for the most part fine and without incident.

As far as I'm aware, the Vive Pro 2 requires a controller for initial setup.

I would not say clarity. I would say sharpness. Because the G2 is sharper than the 8Kx but the 8Kx has more consistent clarity across the lens (a much larger sweet spot) than the G2. The 8Kx is a bit softer than the G2 but you can actually look around with your eyes.

I guess I've never looked in F2 when I've done a high G turn but does the heatblur tomcat have visible wing flex modeled?

You can turn the slew into a hat by enabling switch mode in the simapp pro software, if that works better for you.

Is there an ETA for the UH-60 grip?

Finally tried this out. The effect is very good, however running to an order of operation issue where if I start shakersynth before simshaker, simshaker doesn't get any data. Also is there a way to launch via the CLI and target a specific audio device without requiring interaction? I know enough python to mess this up pretty good if I try and add argparse to it myself...

Did you have HAGS enabled? Just curious.

I think their terrain loading optimization spread the I/O load out so that you don't get a full draw call block and the game stutters and dies at 5 FPS for 20-30 seconds when changing air-frames or going in and out of the F10 map anymore. But now I think what's happening is that it's continuing to load/stream in the background and that's taking away some of the CPU for draw calls. While it's less noticeable you do see a performance hit for a minute or two while it's streaming everything in. Just a theory. Because I've noticed when I was getting 40-45 FPS on load previously now I'm getting 26-30 and then after a few minutes it'll shoot back up to the 45ish I have experienced before.

Holy crap, if you guys actually fixed the terrain loading issues that's huge. At worst it was causing frequent steamvr crashes and at best it was incredibly disorienting as FPS dropped into the teens. And with HB optimizing the F-14 load... I can't wait to try a multiplayer mission. Keep up the good work.

To be honestly I don't know that it's too dim it's just that the lines are so thin they are difficult to see in bright lighting conditions. I can see NAV on the HSD just fine but the TID repeater is just a struggle.

Stuttering? No. It's not 75 fps, but its a smooth experience. I don't chase capping the frame rate, it's not possible at these resolutions with this generation and the limitations of the engine.

I do not use motion smoothing or any frame interpolation. I can't stand it, it's disabled in pimax and in steamvr.

I'm currently running a 3080ti and a 10850k with the pimax set to wide, parallel projection disabled, and SteamVR running at 100% which is like 5100x3400. I get 35-40 fps in syria in multiplayer with 2x MSAA. Most of my settings are on high, clouds on ultra. Shadows on medium. SSAO and GI off. If I enable fixed foveated rendering I can squeeze out another 5-10 fps. But I'd rather not. 30-40 fps is fine for me.

Switching aircraft or going into the F10 map in multiplayer are enough to cause this to happen to me with a Pimax 8kx. I suspect it's a problem with the single threaded nature of DCS; it's busy focusing all the CPU on I/O to load assets into RAM and the draw calls stop, which gets interpreted as a crash by SteamVR.

Having tried/owned both, the sweet spot on both the G2 and the Vive Pro 2 are on the small side, but they are both very sharp when you're in it. Honestly it was never an issue for me as I usually just turned my head to look at something rather than just eyeballing it. The FoV in the Vive Pro 2 did not blow me away. If I wasn't using the headset back to back I doubt I'd have noticed a difference. The best sweet spot headset I've ever used is a Pimax 8KX. It's not as sharp as the G2 or the Vive Pro 2 but the clarity is consistent across almost the entire view space.

Hmmm... as of today when I try and start simshaker it's just crashing. The system tray icon loads momentarily but then disappears. The sound module still loads file, but simshaker doesn't. I've tried uninstalling and reinstalling it and deleting the config folders as well as anything in appdata. Nothing has helped. I can see the app crashing in the windows app event viewer log. Faulting application name: SimShaker for Aviators beta.exe, version: 2.2.3.0, time stamp: 0x60cdb97a Faulting module name: KERNELBASE.dll, version: 10.0.19041.1082, time stamp: 0xca3356a4 Exception code: 0xe0434352 Fault offset: 0x0012b4c2 Faulting process id: 0x3234 Faulting application start time: 0x01d779b4fba291fd Faulting application path: C:\Program Files (x86)\SimShaker\SimShaker for Aviators Beta\SimShaker for Aviators beta.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 678112ad-1ffa-490b-ba8e-31fae175af5e Faulting package full name: Faulting package-relative application ID: Application: SimShaker for Aviators beta.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Xml.XmlException at System.Xml.XmlTextReaderImpl.Throw(System.Exception) at System.Xml.XmlTextReaderImpl.Throw(System.String, System.String[]) at System.Xml.XmlTextReaderImpl.ParseText(Int32 ByRef, Int32 ByRef, Int32 ByRef) at System.Xml.XmlTextReaderImpl.ParseText() at System.Xml.XmlTextReaderImpl.ParseElementContent() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlTextReader.Read() at System.Xml.XmlTextReaderImpl.Skip() at System.Xml.XmlTextReader.Skip() at System.Configuration.XmlUtil.StrictSkipToNextElement(System.Configuration.ExceptionAction) at System.Configuration.BaseConfigurationRecord.ScanSectionsRecursive(System.Configuration.XmlUtil, System.String, Boolean, System.String, System.Configuration.OverrideModeSetting, Boolean) at System.Configuration.BaseConfigurationRecord.ScanSectionsRecursive(System.Configuration.XmlUtil, System.String, Boolean, System.String, System.Configuration.OverrideModeSetting, Boolean) at System.Configuration.BaseConfigurationRecord.ScanSections(System.Configuration.XmlUtil) at System.Configuration.BaseConfigurationRecord.InitConfigFromFile() Exception Info: System.Configuration.ConfigurationErrorsException at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean) at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(System.Configuration.ConfigurationSchemaErrors) at System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors() at System.Configuration.ClientConfigurationSystem.OnConfigRemoved(System.Object, System.Configuration.Internal.InternalConfigEventArgs) Exception Info: System.Configuration.ConfigurationErrorsException at System.Configuration.ConfigurationManager.PrepareConfigSystem() at System.Configuration.ConfigurationManager.RefreshSection(System.String) at System.Configuration.ClientSettingsStore.ReadSettings(System.String, Boolean) at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(System.Configuration.SettingsContext, System.Configuration.SettingsPropertyCollection) at System.Configuration.SettingsBase.GetPropertiesFromProvider(System.Configuration.SettingsProvider) at System.Configuration.SettingsBase.GetPropertyValueByName(System.String) at System.Configuration.SettingsBase.get_Item(System.String) at System.Configuration.ApplicationSettingsBase.GetPropertyValue(System.String) at System.Configuration.ApplicationSettingsBase.get_Item(System.String) at SimShaker.Properties.Settings.get_Starter_ShowBalloon() at SimShaker.UI.AutoStarterForm..ctor() at SimShaker.Program.Main(System.String[]) Ok further testing... I installed the 'release version' of 2.2.0.0 and it runs fine. Beta 2.2.3.0 crashes.

I believe that's max range, I've seen 1500-2000 for effective on armor.

I don't think he wasn't expecting a failure. I think he was expecting the ground crew to fix it when he requested repair. The fact that they did not seems to point towards there being a bug to report.

AMD beats Nvidia for pure rasterization performance and driver draw call CPU efficiency. In theory this should provide a superior experience in DCS.

https://forums.eagle.ru/topic/214525-wmr-debug-tool-cross-eye-alignment/ It's not strictly a WMR only configuration, but it was designed to address problems with some WMR headsets.

Well it works, and there is a performance benefit. However there is noticeable image degradation. Not significant but it's questionable whether or not just running the game at 75% resolution instead of 100% would give the same effect and overall performance benefit. Hard to say without back to back screenshots but my gut feeling after experiencing it first hand is it's about equivalent.

It's a non-temporal scaler with edge enhancement/sharpening applied. DLSS isn't THAT much different, it just has a second step where it infers the missing pixels by using temporal data (previous frames). Right now fidelityfx sr is about on par with early DLSS 1.0 implementations. It is an entirely open solution, and one that has an actual chance to gain market support as both consoles will be using it. It will only get better as time goes on. DLSS is as much hype as anything else, early DLSS didn't even utilize tensor cores at all.