Yep I def see the issue then. The reparenting of the workspace children happens outside the pcall so having a script in your general workspace would def trigger the issue and fail to fully reparent.
Great catch with this. Thanks for the report!
Edit: Just pushed a fix that will catch this error going forward so your workspace shouldn’t get nuked by it anymore
Hi!! Wanted to ask if there’s ever gonna be a possibility to use multiple/different images in the effects editing scene unless theres a way to do that already?
Currently there’s only the ability to only use the singular source image. You can have multiple layers of that same source, but if you’re looking to combine to separate images that functionality doesn’t exist atm.
The main reason for this is b/c under the hood when you load an image in the post processing widget it calculates what I internally refer to as a SVF (signed vector field). This is an expensive calculation and it’s what ultimately allows the ability to generate many of the effects quickly. This is why when you lose focus the app doesn’t update until you switch back - I don’t want to recalculate this if you’re just messing about in the explorer.
The challenge with adding multiple image layer support is that I’d have to calculate the SVF for each of them. This would increase the memory pressure and the load time.
Is there a specific case you’re trying to cover?
Oh I see! Yeah, I’d like to render an icon with a stroke being applied to solid parts only (excluding half-transparent stuff, such as particles). Thanks for responding, I’m guessing I just gotta use Photoshop or something like that
Yeah the cutoff is at 127.5 on the alpha channel (half transparent). Maybe in the future I can let the user set this, but it’s hard to convey. For now, I agree that using an external program for that level of granularity is probably easiest.
For some reason with auto capture on free mode I can no longer move around and customize the camera angle as I was able to before, I have restarted studio and my pc even idk if its just me…
Maybe something to do with the beta changes they’re making to studio camera navigation? Can you confirm if that beta is on or off? I wont be able to get to a pc to check until tomorrow.
That was the issue thank you! I guess I was forced into it somehow
I just pushed an update that should fix this going forward. Thanks for the report!
hey so every time I export the selection into an obj there is a chance that it just gets stuck in “Exporting Selection” and crashes studio
Yes this is a roblox bug with exporting objs. As far as I’m aware it has nothing to do with the plugin and can happen even if it’s not installed.
My suggestion is to use the gltf export / website. You can find more details on this in the OP under saving as a png.
Edit: found this post which says they’re working on a new obj export - so whenever that comes out the problem will likely no longer occur.
I just pushed an update that has a few minor fixes, but one new feature as well.
I added an icon grid view to the gallery. This should make it easier to see what image you’re selecting at a glance while in the gallery. Hopefully that eases some of the burden for users who don’t rename their captures.
How do I use this feature? I have CreateAssetAsync enabled and can’t find an option for this anywhere in the settings panel or in plugin list
Read the rest of the section:
You can find the link to the standalone in the OP
Thanks! Any chance in the future for this to be built into the plugin on the marketplace? behind the experimental flag or similar?
It actually is built into the plugin already. It just doesn’t show itself unless the beta is enabled and the plugin is installed locally (i.e. not via the creator store). If those conditions are met it shows up in the gallery:
This is due to the constraints Roblox has put on the feature as a result of it being in beta. If you read their beta announcement post you’ll see mention of this:
I agree this is frustrating b/c the protections they mention in the post haven’t made any progress. Their announcement was made at the end of 2024 and the “Next year” that’s mentioned in the above quote (2025) has come and passed.
For now the best I can offer is the standalone. I don’t know when the feature will move out of beta, but when it does the standalone will become redundant.
Would it be possible to add mouse wheel zoom while adjusting the Distance Scale camera in Auto Capture?
Also, could you add an Orbital Lock button in the Viewport? It would be useful to lock the orbit ?
Can you define what you mean by orbital lock? You want to lock the camera in place so that you can’t move it by accident?
That is because of the new studio camera controls beta.
You can already achieve your desired orbit behavior if you hover the ViewSelector and toggle to “focus mode”:
