Does this fix this bug with the client camera?
7 Likes
No, this doesn’t fix that.
Which behavior is used depends on what the firmware of the device you’re using reports for hasPreciseScrollingDeltas. If it’s true, you’ll get panning from (vertical and horizontal) scroll, if it’s false, you’ll get zooming from scroll.
-
For MagicTrackpad and built in Macbook trackpads,
hasPreciseScrollingDeltasis true and gives panning. -
For most traditional mice, even some fancy ones with horizontal scroll capability,
hasPreciseScrollingDeltasis false, and gives the intended zooming.
You can probably find a third party program that gives you more control over this but there’s not much we could do short of offering some optional force override of the device behavior.
7 Likes
Did they change that? Because, I can’t open the chat anymore when it’s manually closed. 
5 Likes
Excellent! The Mouse Enter/Exit behavior has been broken forever
6 Likes
Thank you for considering the feedback!
Does this mean we can finally use trackpad to easily navigate Roblox studio camera?
3 Likes
“Easily” is in the eye of the beholder, I’m fixing scrolling here, not rewriting the Studio camera.
Though it will certainly be a big step up in experience, because Edit camera will zoom smoothly at a sensible rate with trackpad now similar to the other improvements.
10 Likes
-- Why specifically Playstation and not Xbox? My first assumption was the touchpad but the touchpad just isn’t utilized at all last I checked? Can we see input from the touchpad now?
4 Likes
while you plan to bring studio behaviour to client, i’d appreciate a toggle switch to do the opposite, turn off trackpad support in Client… only because logitech’s terrible driver software for their mouses forces trackpad emulation, even though a mouse is not a trackpad (who knew?), so if you try and play roblox with a mx master with the drivers installed, attempting to zoom the camera instead pans the camera on the y axis
and also lack of the ability to shift+scroll on macos has been a pain for YEARS
5 Likes
Sorry, XBox is included, updated the text.
Just forgot to mention XBox because it has no unique code for this: XBox is basically a stripped down Windows computer underneath the covers so it actually uses the same input code as Windows Client.
You can expect the same thing that Windows Client does if you plug non-controller input devices into an XBox.
You may be able to get a third party program that undoes the emulation:
6 Likes
The beta feature is now available,
We recommend keeping the beta feature disabled when you’re not you’re testing how an experience will be impacted, to avoid unintentionally seeing unexpected differences in experience behavior compared to when you were testing in Studio.
10 Likes
Oh, yes.
No, I think I was more thinking about something that I discovered once long ago.
I think that method doesn’t return a string for everything though. Which you can easily counter by checking for that, and if it did, just display the KeyCode Enum itself or something.
Summary
I think here I had wrong design in mind. But I am not sure.
Based on my old threads, if I look at this https://devforum.roblox.com/t/id-like-to-tell-you-about-textchatservice-and-specialkeypressed-and-the-problem-with-keybinds/2525959
It was “string based”
If I want to look at it today again, I’d have to experiment with what SpecialKeyPressed actually does, and study it a bit better.
A lot of these issues… e.g. having / through Numpad or SHIFT + 7 (depending on keyboard layout) was just a thought.
I don’t think there’s any games that determine key based on the string they give. For some reason Roblox had it like that, not sure if they still do, would have to check.
I think the bug here is that the Numpad key that returns /, gets returned as an empty string by UserInputService:GetStringForKeycode() the last time I tried it. Which was like 2 years ago.
The right design is to use KeyCode IDs, and not string. I think the only issue I encountered back then is that not all of the GetStringForKeycode() returned a string. Which you can easily counter by checking if it returned an empty string, and if it did, just display the KeyCode Enum itself or something.
4 Likes
This is awesome, this will make camera control much easier.
4 Likes
That took slightly longer than expected, but we’re now ready to begin rolling out these changes.
Tomorrow morning we’ll begin rolling the changes out to a small number of desktop users to check that everything is working before doing a full rollout.
1 Like
hi, did this change the studio trackpad controls? The studio trackpad feels a bit unusable right now, it’s very jittery and isn’t recognizing small inputs (camera doesn’t move if I don’t make a huge scroll)
Also when play testing in studio I’m completely unable to zoom now (pinch to zoom does nothing) and the camera controls are super slow
Yes, I rolled this out to desktop, can you DM me detailed information? (OS, Version, Hardware, video of what you’re seeing)
ohh it’s because I didn’t have New Studio Camera Controls enabled. My studio controls feel way better now that I enabled it, I especially love that it doesn’t move in steps anymore, way to go!
The only issue I’m still having is playtesting still doesn’t let me zoom in and out. I’m able to move my camera with the normal swiping trackpad gestures but pinching does nothing. Also the camera swiping movement speed feels out of sync with the normal movement speed that I have in-game on Roblox (feels slower in studio play mode)
Macbook Pro 16-inch
Apple M3 Max
Sonoma 14.1
Yes, that’s because that’s how it works in Mac Client as well.
As noted in the post, Studio is currently missing pinch-to-zoom, which is how you would typically do it on Mac Client. For now you’ll have to use the i/o key to zoom in playtesting on Mac if you’re not using a mouse with a wheel.
1 Like
sounds good, I’ve gotten pretty used to testing in-game frequently anyways because the studio play test has needed improvements for a while so I’m looking forward to getting the pinch to zoom extension implemented.
I think it would also be good if my camera’s speed can more similarly match the camera speed that I use in-game, it’s currently slower and requires more swipes than what I do ingame to move my camera around.
I also think a way to quickly toggle to full screen mode while playtesting would be great, and make studio testing feel a lot closer to the regular in-game playTest, it currently involves more steps to make it full screen, (dragging the tab, then double clicking the top bar). I also think a lot of devs are unaware of how to do that too (I didn’t until today), and a large/obvious button to switch back and forth (to get back the widgets) would be super useful. Maybe this makes more sense as a plugin feature but idk
Update: The changes are fully rolled out on desktop and we haven’t seen any issues which would require them to be reverted.
We will roll things out to the remaining platforms starting on Monday next week.
1 Like
These changes are now enabled on all platforms. Enjoy the fractional deltas!
5 Likes