Keyshot 10 and new SolidWorks plug in - issues continue

[quigley]

I have just installed the current release of Keyshot 10, along with the current release of the Solidworks plug in.

I have come across an ongoing issue I reported a few years ago but nothing was resolved. It relates to using the plug in on files that have assembly level cuts in Solidworks. I'll explain by example.

Take this relatively simple structure in SolidWorks. It is a assembly file with multiple configurations. This configuration uses a few assembly level cuts as indicated:

See attachments

So with this file I have rebuilt it, ensure all components are fully resolved and pressed the "Send to Keyshot 10" icon on the Keyshot toolbar.

This sends the file to Keyshot 10. Note that I have tried this with keyshot 10 closed and keyshot 10 already open. The results are the same each time. This is what I get in Keyshot 10:

See attachments

Note that the upright component is made as a multi body part. Only the bodies that have the assembly level cut acting on then are not take through to keyshot.

This is 100% repeatable on all the machines we run Keyshot on. It was the same In keyshot 8 and keyshot 9, and now keyshot 10.

I really don't want to have to reduce our use of Keyshot but this is an ongoing issue. The only solution is to export the SolidWorks assembly as a STEP file – which works fine:



Can this issue be explained or resolved please? If it is an issue with the Solidworks API then can you please confirm.

I have attached the BIP file and the SolidWorks package for the above.

We are using fresh installs of Keyshot 10 and the SolidWorks plug in downloaded from the Keyshot website. We are using SolidWorks 2020 SP5. We have tried this across multiple machines and the same results each time in Keyshot 9 and 10 – all Windows 10 (latest update), with a variety of nVidia and AMD graphics cards with the same results.

[Higuchi]

I'm also feeling stress for transferring from Solidworks to Keyshot too since I started to use Keyshot for the first time.

They are about,
- cannot updating the models well revised on Solidworks
- cannot transfer the original name done on Solidworks to Keyshot (*this problem is only for Part data, not for Assemble data)

Hope it will be improved soon on Keyshot 10.x for all Solidworks users!
Thank you,

[quigley]

Im bumping this one up again as it is so critical to our workflow. The files were submitted and a case raised, and apparently sent up the chain to development. Then I get an email backing saying the case is closed? Just tell us, is this replicated or not. Is it an issue as I have detailed? Is there any point in using the plug in?

[DriesV]

Hi Kevin,

I checked out your SW model, and can confirm the issue with the disappearing bodies when transferring the assembly to KeyShot through the plugin.
Your issue (together with the model) is logged into our issue tracker and is currently in investigation by QA.

However, it does seem like the geometry and NURBS data does actually make it into KeyShot, even though the parts aren't being shown in the Real-time View.
Here are a few workarounds you can use, while we get to the bottom of the issue and try to get it resolved (if the SW API will allow).

• Use NURBS Mode. When you enable NURBS Mode, all parts should be shown in the Real-time View. Of course NURBS Mode has its limitations when it comes to (UV) texturing and performance.
• Re-Tessellate the parts that aren't being shown. Even though the parts are not shown in the Real-time View, they still exist in the Scene Tree. You can enable NURBS Mode in order to show them in the Real-time View. You can then select/pick the parts in the Real-time View to highlight them in the Scene Tree. Finally, select the parts and open the Re-Tessellate tool. After re-tessellation, the parts should be visible in the Real-time View without NURBS Mode.

Dries

[quigley]

Thanks Dries I'll give that a try.

[DerekCicero]

Im bumping this one up again as it is so critical to our workflow. The files were submitted and a case raised, and apparently sent up the chain to development. Then I get an email backing saying the case is closed? Just tell us, is this replicated or not. Is it an issue as I have detailed? Is there any point in using the plug in?

I think it's gets set to 'closed' when it gets escalated, but I will check. I agree it's not terribly helpful. Hopefully we can provide better visibility into issues sometime next year.