This is only really small but I think it should be brought up.
As I’m sure, many of you are aware that a lot of people who use OSX normally use bootcamp on their OSX machine. However, there’s a really annoying bug like annoyance when using the Mac keyboard on the client in in windows the volume control keys are bound to things in the client F12 also the Volume Up button makes ROBLOX record video whilst the F11 (volume down button) makes the client full-screen. This can be really annoying as I find I’m constantly adjusting my volume and pressing the volume down button a few times to make it go down by for example 3 bars will cause the client to go in full-screen and then out and then in then finally get stuck full-screen. (The menu button for full-screen breaks and doesn’t do anything)
This bug is similar and can also happen on windows machines if they keep pressing the F11 key a few times it breaks the fullscreen button in the GUI. This is the real bug
(I know it’s impossible to tell if someone is using bootcamp, so instead can we set our own buttons for bindings like full-screen and video recording?)
Hopefully I explained well enough, not very good at getting my words out 
tl;dr
We need the option to define our own keybounds to prevent this from happening, as well as the fullscreen button GUI from breaking
[quote] This is only really small but I think it should be brought up.
As I’m sure, many of you are aware that a lot of people who use OSX normally use bootcamp on their OSX machine. However, there’s a really annoying bug like annoyance when using the Mac keyboard on the client in in windows the volume control keys are bound to things in the client F12 also the Volume Up button makes ROBLOX record video whilst the F11 (volume down button) makes the client full-screen. This can be really annoying as I find I’m constantly adjusting my volume and pressing the volume down button a few times to make it go down by for example 3 bars will cause the client to go in full-screen and then out and then in then finally get stuck full-screen. (The menu button for full-screen breaks and doesn’t do anything)
This bug is similar and can also happen on windows machines if they keep pressing the F11 key a few times it breaks the fullscreen button in the GUI. This is the real bug
(I know it’s impossible to tell if someone is using bootcamp, so instead can we set our own buttons for bindings like full-screen and video recording?)
Hopefully I explained that well? I’m not very good at explaining
tl;dr
We need the option to define our own keybounds to prevent this from happening, as well as the fullscreen button GUI from breaking [/quote]
1 Like