topic Re: Import of large (55MB) Rhino v.4 file fails in Fusion Design, Validate & Document Forum

Import of large (55MB) Rhino v.4 file fails

lure23 — Wed, 26 Jun 2013 05:49:56 GMT

Hi,

I tried to import 4 Rhino models to Fusion 360. Three of them succeeded whereas the largest one failed twice (so I think it's a systemic fail).

Maybe this has to do with bandwidth or timeouts. We do have a 10Mbps connection but the actual throughput used seemed to vary quite a lot.

Here's an error message that like has to do with the problem. Should I try a third time, or would you like to get access to the file?

Re: Import of large (55MB) Rhino v.4 file fails

innovatenate — Wed, 26 Jun 2013 16:21:05 GMT

Hello,

Could you verify which version of Fusion you are running by checking the Help > About dialogue? A work around may be to break the file down into two smaller files.

Could I get access to your file? I've sent a link to an FTP site for you to upload the data to. Let me know if there are any difficulties uploading the data.

Thanks!

Re: Import of large (55MB) Rhino v.4 file fails

lure23 — Wed, 26 Jun 2013 18:30:18 GMT

Hi, Nathan

Fusion 360 is 1.8.557 on OS X.

The second update of the same file eventually succeeded. But I uploaded the file to the FTP in case you want to test. The filename is a bit wacky, "Tokaversio\ 009\ rendaukseen\ monta\ jonossa.3dm".

One issue I noticed is that for a failed upload one gets rather many notifications. Seems it retries occasionally or something. This gets confusing for the user (well, async interfaces do anyhow; not sure how it could be fixed).

Cheers,

- asko

Re: Import of large (55MB) Rhino v.4 file fails

innovatenate — Wed, 26 Jun 2013 22:25:05 GMT

Asko,

I'm glad everything eventually worked out, thanks for update.

There are some known issues with importing large files. There is a potential for a time-out to occur in some scenarios. If the first translation service fails, further attempts will be made, resulting in a high number of warning messages. Development is looking at this issue closely. Thanks for the feedback, keep it coming!

Cheers,