Remote Desktop use of local Space Navigator

Questions and answers about 3Dconnexion devices on Windows.

Moderator: Moderators

Post Reply
jwick
Moderator
Moderator
Posts: 3328
Joined: Wed Dec 20, 2006 2:25 pm
Location: USA
Contact:

Re: Remote Desktop use of local Space Navigator

Post by jwick »

I've also added a global way to switch the way KB keys are sent.
This allows you to specify a mechanism that works with RDP for all keys and even user macros.
So you don't need to mess around with these Driver_* assignments in global.xml, base.xml, etc.
Surcouf
Posts: 2
Joined: Mon Jun 28, 2021 11:22 pm

Re: Remote Desktop use of local Space Navigator

Post by Surcouf »

jwick wrote: Tue Jun 29, 2021 1:55 am Surcouf,

PM your file to me, so I can see what changes you made.
Jwick,

sorry can't PM yet. Any chance to activate this feature or mail to my provided address so I can response directly?

Thx
jwick
Moderator
Moderator
Posts: 3328
Joined: Wed Dec 20, 2006 2:25 pm
Location: USA
Contact:

Re: Remote Desktop use of local Space Navigator

Post by jwick »

Surcouf wrote: Wed Jun 30, 2021 11:51 pm
jwick wrote: Tue Jun 29, 2021 1:55 am Surcouf,

PM your file to me, so I can see what changes you made.
Jwick,

sorry can't PM yet. Any chance to activate this feature or mail to my provided address so I can response directly?

Thx
Email sent
jwick
Moderator
Moderator
Posts: 3328
Joined: Wed Dec 20, 2006 2:25 pm
Location: USA
Contact:

Re: Remote Desktop use of local Space Navigator

Post by jwick »

New file sent
FoxbatNL
Posts: 2
Joined: Fri Jul 16, 2021 5:20 am

Re: Remote Desktop use of local Space Navigator

Post by FoxbatNL »

Hi All,

Got the Space Navigator to work over Remote Desktop. Followed the instructions to update both machines via gpedit.msc (run as admin). Be sure to select 'Administrators and Users' for the appropriate properties as descibed in the instructions.

Took some effort to understand but 2 side buttons are working fine. Key commands can't be used, however CAD software commands (in my case SolidWorks) can be assigned via the 3DConnexion properties menu on the destination machine and work like a charm.
No lag experience on rotations experienced so far. Below post gave the correct direction to go about. @Weymouth has added informational pictures in this thread as well.

Running 3DxWare version 10.7.4
pockybum522 wrote: Mon Dec 21, 2020 9:49 am Here's what finally worked for me when I was in the same boat of it wouldn't show up in the RDP Local resources section no matter what I did.

It looks like a new windows update may have added a new item under RemoteFX USB Device Redirection. See below for modified instructions. Original instructions are not mine.

(Install the same version driver on the host and client PC. I used 64-bit fine.)

These settings need to be changed on both (host and client) systems.

RemoteFX does not work with the universal receiver. You need to connect your wireless device via cable.

Run gpedit.msc

In the group policy editor open

Computer Configuration ->
Administrative Templates ->
Windows Components ->
Remote Desktop Services ->
Remote Desktop Connection Client ->
RemoteFX USB Device Redirection.

Enable: "Allow RDP redirection of other supported RemoteFX USB devices "
THIS IS THE KICKER ====> And set USB redirection rights to "Administrators and Users"

Remote Desktop Services ->
Remote Desktop Session Host ->
Connections

Enable: "Allow user to connect remotely by using Remote Desktop Services ".

Remote Desktop Services ->
Remote Desktop Session Host ->
Device and Resource Redirection

Disable: "Do not allow supported Plug and Play device redirection".

Remote Desktop Services ->
Remote Desktop Session Host ->
Remote Session Environment ->
RemoteFX for Windows Server 2008

Enable: "Configure RemoteFX".

Now open the command prompt with administrative rights.
run "gpupdate /force"

Next restart the machine.

After the restart right click the RDP connection and press edit.

Go to the “Local Resources” tab
Click on “More” on the bottom of the window (section "Local devices and resources").

You should see "Other supported RemoteFX USB devices".
Open it - it shows the connected SpaceMouse device.
Activate the checkbox for the SpaceMouse device.
The device will be forwarded to your target system next time when you connect via RDP.
FoxbatNL
Posts: 2
Joined: Fri Jul 16, 2021 5:20 am

Re: Remote Desktop use of local Space Navigator

Post by FoxbatNL »

Hi All,

Got the Space Navigator to work over Remote Desktop. Followed the instructions to update both machines via gpedit.msc (run as admin). Be sure to select 'Administrators and Users' for the appropriate properties as descibed in the instructions.

Took some effort to understand but 2 side buttons are working fine. Key commands can't be used, however CAD software commands (in my case SolidWorks) can be assigned via the 3DConnexion properties menu on the destination machine and work like a charm.
No lag experience on rotations experienced so far. Below post gave the correct direction to go about. @Weymouth has added informational pictures in this thread as well.

Running 3DxWare version 10.7.4
pockybum522 wrote: Mon Dec 21, 2020 9:49 am Here's what finally worked for me when I was in the same boat of it wouldn't show up in the RDP Local resources section no matter what I did.

It looks like a new windows update may have added a new item under RemoteFX USB Device Redirection. See below for modified instructions. Original instructions are not mine.

(Install the same version driver on the host and client PC. I used 64-bit fine.)

These settings need to be changed on both (host and client) systems.

RemoteFX does not work with the universal receiver. You need to connect your wireless device via cable.

Run gpedit.msc

In the group policy editor open

Computer Configuration ->
Administrative Templates ->
Windows Components ->
Remote Desktop Services ->
Remote Desktop Connection Client ->
RemoteFX USB Device Redirection.

Enable: "Allow RDP redirection of other supported RemoteFX USB devices "
THIS IS THE KICKER ====> And set USB redirection rights to "Administrators and Users"

Remote Desktop Services ->
Remote Desktop Session Host ->
Connections

Enable: "Allow user to connect remotely by using Remote Desktop Services ".

Remote Desktop Services ->
Remote Desktop Session Host ->
Device and Resource Redirection

Disable: "Do not allow supported Plug and Play device redirection".

Remote Desktop Services ->
Remote Desktop Session Host ->
Remote Session Environment ->
RemoteFX for Windows Server 2008

Enable: "Configure RemoteFX".

Now open the command prompt with administrative rights.
run "gpupdate /force"

Next restart the machine.

After the restart right click the RDP connection and press edit.

Go to the “Local Resources” tab
Click on “More” on the bottom of the window (section "Local devices and resources").

You should see "Other supported RemoteFX USB devices".
Open it - it shows the connected SpaceMouse device.
Activate the checkbox for the SpaceMouse device.
The device will be forwarded to your target system next time when you connect via RDP.
markus123
Posts: 2
Joined: Tue Jul 20, 2021 6:10 am

Re: Remote Desktop use of local Space Navigator

Post by markus123 »

I have the same issue: I use the Enterprise in a remote session, it works perfect, but the Esc/ Tab/ Shift/ Ctrl/ Alt/ Space keys don`t work.

jwick ... can u send me the edited base.xml, maybe it works with it?

Thank u very much for your help.
Best regards
jwick
Moderator
Moderator
Posts: 3328
Joined: Wed Dec 20, 2006 2:25 pm
Location: USA
Contact:

Re: Remote Desktop use of local Space Navigator

Post by jwick »

markus123,

PM sent
markus123
Posts: 2
Joined: Tue Jul 20, 2021 6:10 am

Re: Remote Desktop use of local Space Navigator

Post by markus123 »

Thank you very much jwick!

Esc/ Shift/ Ctrl and Alt work great now!

But i`m still struggling with the Tab/ Space/ Enter and Delete key- they don`t work. Do u have an idea what could be wrong?

Thanks
jwick
Moderator
Moderator
Posts: 3328
Joined: Wed Dec 20, 2006 2:25 pm
Location: USA
Contact:

Re: Remote Desktop use of local Space Navigator

Post by jwick »

There is no equivalent Tab in the released driver. You have to wait for the next major release for fuller support.

Delete and Return can be added by editing that Base.xml.

Change

Code: Select all

            <ActionID>KB_Enter</ActionID>
to

Code: Select all

            <ActionID>Driver_KB_Return</ActionID>
and

Code: Select all

            <ActionID>KB_Delete</ActionID>
to

Code: Select all

            <ActionID>Driver_KB_Delete</ActionID>
You will find them in the ID_Standard_3D_Mouse, but you can just search for them.
apmik2
Posts: 2
Joined: Thu Oct 14, 2021 6:08 am

Re: Remote Desktop use of local Space Navigator

Post by apmik2 »

Hi,

is there any info on when we can expect this new version? Tab, space and macro support is required for me and right now I am out of luck.
jwick
Moderator
Moderator
Posts: 3328
Joined: Wed Dec 20, 2006 2:25 pm
Location: USA
Contact:

Re: Remote Desktop use of local Space Navigator

Post by jwick »

apmik2,

Install 10.8.3 (new as of a few days ago).
Add this bolded line to your %appdata%\3Dconnexion\3DxWare\cfg\Global.xml file:

<Global...>
...
<Settings>
...
<KMJMechanism>SendInput</KMJMechanism>
...
</Settings>
...

Let me know if it works for you for all macros and keyboard keys in the remote environment.
apmik2
Posts: 2
Joined: Thu Oct 14, 2021 6:08 am

Re: Remote Desktop use of local Space Navigator

Post by apmik2 »

Hi,

after some quick testing it seems like it works, I will test it further in a few days. I just changed the line in Global.xml and all the keyboard inputs work. If anything happens or I have any problems I will let you know.
dogansur
Posts: 1
Joined: Fri Oct 29, 2021 2:32 am
Contact:

Re: Remote Desktop use of local Space Navigator

Post by dogansur »

I am having the same issue you are with Virtualhere. Unfortunately, I have not found any resolve.
LinaClark
Posts: 4
Joined: Wed Dec 22, 2021 4:48 am
Location: Singapore

Re: Remote Desktop use of local Space Navigator

Post by LinaClark »

D_Roam wrote: Fri Jun 19, 2020 5:57 am Has anyone had success in getting the RemoteFX solution to work when the local (client) computer is running Windows 10 Home (not Pro)? I have Windows 10 Home on my home PC, so I can't open gpedit to enable Remote FX for RDP. I read some posts saying there are scripts to enable the correct settings, but it did not work for PCs running Windows 10 Home.

Has anyone gotten this to work? Greatly appreciate any help.
It's possible to setup remote desktop windows 10 home, but you'll have to work with libraries (Wrapper and RDP wrap). You'll have to download them from GitHub. Here's a step-by-step instructions https://www.helpwire.app/blog/remote-de ... s-10-home/
Post Reply