Search results

uninstalled and reinstalled, still the same. in normal user account, when install a program that needs admin right, the UAC dialog box does not show up. need to connect to admin instance to see it.

it is the same whichever encoding to use. quicksync or nvenc with or without HEVC or any max bitrate I set from 5 to 50mpbs. without hardware encoding, it is even worse. sometimes it is once in a few minutes, sometimes it is once every minutes. worse with android. it happens with two...

always have had the problem. have changed client, server, router, and issue stays. making me think might be from remotly itself. run in home wifi >500mbps, RTT < 5 ms, never above 20ms. once in a few minutes, get a freezing with the bad network symbol on for 0.5-3, typically 1-2 seconds, and...

the voice chat button works fine in window mode, can turn on or off. in full screen mode, it can only be pushed once, then it stays in gray color. I think the function still works, just the icon.

yes. remotly_boot_svc.exe is running.

used to work fine in 1.15. in 1.17 (maybe 1.16), the UAC (for admin) dialog box is not visible in normal user instance anymore. need to re-connect to the admin instance to type in admin password

Got another laptop with Intel Arc 370 video card (which should be similar to what is in Core Ultra 9 CPU) and 3k screen. works fine. something unique about the ASUS laptop I have that caused the freezing

It has most likely been thoroughly considered by the developer, but I am curious as to why only use id instead of id (which stays the same with computer) + passcode (which can be changed)? seems to be different from most other apps. there are certain benefits of having ID+passcode...

Mine is the same as yours

per suggested by Mirillis, the following seems to have fixed the freezing problem. task manager -> remotly.exe -> right click -> properties -> compatibility -> change high DPI settings -> high DPI scaling override -> check override high DPI scaling behavior -> "System". note that the same...

No freezing scaling at 175% or below, can move GUI to different screen. freezing at 200% or above, crash when moving GUI to different screen. happens both with external monitor and laptop screen only, both start freezing at 200%. This is with ASUS Zenbook Duo with Core Ultra 9 iGPU and 3k...

1.16.0 behaves the same as far as I can tell.

tested with 1.13 and 1.14. same thing. Definitely affected by DPI setting ("screen scale"). the freezing does not happen at 100%. and consistently happens at 200% and 225% which is what I use with 4K display. killing and restating remotly.exe enoug times, it eventually works. that is how I am...

there is no crashlog.txt under C:\Program Files (x86)\Mirillis\Remotly it does not show white screen anymore, just GUI freezing. can only interact only once with any GUI element (including mouse over if that has effect on GUI). second time interacting with any GUI element, it freezes. does...

screens have different DPI. also happens with only one screen in the laptop.

tried that. did not work. did uninstall - reboot - reinstall. now killing launcher.exe did not work anymore. found out that if moving the window to other screen, the GUI crashes -- remotly.exe is gone. now this is completely unusable in my client computer. installed on server, does not...

one possibility is that once remotly.exe gets killed, the watchdog process launches another one right away, which gives white screen. without watchdog, the remotly.exe is indeed manually launched, and without problem. this is behavior is highly repeatable on the computer. I have tried 10+...

yes. I have done quite a number of times. have to kill both launchers for manually started remotly.exe to work. if only _64 is left (and remotly.exe dos not auto-start), same white/freeze.

not deleting the file. just kill the process from task manager. I have only tested on one computer so far, so there might be particular conflict with other software though as there is a ASUS virtual keyboard software and windows manager software. keep that in mind. but this is the same client...

yes. that is what I had to do. kill all remotly.exe and launcher (incl. launcher_x64). then run remotly.exe manually. that is the only way to get it to work without either white window or GUI freezing.