Keyshot 3 crashes on open of large .BIP

Ryno · August 03, 2013, 11:19:46 AM

I have a .BIP file that's approaching 1.6GB in size, and Keyshot is having trouble opening it now. The program either crashes, the scene is pitch black, or the scene remains the default scene, despite the objects being listed in the project window.

I'm running KS3 64BIT on Windows 7. It is a large file, but I was able to open it before and nothing has changed since. I've tried killing some background processes to free up memory but it's not having any effect.

In the project tab it looks like it's trying to render the material spheres, but the progress bar just sits there and doesn't move.

The only thing I can think of to try is to give KS3 a highest priority in the task manager, but aside from that I can't come up with any other ideas at this point. The process in the task manager currently is using about 3,9500,000 K of memory when trying to load this .BIP.

Brandon Davis · August 05, 2013, 07:52:40 AM

How much RAM do you have on the machine?

Speedster · August 05, 2013, 09:26:09 AM

Almost identical to the problems I'm having, except in 4.1, with .bip files now approaching 6 GB, but it starts at about 750 MB. I'm running 8 cores and 16 GB of RAM. Smaller assemblies no problem. I have a post on the Forum >General Discussion, in the same vein-
Bill G

Brandon Davis · August 06, 2013, 11:10:49 AM

Speedster,

Would you mind sharing a smaller model that is producing this issue? You can send it to support@luxion.com via keyshot.wetransfer.com.

Speedster · August 06, 2013, 02:40:08 PM

QuoteWould you mind sharing a smaller model that is producing this issue?

Actually, smaller models and assemblies are mostly OK, so it would not be helpful in diagnosing the problem. But judging from the many users having this problem, on this and other posts, it really needs to be resolved. I can send you the SolidWorks 2013 Top Assembly that I'm having fits with- it's 119 MB.

I did a test- I suppressed all but the main set piece and two assemblies. It opened OK after about 30 minutes, resulting in a 1.3 GB .bip @ 10,000,000 + polys. I then successfully imported one additional assembly. Then when I attempted another import, it just crashed, on numerous attempts, various import techniques and with beta checked and un-checked. Even tried after a cold re-boot.

Another interesting test- I attempted to import an existing .bip, with all materials already applied. Immediate crash! Crashed regardless of import method.

I'm not in a panic on it as it's not for a client- I'm trying to create a museum exhibit with all of my vintage automobiles. But I had the same problem with a large (and important) client project several weeks ago, and Bruno helped me out. That's when we discussed the possibility of disc space and paging issues.

Bill G

Ryno · August 07, 2013, 11:28:05 AM

Quote from: Brandon Davis on August 05, 2013, 07:52:40 AM
How much RAM do you have on the machine?

Sorry for late response, busy weekend! My specs are below:

PC Specs: OS: Windows 7 Home Premium 64-Bit CPU: Core i7-2600 @ 3.4GHz RAM: 16GB GPU: AMD Radeon HD 6900

I am loading off of a different drive than the program is installed to, as well (I have all my personal work on a third hard drive). I forgot about that detail. I can try copying the files to the main drive and trying that when I get a chance.

One thing; could having a very large HDR in the scene wreak havoc here, as well? I have a very large HDR in the scene right now because I've been trying to output 7000px wide renders. It's surprising that it's having such a tough time loading the scene, though, when a render that size takes only ~30mins.

Chad Holton · August 07, 2013, 11:45:47 AM

Hi Ryno,

Sorry if you mentioned it somewhere but what exact version of KS3 do you have? You can find out under Help>About.

Thanks,
Chad

Ryno · August 07, 2013, 12:10:45 PM

I'm running 3.3.33 at work. Probably the same version at home (which is where I've been doing those renders).

Chad Holton · August 07, 2013, 12:32:57 PM

Please check at home to be sure.

Speedster · August 07, 2013, 01:10:58 PM

QuoteI am loading off of a different drive than the program is installed to, as well (I have all my personal work on a third hard drive). I forgot about that detail. I can try copying the files to the main drive and trying that when I get a chance.

Interesting- that's what I plan to do later today. Just got off the phone with the company that built my custom workstation (Datel Systems, San Diego) and he mentioned that there may be a split-off and bandwidth issue here.

I have KS 4.1 on my C-drive (that I'm upgrading from 160 GB to a 500 GB SSD), BUT, I have my KeyShot Resources on the E-drive, re-pointed, and I keep my assets on either E, F or G. I never had any problems back to KS 2 until I shuffled everything around to gain headroom.

So this is well worth the test. Let us know your results, as will I.

Bill G

Ryno · August 07, 2013, 01:13:16 PM

Quote from: Chad Holton on August 07, 2013, 12:32:57 PM
Please check at home to be sure.

Will do.

Quote from: Speedster on August 07, 2013, 01:10:58 PM
QuoteI am loading off of a different drive than the program is installed to, as well (I have all my personal work on a third hard drive). I forgot about that detail. I can try copying the files to the main drive and trying that when I get a chance.

Interesting- that's what I plan to do later today. Just got off the phone with the company that built my custom workstation (Datel Systems, San Diego) and he mentioned that there may be a split-off and bandwidth issue here.

I have KS 4.1 on my C-drive (that I'm upgrading from 160 GB to a 500 GB SSD), BUT, I have my KeyShot Resources on the E-drive, re-pointed, and I keep my assets on either E, F or G. I never had any problems back to KS 2 until I shuffled everything around to gain headroom.

So this is well worth the test. Let us know your results, as will I.

Bill G

I'll get on that tonight when I get in from work. Hopefully I can do a test before my better half gets home from work; she needs the computer all night.

Ryno · August 07, 2013, 02:50:53 PM

Alrighty, 3.3.33 at home as well.

Tried loading the file right from the main disk as well, and it's exhibiting the same basic behaviour.

Chad Holton · August 08, 2013, 05:52:26 AM

Quote from: Ryno on August 07, 2013, 02:50:53 PM
Alrighty, 3.3.33 at home as well.

Tried loading the file right from the main disk as well, and it's exhibiting the same basic behaviour.

Thanks for checking. I was hoping for an easy fix but it's not looking that way. You mentioned using a large HDR; just to see if that could be an issue here, would you mind renaming the HDR or moving it (basically hiding it from KS)? This way KS will grab the startup HDR instead. May be worth a shot.

Ryno · August 08, 2013, 06:12:03 AM

I'll give that a shot when I get home tonight!

Ryno · August 08, 2013, 04:54:22 PM

Alright, I pulled out the file that I believe to be the one that has been used and the file opened. I tried adding the file back, then changing the environment back to the desired HDR, and the real view render would not renew to the new HDR. I tried a test render which rendered with the HDR that loaded when the program loaded up (not the desired HDR). When I cancelled the render, Keyshot crashed. The HDR I want to use is 102MB

[EDIT] Alright, so I tried opening Keyshot again, with the HDR in the environments folder. It opened this time, and I'm currently processing a 7000px render (yay!). I'll let you know if it starts acting up again.