Freeze/Hang on Open Project Set Up

[Marty]

This post has the problem and the successful workaround, but I'm still seeking the cause.

For whatever reason, I have a history (spanning V5 and V6 of KeyShot and multiple computer systems and OS) of what I would term a "corrupt" BIP file.

My project files are rather large (2 to 9GB). At seemingly random times, a project file will either load to a black screen (inventory of models intact in the Scene window), or hang at the Setup phase upon loading (also hangs when importing the project into an existing one).

Lo and behold, it happened today with version 6.1. This is not a RAM issue. I have 64GB and I monitor the Performance meters in the Task Manager (I'm running Win7 64bit) while attempting to open. The CPU activity and RAM activity motor along just as they do with a project that opens without issue.... the CPU cruising at near minimum, then spiking to 100% for a few seconds, then flatline. The RAM never drawing more than 16% on the 2.3GB project file.

I decided to update to 6.2, and this resolved the issue. My problem file opened flawlessly.

While I'm quite relieved that the project has been retrieved, I would sure like to understand what is going on with my project files.

I replicated the Freeze/Hang on a second system with Keyshot 6.1 as well.... so it's something to do with the project file and not the installation or the system itself.

I suppose my permanent workaround is a reinstallation of the software..... but that hardly seems like a fix.

Am I missing something? Any similar episodes out there?

[Chad Holton]

We have updates that fixes different bugs and issues, so I would assume 6.2 must have fixed the issue you were seeing. I wouldn't call updating to the latest version a "workaround" though, as you would want to be using the latest version for various reasons.

[Marty]

I would agree, however, I just confirmed that a re-installation of the same 6.1 version also resolved the issue. So the remedy is not in the update, it is in fact a workaround of sorts in the form of re-installing the software.

Regardless of what we are calling it, since there is no specific fix we can identify, that means it can keep happening regardless of the version. I would like to know the cause. If a re-installation of the software is a 100% surefire method of dealing with the issue, I'm okay with that too... but until the problem is understood, there's no assurance that today's fix is going to work tomorrow.

It's a scary environment to be working in.

[Chad Holton]

Did you go from 6.2 back to 6.1? If not and the issue is random as you say, then maybe the 6.1 didn't fix the issue as you assumed (and maybe not even 6.2). Random issues are hard to pinpoint but either way you will want to install the latest version.

[Marty]

I have two systems and bounce back and forth with KeyShot work.

When the issue popped up again... I was on my primary work station running 6.1. I took the project file and attempted to load on my portable, also running 6.1.... it failed as well.

I downloaded 6.2 and installed on my work station, and the project loaded fine.

I re-installed 6.1 on the portable (without having made the update to 6.2)... it was simply a re-install. The issue was resolved.

This was a problem for me with version 5 as well. The common denominator in this is ME, so when I say I want to determine the cause... that can also read as "I would sure like to know what it is I am doing, or my setup, that is potentially causing this problem".

It doesn't seem to be a widespread issue for other users, so I would really like to discover what's going on.

The only thing that I can possibly think of is that I prefer to set up the KeyShot resources in a directory other than the default. But since I replicated that preference in the re-installation of 6.1, that doesn't seem to be an obvious culprit.

And as I said before.... if a re-installation of the SAME version consistently remedies the problem, I am happy.

[Chad Holton]

Thanks for the information. If it happens again with the latest KeyShot version, please contact us and we'll dig a bit deeper: support@luxion.com