Search results

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.

had white windows problem in 1.15.1, upgrade to 1.15.2, it becomes persistent. even killing remotly.exe with task manager does not solve. once remotly.exe launches it either becomes white window or the window freezes, it happens either right away or after a few seconds. the solution is to...

I think I notice a bit audio lag playing movies over lan. but might just be me being picky. I don't feel I noticed any with Parsec. but the lag, if it is real, is quite small. others might not notice

everything else works, except for the minimize/maximize/close. if close remotly from notification icon and re-start, works fine afterwards. also had an event earlier when the entire GUI area was white. had to close the GUI and restart. will post if I enter more such event.

No. this is not the connection window. it is the main GUI without any connection.

does not happen often but definitely does. the title region of remotely GUI freezes and does not react to mouse. rest is fine, can move the window. just the miminize/maximize/close buttons do not respond to mouse anymore.

seems like a good approach of creating computer/user instances observations/potential problems 1. only computer/administrator shows up in "connect to a remote computer" drop down list. need to find computer/user in "Devices" tab 2. remotly.exe does not auto-run in admin account, only in...

some observation, not sure what is supposed to work like this, what is not. 1. can connect now after reboot without login 2. connect to login screen, login to regular or admin, remotly auto-starts. this disconnect though. 3. when sign-out from account, or switch user back to sign-in screen...

one thought .... An authorization request is sent to mobile App for approval -- similar to authenticator app -- if there is a mobile client already authorized. or designate a mobile client as the authenticator.

thanks for the quick fixes. did a clean install to test the new version: install in admin account, run, login to remotely account, add authorization, set start with windows. reboot. login to normal user account, run remotly.exe, need to login to remotely again, add...

mobile app seems to be a reasonable solution. thanks