Search results

The bug was even more serious. The remotly_svc.exe leaked system handles (one every second) and after the weekend it showed 180000 opened handles for this process :/

Is this happening only on this one specific machine? It might be related with this service. In the next update it will have lower priority and will be optimized by a factor of 4-5x in terms of CPU usage.

This was a bug. After improvements CPU consumption of winlogon service is now reduced to near zero. Fix will be available in v1.18.0 (Monday).

Made some quick tests on this old PC. 1. Low-level capture mode 1080p@60Hz 10Mbps GPU clock runs at 320Mhz 1. Standard capture mode 1080p@60Hz 10Mbps GPU clock runs at 1050Mhz I can feel that when the GPU clock runs at 320Mhz there is 1 frame more lag. After starting something that stresses...

Another funny thing. On Window 8.1 with and old Nvidia GTX 745 and an old Core i5 CPU performance is better than on newer machines. Everything runs smoothly (no sluggishness) and CPU runs at 0.8Ghz during connection in 1080p at 60fps 10Mbps. No idea what is going on on newer PCs and new Windows...

You can monitor these clocks with GPU-Z in both cases.

Can you make the same test running Remotly.exe from the installation folder (starting without admin rights). I think I know where this "sluggishness" feel might be coming from. As Remotly is very light on GPU the clock is running lower than it should. I've seen this on Nvidia (not on Intel)...

Thanks for reporting this. In v1.18.0 next week the background processes (services) will be either suspended or run in efficiency mode when there is no connection to the host.

UPDATE: Version 1.17.4 is now available with the following hotfixes for v1.17.3: - Fixed support for very low quality/speed jittery networks (was not working properly in some situations) - Fixed "Old host version" message showing, even when connecting to newest host/server version (this message...

Hi Everyone, Please find the list of changes in this update below: - Fixed problem when devices are not visible for connection after network loss (when more than one network interface is present on the host machine) - Fixed support for very low quality/speed jittery networks (only works with...

Hi hhspiny, Sorry for the late response. We are working on v.1.17.3 that will fix all recently reported issues and bring more improvements. "3D" usage by iGPU is probably caused by RGB to NV12 conversion (or HDR RGB to NV12/P010 for HDR displays). This number can vary depending on current iGPU...

Fix to this problem will be available in v1.17.3 soon.

Changelog: - Fixed Hyper-V vGPU support for Nvidia GPUs - Improved high bitrate streaming (less stuttering, better/faster error recovery for P2P) - Fixed start with windows after fresh/clean installation - Fixed UAC popup not showing without admin rights

Nvidia hyper-v vGPU support (BSOD) has been fixed in v1.17.2 for PC: https://remotly.com/download The bug is still in the drivers that do not support asynchronous encoding in Hyper-V mode. We are now using synchronous mode for Nvidia in Hyper-V.

I didn't understand at first that this happens on normal user account and not when runing without admin rights on admin account. We will check again.

Does this happen for a non-admin instance running in the background (close Remotly on admin account, enter installation folder and run Remotly.exe will cause Remotly to start in non-admin mode). This would be a useful hint.

Only happens when "draw frame while connected" is DISABLED in Settings->General. Fixed in 1.17.1.

Please check priv message.

Please check priv message.

Fix wil be available in v1.17.1