You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current stable version of the Agility SDK reports 614.
We (Pioneers of Pagonia) check if we get the version (or newer) that we are requesting. To ensure that the game doesn't become unplayable after the patch with the current Agility SDK has been rolled out I needed to check for vkd3d and relex the SDK check to 610.
Preferable I'd like to avoid these kind of hacks.
The text was updated successfully, but these errors were encountered:
Merged an update, but out of curiosity, what is the reason the game needs to check that value to begin with? From a Windows point of view, the runtime version will always be greater or equal to the one application ships, so an application should never have to check that value.
If you have a old Windows you can create a D3D12 device without the runtime loading the D3D12Core.dll at all. Therefore we need to check if it is loaded anyways. As we already have the module handle we although ensure that the version match. It's mostly part of better safe than sorry. Players sometimes running strange tools that manipulate system dlls and we got the blame for crashes
The current stable version of the Agility SDK reports 614.
We (Pioneers of Pagonia) check if we get the version (or newer) that we are requesting. To ensure that the game doesn't become unplayable after the patch with the current Agility SDK has been rolled out I needed to check for vkd3d and relex the SDK check to 610.
Preferable I'd like to avoid these kind of hacks.
The text was updated successfully, but these errors were encountered: