DLSS 4.5 Frame Generation frames are not captured in stream

Description

DLSS 4.5 Frame Generation / Multi Frame Generation frames do not appear to be captured by Apollo when streaming.

On the host, DLSS frame generation is enabled and the game reports the higher frame rate from frame generation. However, on the client side the incoming stream only reaches the native/rendered frame rate. The generated frames are not transmitted to the client.

This seems similar to the previously mentioned DLSS4 capture limitation in discussion #717, and also similar to the Sunshine report where newer DLSS Frame Generation DLL versions only streamed native frames:

• https://github.com/ClassicOldSong/Apollo/discussions/717
• https://github.com/LizardByte/Sunshine/issues/3621

Expected behavior

When DLSS Frame Generation is enabled on the host, Apollo should capture and stream the final displayed frame rate, including generated frames, so the client receives the same smoothness/FPS as the host display.

Actual behavior

The client only receives the native/rendered frame rate. DLSS-generated frames are missing from the stream.

Example: if the game is rendering at a lower native FPS and DLSS Frame Generation increases the host-side displayed FPS, the client still only receives the lower native FPS.

Environment

• GPU: NVIDIA GeForce RTX 5070 Ti Laptop GPU
• NVIDIA driver: 610.62
• Apollo version: 0.4.6 (latest release at time of report)
• DLSS version/path: DLSS 4.5 Frame Generation / Multi Frame Generation
• Games affected: all tested games with DLSS Frame Generation enabled
• Client: not provided yet
• Client target FPS / refresh rate: not provided yet
• Capture method: not provided yet
• Host OS: not provided yet

Reproduction steps

1. Start Apollo on the host.
2. Start streaming to a client.
3. Launch any game that supports DLSS 4.5 Frame Generation / Multi Frame Generation.
4. Enable DLSS Frame Generation in the game.
5. Compare the host-side reported/displayed FPS with the client incoming FPS.

Notes

If this is an expected limitation of the current Windows capture path, please confirm whether there is any supported workaround, such as WGC vs DXGI, running Apollo with administrator privileges instead of service/System privileges, forcing an older DLSS Frame Generation DLL, or using a specific virtual display / capture configuration.