Sign In
The path of exile jumps to Vulcan API from tonghuan's blog
Since its release in 2013, “Path of Exile” is no longer considered a
recent game, but because of continuous improvements, it continues to
receive new content, so I still consider it is still popular among
today’s players. With the new 3.10.2 update, Grinding Gear Games has
also taken a technical step. Besides the existing POE Currency mapper, it also supports the Vulkan API.
The latter is unaffected by the programs in the DirectX 11 API, and based on the experience of developers, the built-in multi-thread optimization in recent years will only make the situation worse. This phenomenon is not unique and almost everyone complained about similar things before introducing the explicit API. In short, the previous model did not allow you to control the process of critical performance, so the program developer could do nothing.
The solution is no explicit API for the above problem, because the component that caused the problem (ie the graphics kernel driver) does not exist, and the developer can control everything from the program.
Grinding Gear Games chose the Vulkan API. The renderer is still in beta, but compared to the DirectX 11 option, it has provided a more consistent performance. The current chief goal is to solve the problem of loading shades, so sometimes, DirectX 11 will be faster, but the minimum speed of the Vulkan API has been better. The later version of fix pack 3.11 will focus on more general optimization of Vulkan images, which will increase the average speed.
DirectX 11 is still the default mapper, but you can choose buy POE Trade Currency to switch to Vulkan API. For this reason, developers will recommend the latest device drivers. Starting with the 3.11 update, I plan it that Vulkan will become the default mapper, and from then on, they will focus on the possibilities inherent in explicit APIs.
According to the developers, the video game engine on which the exile path is based has been continuously developed in recent years to take advantage of multi-core processors, but when using dynamic shaded systems, shades may be loaded relatively frequently during the game, Which reduces performance. Although DirectX 11 puts its work on threads running in the background, it also requires core server threads to run graphics drivers so that the GPU can use the uploaded shade.
The latter is unaffected by the programs in the DirectX 11 API, and based on the experience of developers, the built-in multi-thread optimization in recent years will only make the situation worse. This phenomenon is not unique and almost everyone complained about similar things before introducing the explicit API. In short, the previous model did not allow you to control the process of critical performance, so the program developer could do nothing.
The solution is no explicit API for the above problem, because the component that caused the problem (ie the graphics kernel driver) does not exist, and the developer can control everything from the program.
Grinding Gear Games chose the Vulkan API. The renderer is still in beta, but compared to the DirectX 11 option, it has provided a more consistent performance. The current chief goal is to solve the problem of loading shades, so sometimes, DirectX 11 will be faster, but the minimum speed of the Vulkan API has been better. The later version of fix pack 3.11 will focus on more general optimization of Vulkan images, which will increase the average speed.
DirectX 11 is still the default mapper, but you can choose buy POE Trade Currency to switch to Vulkan API. For this reason, developers will recommend the latest device drivers. Starting with the 3.11 update, I plan it that Vulkan will become the default mapper, and from then on, they will focus on the possibilities inherent in explicit APIs.
The Wall