Posts by Willsud

    For anyone else like me, who can't see the obvious...:rolleyes: :)

    If your Spacemouse in Enscape - or Revit - even after the latest driver updates, makes movement very 'twitchy' and is over-sensitive, just pull back the 'Speed' slider on the first page of the 3D Connexions settings menu.

    It seems to me that movement in some axes is more sensitive than others :/

    Thanks RandalRDesign,


    3DConnexions' Windows 10 driver- 64 bit version 10.8.7.3448 and Enscape version 3.3.1 + 75071 (the latest release versions as far as I know) do now seem to work OK with Revit 2023 hotfix 1.

    With Enscape linked to Revit 2023 the trick does seem to be to enable 'Lock Horizon' in the 3DConnexions' Enscape menu. My preference is to also reverse the direction of all the joystick directions in the same menu.

    If your Revit model appears in Enscape not horizontal I find tapping the 'F' key or other hotkey on the Spacemouse will place it level.

    Walk Mode in Enscape still does not work - it can be enabled in the menu bar but it immediately flips back to Fly Mode.

    FWIW in Revit 2023 the Spacemouse is too sensitive by default but this can be cured by selecting an object to pivot round in Revit first and then the Spacemouse uses the same pivot. There are no pivot point choices in the Revit menu for the Spacemouse (it recognises the current application).

    A big relief to have the Spacemouse usable again. I do wish software developers would stop using customers as beta-testers though :/ :)

    I agree Tim that it's likely mostly a 3D Connexions developer change which has impacted on Enscape. Developers can be and are, everywhere in the World so hard to know how 3D Connexions work.


    You do get the impression that someone - or some people - at 3D Connexions are trying to recreate something that worked in the old setup but doesn't work as well now.


    I always wondered why Lumion wouldn't have anything to do with 3D Connexions devices.

    I use Revit - version 2022 mostly but I also have 2023. The Spacemouse goes crazy in Revit 2023 at present but OK in 2022 as long as Enscape is not running.


    With the latest Enscape and latest 3D connexion drivers, in Revit 2022, using the Spacemouse kind of works if you use a shortcut key on the spacemouse - 'F' for example - which aligns the model to the horizontal. Then turn off the left/right roll key option. Moving around the model it starts to drift off horizontal and whichever camera mode is in use, movement is 'jittery'.


    That it is better than a few months ago suggests this is a work in progress. Hopefully 3D Connexions and Enscape are still working on it but it's probably affecting a relatively small number of users.


    Being an eternal optimist I will have another try at using the Spacemouse with the latest versions over the weekend :)

    Nice to see the 3.3 release which works with Revit 2023 - and 3.3.1 already :)


    3D Connexions driver version 10.8.7 and the Spacemouse shows 'Enscape 3D', so far so good.


    There is no real improvement in use. The Spacemouse is 'nervous' and jittery. It used to be a very smooth, enjoyable experience travelling around the Enscape model with the joystick but it is unusable in a professional context.


    FWIW I notice that the Spacemouse goes really wild and uncontrollable in Revit 2023.


    The Spacemouse stays in the bin for now I think which is a shame as it was the main reason I used Enscape for client presentations. I'll stick with Lumion if I'm going to have to use keyboard keys and a mouse to move around the model in presentations.

    I've spent a while playing about with the Menu options in the latest 3d Connexions driver and Enscape 3.3


    The best workaround I have come up with - for me - so far is:


    Navigation Mode = Target Camera mode


    Speed (I have all these Reversed) = disable Left/Right Roll


    Unfortunately, disabling the Left/Right Roll for the joystick is no guarantee that the horizon will stay level ('Lock horizon' in the menu options doesn't seem to work?)

    When it starts to drift away from vertical I use the 'F' or 'R' button on the Spacemouse to get the building back level again - it forces a Front or Right View.


    All this is OK for outside but inside a building the camera is very jittery. I've tried the other Navigation Modes but one doesn't seem better than another.


    At least this has forced me to learn what the buttons on the Spacemouse can do.


    It's still rubbish compared to how it used to be so the best solution might be what I've just done - throw the Spacemouse in the bin ! :)

    So here we are 6th April 2022. I've installed Enscape 3.3 and the latest 3D Connexion drivers 10.8.6.


    There is no mention in the release notes about fixing the problems detailed above but I thought I would give it a try.


    In short, it isn't as bad. It works, a little jittery and unfortunately there is no way I could see of keeping the view level - other than making sure your view is level and then disabling that rotation feature from the 3dConnexions Menu.


    It's rare for products to become worse with newer versions but I'm going back to 3.1 as this combination is still too unstable to use for client presentations.

    Ah, you are in Sketchup, my issue is in Revit 2022.


    I tried Enscape in the latest version of Sketchup and it seemed to have the same problems as Revit which I guess is not unexpected given that it seems to be something to do with the 3DConnexions developer toolkit?


    I'm resigned to waiting with 3.1 - fortunately I use Lumion for rendering - and that doesn't even support a Spacemouse LOL

    Another client presentation this morning so I uninstalled Enscape 3.2 and reinstalled 3.1 but the 3dConnexions spacemouse driver seems to have been corrupted by using it with 3.2 as it would not work properly with 3.1 until I uninstalled the driver and reinstalled it.


    Thankfully, got it working just in time for the presentation.


    It isn't clear whether it's the Spacemouse driver or Enscape 3.2 that is the problem but something between them doesn't seem to be working quite right.