-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
[Arch: AMD] Toggling crosshair causes lag spike & resets ReLive's Instant Replay. #221
Comments
I appreciate the digging you've done. It could be caused by the fade, the iohook native library I'm using on Arch, or possibly a conflicting keybind. Hopefully the former, I'll add an option to disable the fade. |
Also is arch short for architecture or is it Arch Linux? Cause I noticed you changed my previous issue to that so I labeled this one that way as well assuming that it was architecture (like nvidia gpu or amd gpu), but I am running Windows 10 Pro 22H2 (19045.2251) with an RX 480 8GB if it's meant to mean Linux. |
Also, yep, arch is for architecture (intel vs amd vs m1/2), I see where the confusion came from. |
Alright, just wanted to make sure I wasn't providing misleading/incorrect information. |
This should be fixed in the pre-release version posted soon. |
When you hide/unhide the crosshair the game will lock up for a split second (duration of the hide/unhide animation maybe?), and AMD's instant replay recording will get reset.
Disabling Freesync, and trying with hardware acceleration on and off doesn't change anything. Disabling instant replay still has lag.
Attached video recorded with OBS. You can't tell from the video really that there is a spike cause I guess its spiking to above 60fps, but I can feel and see it on my monitor, and you can see the dip with fraps. At first I only click slowly, then I click rapidly to show how bad it can get. You can also see the indicator in the top left is resetting every time I hide/unhide the crosshair.
My guess is it's to due with how crossover hides/unhides them window, or maybe it's caused by the fading of the crosshair instead of it being and instant on/off (which I would prefer even if it didn't fix this).
I don't know how this program works, but maybe make the crosshair turn transparent or something so nothing about crossover's window really changes so anything that looks for the focused/main window (instant replay or freesync) doesn't see crossover as the new focused/main window, then back to the game as the focused/main window. If that's what it does already, idk.
out.mp4
The text was updated successfully, but these errors were encountered: