As an aside, ROBLOX forcibly shut down my studio sessions when I tried opening a new one, so it could apply the update. I try not to assume the worst, but dang it sure did feel like ROBLOX was coming down with Thor’s hammer for this.
Yeah that happens with every studio update. I know the pain. Every Tuesday I lose all my windows. >_<
Really? Maybe I’ve just not had multiple studio sessions open the past few Tuesdays.
Retracted old post. I was using an older instance of studio. When I restarted I got the latest flags, which contain this: "FFlagStudioDisablePlaySoloAction": "True"
It seems to be an intentional change. I don’t personally see a need for two partially-flawed features that do the same thing, so I’m all for play solo being removed, so long as it’s truly obsolete. Would be nice if the in-window play solo gracefully handled crashing so you wouldn’t lose your work. As for the saving, play solo is for testing – not development.
If you’re developing in play solo or using build tools, yes I know old habits die hard, but you need to get rid of them eventually. The only value of those two is not having to learn anything new, but with development you’re always having to learn something new anyway. I used to use build mode, but find that freecam development – for both building and programming – is superior to doing the same with a character. Don’t fight change just because it’s change.
This ain’t no useless Build Mode on the site. This is F6 play solo, a mix of F5 test and F7 start server/player. For instanced testing with your own character. Pls giv back
(Agree with your other points btw, but thought this might be useful for anyone who didn’t notice it! )
Snake seems to be using SystemMenu, and in SystemMenu you have the choice of Start Server/Player, which deposits you at the spawn locations, or the (hidden) in-window Play Solo which deposits you at the spawn locations. Unmentioned of course is Play Solo, which deposits you at the camera location, but it’s been removed.
I’m not using system menu you could still use play solo with F6 and the quick access bar with the ribbon bar.
Wait what
As a ROBLOX developer, it used to be quite easy to develop and bug test at the same time. Here are a list of useful features that Play Solo gave developers:
- You don’t risk losing anything in your studio window because it’s a separate window
- It is possible to save everything created in Play Solo, not just script modifications
- Creates a backup in the form of Visit.rbxl
With the removal of out-of-window Play Solo, if you try to use build tools that aren’t plugins, you’re basically just up the creek.
Doesn’t it autosave when you launch Play Solo?
Oh, right – I forgot about that. Yes, it does. Because of this, you shouldn’t lose any work, but crashing just the test is more convenient than crashing your entire Studio instance, so there’s room for improvement with in-window.
I used it to keep my tests completely isolated from my working copy, which the non-new-window play solo option doesn’t do. Start server would certainly work for this purpose, but I’d have to load a massive place twice instead of just once. I’d appreciate this removal being reversed.
Why? ROBLOX isn’t going to revert the change without understanding why you need the old behavior.
Because of potential crashes and freezes. For example:
while true do
--some stuff but not a wait()
end
It’s not very difficult to forget a wait()
in a long loop.
Yes, you’ve made your needs clear. Not everyone’s are the same.
I was asking why in-window Play Solo was insuitable to warrant that in the first place. As in, why is there a need to “keep tests isolated from a working copy”?
When working on large maps or just loading the level in general you’re forced to wait for it to load when starting and stopping, but because play solo was in a separate window you could continue to work while it loaded.
Thank you for reporting this issue. We intentionally disabled this feature because it was causing problems with another feature. Based on your feedback, we will reenable this feature on Tuesday.
Thank you for listening and replying to our feedback!
Thank you!!!
I have a map I’m working on and the spawn is a fair distance away from the spot I’m working on.
Also, if you are working on an obby section, it’s much better to test and spawn at the camera rather than having to redo all the steps in your obby just to get to the spot you’re working on.