Originally posted by ryz4308 August 10, 2026
Hi! First of all, thank you for developing OpenNOW and for the work already done on WebRTC stability.
I would like to suggest an optional adaptive network mode for unstable or lossy connections, similar in purpose to the official GeForce NOW client’s “Adjust for network conditions” feature.
Background
My internet connection is not perfect and occasionally experiences short bursts of packet loss, RTT spikes, and jitter. I understand that OpenNOW cannot fix the user’s local network or recover data that never arrived.
However, when comparing OpenNOW and the official GeForce NOW client on the same laptop, network, server region, resolution, and similar bitrate settings, the official client appears to handle these short network problems more gracefully. OpenNOW tends to show more noticeable image degradation, repeated stutters or short freezes, while the official client usually recovers more smoothly.
I am not reporting this as proof that OpenNOW itself is responsible for every freeze. My local Wi-Fi connection is part of the problem. I am asking whether OpenNOW could provide better optional adaptation for such conditions.
Suggested feature
Would it be technically possible to add an optional network adaptation setting with modes such as:
- Current behavior / Off
- Latency-first — prioritize low input latency, even if some frames or image quality must be dropped
- Quality or stability-first — allow a larger buffer or slightly more latency to reduce severe image corruption and repeated freezes during brief packet-loss bursts
- Automatic — dynamically adjust the strategy based on packet loss, RTT, jitter, and the estimated available bitrate
Possible areas of adaptation could include receiver buffering, packet-loss recovery, pacing, FEC/NACK behavior, bitrate estimation, or other parameters already available through WebRTC and NVIDIA’s session negotiation. These are only examples—I do not know which parts are actually controllable by the OpenNOW client.
I saw that PR #635 already improved FEC, NACK, packet pacing, and adaptive receiver jitter buffering. This request is about exposing a broader optional adaptation policy similar to the official client’s network-condition setting, if that is technically possible.
Main question
Is this something that OpenNOW could implement on the client side, at least partially?
Or does the official GeForce NOW behavior depend on proprietary NVIDIA client logic or server-side encoder controls that OpenNOW cannot access?
Even if complete parity with the official client is impossible, an explanation of the technical limitations—or a smaller set of configurable recovery modes—would be very useful.
I can provide OpenNOW WebRTC diagnostic logs from test sessions with packet-loss bursts, RTT/jitter spikes, frame drops, and marked freeze periods if they would help investigate the feasibility of this feature.
Thank you for considering it. I understand that this is an open-source project, so I am not requesting an ETA or treating this as an urgent requirement.
Discussed in #727
Originally posted by ryz4308 August 10, 2026
Hi! First of all, thank you for developing OpenNOW and for the work already done on WebRTC stability.
I would like to suggest an optional adaptive network mode for unstable or lossy connections, similar in purpose to the official GeForce NOW client’s “Adjust for network conditions” feature.
Background
My internet connection is not perfect and occasionally experiences short bursts of packet loss, RTT spikes, and jitter. I understand that OpenNOW cannot fix the user’s local network or recover data that never arrived.
However, when comparing OpenNOW and the official GeForce NOW client on the same laptop, network, server region, resolution, and similar bitrate settings, the official client appears to handle these short network problems more gracefully. OpenNOW tends to show more noticeable image degradation, repeated stutters or short freezes, while the official client usually recovers more smoothly.
I am not reporting this as proof that OpenNOW itself is responsible for every freeze. My local Wi-Fi connection is part of the problem. I am asking whether OpenNOW could provide better optional adaptation for such conditions.
Suggested feature
Would it be technically possible to add an optional network adaptation setting with modes such as:
Possible areas of adaptation could include receiver buffering, packet-loss recovery, pacing, FEC/NACK behavior, bitrate estimation, or other parameters already available through WebRTC and NVIDIA’s session negotiation. These are only examples—I do not know which parts are actually controllable by the OpenNOW client.
I saw that PR #635 already improved FEC, NACK, packet pacing, and adaptive receiver jitter buffering. This request is about exposing a broader optional adaptation policy similar to the official client’s network-condition setting, if that is technically possible.
Main question
Is this something that OpenNOW could implement on the client side, at least partially?
Or does the official GeForce NOW behavior depend on proprietary NVIDIA client logic or server-side encoder controls that OpenNOW cannot access?
Even if complete parity with the official client is impossible, an explanation of the technical limitations—or a smaller set of configurable recovery modes—would be very useful.
I can provide OpenNOW WebRTC diagnostic logs from test sessions with packet-loss bursts, RTT/jitter spikes, frame drops, and marked freeze periods if they would help investigate the feasibility of this feature.
Thank you for considering it. I understand that this is an open-source project, so I am not requesting an ETA or treating this as an urgent requirement.