3DConnexion settings not working as expected #4104

foreachthing · 2020-04-21T09:20:28Z

Version

version_2.2.0-157-g40e4be6ed

Operating system type + version

Windows 10 x64

Behavior

Maybe I missed something but:

3Dx-Device is really slow
Press CTRL+M ..... does nothing.
- also, it's not listed in the keyboard shortcuts list.
EDIT: 3Dx settings (speed, etc.) have no effect

Expected

Press CTRL+M to change the 3Dx settings

bubnikv · 2020-04-21T09:38:41Z

You have to have the 3D scene active. It has to have a keyboard focus. út 21. 4. 2020 v 11:20 odesílatel Gilbert <notifications@github.com> napsal:

…

Version version_2.2.0-157-g40e4be6ed Operating system type + version Windows 10 x64 Behavior Maybe I missed something but: - 3Dx-Device is really slow - Press *CTRL+M* ..... does nothing. - also, it's not listed in the keyboard shortcuts list. Expected - Press CTRL+M to change the 3Dx settings — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4104>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMPSI6GPSUOW6CFVVL2223RNVQO7ANCNFSM4MNENSRQ> .

enricoturri1966 · 2020-04-21T09:41:27Z

Newer versions of PrusaSlicer on Windows use the 3DConnexion device settings, that's why the settings dialog embedded into PrusaSlicer is no more available.

bubnikv · 2020-04-21T09:59:46Z

Newer versions of PrusaSlicer on Windows use the 3DConnexion device

settings, that's why the settings dialog embedded into PrusaSlicer is no more available. That is the upcoming PrusaSlicer 2.3. PrusaSlicer 2.3 will not need the built-in settings dialog. út 21. 4. 2020 v 11:41 odesílatel enricoturri1966 <notifications@github.com> napsal:

…

Newer versions of PrusaSlicer on Windows use the 3DConnexion device settings, that's why the settings dialog embedded into PrusaSlicer is no more available. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMPSI4REN7SZZPYBALHLQTRNVS5PANCNFSM4MNENSRQ> .

foreachthing · 2020-04-21T11:40:10Z

Ok.
But I'm still on 2.2 and my SpacePilot is ultra-slow. 3Dx speed settings are ineffective.
Do I have to wait for 2.3 now?

enricoturri1966 · 2020-04-21T11:46:39Z

@foreachthing
You wrote "2.2.0-157-g40e4be6ed" as the version referring to this issue, so the guess was that you built PrusaSlicer by yourself.
That version already contains the changes I was talking about in my previous comment.

foreachthing · 2020-04-21T12:05:43Z

Yes, I did build it myself.
What I'm saying is, that the settings in the 3Dx panel have no effect.
Speeds are all set to 100% and it's still ultra-slow.

Now I am at commit 9bc96bf - no change.
3DxWare 10.6.6.3194

enricoturri1966 · 2020-04-24T06:25:13Z

@foreachthing
Could you please try to copy the attached files into:
C:\Users<username>\AppData\Roaming\3Dconnexion\3DxWare\Cfg
to see if this helps in fixing this issue ?

https://www.dropbox.com/s/prziag60rutngap/prusa-slicer.xml?dl=0
https://www.dropbox.com/s/2vov4o86tf09439/prusa-slicer-console.xml?dl=0

foreachthing · 2020-04-27T06:08:29Z

No, unfortunately I can't.

If I add this line <Transport>RawInput</Transport> to my xml, it gets immediately overwritten.

foreachthing · 2020-04-27T07:04:50Z

Ok ... So, I tried this:

remove old file
restart PS
open 3Dx and import new settings

Whatever I do, it always removes this Transport section!

What I import:

  <AppInfo>
    <Signature>
      <Name>PrusaSlicer</Name>
      <ExecutableName>prusa-slicer.exe</ExecutableName>
      <Transport>RawInput</Transport>
    </Signature>
    <Options />
  </AppInfo>

What it imports:

  <AppInfo>
    <Signature>
      <Name>PrusaSlicer</Name>
      
      
    <ExecutableName>prusa-slicer.exe</ExecutableName></Signature>
    <Options/>
  </AppInfo>

enricoturri1966 · 2020-04-27T07:12:33Z

Please try this:

close PS and 3Dx
Copy the attached file to replace those automatically generated by 3Dx
start PS and 3Dx

If you try to manually edit the files you need to ensure that:
line 1 -> standalone="no"
line 6 -> Default="true"
line 11 -> RawInput
are all set or 3Dx will override your changes (it is likely doing some validation in background)

foreachthing · 2020-04-27T08:59:54Z

I didn't pay enough attention to details :-
I fixed line 1 and 6 and it got better - not great but better.
Right now I have everything (main speed and all the individual axis) at full speed and it's OK. Could be faster, though! ;-)

foreachthing · 2020-05-26T06:11:31Z

Ok ... I don't know if I should open a new issue for this:
My 3DX-devices work (poorly) in the "3D editor view" but not at all in "Preview"!
Can somebody please confirm (or deny!) this issue?

EDIT: I'm at commit f78f5c8

foreachthing · 2020-06-15T12:37:54Z

This is not fair:
In PS 2.2 (latest release), my 3DConnexion device works perfectly!!
But in the latest commit from today (76d9f0f) it does not work at all. All the axis are reversed, for one. Then bringing up the 3DX-Menu and reversing all the axis - does nothing!
Speed is just ... not what it should be.
I am very sad! :'-(
It worked in PS 2.2 just the way I liked it and now it doesn't....

bubnikv · 2020-10-09T14:23:36Z

@foreachthing
Would you please test with the current master? We are close to the first alpha.
If it is not working for you as expected, would you please give us an exact type of your device? Thank you.

foreachthing · 2020-10-13T09:24:12Z

So - finally was able to rebuild the latest commit (#f0de7f1). But still no banana!
When downloading the prebuild zip, all is just fine. That's with the CTRL+M still available.

Lastest Build: axis are all wrong, speeds are wrong.... can't find anything I'd like - sorry :-(
"Fit" does not zoom to view, nor are any other "view" buttons are working for that matter.

Device: 3DConnexion SpacePilot Pro (FW: 4.11)
3DxWare 10.6.3
3DxWinCore 17.6.3.16588

Hardware Info

Device instance path

HID\VID_046D&PID_C629&MI_01\9&75C0191&0&0000

Hardware IDs:

HID\VID_046D&PID_C629&REV_0411&MI_01
HID\VID_046D&PID_C629&MI_01
HID\VID_046D&UP:0001_U:0008
HID_DEVICE_UP:0001_U:0008
HID_DEVICE

If you need more info, I'd be glad to help!

bubnikv · 2020-10-13T13:10:48Z

Ctrl-M is no more available on Windows with the current master.

We have received a great news from 3DConnexion that they added configuration for prusa-slicer.exe into their 3DConnexion driver package version 10.7.0. This package shall install
C:\Program Files\3Dconnexion\3DxWare\3DxWinCore\Cfg\prusa-slicer.xml

foreachthing · 2020-10-13T14:32:20Z

Unfortunately has the SpacePilot Pro "expired" with this driver version :-(
But, maybe it might still work. I'd be glad to try, though!! 👍

foreachthing · 2020-10-15T07:20:48Z

Ok, I've installed the latest driver from 3DConnexion.
My SpacePilot is now a "discontinued device" :-D

Anyways! It works much better now.

BUT: It works in the Editor View just as expected.
In Preview ... not so much! If I don't touch my mouse (2D mouse!!) while orbiting with my SpacePilot, all movements are junky (< 1 fps). So, now I move my 2D-mouse while orbiting, it's all good! What is going on here?? The faster I move my 2D-mouse, the more responsive my SpacePilot gets.

Need more info? Please let me know.

bubnikv · 2020-10-15T08:46:08Z

The G-code viewer application has to have its own xml file installed
C:\Program Files\3Dconnexion\3DxWare\3DxWinCore\Cfg\prusa-gcodeviewer.xml
just take the prusa-slicer.xml and replace the prusa-slicer.exe with prusa-gcodeviewer.exe

we have fixed some issue yesterday which prevented prusa-gocdeviewer.exe to work with the 3D mouse.

foreachthing · 2020-10-15T09:07:02Z

Ok, to clarify:

Exit PrusaSlicer
Stop 3dx driver
COPY prusa-slicer.xml to prusa-gcodeviewer.xml
Rename string <ExecutableName>prusa-slicer.exe</ExecutableName> to <ExecutableName>prusa-gcodeviewer.exe</ExecutableName>
-- Also tried to add that file in c:\Users\USER\AppData\Roaming\3Dconnexion\3DxWare\Cfg\
Start 3dx driver
start PrusaSlicer

Aaaand that does not work. Or, same behavior as before.
Something else to try?

bubnikv · 2020-10-15T09:11:38Z

recompile from the current master. čt 15. 10. 2020 v 11:07 odesílatel Gilbert <notifications@github.com> napsal:

…

Ok, to clarify: 1. Exit PrusaSlicer 2. Stop 3dx driver 3. COPY prusa-slicer.xml to prusa-gcodeviewer.xml 4. Rename string <ExecutableName>prusa-slicer.exe</ExecutableName> to <ExecutableName>prusa-gcodeviewer.exe</ExecutableName> -- Also tried to add that file in c:\Users\USER\AppData\Roaming\3Dconnexion\3DxWare\Cfg\ 5. Start 3dx driver 6. start PrusaSlicer Aaaand that does not work. Or, same behavior as before. Something else to try? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMPSIZ2JRQYTDV7DBGEG2LSK23UPANCNFSM4MNENSRQ> .

foreachthing · 2020-10-15T09:43:13Z

I'm at commit 3fc12fd but I still need to wiggle my mouse to get it working properly (in preview).
Maybe it's because my device is no longer supported???

BTW: the speed settings are not saved. Who does the saving, 3DConnexion or PS?

bubnikv · 2020-10-15T11:34:25Z

3DConnexion should save the settings. The 3DConnexion shall detect the application, see PrusaSlicer at the top. Sometimes it shows Explorer, which is not correct. [image: image.png] čt 15. 10. 2020 v 11:43 odesílatel Gilbert <notifications@github.com> napsal:

…

I'm at commit 3fc12fd <3fc12fd> but I still need to wiggle my mouse to get it working properly (in preview). Maybe it's because my device is no longer supported??? BTW: the speed settings are not saved. Who does the saving, 3DConnexion or PS? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMPSIY2VZ5N2PP7QLMU2MTSK274JANCNFSM4MNENSRQ> .

foreachthing · 2020-10-15T11:46:50Z

I've been using 3DX-devices since 2004 ;-) I use it every day at work and even got one at home.
So .. here's my screenshot:

I wish that most of those commands would be standard in PrusaSlicer.
I had to create a Macro for each button. Ever for top, left, right and ISO view ... etc.
Every button assignment with (PS) in it, is a custom macro.

bubnikv · 2020-10-15T16:40:30Z

@foreachthing

There are too many of these devices around, we cannot test and configure all of them.
We are in touch with 3DConnexion. You may pass your configuration of PrusaSlicer/3DConnexion here, I may pass it to them, so they will integrate it into their driver installer.

bubnikv · 2020-11-28T13:09:13Z

Could you please retest with the upcoming PrusaSlicer 2.3.0-beta1? Thanks.

foreachthing · 2020-11-28T14:07:39Z

@bubnikv - THANK YOU!!!!! 😍
It works perfectly!!!!

bubnikv · 2020-11-28T14:10:01Z

A closed issue is a good issue.
Thanks @enricoturri1966

foreachthing changed the title ~~3DConnexion Settings CTRL+M not working~~ 3DConnexion settings not working as expected Apr 21, 2020

bubnikv closed this as completed Nov 28, 2020

This was referenced Dec 22, 2021

3Dconnextion does not work, driver issues #7277

Closed

PrusaSlicer and 3D Connexion Wireless Space Mouse #7549

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

3DConnexion settings not working as expected #4104

3DConnexion settings not working as expected #4104

foreachthing commented Apr 21, 2020 •

edited

Loading

bubnikv commented Apr 21, 2020 via email

enricoturri1966 commented Apr 21, 2020

bubnikv commented Apr 21, 2020 via email

foreachthing commented Apr 21, 2020

enricoturri1966 commented Apr 21, 2020

foreachthing commented Apr 21, 2020 •

edited

Loading

enricoturri1966 commented Apr 24, 2020

foreachthing commented Apr 27, 2020 •

edited

Loading

foreachthing commented Apr 27, 2020

enricoturri1966 commented Apr 27, 2020

foreachthing commented Apr 27, 2020

foreachthing commented May 26, 2020 •

edited

Loading

foreachthing commented Jun 15, 2020

bubnikv commented Oct 9, 2020

foreachthing commented Oct 13, 2020 •

edited

Loading

bubnikv commented Oct 13, 2020

foreachthing commented Oct 13, 2020

foreachthing commented Oct 15, 2020 •

edited

Loading

bubnikv commented Oct 15, 2020

foreachthing commented Oct 15, 2020

bubnikv commented Oct 15, 2020 via email

foreachthing commented Oct 15, 2020

bubnikv commented Oct 15, 2020 via email

foreachthing commented Oct 15, 2020

bubnikv commented Oct 15, 2020

bubnikv commented Nov 28, 2020

foreachthing commented Nov 28, 2020

bubnikv commented Nov 28, 2020

3DConnexion settings not working as expected #4104

3DConnexion settings not working as expected #4104

Comments

foreachthing commented Apr 21, 2020 • edited Loading

Version

Operating system type + version

Behavior

Expected

bubnikv commented Apr 21, 2020 via email

enricoturri1966 commented Apr 21, 2020

bubnikv commented Apr 21, 2020 via email

foreachthing commented Apr 21, 2020

enricoturri1966 commented Apr 21, 2020

foreachthing commented Apr 21, 2020 • edited Loading

enricoturri1966 commented Apr 24, 2020

foreachthing commented Apr 27, 2020 • edited Loading

foreachthing commented Apr 27, 2020

enricoturri1966 commented Apr 27, 2020

foreachthing commented Apr 27, 2020

foreachthing commented May 26, 2020 • edited Loading

foreachthing commented Jun 15, 2020

bubnikv commented Oct 9, 2020

foreachthing commented Oct 13, 2020 • edited Loading

bubnikv commented Oct 13, 2020

foreachthing commented Oct 13, 2020

foreachthing commented Oct 15, 2020 • edited Loading

bubnikv commented Oct 15, 2020

foreachthing commented Oct 15, 2020

bubnikv commented Oct 15, 2020 via email

foreachthing commented Oct 15, 2020

bubnikv commented Oct 15, 2020 via email

foreachthing commented Oct 15, 2020

bubnikv commented Oct 15, 2020

bubnikv commented Nov 28, 2020

foreachthing commented Nov 28, 2020

bubnikv commented Nov 28, 2020

foreachthing commented Apr 21, 2020 •

edited

Loading

foreachthing commented Apr 21, 2020 •

edited

Loading

foreachthing commented Apr 27, 2020 •

edited

Loading

foreachthing commented May 26, 2020 •

edited

Loading

foreachthing commented Oct 13, 2020 •

edited

Loading

foreachthing commented Oct 15, 2020 •

edited

Loading