Keyboard shortcut conflict - CTRL+C and CTRL+V

[ameilihog]

Hi, this started after the last update and I forgot it was still occurring.

Obviously the issue is the fact that supposedly ctrl+c and ctrl+v both have conflicts when nothing done user side has changed, and resolving the conflicts require finding the function that is in conflict - which I have no idea. There is no indication visually from the tool bars that this has been assigned to anything. Has Fusion itself reassigned them?

[bwalker145]

I'm having the same issue, no changes outside of updating Fusion.

https://forums.autodesk.com/t5/fusion-support-forum/bug-drawings-keyboard-shortcut-conflict-warning/...

[xo.rahul]

Same here. Probably a bug. I ended up contacting support.
This is what they said, 

Thank you for bringing this to our attention and apologies for the inconvenience caused.
I was able to replicate the mentioned behaviour and I have escalated this issue to the development team.
I would like to inform you that the change request FUS-245081 for this case has been entered into our development system.

We will update this case with any information we get from our development team as it relates to this change request.

---

I guess, we will have to wait for the next update. Hopefully soon.

[nodnarb93]

This issue is not limited to Ctrl+C and Ctrl+V. ALL of my custom shortcuts are resulting in a "Keyboard Shortcut Conflict" error. I just spent 20 minutes re-applying all of my old shorcuts to wipe out the forcefully instanted default shortcuts, only to find that my fix was not persistent across software restarts. WTF.

This bug was introduced with the mid-April update and was NOT fixed with the late-April update. Meaning that Autodesk leadership is NOT prioritizing this issue. 

So I want to take this opportunity to make my frustration perfectly clear in terms they understand. This bug breaks my entire workflow and therefore makes Fusion an unviable product for my use-case. If this isn't fixed immediately I will have no choice but to abandon this software suite entirely (and I suspect I'm not alone).

Quit replacing developers with sloppy AI vibe coders or it WILL hit you in the only place you care about: your wallet.

Update: I just got off the phone with support and they seemed genuinely unaware that this issue affected all user shortcuts. The support rep reproduced the issue on his end during the call and was adament that it would be escalated and prioritized. Really hoping that pans out in time for the next update 🤞

[xo.rahul]

Ha, to be fair, been a long time user (almost 8 years) and they have had these kind of issues since then. Safe to say it's not necessarily AI written code, but just good old buggy code which takes them lonnnnng time to address. I have personally been trying Onshape, but they are very expensive for our work vs the amount they offer, so in that regards, Fusion remains with high value proposition.

[jon46XEC]

5yr user here - and this is annoying 

@jon46XEC - this post has been edited due to Community Rules & Etiquette violation. 

[devFS]

I'm getting this error too. Please fix it!
Also, please add a list of all shortcuts in the settings that can be edited within the app.

[bbroughton9XLN3]

Is there any update on this issue? It is having an extremely serious impact on my workflow and I suspect many others are dealing with the same frustration. I think since I started using Fusion 360 several years ago, this has been the most frustrating and serious bug that I have encountered to date.

[nodnarb93]

2 months later and this bug has STILL not been fixed in any of the sebsequent updates. 

Whats worse is that Autodesk hasn't given any public indication that there's a plan to fix it. 

Here's the mental math going  through my head right now:

[Massive bug] + [No fix] + [No statement from Autodesk] = [Abandonware]

But if there's any Autodesk reps reading this, it would be so easy to change my mind.

All that to say.... The $15/month Solidworks Maker Edition is looking more and more attractive every day.

[ellis_woollatt]

Any update here?

[sbingDU6EK]

This is so annoying ! Using CTRL C, CTRL V makes the sofware crash and I need to restart all. It's such a reflex that even knowing it, I still do it all the time !!!

Please fix this !

[liang_chen]

The issue was reported as FUS-245081, and now is fixed in internal build, which is planned in the next Major update of July.

Thanks all for the feedback and patience.