Closed dahuafschmied closed 4 years ago
This piece has been reworked in PrusaSlicer 2.2.0-rc2 to be released today, it should work. Please retest and close this issue if it is fixed in PrusaSlicer 2.2.0-rc2. Thank you.
so 7. 3. 2020 v 8:33 odesílatel dahuafschmied notifications@github.com napsal:
Version
2.2.0 RC Operating system type + version
MacOS 10.13.6 Behavior
Since the RC the 3Dconnexion settings (cmd+m) are not stored anymore. Close and Reopen the Prusaslicer resets them to default values. (by the way: the default values are way off as i am used to in "normal" CAD programs and the zoom is binary not analog)
[image: 3dcon] https://user-images.githubusercontent.com/3955019/76139159-15f03200-604e-11ea-96a7-c6a7eb32565b.png
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/prusa3d/PrusaSlicer/issues/3791?email_source=notifications&email_token=ABMPSI7I7Z2V7ERIGPFA3DDRGH2F7A5CNFSM4LDNJCK2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ITI2EFA, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMPSI5OUKV76Q6DCCU4XLLRGH2F7ANCNFSM4LDNJCKQ .
Sorry not fixed. Values are still not stored and zoom is still digial
by the way: the default values are way off as i am used to in "normal" CAD programs and the zoom is binary not analog
Could you provide a screenshot with the sensitivities that you are used to? Maybe you want to set the deadzone to zero?
the zoom is binary not analog
What do you mean that? You mean zooming with pulling the knob towards you and away from you?
OK. I try to explain the zoom: if i push the mouse light the movement is slow. if i push the mouse hard the movement is fast. this is analog. more force -> more speed. in prusaslicer this works for rotation and movement. but at zoom (bring the object closer or further away) the speed is fix and always the same no matter if i push (or pull) harder or softer. this needs to be fixed. or you have a very bad feeling at moving objects around.
now the speed settings: usually i setup speed und threshold and everything else at the 3Dconnexion Settings Tool. No need to setup anything at the CAD application.
to have a natural feeling at prusaslicer i have to set the speeds to about 6 and the threshold to 0. but then the zoom (as it is just on or off) way too fast.
If you have everything correct you do not need the crtl+m menu anymore. everything is controlled by the 3Dconnexion Settings Tool.
i do hope this helps.
update: set the speeds to 10 is perfect. and deadzone to 0. (zoom should be at 10 to. but you have to fix the on/off bug first)
I can confirm that the settings is not saved, but I cannot reproduce the binary zoom. Do you still have it? Maybe your settings in the system driver is set to extremes? What happens if you set the resolution in 3Dconnexion driver to default and then set the sensitivity in slicer?
ne 8. 3. 2020 v 10:59 odesílatel dahuafschmied notifications@github.com napsal:
update: set the speeds to 10 is perfect. and deadzone to 0. (zoom should be at 10 to. but you have to fix the on/off bug first) [image: Bildschirmfoto 2020-03-08 um 10 58 20] https://user-images.githubusercontent.com/3955019/76160593-c3854300-612b-11ea-82d6-415b5a0036f1.png
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/prusa3d/PrusaSlicer/issues/3791?email_source=notifications&email_token=ABMPSIYRLRU6N27SJ5EU7J3RGNUALA5CNFSM4LDNJCK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOERQQA#issuecomment-596187200, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMPSI2EZT7QA6PQYAT73OTRGNUALANCNFSM4LDNJCKQ .
i already reseted the mouse settings to default values.
zoom is still binary.
i changed the values for testing but it stays binary...
in Fusion360 the zoom works as it should
Would you make a movie of the binary zoom please? We are not able to reproduce it in any way.
po 9. 3. 2020 v 15:09 odesílatel dahuafschmied notifications@github.com napsal:
in Fusion360 the zoom works as it should
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/prusa3d/PrusaSlicer/issues/3791?email_source=notifications&email_token=ABMPSI3W6NX6JZ23LE7THKTRGT2AZA5CNFSM4LDNJCK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOHJBYY#issuecomment-596545763, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMPSI2KNRCSKS75BNHC7ATRGT2AZANCNFSM4LDNJCKQ .
this last commit seems logical to me. is it possible to get a test version? or do i have to compile it by myself?
@dahuafschmied The fix will be part of next release candidate, which should be published later today.
After trying 2.2.0 out last night, i immediatly noticed the zoom issue you described.. Where as all of the other axis are 'analogue' (i.e the amount you move the puck dictates the speed of travel), the zoom is either on or off.. So you have no 'analogue' control over it.
Are we saying that the fix thats been suggested/implimented is going to address this?
3D Mouse is perfect now! thank you for the fast and helpful support!
Great. Thanks for letting us know. You would not believe how time consuming thus expensive the whole 3DConnexion integration was.
st 11. 3. 2020 v 22:08 odesílatel dahuafschmied notifications@github.com napsal:
3D Mouse is perfect now! thank you for the fast and helpful support!
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/prusa3d/PrusaSlicer/issues/3791#issuecomment-597879378, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMPSI2GV2QJKRQ2GAAIKPTRG74U7ANCNFSM4LDNJCKQ .
You would not believe how time consuming thus expensive the whole 3DConnexion integration was.
I appreciate every second you invested in this feature!!! :-D
Now ... let's talk about function keys ... duckandrun
Now ... let's talk about function keys ... duckandrun
Buttons on 3DMouse with PrusaSlicer:
Works Perfect
OFF TOPIC! Yes, I started using Macros, too. But if PS could use the default keys ... that'd be something!!! :-) Now, you have to program all the functions (macros) manually - basically make a macro for each PS-function you want to map. Not impossible, just tedious.
I am not sure I understand what the issue is with buttons.. I have an unsupported SpacePilot which works well.. And whilst the speed/sensitives don't work in the 3DConnexion setup tool (but CTL+M works in Slic3r), the button seem fine.
So I have been able to add all the features I want assuming that Prusa already has hotkeys for the function.
For me, 3D mouse support is working very well... Its just a shame that having one connected affects the way that a "normal" mouse works.
I am not sure I understand what the issue is with buttons..
When I click the TOP (-view)-Button (SpacePilot Pro), it does nothing. I have to assign an custom macro (where I have to map the [1]-key to) to this button. Short: create a macro where I map [1] to. Assign this macro to the TOP-button.... whereas SolidWorks just takes the TOP-button command and shows the top view. Same for front, back, etc. This is, however, a topic for a new issue.
It would be great if you guys could export your 3DConnexion button assignments from your 3DConnexion settings dialog and share it somewhere for the others. One will not fit all as there are so many different 3DConnexion models with different number of buttons. I believe this is a better way than trying to integrate it into our application.
čt 12. 3. 2020 v 16:28 odesílatel Gilbert notifications@github.com napsal:
I am not sure I understand what the issue is with buttons..
When I click the TOP (-view)-Button (SpacePilot Pro), it does nothing. I have to assign an custom macro (where I have to map the [1]-key to) to this button. Short: create a macro where I map [1] to. Assign this macro to the TOP-button.... whereas SolidWorks just takes the TOP-botton command and shows the top view. Same for front, back, etc. This is, however, a topic for a new issue.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/prusa3d/PrusaSlicer/issues/3791#issuecomment-598251654, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMPSI2XUO6PXT3F773AE2DRHD5TLANCNFSM4LDNJCKQ .
Here are my settings for my SpacePilot: https://github.com/foreachthing/PrusaSlicer-3DConnexionSettings
thanks, I have passed it to our content guys for the manual.
po 16. 3. 2020 v 10:00 odesílatel Gilbert notifications@github.com napsal:
Here are my settings for my SpacePilot: https://github.com/foreachthing/PrusaSlicer-3DConnexionSettings
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/prusa3d/PrusaSlicer/issues/3791#issuecomment-599419693, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMPSIY2QJH6TGS56ZAXWHDRHXTB5ANCNFSM4LDNJCKQ .
Version
2.2.0 RC
Operating system type + version
MacOS 10.13.6
Behavior
Since the RC the 3Dconnexion settings (cmd+m) are not stored anymore. Close and Reopen the Prusaslicer resets them to default values. (by the way: the default values are way off as i am used to in "normal" CAD programs and the zoom is binary not analog)