![]() If you don’t have a UI or a GPU and are trying to run RV on a headless server, RV won’t work either through VNC or RDP. You will likely be limited to whatever GPU you have on your local machine. If you’re using a VNC solution like RGS Desktop, but don’t have a monitor connected at the host you’re connecting to, you may need to forward your local Display (for example X server) to the machine you’re remoting into. Unfortunately Nvidia limits OpenGL over RDP to their professional grade GPUs. RDP, for example Microsoft Remote Desktop, does NOT work with RV unless you have a Quadro-level professional graphics card from Nvidia on the host that you’re remoting into. Once this is set up, RV will likely work as expected for most remote desktop clients. You’ll also need to check your Display server configuration ( nf for Linux X server) on the machine you’re trying to remote into to allow GPU forwarding. ![]() Otherwise, as you may have noticed from previous posts, RV is very tightly coupled to hardware, which means that for RV to work remotely you need to have a way for RV to register the remote monitor and for remote machine to have access to at least OpenGL 4.x. If you have a Teradici host, there’s nothing you need to set up to get RV to work remotely, it should just work. RDP: Remote Desktop Protocol, where examples are Microsoft Remote Desktop, Free RDP, etc. VNC: Virtual Network Computing, where examples are HP RGS Receiver, OpenVNC, etc. We’ll keep this post updated as we discover more. Please note that this information is incomplete as we’re also discovering how to solve this new challenge on our end. With studios moving to work remotely due to the unprecedented COVID-19 outbreak, we thought it may be useful to go over how RV works in a virtualized environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |