On my 3070ti the problem does not appear. But users report problems on AMD cards.
https://forums.x-plane.org/index.php?/files/file/37864-terrain-radar-vertical-situation-display/&do=findComment&comment=377467&tab=comments

You can absolutely run Zink on an Nvidia card, which might be enough to reproduce the issue on your end (there currently is a bug with 10xx cards, that’ll be fixed in the next version or you can contact me privately for a fixed build, see a few sentences later). Although in general, the goal is to not require plugin modifications, so this is most likely a bug on our end. If you are in our dev lobby, feel free to hit me up there or alternatively you can email me at [my last name + first three letters of my first name]@x-plane.com, so like, that’d be ‘justsid’. I can most likely turn this into a bug report or direct you further.

Thanks for the update, although just to be clear, when you enabled ReShade you did so after X-Plane told you “Disabled ReShade. This layer is known to cause issues such as crashes with X-Plane. Use –allow_reshade to bypass, you have been warned!”.

I’ll make sure that in a future update, with Zink enabled, no bypass is possible anymore and ReShade gets automatically disabled.

I have discovered that my problem is not Nvidia, nor ZINK, but a plugin that was causing the problem. This is RESHADE (www.reshade.me) which -apparently- is incompatible with these new XP12 technologies, despite using it with the VULKAN option.
I removed the parameter that allowed me to load Reshade from startup and now I can load ZINK and solve other problems I had with the simulator. Thank you very much for your answer and your brilliant explanation.

You can already create shared OpenGL contexts and then render into an off-screen FBO in the background, which is something a few plugins already do. Our pipe dream is to make it more automatic without requiring any changes to the underlying plugins. But this is still ways off, solid Zink comes first and then we’ll have to actually sit down and see what we can implement. X-Plane plugins are somewhat limited in how concurrent they can be because of the whole dataref system. But we have some ideas that involve CPU side time travel with how we encode GPU workloads and then submit them in the correct order.

Runs fine on my 3080Ti, same OS and driver. Tested with default 737 and 330.
It does run slower and laggier then native though

Hold the phone…you’re saying that because this is fully contained and administered within XP, you’ll be able to let plugin authors break the decades-old mandate to only make GL calls from their master thread? You’re essentially going to make GL multi-threaded? Multiple concurrent contexts??