KeyShot Forum

Can Keyshot 3.3.33 import Solidworks 2013 files?

I've recently updated from sw2012 and anything I've worked on since will not open - "XXX does not contain 3d geometry"

If not does anyone know when if there should be an update due to fix this?

If you check the BETA importer in the advanced tab of the Import dialog, then you will be able to import SW 2013 files. We hope to have a more official support soon.

Maybe a bit slower than normal, but it worked!

Thanks Thomas  8)

It is slower because it tessellates the model on the fly, rather than reading the tessellated information that is stored in the file.

I'm glad that it worked, though.

When will there be official support/plugin for SW2013? Running into a few difficulties opening SW2013 files.

+1

Any update on this. My company has only just bought Keyshot and after updating Solidworks to 2013 I'm having problems importing asm models. For example not all parts import in the model.

Try the plugin. It works with SW 2013. You can import the models directly from SolidWorks into KeyShot.

Hi Thomas,

This option does work for parts, but my larger .asm files (15mb) wont import into KS. KS loads up, imports, but there is just a blank screen with no assembly visible and the project tree is empty.

15mb is not large. Can you send me the assembly so we can take a look? Please send to support@luxion.com. Confidentiality is guaranteed.

Thanks,
Thomas

I have sent the asm and part files via a yousendit link, fao yourself.

Thanks for your help Thomas.

Thanks  -we will take a look.

Hi Thomas. I'm in trouble with Solidworks 2013 and Keyshot 3.
I've downloaded and installed the plug-in for SW13 from the Keyshot website, but Keyshot doesn't see or recognize the plug-in in the dedicated option panel, and i'm still not able to open my .asm and .prt files correctly.
Also checking the BETA importer in the advanced tab of the Import dialog, does not totally resolve the problem, because Keyshot reads wrong surfaces or forgets to import other surfaces.

I'm having the same problem Andrea. Keyshot doesn't import all surfaces from SW13 even with the 'New Importer (Beta)' checked. Just have to wait for Keyshot 4 and hope they have fixed the plugin.

It will be updated for KeyShot 4, which will be released mid February.

The plugin works today. It puts a button into SolidWorks, allowing you to transfer your data from SolidWorks directly into KeyShot.

Thank you so much Thomas! It works perfectly!  :D

Still having the same problem importing some SW13 files into Keyshot 3.3. Hopefully KS4 is out soon and will rectify.

(http://i45.tinypic.com/2egd6cy.jpg)

Can you share this model and I will take a look? Send to me, please: thomas@luxion.com

I will need the entire assembly with all the parts.

Thanks, Thomas

Thanks for sending. Looks good in KeyShot 4. In the meantime, you may want to try the plugin to get the assembly directly from SW in to KeyShot.

Hi Everyone,

I apologize if this question has already been answered somewhat but I'm having the same issues as the original poster, however, I'm currently using the latest version of keyshot 4 in conjunction with solidworks 2013. Importing with tesselation is not an option for many of my projects because, for some reason, tessellation in keyshot 4 will add unwanted surfaces and distort surface geometry on surfaces with continuous curvature.

My only current work around is to use the plugin for solidworks, however it's not ideal for workflow since it creates a separate file which I then need to import into my scene again and reassign all materials.

I've included some screen shots of what I'm experiencing.

Don't understand what you mean by "separate file". The plugin doesn't create a separate file that needs to be imported or managed.

It creates a new .bip file on export, doesn't it?

Only if you select "export". If you select "render" then it will transfer the geometry in session directly into KeyShot by opening the application upon transfer.

Thanks for the clarification but my core issue still stands. Is there any foreseeable fix for the "does not contain 3d geometry" error? This has been an ongoing issue for the better part of a year now and creates a small but quite disruptive kink in my (and I imagine others') work flow.