We found the underlying issue. This will be fixed in the next patch. Enabling sharpening for FSR2 is a workaround you could try in the meantime. The post process shaders for those write 1 into the alpha. If you're texturing your windows with a vcockpit $ texture rather than the RTT texture directly,...

It looks like the alpha channel of the RTT view is 0 for some reason. We'll try to track down why and fix it but you could work around this by using TEXTURES_USE_ADDITIVE_BLEND=1 in your panel and making sure you have a black/dark background under the texture. background_color = 1, 1, 1 TEXTURES_USE...

If you don't plan to use VR for a given session you may want to power down your HMD to avoid any extra GPU/CPU work going into driving the HMD displays and running the background/home environment. That said, it shouldn't be causing the app to freeze. More details about your system, vr hardware, vr i...

Can you provide system specs? We have had some reports of poor performance/stutters on new intel chips such as the 13900k while in VR mode with Varjo HMDs (especially in Windows 10). Some users have worked around this by disabling efficiency cores in the bios or using windows registry edits to disab...

It might be worth creating a batch script or use some other form of automation tool to run Prepar3D.exe at startup. This would then give you the option to utilize the command line switches to do things like select a starting scenario, launch multiplayer, etc.

The view matrix typically does not include any offsets, so indeed the camera is origin in world space. For our internal rendering we use a custom transform that includes a 64-bit xyz from the center of the earth and has a local level matrix pre-multiplied. We construct a standard world matrix on the...

The callback is only called when the window plugin is added to a specific window. You need to get a window (by name or GetCurrentWindow, or getting the list of windows and iterating over them) and call AddPlugin() to register your plugin to that window. Then you'll get all the window plugin specific...

I looked back at the commit logs. The issue fixed in 2021 was tied to the use of multiple gpus. The other issue turned out to be related to using multiple views/displays on a multi-channel client and could be replicated even with a single GPU. The multichannel issue has now also been fixed, and that...

At this time, no decision has been made on a future Prepar3D v5 patch release. The same approach would work to fix this in v5, so If there is another patch in the future, this fix would be a candidate for inclusion.

Thanks for the update and the detail reproduction steps. I was able to reproduce the issue and track down the cause. It should be fixed in the next release.

The field of view displaying on the server may be limiting what effects/animations run on the server which could in term limit what shows up on the clients. I believe when the view group is activated on the server it tries to assign the overall field of view of the group to the view on the server so...

One issue is that you are calling GetCurrentWindow() which may not give you the same window as your controllable camera. If no window is currently drawing, it will give you the active window or the main app window. Our frame and 1hz callbacks don't happen during a camera draw. You will get valid res...

When you sample the texture you’ll get a value from 0-1.0. To compare material IDs you need to multiply by 255. The object type passed into the shaders comes from an internal enum: RENDER_OBJ_TYPE_DEFAULT = 0, RENDER_OBJ_TYPE_SKY, RENDER_OBJ_TYPE_STARS, RENDER_OBJ_TYPE_CLOUDS, RENDER_OBJ_TYPE_TERRAI...

You should try using TerrainLodOrigin and SceneryLodOrigin in your camera definition as a first step. There is more info on this in the learning center. This features was available in v4.5. https://prepar3d.com/SDKv4/sdk/cameras/camera_configuration.html If you are using C++ you can also control thi...

There is a work-around posted here:
https://prepar3d.com/forum/viewtopic.ph ... 29#p265529

This issue is caused by new v6 defaults for the JobScheduler settings in the case where only 4 logical CPU cores are found.