Oh wow. Two bugs I can already see in the #NVDASR 2025.1 remote's implementation that I absolutely dislike:
- When muting the remote computer, with the "mute remote" option, this was reworked so that any time the remote machine speaks, it gets unmuted again. This makes the feature useless now, because I do this often when I'm on another laptop, have headphones connected through my desktop through which my work laptop is connected. I know, I'm complicated, 3 computers. But this is when using "mute remote" on that secondary laptop, like the HP I just got back finally today, really helps. Thanks NVDA for breaking it.
- If connected to a remote computer, and your remote computer disconnects but you left control inside the remote session on the target, you cannot switch back out of the remote session, because it will just keep saying, "no computers are connected." Now, again, I do the "host control server" thing, so I don't know if this applies to when connecting to a server directly, but it means that you are stuck in a non-functional target machine until your remote host reconnects. Also, very very bad.
Both of them are horrible and make NVDA's remote implementation quite different from the add-ons.