Just as a quick test.Ĭlouds are what really kill the FPS for me. In the end I went with High, sometimes even Medium, objects as I do most of my flying ‘in the bush’ and in VR I’m trying to get it as smooth as possible.įWIW, full-screen with my 4K monitor is about 2x the FPS I get in VR. So I didn’t notice a loss in texture quality there might have been, but it wasn’t enough to draw my attention to it. Sounds like what I experienced, more or less. Load it up in 11.41 openGL, and its buttery smooth. It crashes every time for me becuase it says I dont have enough VRAM. Laminar C172 etc.Įasy way to test is try to fly the Zibo 737 4k Texture version on Vulkan out of LAX w/ maximum objects. You may not experience the blurry textures if you:Ī)have 11gb of VRAM (might still occur, I can’t test)Ĭ)you are using a light aircraft in regards to textures. “But I run Vulkan with maximum objects and I dont have this problem!!!” Personally, I prefer to run Max Settings on 11.41 with lower FPS. The solution: Limit objects to High if you have 8gb of ram and want to use Vulkan. I can run High (HDR) effects, Maximum objects and get about 40FPS over a big city and look great in OGL, but in Vulkan I’ll get 60+ FPS but the texture quality is greatly reduced. But for me with 8GB, I may run 20-30fps slower on OGL, but the image is vastly improved. For the 1% of people that own 2080ti’s with 11gb of VRAM, you may not notice this. So the problem is the game runs smoother and faster, but you cannot raise the settings to take advantage of the newly found headroom because you are hard limited to your VRAM amount. If you look in the Log.txt you will see lines that tell you something like:Ġ:03:35.388 E/TEX: Target scale moved to 2.000000 If the game requests more VRAM than you have available, it lowers the quality (resolution) of the textures to fit the available amount. As you fly, the game manages how much VRAM is currently being used. Flying over big cities or crowded areas brings on the problems. Sounds great, works great too as long you are in relatively open areas. The way the new API handles texture loading is voodoo magic to me, but essentially it loads the textures onto the GPU, filling up your VRAM for smoother flying. HOWEVER: I did encounter a massive drawback, and I hope it is merely related to beta testing, but if you have 8gbs of VRAM, you will not be able to run maximum object settings in crowded places without the ground textures/buildings looking like it reverted to Xplane 9. Where I was getting 30-40 FPS over crowded areas like LAX, Vulkan API can keep it will over the 4k 60fps threshold. No doubt the Vulkan mode provides a significant FPS/smoothness increase. Vulkan API in its current implementation is not better than running OpenGL. In certain situations, Vulkan API can decrease the overall image quality The Vulkan API provides a significant boost in performance
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |