My Keyshot is so large

[tangballgunter]

Hi everyone,

So I've got a problem with a very large assembly that when I import into keyshot there are lots of extra parts from the vendor that supplied the file that need to be kept in the NX file but I don't need them in my keyshot scene. in keyshot I assigned all the extra parts a bright, unique color, search for that material and delete them all at once. after working on the file and deleting a little over 3,000 extra parts that i don't need i saw a location that needed adjusted so i fixed it in the NX file saved it and imported it as update geometry in keyshot and it updated what i wanted, but also replaced the 3,000 parts (untextured again) i just spent 10 hours filtering through and deleting. is there any way to tell it to NOT bring in parts to keyshot that have already been previously deleted from the scene?
I know you can use the NX plugin and update with manual selection, but my assembly is so large it crashes NX out before it can push the update to keyshot. I have contacted the luxion support about this issues but for now the only work-around they were able to provide was importing the NX file as update geometry but now doing so also replaces thousands of deleted parts that i dont want to sit and filter through EVERY time i make one small update to my model.
แทงบอลออนไลน์UFA800
Suggestions and ideas are greatly appreciated. Thank in advance.

[HaroldL]

Just a thought, but can you either SUPPRESS or DELETE everything in NX that you don't want to update in KS? Then use the add in to update the KS file. It may be that it will retain the origin of the file so you don't have to reposition the updated parts in KS.

[INNEO_MWo]

I've got no experiences with NX, so far. In Creo we use techniques to simplify massive assemblies. For this we use to hide or suppress inside parts that behind a cover. We merge (group) parts together (e.g. all parts of an engine) to get a solid body (and I don't want to discuss all ways to define a shrinkwrap with Creo at this point).

So the solution is all about structure. If I have to bring a massive assembly to KeyShot, I'd prepare it in CAD (as Harold mentioned right!).
Maybe you can hide unnecessary parts, merge some groups to get a simplified assembly. Then export this as a JT or parasolid file. The file types can be imported to KeyShot and can be used for updates as well.

One more complex way would be, if you export several simplified sub assemblies and import them as separated model sets. This structure can be updated individually.


Hope this ideas would help you to find your right way - otherwise ask a consultant.

Cheers
Marco