I was trying the new Studio physics Pause feature (an amazing update so THANK YOU to all the staff who helped implement it!!) and found that the camera works fine in ‘Run’ testing, but when in ‘Play here’ testing the camera controls only move in one direction.
When you press WASDQE or the arrow keys the camera only moves forward. I could still rotate the camera with mouse right click and point the camera in a new direction, but the controls were still limited to forward only with any camera key pressed.
Pausing in ‘Run’ testing you can still control the the camera normally.
Running Google Chrome
12th Gen Intel Core i5-12400F 2.5 GHz
Windows 11 Home
Expected behavior
I’d expect the camera controls to follow the normal setup for Studio controls.
Hello @Scottifly, can you help me understand what is wrong here?
First: when I pause physics in Play mode. and set ‘current’ to ‘client’ (the default after hitting play), none of the WASD keys do anything. I can rotate the camera but not move the character at all and so do not get the ‘forward motion’ when I press a camera key.
Can you post a video starting with a blank world, hitting play or playhere, then pause, and showing navigation with the keys? Does the character walk or does the camera move relative to the player?
Or if you are working with a particular world, can you upload it here so I can get the same result?
Second: Otherwise, this is what I’d expect, since turning off the physics engine turns off player movement.
What I see is this:
[1] In ‘run’ mode all the camera controls work, as you say, because in run mode there’s no player/avatar movement
[2] in ‘play’ mode when you set ‘current’ to ‘server’ the camera controls work, because again you’re not tied to player motion
[3] in ‘play’ mode when you set ‘current’ to ‘client’ (the default) only camera rotation and zoom work, because those are relative to the player; but WASD don’t do anything because player navigation is disabled.
This is all expected behavior.
But!
You can hit shift+P to enter “cinematic mode” and in this mode, you can move the camera with WASDQE without moving the character. So this may give you the solution you seek.
Does Shift+P solve your problem? If so please let me know and we will close this bug.
If you still think there should be some alternate camera mode that happens when paused, let us kn,ow that as well; in that case, we will convert this bug report into a feature request, since that would constitute new work.
My issue is that in example 3 using “Play” or “Play here” I don’t get a locked camera. I also didn’t choose any camera input, I just left it as Current: Client.
Any key input moves the camera forward in this example. In the video I’m using all the camera inputs I’m used to, WASDQ & E. In the video I use all those keys in the first pass but I only move forward through the workspace relative to the camera. After each of the straight movement passes I use my mouse to pan around and press many of those 6 keys again and I just get straight movement. robloxapp-20240701-2126493.wmv (1.8 MB)
I do have camera control scripts in that place, so thinking that might be the issue I tried it on a brand new baseplate as you requested. The camera then backed up like I was pressing S whenever I pressed any of those 6 keys and I was able to rotate it with the mouse. It was very hard to get a video that had any good visual references to show what was going on in that case. I tried again and the camera was stuck moving like I pressed A with any of the 6 inputs.
Shift P has always worked ok for me.
I don’t see this as game or studio experience breaking, but in my case if there should be NO keyboard input when selecting Current: Client why is the camera using those inputs and only travelling in one direction?
I use a trackball mouse instead of a conventional mouse but I seriously doubt that should affect how studio would get keyboard inputs since I haven’t customized it at all. Fyi it’s an Elecom EX-G, M-XT3UR.
Okay @Scottifly,
I’ve found that if I disable the “New Studio Camera Controls” beta then I get your behavior: in play mode, any/every navigation key backs up the camera.
Can you try enabling the beta for “New Studio Camera Controls” and see whether the problem goes away, and report back?