When opening my files from my machine, I am unable to save my work to my machine via the worldwide industry-standard convention for assigning a shortcut to allowing a user to save their own work to their machine, Ctrl/Cmd + S.
In Team Create sessions, Ctrl/Cmd + S works without issue.
Edit: Post changed to be more productive
Like I know I wrote this quite sensationalist; I guess Iām just really jaded on prior bug reports not being resolved and if Iām not happy with that then I should stop making bug reports.
I found out that they changed the default Ctrl+S keybind to this weird hybrid thing (I actually donāt know if it was like this beforehand and it managed to break today, still annoying) that doesnāt even work with local places, and without warning, too. It made me have to change my shortcuts for the first time because the one Roblox forces is half-broken. Really hope they fix this ASAP
Adding on to this as I have been able to commit some time looking into it.
āSave To Robloxā is for saving an active team create / online document.
āSave To Fileā is for saving an active local file.
As these are both expected to be initiated by the save shortcut, it appears now that identical shortcuts are NOT able be shared between multiple actions.
What this means now is that Iām forced to make a choice for where I want my save shortcut to be; for my online work, or for my local work.
I am choosing local.
I canāt reproduce this. Maybe Iām misunderstanding:
I will double-check now following the repro steps youāve listed
Before following your repro steps, I reset my keyboard shortcuts to default, closed studio then opened a fresh instance.
Following the above, your repro steps results in expected Cmd+S behaviour.
I wanted to make sure I didnāt just pull your time for a nothing-burger so I did some more digging, tried various patterns of opening/closing TC/online/offline documents and closing/reopening studio at different points to see if I could trip anything, but all seems fineā¦
Given that the bug did occur from myself and anecdotally others in private conversations, I would have to hazard that resetting my keyboard shortcuts in studio (In order to get a ground-truth approach) allowed a fresh slate for shortcut behaviour.
Was there a recent update that changed how the shortcuts are interfaced without correct sanitising?
Hereās my version info for context; my studio did update today before this bug started happening (I was happily Cmd+Sāing on a local place without issue til ~3am last night).
No changes to shortcuts or saving that Iām aware of. Thereās been quite a lot of work around Contexts which is our new way of enabling/disabling things depending on whatās happening.
I am also on production v686. This weekās update hasnāt gone live yet. I do believe you! 
Oh I do have the new UI turned on(Next Gen Beta Feature) . I assume you donāt?
Yeah I was using the legacy UI which exhibited those behaviours before resetting my shortcuts, so thereās a discrepancy between us both atm.
This is wild guesswork since Iām on the outside, but it might be worth running a fresh install of the previous production version, ensure legacy UI (Possibly reset shortcuts after switching to legacy if its dynamics donāt trail back a few versions?), then try the repro before & after forcing the v686 update.
Thanks for committing your time to this 
Weāve got someone able to repro internally so weāll chase it down!
Hey, I can explain what is going on with the shortcuts here. Some time ago we added a generic action named just āSaveā which will automatically save to wherever you saved last which is now the default binding for ctrl+s. The idea with this was that ctrl+s should work intuitively whether you are working on a local file or a place that is saved to Roblox.
Looks like there is some windows-specific bug here that is causing the generic āSaveā to fail to write your place out to a local file, so remapping to āSave to fileā for now is a reasonable workaround.
Sill looking into the exact cause of the problem and Iāll post an update here once I know more.
Hey, thanks for updating me; I do use studio interchangeably on windows & mac systems if thatās info of any value; the issue I reported occurred today on my mac however.
Hope you find a fix, I am glad I get to workaround it for now with a shortcut remap for the time being.
Hello, we were just coming around to fixing this and noticed that we could no longer reproduce this bug. On my system whenever I try it will now correctly save every time where I expect. Let me know whether you are still seeing this problem or not.
If not we can close this thread.
If it is still happening we can look a little deeper and figure out exactly what is going on here.
We havenāt received a response, so weāre closing this report for now. If youāre still experiencing the issue, please feel free to file a new report with additional details. Thank you!
