Search results

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

reboot without internet. "connect failed, not logged in" prompt just keeps popping up and won't stop. please fix.

well, running remotly.exe in normal user account has a problem -- UAC dialog box is not accessible (the one asks for admin credentials for app install etc). I figure remotly.exe runs in user's context, hence can't access UAC dialog box. The solution right now is to a), in normal user...

I really like the "require device authorization" at per host level. however, it does bring a problem. say if I am away, and need to access a host from a new computer, there will be no way for me to authorize the new device via dialog box popped on host's screen. Need an alternative way of...

any idea on timing of paid plan? 1MB/sec is too slow to be practically useful

the P2P with error correction indeed prevented pixelation. but the picture would completely freeze for 1-3 seconds. while Parsec only slows the framerate down. tested on the same host/client/network/app between remotely vs. Parsec.

looks like file transfer is capped at 1 MB/s. would it be possible to allow high speed file transfer for P2P connection? or is the high speed file transfer is reserved for future paid version?

I can confirm that the method you listed above for use under normal user account works well. HW encoding is enabled now. also did a comparison to Parsec, and performance is similar for 3D benchmark. the only difference been that Parsec seems to handle network jittering somewhat differently...

I think I understand how it works. remotly_boot.exe runs in background at boot, but gets replaced once remotly.exe actual runs. but many features are implemented only in remotly.exe only, hence the problems I have faced. did you by any chance test out this following? which might also result...