Rhino using 100% CPU on single core constantly

Uh oh. Rhino just sits there bouncing at 8.2-8.4% or (77-100% of the core). For a while before it got really bad, Rhino wanted to make bounding boxes out of not too complex geometry. I am also using a 3dconnexxion spacemouse, current drivers, etc. But Rhino is doing this even after a reinstall of both 3dconnexxion drivers and Rhino as well as just not loading the plugin.

Also, Rhino5 seems to be just fine.

If you unplug the space mouse completely, is it any different? Making bounding boxes seems like a view adjustment thing, potentially.

-Pascal

Whoa. OK. Unplugging the receiver seemed to do the trick. Different problem, but not so much yours as mine! Do you have any suggestions? I’ve grown to rely on the ol’ Spacemouse through the years… Many thanks, B

I’d contact 3dConnexion and try to work with them - they’ll shout for help if it’s Rhino’s fault. I’ll ask @Markus as well.

-Pascal

If you plug the receiver in again does the problem come back, or are you still good?

And for context, did you recently get the Windows 10 1903 update?

I don’t know if you have it installed but I had several problems with the Gforce Experience app. once unistalled, everything goes normal.

2 Likes

@DiegoKrause

This is a long shot, but I had the same issue a while ago with my SpacePilot and its an easy fix.

My sluggishness was due to my SpacePilot being slightly out of alignment. So, Rhino thought I was always moving when I was actually still. It drove me crazy!

The fix was a simple ‘calibrate’ function, so that the space pilot was reset / re-centered.

2 Likes

Thanks a ton! I’ll reach out.

J

Hi Jeremy, plugging it in brought it back, sadly. I am on the 1803 update from April. Thanks.

Hello all, Just wanted to follow up on this as I found a not great, but serviceable solution!

I uninstalled the 3dconnexion program entirely and the unit works as it did before when it is plugged in, albeit without the fine controls offered by the Spacemouse program in the tray. It even works wirelessly though it is choppy; it is not dragging down the whole Rhino program when wireless as well.

If anyone knows a way to increase the rate at which the mouse reports to the receiver wirelessly, that would be great, otherwise, I’ll just keep rockin’ the extra cable on my desk.

Again, big thanks to everyone who contributed to this thread. -Ben

This is why I don’t use a wireless mouse, keyboard or spacepilot. (1) There is always the chance of interference and (2) the batteries can die and leave you stuck. Plus, with a mouse, the extra weight of a battery can cause hand and wrist problems after a long day of use.

Did you try the calibration suggestion?

I had a problem where my SpaceMouse suddenly refused to connect with the receiver any more. I had to remove the reference to the SpaceMouse from the system and go through the discovery process again, after which it worked fine. Different problem but might be worth trying.

OK. Here is what I hope to be the last installment of this thread!

I mentioned earlier that uninstalling SpacemouseExplorer and just using the existing plugin in Rhino worked; I was wrong. I encountered the same problem an hour after I wrote that. What has happened today, after reinstalling Windows and all of my programs etc., was that the problem disappeared when I removed the BoxEdit tab from the side menu. This seems completely random and absurd, but could be recreated with a click. I now have current Rhino6 and Current SMExplorer running and everything works as long as I do not use BoxEdit.

Thanks again for the helpful comments and such. -B

@schultzeworks the calibration suggestion didn’t work, but good to know where it is. Thanks
@jeremy5 I have had this problem in the past as well. It stinks and their support was never able to get me past it, except using the start3dconnexion and stop 3dconnexion commands at the start menu.

Hi Benjamin - the 6.18 build that has some significant fixes to BoxEdit - see if installing that makes the problem go away. To get 6.18, open Options > Updates and statistics and set Update Frequency to ‘Release Candidate’ and then Check Now.

Any luck?

-Pascal

Yes, please do contact 3Dconnexion if you are having issues with the receivers/wireless.

I will assume, for now, that 3Dconnexion device is out of the equation.

Hi @pascal and @Markus, It looks like the 6.18 build sorted out the conflict between BoxEdit and the SpaceMouse. Thanks again! -B

Hi Markus - yes, thanks - it was Rhino’s fault.

-Pascal

1 Like

A post was split to a new topic: High single core CPU usage