-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overlay corruption in some DirectX 12 games #68
Comments
edit configs.overlay.ini to use this:
And response if this fixed your issue |
Check new Release |
I checked a couple of forums, mostly related to imgui, and from what I read, this seems to be more of an issue with how the drivers work and how the AMD graphics card loads things. It appears that it takes time to find the correct hook, and when it tries to load it, it causes corruption in the overlay. (Just a note, what I’m saying might or might not be the problem, since I only skimmed through the information, and someone with more knowledge on this might be able to clarify it better.) Just in case, try adding the following lines:
Then set hook_delay_sec=0 to 30, to give the overlay enough time to find and load the DX12 hook correctly. (This might work or not, as this goes beyond the support that can be provided to the overlay.) Regarding whether I’ve encountered this problem in other games, it only happened once with Lies of P, but the error only occurred when I was switching the graphics API from DX12 to Vulkan. When I did that, the game rendered the overlay incorrectly, just like in your photos |
Unfortunately it is still the same. I think the problem lies in the AMD software. Maybe we should report this problem to ImGui. |
The overlay works fine in the game STRAY, but in Spider-Man: Miles Morales, the SHIFT + TAB shortcut doesn't open the overlay at all. Considering Spider-Man runs on DX12, what could be causing this issue? |
In some DirectX 12 games (e.g. The Last of Us™ Part I) the overlay is corrupted. In some DirectX 12 games (e.g. The Last of Us™ Part I) the overlay is corrupted. Most probably the problem is in render hooker. Because the old render hooker didn't have this problem (I don't want to be misunderstood. The old render hooker was definitely worse).
The text was updated successfully, but these errors were encountered: