yeah, I already now this thing about the Vulkan API. However, I'm a big fan of betas if sth works not as it should and voila: newest X-Plane 11 beta, set the workaround for AMD to true again (default settings, a dev from LR wrote this once: you can add a --no_workaround to the destination in the shortcut's start properties to maybe archieve better results) meaning that I deleted that tag and fired it up: voila, 21 FPS in outside the glareshield of the A330 on EDDF's 07C at night with the following settings:
Texture quality Maximum with 2771MB of texture loaded (I've got Ortho4Xp overlays on 16 or 15 I guess for Frankfurt)
No shadows on scenery
High amount of objects
Medium reflection details
all @1080p so 1920x1080
My system specs:
Windows 10 Pro 64bit (or x64 as you wrote ) - i7-6700k @Stock which means 4Ghz and 4,2Ghz on Turboboost - 16GB RAM clocked at 3200Mhz - MSI RX480 Gaming X 8GB - Saitek Pro Flight Yoke (with one throttle quadrant incl) - Saitek Pro Flight Throttle quadrant (seperate) - Saitek Pro Flight Pedals - (sometimes a Saitek Cyborg X)
Software: X-Plane 11.11r2 - JD A330 v2.2R2 with Blue Sky Star RR700 soundpack - nothing from Flightfactor (A320 coming soon ) - Navigraph Simlink - AutoGate v1.72 - Better Pushback v0.45 or 46 (hard to see) - Ground Handling - Sim Coders Headshake 1.7 - X-Life - X-RAAS 2.0.3 (recommended !) - XSBMsgSound 0.1.1 - XSquawkBox - Landing Speed 2.0.2 - many map related things for MisterX KSFO and KBOS (ground traffic) (both turned off)
ACFT: A330 as mentioned above, free EC 145, free Eurofighter Typhoon (hardly use them).
Tell me more about TerrainRadar...
Good night (Middle Europe for me, Germany) and happy landings
EDIT: no, afaik it's not only about OpenGL, but also about the use of Render Threads: X-Plane has only one render thread, so you're not better of with a Ryzen processor, but with high clock rates. CPU as a limiting factor, so you've got a better cpu
EDIT2: Betas if things not work as expected: I'm a Windows Insider, but Windows works fine