Hello again. My studio recently updated. And this patch crashed, I no longer see that the studio is in Roblox Internal mode. I can apply the patch again, but is there a way to somehow automate this, so that it is applied immediately when updating to a new version, while preserving the changed FFlags / other features?
1 Like
Maybe head over into Task Scheduler and set it up everytime a program such as Roblox Studio runs? I would provide a tutorial to this but I’d rather not because you can tutorials like this on the internet if you look around. If you want a simpler approach, you can try the Roblox Studio Mod Manager.
1 Like
Hi, this thread was helpful for me since i dislike the new explorer. Roblox Internal has worked wonders so far, but im replying so i can say that it does sometimes disable itself upon loading roblox studio for the first time (you did mention this since its unstable, but it has only happened to me once out of over 50 opens so its rare) and another thing is some features dont work, such as setting weldconstraint welds. Havent noticed anything else yet, but i felt like saying this for anyone wondering! Thanks for the internal!
EDIT: Its not only weldconstraint stuff, its anything where you have to set a part into another parts properties. Stuff like setting primaryparts or welds. This can be counteracted if you know how to set it via CMDbar, but otherwise you can also reset the flags, but its a longer way…
1 Like
You have to have both set to false for it to appear. This happens since having KillOldExplorer set to true, and new explorer as false leaves no explorer available for the option to work. Its intended i assume
1 Like
No problem, also sorry you’re seeing errors with this version of Studio! I did notice it was a little buggy for me as well (randomly logs me out) and stuff. Probably something to do with tricking Studio into thinking you have an @roblox.com email to your account, which I guess would make sense. Just not sure about why the weldconstraint things and such is causing problems. Maybe it’s something with the old explorer? Roblox might have broke some things with it when releasing the new one.
1 Like
It doesn’t work and when I try to open the file it closes ?
1 Like
I did get randomly logged out of studio aswell but it instantly reopened the file. And even if the bug is with the old explorer, they wont probably fix it since it wont be used anymore. Also, its not your fault, no need to say sorry.
2 Likes
It might not be finding studio if it closes. Try running it directly from windows cmd, powershell, or the windows terminal. See the error you get there. If it does happen to be an issue with studio not being found, you can try reinstalling studio, or restarting your device. Reinstalling did work for me.
1 Like
i think you need to also disable lua explorer packages and you cannot still set the part into another part’s properties in the explorer but you can do that by clicking on the part in the workspace
(edit: you dont need to disable lua explorer packages as it works without it being disabled)
video:
image:
1 Like
Oh how neat! That actually works, thanks i appreciate it alot. This does fix all the weldconstraint and primarypart problems, but if i were to set Viewportframe’s camera to something, i would still need to use the CMDbar. Thanks again!
1 Like
How should I do it in windows cmd, powershell, or terminal?
1 Like
Just open up CMD, head into the folder where the exe’s inside (by using cd and then the path to where the exe is), then put the exe’s full file name with .exe at the end, and see what that outputs. Or you can try dragging in the exe to the CMD prompt. If that doesn’t work, try the other method, or reinstall studio, and/or restart your computer if you get a “cannot find specified file” error.
Thanks for pointing this out! I updated the guide once more for anyone who was still using it.
1 Like
Is there a fix yet for being unable to assign properties such as Primary Parts via the Object Picker through the Explorer? Setting the LuaExplorerPackages to false doesn’t seem to fix the issue.
1 Like
Yes, sadly, it is forced on everyone.
1 Like