Repository navigation
Conversation
OptiScaler's XeFG forced XeLL as the low latency output. XeFG still needs an XeLL context to pace with, so with a Reflex or AntiLag 2 output it now gets one of its own that only follows the game's markers while the chosen output does the sleeping. XeLL (and Auto) keep sharing the output's context as before. - Reflex and AntiLag 2 are only offered on their vendor's GPU, a configured one the GPU can't run works as Auto - With the low latency inputs the Reflex hooks no longer send the Reflex output's own calls to fakenvapi while XeFG is active - XeLL's sleep mode cache is per instance instead of shared by every XeLL - A switch away from the XeLL output XeFG shares waits for XeFG to restart - LatencyFlex is disabled with XeFG, the FPS limit shows Reflex for the Reflex output instead of fakenvapi's own mode
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OptiScaler's XeFG always forced XeLL as the low latency output. XeFG does need an XeLL context to pace with, but that context doesn't have to do the sleeping. So now with Reflex or AntiLag 2 selected, XeFG gets its own markers only XeLL context and the output you picked does the sleeping. XeLL and Auto work the same as before.
@FakeMichau 1 trillion prs