The reverb did work in v4.5 when it was released. The reverb G2 was not out yet of the release of v4.5, though I can't think of any reason why it shouldn't work. It's possible that updating drivers, steamvr, and/or windows/windows-mr portal might help resolve the issue you are seeing. The newer mixe...

Every system is different and your mileage may very. By default P3D is doing its best to utilize all the CPU resources available. Tweaking these settings is not likely to give you a big FPS gain, but it may help reduce stutters and long frames that can be caused by the OS pre-empting our main or ren...

If you clear out the affinity mask settings from your config, Prepar3D should populate it with defaults based on the number of logical cores detected. That should give you a decimal number with one bit per core. (eg 65535 is generated for 16 logical cores on an 8 core i7 with hyperthreading enabled)...

Sorry about that. We initially held back on documenting it while getting feedback from beta testers. Here is the info I provided to our beta team: After you run v5.3, you'll see some new entries in the prepar3d.cfg. If you just want to move P3D's main thread off of core 0, you should be able to achi...

Ah ok. Does disabling Vsync help at all? I thought the initial report was that there was some kind of permanent offset once you moved the vehicle enough. I can clearly see in some cases that just pitching the camera up and down will cause visible tearing even inside the cockpit view where objects ar...

Is Vsync on of off? Do the views snap back into alignment when you pause the sim? If you only see this while moving, it may be that one display is a frame behind the others with swap chain presentation. I did test while moving although i've been verifying the results by using print screen and compar...

I've used your ViewGroups.xml and tested with 3 displays in a few different combinations (same GPU, two different GPUs, etc). On my system the view groups are producing identical images on startup and scenario reset. I'm wondering if there is something at play with the OS or video drivers. Perhaps t...

One thing I noticed while testing WMR recently is that the cursor hover messages might not make it into P3D if the Mixed Reality portal is blocking the desktop and showing the "Press Win+Y" prompt across the top of the screen. I think input to the desktop is blocked when you're wearing the...

The actual on-screen mouse cursor is used and it's ray tested against the left eye view. The 3d ball shown in VR is placed at the location of the left eye ray cast and the cockpit model. If you're not seeing the VR cursor, or its not moving, make sure your mouse is hovering over the p3d window and t...

Yes. Open a new views or instrument panel using the app menu. Right click the window and undock it. Drag the window to any display as long as it is connected to a compatible Dx12 GPU. Save your scenario and the window type and location should be save with the scenario.

Do the artifacts show up if enhanced atmospherics and/or volumetric clouds are disabled? Once EA is disabled, you could also try disabling HDR. It would help us narrow down what might be causing the artifacts.

Thanks

In general the recommended spec can handle P3D on higher settings without running out of system or GPU memory and while maintaining a reasonable FPS. (By default FPS is locked to 30hz). The recommended spec should also be able handle use cases such as VR, multi-view, and multi-monitor use without ha...

Thanks for all the detailed reports on this. We were able to track down the issue and it will be resolved in the next release.

I can't seem to reproduce this and I'm wondering if it might be something specific about the camera definition. Do you see this issue in the default scenario with the default aircraft?
Also, are you running any add-ons that might be using the PDK or SimConnect to manipulate windows and cameras?

If you have vsync enabled, you could try finding this entry in the Prepar3D.cfg DISPLAY section and setting it to 0: SwapChainVSyncOnlyMainWindow=1 In the past we wait for every swap chain (undocked window) when vsync was enabled, but using D3D12 and Win10, this behavior often causes a large FPS dro...