Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Comments
HWM-Water Ltd
Maybe now's the time to make the switch!
HWM-Water Ltd
I've been able to 'wake' my devices with closing browser (not just onshape tab) and kill all 3dconnexion processes and start again. Takes about 45sec but is super annoying. I tend to blame myself for leaving everything on and just put computer sleep while I sleep, I think it would be better if shut down browser (and computer).
For this reason I use Chrome just for Onshape and sheets, Firefox for browsing, to be able to restart browser without closing other important sites (like Onshape forums etc..).
About drivers (in general) I would say if they work for you, don't push your luck with updating 'em.
3dxConnexion not working with Onshape is caused by 3dxService.exe in Windows Startup not loading 3dxNIServer during Windows boot on faster machines. Works fine on slower machines like my Lenovo Ideapad.
This is what I have to do each day, when I boot my Dell Precision M4800 laptop:
1. Disable 3dxService.exe in Windows Start (found in Task Manager, you only have to do this once).
2. Boot Windows and let everything settle.
3. Click on the Windows icon in the bottom LH corner of the screen, Type "Start Driver" and hit enter. This executes 3dxService.exe, ensuring it runs after everything else in the Windows Start Routine.
Once I perform the daily ritual Steps 2 and 3 described above, 3dConnexion Mouse works everytime with Onshape, regardless of driver version.
There appears to be a sequence timing error on fast machines which prevents 3dxNIServer from being loaded during Windows boot.
3dConnexion in Germany are aware of this issue, because I have been working with them for a permanent fix. To date and, even with driver (10.5.8) issued Jul18 , the problem still persists. I notice this morning there is yest another driver released (10.5.10) but I haven't had time to test it.
The obvious solution to fix this problem is to change the Windows Boot sequence with a batch file, to load 3dxService.exe after everything else, but I am not smart enough to be able do this. Perhaps more savvy persons
I am very curious about a permanent solution.
I just added the 3DxNLServer to allowed programs for the firewall. It immediately started working after that. We'll see if it's a permanent solution.
If it needs any holes to firewall, they should be added on installation (by software).
The issue discussed in this thread needs to be resolved by 3DConnexion.
The latest driver issued in December 2018 still does not fix this issue being experienced by many of 3DConnexions's customers. It has been going on for years. In my case, it is NOT a firewall related problem.
Carefully read through Post Number 167. My post clearly describes the problem, the conditions under which it occurs,and the totally reliable workaround.
Windows arranges programs in the startup routine in alphabetical order, so the driver 3dxService.exe appears at the top of the list, before other programs Unfortunately, Windows startup routine sequence cannot be rearranged to have 3dxService.exe start last, which may solve the issue, if it could be done.
Thank You.
The bug reveals itself when "fast switching" between users (sign in as one user, then switch to another). In this scenario, 3DxNLServer.exe will crash. This leaves Onshape unable to connect to the driver which, in turn, will identify a running instance of Onshape as just another web page in Chrome and other browsers.
We are sorry for the inconvenience the bug is causing to our costumers, users of Onshape and 3D mice. If the fix for WIN-255 does not address the problem reported here, we will continue to look for a solution.
As mentioned in my post above, this release includes a fix for issue WIN-255 which is believed to have had a impact on the driver stability (3DxNLServer.exe crashes).
We recommend our costumers to upgrade the just-released version. The software is vailable from 3Dconnexion's web site here.
When will this be pushed for macOS? I am also having 3DxNLServer crashes on my Macbook with 10.6.1.
Onshape, Inc.
We're aiming for a macOS update (v. 10.6.2) before month's end but the fix to 3DxNLServer (WIN-255) does not apply on Apple's platform. The only 3DxNLServer crash on macOS that we're aware is MAC-96. This bug is triggered by running the "QuickZoom" commands ("In" or "Out") in sequence. A fix will ship in v. 10.6.2.
Ahh okay. I have a ticket open currently on a crash triggered by some other unknown source.
Onshape, Inc.
We understand from @TimRice there's a stability issue with 3Dconnexion's proxy server on the Mac. The issue is 3DxNLServer.app crashing. We're trying to chase this down.
Without a running instance of 3DxNLServer.app, there's no way for Onshape to communication with the 3Dconnexion device driver.
We're looking into this. What's impeding progress is the lack of a reproducible scenario. The crashes appear to be random.
yesterday, and it's been flawless ever since. It's been ok on my macbook pro, but the mid 2010 iMac didn't like the modern driver.
HWM-Water Ltd
(I bought but never used after day 1 the wireless radio versions of any of these 3D mice, that's just a whole other pain in the bum that is simply not worth it. Blame will always be put on 'other devices interfering' rather than 'our mouse radios are crap' so it's an added layer of crap you don't want to add to the already impressively high crap sandwich that is modern technology).
Looking (on Mac) in Activity Monitor, I see 3DxNLServer not present. Going to Finder, then Applications, under 3Dconnexion, and starting that 3DxNLServer.app, then simply refreshing the browser under Chrome or Safari, fixes the problem. Over the last few days it seems to stop working several times a day which is rather frustrating. I can't figure out the event that causes it to crap itself, but at least the above method avoids having to restart the computer, which is what I've been doing for the past couple of years.
If that sounds like too many uses of the word 'crap', then please appreciate these mice are from $300 to $600, not cheap, and I charge by the hour for my CAD work, so while I'm farting around trying to solve problems that simply should not be present on expensive and state of the art hardware and software, I'm earning zip. That's frustrating. Crap.
Onshape, Inc.