Play solo dumps me at (0,0,0) not camera location

Running ROBLOX studio version 0.308.0.150864 on windows 10. Occurs in both System Menu and Ribbon Bar. Opening Play Solo places the character at (0,0,0). SpawnLocations are ignored.

Expected behavior: the character is placed on the ground below where the camera was when Play Solo was started.

Here is a video:

https://gfycat.com/QuarterlyGracefulFluke

4 Likes

I have the same issue here.

I thought the “Play here” option (to spawn at the Camera) started the solo session in the same window, not open a new one. What are you using to start this?

1 Like

Yep, I’m not experiencing any problems. As einsteinK mentioned, make sure you’re using Play Here and not Play.

I’m using Play Solo like I said. We went over this a few months ago when it was removed for a few days.

image

I’m pretty sure all non-“Play Here” Play options are supposed to spawn you at a SpawnLocation, or the origin if there is none, similar to how spawning works in a real server.

1 Like

Yeah, then this is intentional. Play Solo is not Play Here, and is not intended to spawn you at the camera. In RibbonBar, they are two separate modes – Play Here was not a replacement for Play Solo.

1 Like

It’s been a long time since I used it, but I also thought that play solo had always spawned you at the spawn points or 0,0,0?

It has. RibbonBar introduced a new mode which spawns you at your camera, and OP mistakenly thought that it replaced the old spawning behavior instead of being a separate mode.

I have used play solo continuously since 2007. It’s nothing new. For up to three years, I forget the exact date, Play Solo has spawned you into the world at the camera’s position. It’s not new.

I come back to ROBLOX after a month break and suddenly Play Solo does not place me where the camera is at, or where a spawn location is. It places me at the origin. It’s not useful behavior in any quantity.

@einsteinK @EchoReaper You can test this behavior yourself. Insert a brick at the origin, a spawn location, and place the camera in a third location. Press F6 to enter Play Solo mode. Then tell me this isn’t a bug.

The best educated guess I can make is that the camera location data is no longer being passed into Play Solo, and Play Solo’s fallback behavior is to place you at the origin instead of SpawnLocations.

For me, Play Solo has never spawned me at the camera. It either spawns me at a SpawnLocation if there is one, if not then the origin.

Play Here, however, spawns you at the camera’s position. Maybe it’s a hotkey change?

EDIT: Woah okay so pressing F5 instead of clicking the Play Solo button opens a new window for testing? That’s weird…
Ignore this, all I do to test is use Play Solo or Play Here. I haven’t really used the hotkeys.

F6 is by default linked to Play Solo, which doesn’t even have an icon:


But it’s indeed weird that F6 spawns you at the origin instead of a SpawnLocation. I don’t remember it ever spawning at the Camera, though. (assuming this is the old Play Solo before the Ribbonbar Play (Here), which is what seems to be the case)

I can assure you that the “old” play solo spawned you at the camera for a decently long period of time.

It’s definitely a bug that it strictly spawns you at the origin, but I don’t think it ever spawned you at the camera. Was that between now and early 2015? Because I used Play Solo from 2008-2015 and I don’t remember that at all (or any of the dozens of times I’ve accidentally hit F6 instead of F5 since then).

I have the same issue as @NWSpacek. It started 2 weeks ago on my end. I have always used F6 to open up a Play Solo session. I’m fine with spawning at a pre-placed one instead of the camera but this gets on my nerve now that I have to reset every damn time

https://gfycat.com/FemaleOnlyHochstettersfrog