topic Re: McMaster-Carr repeat login request in Fusion Support Forum

McMaster-Carr repeat login request

Careless_ — Fri, 17 Sep 2021 04:33:44 GMT

Fusion360 version 2.0.10940 on macOS 10.16.0

Recently, McMaster-Carr changed their download process to require an active login in order to download CAD files (understandable).

Fusion360 does not save the login information, but it would be great if it did save it in the macOS keychain somehow.

Is this going to pose a security issue if this is implemented? How would Autodesk store this information if/when fixed?

(Also: McMaster-Carr is really fast on a browser, but terribly slow in F360. Is there a possibility of optimizing this?)

Re: McMaster-Carr repeat login request

mohammed.aliTDPXK — Fri, 17 Sep 2021 06:23:18 GMT

Hello @Careless_ ,

For now, for every session of Fusion we need to login to Mac master carr . I am not sure when this will be fixed or stored as you mentioned but seems a good feature to me.

Let me check with the team and get back to you on

If we can store this with Fusion
If there is any security issue.

On the download side, I see very less delay in getting the parts directly imported to Fusion and it will be available for use :). If you download from website, again you have to add/upload to Fusion projects which is time consuming in my view 🙂

Thanks!

Re: McMaster-Carr repeat login request

Careless_ — Fri, 17 Sep 2021 06:30:08 GMT

Thank you for looking into this, Mohammed.

Yes, you are definitely correct in that it takes less time to import through Fusion's McMaster interface, but it is very sluggish sometimes and I find myself clicking on links it can take up to 3 or so seconds to respond, which causes me to mis-click sometimes and require me to start all over again because of how slow it is. I always know to exercise patience within F360's pop-up, but it can still be quite finicky due to how unpredictable it is.

I'm not sure why it is this slow to respond. It very responsive in Safari, Brave, Chrome, and Firefox. I tested all of them just to see if it was something with the web-rending engine used in different browsers, but none of them were as slow as F360. I just know there has to be some kind of optimizations that can be made, though I am presuming the entire F360 browser implementation isn't written from scratch.