My machine is really sluggish after quitting KeyShot 2.2.45 (Dell Precision M4400 quad core; Nvidia M1700: Win7 Professional 64bit). The cores are all running erratically around 30% when normally they barely crack 5% when idle. This can go on for more than half an hour. I can't see anything in the running processes that take up this bandwidth, and again, it's only after quitting Keyshot. It seems to not be letting go of something.
I have not heard of this issue before. KeyShot does not leave any processes behind after quitting. It could be that your operating system is performing a cleanup after running KeyShot. Dince KeyShot uses the cpu cores fully the OS may postpone various tasks until KeyShot is done.
-- Henrik
Well, I'm in no way a tech expert, but if windows was postponing doing something, wouldn't that use less CPU time rather than more?
Not if it starts doing it after you quit KeyShot.
I'm seeing the same thing on Dell Precision m6500 - tend to have a restart after a heavy Keyshot session
Any comments regarding this guys? When I first mentioned this via support I was told this hasn't been reported by anyone else. This seems to be something going on since version 2.2. I also find that I can't really do anything else on the machine while a render is running, while in the past I was able to carry on with pretty much anything in the background.
After you quit KeyShot, are there still KeyShot processes running? How is RAM usage?
Hi Thomas,
No there don't seem to be any processes left running after quitting keyshot.
I'm getting used to having to restart after running Keyshot.
Really strange. We will keep out eyes open. Sorry if I already asked question, but what OS are you running?
Win7 pro x64
For whatever it's worth, I'm also running Win7x64, with 16 gigs, and have not experienced this problem. After a long KS session, I usually jump right to Photoshop CS5 or SolidWorks, and all seems well.
Just curious- does KS store temps that don't clean out after closing a session?
Bill G
No it doesn't - everything is held in RAM.
Win 7 64 bit is what we are running here - never seen it.
I run the same exact OS and haven't seen an issue either. If it were me, I would keep an eye on the task manager, before and after closing KeyShot. I would think something would show in the "Processes" tab if the CPU usage is at 30% (be sure to sort by CPU usage).
Dell Precision M series seems to be the common denominator in this case....
I'm blaming NVIDIA. I updated the drivers and so far so good as far as this issue is concerned; though I have not been using Keyshot that heavily the past couple of days.
Cool - could you tell me which driver you've had the most success with? There's a fair few drivers available as you know!
I'm using 6.14.12.6658
Cheers - I seem to be behind on a couple of the components - will give it a bash!
Nope - not helped for me. I am having to queue all my renders to go overnight now so that I can do other work. To be honest I'm really annoyed with keyshot at the moment and all its little "Quirks": hidden/deleted parts suddenly reappearing in final renders, settings and scene tree randomly changing when a file is reopened - its a shame Bunkspeed Shot is so clunky otherwise i'd have that as an alternative.
Have you upgraded to the latest version? All of these issues should be resolved in 2.2.65.