It is still in development and it WILL change many times till it reach RTM state. > And this Windows build will be likely released end of the year.Īnd that's also a good reason to understand why there is no (and will NEVER be) support early insider OS builds. Uninitialized function offsets will be zero, their names will reflect affected API. You may find affected API by examining contents inside. \ProfileTemplates\Config, but it won't fix the problem. You may suppress the message with Silent=1 in section of. Unablilty to hook each of listed Direct3D versions due to running application is sandbox or application compatibility layer will result in that message. Lack of hardware acceleration support for each of listed versions will result in that message. This includes any Direct3D version supported by RTSS starting from Direct3D7 up to modern Direct3D12, each one in both 32-bit and 64-bit variations. The message guarantees that everything hooking related (including OSD) will not work for sure for some version of Direct3D API. And it is NOT working fine at all, if the message is displayed.
Click to expand.It is not just an annoying message.
0 kommentar(er)
