Announcement

Collapse
No announcement yet.

Work From Home: How to use Unreal through Remote Desktop

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Work From Home: How to use Unreal through Remote Desktop

    UE4 can be used over Remote Desktop or other desktop sharing applications such as VNC. You must make sure that support for GPU acceleration is turned on to avoid using the ‘Microsoft Basic Render Driver’. For Windows 10, this can be achieved through the computer policies:
    • Open the Edit Group Policy tool from Control Panel or use the Windows Search dialog (Windows Key + R, then type in gpedit.msc)
    • Browse to: Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment
    • Enable “Use the hardware default graphics adapter for all Remote Desktop Services sessions”
    • Optional: You can also consider activating hardware encoding. The option is: "Configure H.264/AVC hardware encoding for Remote Desktop Connections". It can also be done through the registry. https://getadmx.com/?Category=Window...CODE_PREFERRED

    Mouse Input: We recently fixed an issue with the handling of mouse inputs. This usually manifests while orbiting in the editor viewport. There is a shelved changelist for 4.24. (CL12393313)

    Game controller support: The following explains how game controllers can be used over RDP. However, we heard that USB replication is only available in Windows 10 Pro. https://www.gavpugh.com/2018/10/03/u...sktop-session/

    - - - - -

    See more work from home tips!
    Last edited by Amanda.Schade; 04-23-2020, 05:19 PM.

    #2
    The orbiting editor viewport mouse input bug is still present when using UE4Editor (4.24) remotely on Linux via a VNC client (e.g. on Ubuntu 18.04 with vino as the default VNC server on the server side).

    The following patch can be used to add a new command-line option (-norelativemousemode) to the Linux build of UE4Editor so it can be used remotely with a VNC client:

    Code:
    diff --git Engine/Source/Runtime/ApplicationCore/Private/Linux/LinuxApplication.cpp Engine/Source/Runtime/ApplicationCore/Private/Linux/LinuxApplication.cpp
    index 2eec72a6d18..ed18ad067ea 100644
    --- Engine/Source/Runtime/ApplicationCore/Private/Linux/LinuxApplication.cpp
    +++ Engine/Source/Runtime/ApplicationCore/Private/Linux/LinuxApplication.cpp
    @@ -1362,7 +1362,10 @@ void FLinuxApplication::SetHighPrecisionMouseMode( const bool Enable, const TSha
     {
            MessageHandler->OnCursorSet();
            bUsingHighPrecisionMouseInput = Enable;
    -       SDL_SetRelativeMouseMode(Enable ? SDL_TRUE : SDL_FALSE);
    +       if (!FParse::Param(FCommandLine::Get(), TEXT("norelativemousemode")))
    +       {
    +               SDL_SetRelativeMouseMode(Enable ? SDL_TRUE : SDL_FALSE);
    +       }
     }
    
     void FLinuxApplication::RefreshDisplayCache()
    Note that some VNC clients also have a problem with key press/release propagation in the editor viewport (most notably Remmina) limiting the ability to move in the viewport via keyboard. TigerVNC seems to be the one that propagates key press/release properly.
    Last edited by teijowd; 04-09-2020, 06:58 PM.

    Comment

    Working...
    X