KS4 keeps crashing

[number12]

Hi Guys, we've been having some serious problems with Keyshot at the moment. All of a sudden we seem to be having problems with Keyshot failing to respond. It always happens after we've set up a custom HDR lighting file and the error message we get is along the lines of: "startup disk full etc etc" however we know this isn't the case as the commuter we've been rendering on has over 160 Gb of space left on it and the scene isn't very big. Every time the only option we are left with is to force quit it. We're running KS on a Mac with plenty of ram etc.
the really odd thing is everything was working fine until the other day. We have been using KS for around 18 months then all of a sudden this!

Can someone help please as it's causing us some big problems right now.

[Rex]

Have you tried uninstalling and reinstalling?

[Katie.smith7236]

We have been having the same issues as well!

We have done as instructed and installed Key Shot 5 and the problems seem to be the same, with the addition of the below issues.
We have had the software professionally uninstalled and reinstalled.

-Every time we open a file in keyshot it will come up with a message saying not responding and then crash. This can happen up to 12 times a day, making the completion of simple tasks extremely difficult and frustrating.

- The materials we had in Keyshot 4 are incompatible with Keyshot 5 resulting in a lot of work to have to be re-rendered and materials recreated to match the previous.
(Colour changes have consisted of a grey colour turning bright Orange, Products have rendered with spots on certain materials etc)
We have now had to recreate the materials library andupdate all our materials.

- The Environments we had in Keyshot 4 are incompatible with Keyshot 5 resulting in even more work to have to be re-rendered and material re-created to match the previous portfolio.

As well as the above, we are still facing on going issues with the following:

Firstly, a number of our Mac computers (Network Render Slaves)  flash up on the network queue and disappear again causing difficultly in  starting and finishing renders.
This results in failed jobs having to be resent and failing work over night/ weekend which ultimately impacts on deadlines.

Secondly, the network manager is not correctly reporting the number of connected slaves and at times showing no cores available when actually there are and it is currently rendering.

On several occasions more than one PC workstation was rendering even though it was not scheduled to, it froze the computer making it inactive for up to 30 minutes whilst we tried to stop the service.

Thirdly, we have to send jobs one at a time to the queue because it fails the other jobs when we send more at once.

These issues are making the software increasingly difficult to work with, could you please advise as to a solution?

We have previously sent debug log files to your support team and not had much luck with the advice given.

Regards,