Importing Fusion files into Keyshot

[Anonymous]

I'm having an issue importing my files into KeyShot.

When I create the entire product in Fusion it tends to import fairly fast.

But typically I get a .step file from engr. that I open in Fusion.  I then "strip" it down, add, subtract, build around it etc. then import it into KeyShot via the live link Plug-in.

Files take hours to import.  

People have asked how big the file is but I can't figure out how to tell.  When I go to A360 the file size is blank.

Is this a Fusion, Cloud, Keyshot or hardware issue?

Thanks,

Gary

Principle Industrial Designer

[James.Youmatz]

Hi @Anonymous,

Welcome to the Fusion 360 Community!

Glad you saw my message on Twitter - I think it will be easier to go over this in detail on here. Do you have any sample files that I could play around with that would be Keyshot ready? I'd love to test this functionality on my computer and see if it is specific to the app, file, or computer. Feel free to post the files here or email me/send a box link to [email protected] and I can take a deeper peek.

Thanks,

[Anonymous]

Were you able to open the file sent yesterday?

Thanks,

Gary

[James.Youmatz]

Hi @Anonymous,

 Yep! I was actually just playing around with it. Embarrassingly however, my Keyshot trial expired so I'm working on finding someone that has one that I can test around with....

Regarding this however, I don't know if I would call this model "simple". It took some time to import, and about 5 minutes to even open the file. There is a lot of geometry on screen and I'm imagining the save/export/upload/open process into Keyshot probably will stall a bit as well. It's about a 100 mb file. How long was it taking you to push the file into Keyshot? Also, if you were to manually export the file and upload into Keyshot how long does this take (mostly concerned about the opening in Keyshot phase). This will help me narrow it down a bit.

Thanks,

[Anonymous]

I don' really know how long it took. I waited 1 ½ hours then went home. It was in KeyShot when I returned the next morning.
If I export the file as a .step and import it, it imports in about 15 min.....really not bad!
It's when I use the plug-in that it doesn't import for such a long time. I of course could just use the step but when I need to make a revision I have to make another step and when I import the new step all the color and materials assignments are lost. With the plug in I can go back and forth.
Maybe it's the plug-in issue.
Thanks,
Gary

[James.Youmatz]

Hi @Anonymous,

That's my initial thoughts too based on what you said. It looks like this app is made by Keyshot however. Do you mind reaching out their support team as well while I dig on our side ([email protected]). I'd be curious to see what's going on.

Thanks,

[Anonymous]

I reached out to them yesterday also....they don't seem to be as fast as you guys are!!!!
Thanks,
gary

[mcramblet]

Unfortunately, getting support for Keyshot is like pulling teeth. I really like the product, but the support is poor. I've seriously been trying to get an answer to a question for over a month. I've asked the question via email, support ticket, and the forum, still no response. I've even tried posting the question on some social media sites, hoping that might spark a response, so far, nothing. 

The Keyshot LiveLink plug-in isn't very good either, so I rarely use it. Without any control over tessellation or orientation, it's not very good. The plug-in for Rhino is a nice implementation, but for Fusion 360, not so much. I find it easier to export to a .STEP or .SAT. I've asked questions about some issues with the Fusion 360 plug-in, and never received any answer.

With Keyshot, you have a really nice, easy to use product, but such poor support. It's really sad.

[Anonymous]

Thanks for the reply.  I did get a response indicating it would just be best to make a step and import.....I guess that is what I'll do.  I would be convenient if the Live-Link would work!

[James.Youmatz]

Hi @Anonymous and @mcramblet,

Sorry to hear about the lack of responsiveness regarding the app 

I'll keep testing around just to ensure it's not something that can be fixed/work-around on our end, but I do agree, in the meantime manual export/import seems to be the way to go. 

Thanks for the patience guys,

[mcramblet · Accepted solution]

@Anonymous-

I case you didn't know, you can still have the basic functionality of "live-linking" even when exporting files. The key is to maintain names, of the exported files, along with the names of bodies and/or components. As long as the names are being maintained, you can make changes to the Fusion file, re-export it (with the same name and replace the previous file), then import it back into Keyshot and make sure to select "Update Geometry". Keyshot will update the file and material assignments will remain. It's really the same workflow that the plug-in provides.

[Anonymous]

Yes...thanks...I had a feeling about that and was doing some test parts but I never read it anywhere.

But now you confirmed it....many thanks....btw I've only used Keyshot for a month or so.

Thanks again!

[dave.waddellE7ZQK]

I would really like to have native file support for FUSION files. How can this be done ?

[mcramblet]

Currently, it can't. If you wanted Keyshot to open native Fusion 360 files (.f3d or .f3z), I'm pretty sure it would need to start with Luxion/Keyshot wanting to add that functionality. If there are enough users asking for native support, Keyshot would be interested in looking into the possibility. Without Keyshot being the driving force or without a large number of users asking for it, it won't happen. I'd suggest inquiring about this on the Keyshot forum.

[dave.waddellE7ZQK]

I don’t think “Talk to luxion” is an appropriate response . Why can’t
aurodesk do this ?

[mcramblet]

Perhaps I'm not understanding your question. How could Autodesk implement something in another company's software product? If you want Keyshot to natively accept a certain file type, Luxion is going to be the one that does it. Autodesk may need to assist, but how could they add functionality to a software product that isn't theirs?

[dave.waddellE7ZQK]

You are a software company. Your users don't build software . Partnerships
and integrations are a good thing for you, especially if your users want
this. I think it makes plenty of sense for Autodesk to be reaching out to
people like luxion in order to make your product more desirable. Besides ,
if you were to make a keyshot plugin , it would mean that Autodesk would
have to make it. Im honestly confused by your position on this.

[mcramblet]

Nope, I'm not a software company, I'm not even an Autodesk employee, I'm simply a Fusion 360 user expressing my opinion, in this forum. My opinion is still that Luxion should be the one to drive that train, since they are the ones in charge writing their software. You certainly don't need to agree with me, it's only one persons opinion. I just don't see it happening the way you think it should.

[dave.waddellE7ZQK]

I'm replying to these through email , didn't realize you weren't an
Autodesk employee. Afaik both companies need to be involved to get this
happening, if Autodesks' official recommendation on this is "nah , you
should call them and tell them " I still think that is pretty weak.
Certainly Autodesk talking to luxion would be far more effective than one
person at a time reaching out to them.

[Anonymous]

Still need keyshot?