Albeit, that would have been 19-20fps in the same scenario prior to the Vulcan re-code I do hope this info helps someone, or even better, if I'm wrong and someone has a totally awesome solution for getting those frames up. That said, it appears 11.30 breaks a very important script for VR called 3jfps so for people like me that relied on it's LOD abilities to get 45fps, are only seeing 30 now. If I disable ANY core, even the fake hyperthread core, CPU utilization goes down by about 2-3% and a frame rate drop is visible from the counter inside X-plane. With all cores enabled the application (X-plane) is distributing 35 threads and average CPU is 30%. Now, it seems that Vulcan is as impressive as people say. Before, if you didn't disable CORES 0 and 1 X-plane lost 8-10 FPS, significant in the flight sim world. Quote from: Pokeyoats on January 16, 2019, 08:06:41 PM Well, the findings are very interesting, and possibly not the best news for Bitsum (though Prepar3d is still a hot mess that needs Process Lasso). BTW, I pretty much use the disable cores 0 and 1 methodology for most games and there is almost always (I guess except for Vulcan) an impressive increase in performance. Well, the findings are very interesting, and possibly not the best news for Bitsum (though Prepar3d is still a hot mess that needs Process Lasso).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |