A gaming laptop displays a fantasy mountain scene, with glowing graphics illustrating its internal hardware.
Offloading frame generation to integrated graphics can give a struggling gaming laptop a smoother-looking second wind—but it can also move the bottleneck rather than remove it. An XDA experiment using a Ryzen 7 5800H and a 4GB GeForce RTX 3050 illustrates both sides: substantially higher displayed frame rates in Valheim, followed by severe slow-motion-like behavior when the integrated Radeon GPU was pushed too hard.

The useful lesson is not that an idle iGPU provides unlimited “free FPS.” It is that dual-GPU frame generation needs its own performance headroom, even when the dedicated GPU is doing the original rendering.

A gaming laptop displays a fantasy mountain scene, with glowing graphics illustrating its internal hardware. What the laptop experiment actually showed​

XDA’s Mainak Kumar Dey tested an ASUS Vivobook with a Ryzen 7 5800H, RTX 3050, and 16GB of soldered dual-channel DDR4 memory. According to his account, the internal display connects through the processor’s integrated Radeon Vega graphics, and the laptop has neither a physical MUX switch nor Advanced Optimus.

His configuration split the work between the two GPUs:

  • RTX 3050: Render Valheim and Enshrouded, selected through Windows Graphics Settings.
  • Integrated Radeon graphics: Run Lossless Scaling Frame Generation, selected through the application’s Preferred GPU setting.
  • Lossless Scaling: Use Performance mode and 70% Flow Scale, with a 3× multiplier for Valheim and 2× for Enshrouded.

In demanding Valheim Ashlands scenes, Dey reported approximately 40–45 FPS before generation and more than 100 FPS afterward. He described movement and combat as substantially smoother, including parrying attacks.

Enshrouded benefited during solo exploration, but building and densely populated scenes still produced major slowdowns. The experiment therefore demonstrated improved perceived smoothness in particular conditions—not a general cure for an underpowered system.

These are author-reported results, not independently reproduced benchmarks. The account does not provide controlled frame-time captures or instrumented input-latency measurements.

The catch: the second GPU can run out of room​

The experiment became unstable when Dey increased Flow Scale beyond 70%. Integrated GPU utilization approached 90%, frame delivery deteriorated, and gameplay appeared to enter slow motion.

That distinction matters: 70% Flow Scale is an application setting, not 70% GPU utilization. Neither that setting nor the reported 85–90% utilization range establishes a universal limit for other laptops.

The developer’s Steam listing confirms that Lossless Scaling supports moving processing to a second GPU. However, its requirements also warn that insufficient available GPU resources can affect the game’s original frame rate. Offloading changes where the work happens; it does not make the work disappear.

Nor does the account establish exactly why the slow-motion-like effect occurred. Saturation coincided with the problem, but the available measurements do not isolate compute capacity, capture timing, memory traffic, or another component as its sole cause.

Smoother output is not faster game simulation​

Dey turned to this arrangement because lowering graphics settings did not consistently improve demanding scenes, while running frame generation on the already heavily loaded RTX 3050 reportedly introduced stutter and other problems.

Lossless Scaling’s developer describes LSFG as creating additional frames to improve visual smoothness. Its Fixed mode multiplies the original frame rate; Adaptive mode targets a chosen output rate. Those extra images should not be confused with an equivalent increase in the game’s underlying rendering or simulation performance.

That is why the Enshrouded result is particularly instructive. Interpolation made some movement look better, but could not rescue the underlying performance collapse around complex builds.

The source attributes those limits partly to CPU workload and a reported 35W processor configuration. That power figure needs context: AMD lists the Ryzen 7 5800H with a 45W default TDP and a configurable 35–54W range. The reported 35W setting is therefore within its published range, not the processor’s universal specification. It does not, by itself, prove the cause of the game’s slowdowns.

Memory and latency remain part of the bill​

Dey reported that enabling iGPU frame generation increased Windows RAM usage by roughly 500–800MB. That is an observation from this machine, not a fixed LSFG memory requirement or a measured one-for-one reduction in dedicated VRAM consumption.

His responsiveness assessment also requires care. Although he initially described no noticeable input lag during Valheim combat, he later acknowledged additional delay that remained manageable. Without latency measurements, the defensible conclusion is that he found the experience playable—not that offloading eliminated latency.

The developer’s historical version 3.1 notes reinforce this trade-off. They describe capture queue settings that balance responsiveness against tolerance for unstable frame delivery: a larger queue can accommodate variation but may introduce more latency. Those notes are useful context, not confirmation of the version or queue configuration used in XDA’s experiment.

What Windows users should verify first​

Before treating this configuration as a recipe, establish the basics:

  1. Check software compatibility. The developer specifies Windows 10 version 2004 or newer and supports windowed or borderless-fullscreen operation. Exclusive fullscreen has a limited second-display exception.
  2. Confirm GPU assignments. Microsoft documents per-app GPU preferences under Settings > System > Display > Graphics. Select the intended rendering GPU rather than assuming Windows chose it.
  3. Account for display routing. XDA’s result depended on a particular hybrid-graphics arrangement; it is not evidence that every internal panel or external display connection behaves identically.
  4. Compare the same demanding scene with generation off and on. Following this experiment’s failure pattern, watch underlying game performance, integrated GPU load, system memory, and responsiveness—not merely the larger output FPS number.

The practical verdict is cautiously encouraging. This Vivobook gained useful smoothness by giving its integrated graphics a second job. But the successful configuration was a balancing act, not a hidden hardware upgrade: once the helper GPU became overloaded, the workaround needed a workaround of its own.

 

References

  1. I offloaded frame generation to my iGPU to save performance, but there is a hardware catch XDA 2026-11-16T12:00:21+00:00
  2. Offloading Lossless Scaling Frame-Gen to secondary GPU eliminates overhead | Tom's Hardware tomshardware.com
  3. Optimizations for windowed games in Windows 11 | Microsoft Support support.microsoft.com