Skip to content

Allow Reflex and AntiLag 2 as the low latency output with XeFG - #1212

Open
dashdogy wants to merge 1 commit into
optiscaler:masterfrom
dashdogy:xefg-latency-outputs
Open

dashdogy wants to merge 1 commit into
optiscaler:masterfrom
dashdogy:xefg-latency-outputs

Conversation

@dashdogy

@dashdogy dashdogy commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

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

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

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant