3Dconnexion settings (command + m) are missing #4892
Comments
|
same in new g-code viewer |
|
We dropped the built in configuration dialog as you should be able to do the same configuration and more in the 3DConnexion driver. |
|
ok. sounds logic. |
|
Same here! |
|
For me, the 3DxWare config is not even working.. It has no effect, so the speed of my movement is too slow to use.. I want the old functionality back as it was PERFECT for me.. SInce this is thing I only need to setup once, is there a way to force my 3DMouse speeds to be faster? |
|
My suggestion would be to set the default values to 10 and leave the configuration dialog disabled. |
|
Agreed.. Happy to manually set this up and leave it.. But how?? I can'ty find any way to change the speed... Is there a file I can edit? Wait.. Just saw the update in the original post.. "prusaslicer.ini".. Great.. I have that.. But what params to you edit? Edit: Just seen your post on the Prusa forum.. Will try the changes you suggeted. Edit2: didnt work for me... |
|
My "Space Mouse compact" works flawlessly on the object platter, but does NOT work on the preview platter... |
Move the normal mouse at the same time and it should work in the preview mode.. fix is inbound apparantly. |
This commit 5d3d9d9 fixed it for me ✌️ |
But does NOT fix this hijacked Ticket! |
|
I'm having the same issue, even after editing the prusaslicer.ini file. The 3Dconnextion 3DXware does not affect the speed in any way, nor does editing the values in the prusaslicer.ini file. |
You're absolutely right!!! |
|
still not fixed in alpha 2! |
|
I, too, wish they would revert to the perfectly working "CTRL+M" version. |
|
Going back to old configurator gets my vote too... i had zero issue with the old implimentation. Perhaps it could be a configurable option to have the new or old method? |
|
I see the discussion is getting hot and the pitchforks are getting raised. We are trying hard to do the right thing to integrate 3DConnexion into PrusaSlicer according to 3DConnexion recommendations. We are getting some support from 3DConnexion including their people testing PrusaSlicer for the right default values for the speeds. 3DConnexion normally provides libraries for integration into closed source projects, however as PrusaSlicer is open source, we had to find a way to integrate without the 3DConnexion libraries. We are trying our best, but we are not quite sure whether the issue is on our side or on the side of 3DConnexion. On Windows we seem to be doing good. On OSX the 3DConnexion messages are supposed to be routed through the 3DConnexion driver, thus the 3DConnexion driver should be able to adjust the speeds. If that does not work as expected, we cannot know whether the issue is on our side, whether the 3DConnexion driver is buggy or whether the devices that you guys report are now too slow in PrusaSlicer are simply not supported by the 3DConnexion driver. Frankly I am getting hard time to orient myself in the issues reported. I suppose the best we can do is to adjust the default speeds for the devices we have access to and re-enable the Ctrl-M dialog for those devices that are getting incorrectly scaled values and hope for the best. We will most likely do that for the next alpha. We will also consult with 3DConnexion, however they are not exactly quick to communicate. Knowing up front how much development time the 3DConnexion integration would take, as a project manager I would most likely refuse to implement this feature. |
|
@bubnikv From my point of view there is no need to justify your actions.. I know you are trying to do the best thing, and its not difficult to see how difficult it is to work with 3DConnexion.. The way they "obsolute" there products is nothing short of criminal.. So trying to build support for some of their products is likely to be impossible. All i am saying (And I believe others too) are that for people who liked the old implimentation of the 3DMouse, bring it back.. You spent so much time developing it, it seems a shame not to use it when it worked for many people. The fact that you are doing this in a future realise is fine by me and I couldn't be happier. Just keep doing what you are doing.. Cheers Jon |
|
@bubnikv
The Problem i see is that a lot of people using the unsupported devices because of there low price. If you reenable the cmd+m Settings the complains will disappear and you have time to find the speed problem (for a final solution i see this necessary). |
|
What exactly are the non-supported devices? Are they 3DConnexion products
that 3DConnexion obsoleted? Or are they clones of 3DConnexion devices?
What surprises me is that these "non-supported" devices still seem to
register at the 3DConnexion driver and the 3DConnexion driver produces
movement messages for them. At least this is my understanding of it.
po 26. 10. 2020 v 14:50 odesílatel dahuafschmied <notifications@github.com>
napsal:
… @bubnikv <https://github.com/bubnikv>
Thank you so much for implementing these devices. I appreciate it a lot!
I see here two different things accumulated in this ticket.
1.
Mouse is to slow (MacOS) with supported devices (SpaceNavigator,
SpaceMouse, ...).
Settings can be changed in 3DxWare. But are still too slow.
(that is my case and the original intend of this ticket)
2.
Mouse is to slow with NOT supported devices (SpacePilot,...).
Settings can NOT be changed in 3DxWare and/or INI file.
The Problem i see is that a lot of people using the unsupported devices
because of there low price. If you reenable the cmd+m Settings the
complains will disappear and you have time to find the speed problem (for a
final solution i see this necessary).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4892 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMPSI3K7V6SV5OU7K5KW23SMV5DNANCNFSM4SUQ4HWA>
.
|
|
Here you can find the list of supported devices: and a list of discontinued devices As i see the people with unsupported devices just install old drivers (and have compatibility problems now) |
|
@bubnikv In my case its a "SpacePilot".. A perfectly useable product and an official 3DConnexion device.. But they remove support for their products after a few years. so mine still works, but only using old drivers and this means that a lot of new apps (ie Sketchup) doesn't support it. Its 3DConnexions business model to keep dicontinuing their devices.. I guess if you were a "pro" user, you wouldn't mind upgrading every few years.. But for people like me, I have an old 3DMouse and am happy to use old but unsupported drivers. |
|
@bubnikv I just noticed there is a commit to bring back the old CTL+M functionality, but I noticed its for MAC. When came back to look at this thread I realised it was raised against MACOS, where as my issue is in Windows.. Is it also possible to bring back the old functionality to Windows too? |
|
Hey guys
Summary: Recommendation: |
|
@dahuafschmied, @foreachthing |
|
@enricoturri1966 I have tested and the CTL+M configurator is back.. And the values were set to 1.0 which I would expected because the sensitivity is so low. So it all looked good, but I changed the values (right up to 10.0) and it has no effect on the speed of rotation.... So we are making good progress, but its not working yet. For the record, I am one of the people who had ZERO issues with SpaceMouse support in 2.2.0 so am happy to help test this. Edit: Another weird observation... I relaunched Slicer and did CTL+M and the values were at 1.0 again, so the config isn't even 'saving'. I then wondered if my earlier attempts to use the official 3DConnexion drivers to get it working had any effect.. So I went into 3DxWare and 'reset' the settings for Slicer... But now I have lost the CTL+M config in Slicer again.. CTL+M does nothing, just like it does in other 2.3.0 versions.. The GUI came up several times before.. But now its stopped working.. Edit2: I got the CTL+M dialogue back... It didn't work in the GCode viewer either, so I messed about a bit and found that I had to presss CTL+M whilst moving the 3D mouse.. Then I went back into Slicer and CTL+M was still not working.. But a little nudge of the mouse and CTL+M and it appeared. Now that its back, CTL+M is working normally again (i.e you can bring it up without moving the 3DMouse).. But the values have no effect.. And its confirmed that it does not save.. So if I move everything to 10.0 and then quit Slicer.. When I come back and do CTL+M the values are back to 1.0 again. I have also noted that nothing gets writen in the "prusaslicer.ini" file, which I believe happened in 2.2.0.. Edit3.. CTL+M stopped working again.. But a nudge of the mouse whist doing CTL+M brings it back... So this is a genuine problem and not a one off. |
|
Yeah, I'm with @jweaver100.
Happy to do some more testing! |
|
Same for me as @foreachthing. I'm also happy to test. Using SpaceMouse Pro (wired) with Win10 x64. |
|
in alpha3 command+m sill not working on mac os |
…ttings of 3DConnexion devices (CTRL+M) on Windows
|
@dahuafschmied, @foreachthing, @jweaver100 |
|
@enricoturri1966 IT WORKS!! Just like it used too in 2.2.0 I will do more playing, but my basic tests worked:
So from what I can see, its all working normally again.. Good work.. Edit: Confirmd working in the GCode viewer too... |
|
@enricoturri1966 |
|
Not that you asked me, but that works for me as well and as jweaver100 describes. Windows 10 and Spacemouse wireless. |
|
Sweet!!!!! 😍 |
|
@enricoturri1966 As per @jweaver100 , your latest test build works well for me Win 10 x64, SpaceMouse Pro (wired), a value of 7.5 feels good to me. |
|
@enricoturri1966 |
|
@enricoturri1966 still no command + m on macos with alpha4 |
Nor Windows.. Which was quite a surprise after the successful "test" version based on Alpha3. |
|
We have brought the Ctrl-M dialog back in PrusaSlicer 2.3.0-beta1. You have to enable "Legacy 3DConnexion" in the preferences dialog first. |
Version
2.3.0 Alpha1
Operating system type + version
MacOS 10.13.6
3D printer brand / version + firmware version (if known)
Mini 4.2.1
Behavior
3dconnexion settings menu (command + m) is missing,
In Version 2.2.0 with Command + m the menu is displayed
in adition the speed default values are way to low. i have to set all 3 of them to 10 to get the same speed as in other software.
Workaround:
edit the PrusaSlicer.ini file
The text was updated successfully, but these errors were encountered: