Intel says its XeSS frame generation override does not engage until the game's own is on

Intel says its XeSS frame generation override does not engage until the game's own is on

An Intel support engineer has reproduced the fault reported on Intel's own graphics forum: the XeSS frame generation override in Intel Graphics Software does nothing unless the game's own XeSS frame generation is already switched on. ArchieD_Intel, a Moderator on Intel’s graphics board, wrote on September 28: "I have recreated the issue that you raised."

Intel illustration of XeSS upscaling, a low-resolution frame passing through a neural network on a chip and emerging sharper

Intel's own illustration of XeSS upscaling. Frame generation and Xe Low Latency are the other two parts of XeSS 2. Image: Intel

The same post asks the reporter for trace logs, with a LogLevel value to set under HKEY_LOCAL_MACHINE\SOFTWARE\Intel\IntelGraphicsSoftware and an Intel Graphics Software log to export from Windows Event Viewer. ArchieD_Intel had come into the thread on September 22 as "a Level 2 Engineer from Intel Graphics Support".

The panel's own wording names only XeLL 1.1

The override is the control that decides how many generated frames arrive for each rendered one. The description beside it inside Intel Graphics Software, quoted in the thread, reads: "Override XeSS Frame Generation game settings to enable 2-4x frame generation. Supported on applications using XeLL 1.1 or higher." Nothing in that sentence says the game's own frame generation has to be running first.

Intel's fuller account of the feature, posted to the thread on August 25, lists Application Choice, 2x, 3x and 4x settings and gives the requirement as "The game must support XeSS Frame Generation and XeLL", on "Intel Arc discrete graphics and Core Ultra processors with Arc integrated graphics". That wording makes support a property of the game, not of a setting the player switches on.

The settings themselves are precise enough. Intel gives 2x as one additional frame for each rendered frame, 3x as two and 4x as three, with Application Choice leaving the decision to the game, and says the override can be set globally or per game. XeLL is the low-latency half of XeSS 2, the part meant to hold input lag down while the generated frames go out.

Intel saw the gap in August and has named no fix

JohnM_Intel, the other moderator in the thread, had conceded the mismatch five weeks before the reproduction, writing on August 24 that "Based on your observations, there appears to be an inconsistency between how the option is displayed in IGS and the conditions required for it to work in certain games".

ArchieD_Intel’s summary of the complaint on September 22 set out two separate problems. One was that "You are able to select XeSS Frame Generation Override in IGS for games that don't support XeLL 1.1 or higher, such as Arc Raiders which only supports XeSS 1". The other is the one Intel went on to reproduce. Intel handles one issue per thread, so the ARC Raiders half was sent to a thread of its own.

The thread opened on August 23 and had run to 15 replies when it was read at 12:39 UTC on October 5. Its most recent entry is ArchieD_Intel on October 4: "Thank you for getting back. I will investigate this and update you as soon as possible."

Intel has published no knowledge base article on it, named no driver version that changes the behaviour, and has not said the panel text is wrong. What is on the record is that an Intel engineer reproduced what was reported and asked for logs.

CD Projekt Red pointed Witcher 3 players at an AMD driver that had not shipped, another case of a vendor's own instructions describing something the software does not do. Intel's is narrower, since what is in question is the panel's wording rather than the feature.

Intel's stated requirement has not moved: the game must support XeSS frame generation and XeLL. What the thread adds is that supporting it is not enough.

Leave a Comment

Your email address will not be published. Required fields are marked *