I am very pleased that the plugin that I bought a long time ago is still being supported and even huge updates are being released! Thank you for your work!
1 Like
Just as an FYI thereās a bug that is breaking UI captures.
Itās not related to the most recent update. This is a change on Robloxās side.
Edit: I pushed a temporary fix for this, but Iād prefer to revert back to the old method if Roblox does fix the bug.
1 Like
please add rotating the selected models for auto capture
Not sure what you mean by this? You can already rotate both the model and the camera in auto capture mode. Can you elaborate more?
rotating the model didnt work for me maybe itās cause the selected instances were not parented to workspace. another suggestion i had also was to save angles/presets for future renders staying consistent
If you adjust the target before adding it to the queue it will retain its rotation. If you adjust the target while focusing on it in the queue it will retain and rotation / translation until you clear it from the queue. You can directly modify the camera instance to achieve a specific angle.
With these factors in mind you should be able get consistent renders.
2 Likes
Great work! Itād be really awesome if there were an option for creating simple camera presets. Just like the auto capture menu, but for configuring camera position, capture size, so on. This would let us make changes in the scene and return to the fixed preset to recapture.
2 Likes
can you able to make a character and a transparent background on this plugin or nah
Oh nice. It was giving me some error about stuff not being parented when I tried earlier but it works now. Thanks!
Hey all! I just published an update for photobooth. Most of the changes are small QoL type things - nothing major - except one thing!
I believe I may have finally cracked the code on supporting atmospheres. Iāve added a new experimental capture type (if you donāt know what experimental mode is read the OP) that you can use to try it out. Youāll note that experimental captures are not available in auto-capture mode.
From my testing itās been working as expected, but Iām hesitant to do a full release without more eyes on / testing. Please give it a go and if you find any issues let me know. If it is working properly also let me know!
Ultimately, this wonāt get merged into non-experimental until Iām more confident in it.
Happy capturing! 
6 Likes
hey EgoMoose i keep getting this error i cant even take pictures
OS Scale mismatch. You may need to go into photobooth settings and refresh the OS scale value. (x2)
You can read about os scale in the OP. Ultimately the issue is bc the os scale calculated at start doesnāt match your current. Super easy to refresh. Open the gallery, go to settings, hit the refresh button for os scale.
2 Likes
Just released another update! This introduced two nice things worth mentioning.
First, the plugin now supports the atmosphere instance! 
.
It takes a little longer to capture so if your scene has an atmosphere but itās not really impacting your subject I still recommend removing it. I also suggest increasing yield time between captures with capture delay when automating any captures with atmosphere in them. The lighting of your scene can take a second to adjust to all the atmosphere changes so itās best to give it some time to settle.
Secondly, Iāve greatly improved the UX for full screen captures. It was a bit of a pain to switch to actual resolution in high res emulated devices sice you often couldnāt even see the full screen. Iāve added a nice QoL change here so that if you initiate a capture not in actual resolution the plugin will automatically switch to it for you (and back). That means you can do all your work in fit to window and photobooth will work just fine!
I also refactored the OP since it was due for a bit of an update.
Happy capturing!
5 Likes
FINALLY!!! Iāve been waiting for this forever. It was so annoying not being able to just open Photo Booth and snap a picture. I always had to dig into Lighting and remove the Atmosphere first
1 Like
Hey! I really like this plugin and just tried using it for rendering some models.
However, Iām having issues with the OS Scaling.
I am on Windows using a 125% OS Scale, and I believe the plugin has detected it correctly (when going into Gallery ā Settings, OS Scale shows 1.25, 1.25).
I then try to capture an image with Capture Size set to 512, 512:
The issue is that after I capture the image, when I go into Gallery to see the image captured, it shows a resolution of 409x409 (512 is about 125% of 409) and the object hasnāt been rendered correctly:
I tried setting Capture Size to 640x640 so the final image was 512x512, but the object still wasnāt positioned correctly.
I should note that if I have the object positioned correctly and then capture the image using the Viewport, the render is perfect and exactly what Iām looking for. The issue seems to be with Auto Capture only.
Am I doing something wrong?
1 Like
You are doing everything correctly!
This was a regression from me changing how the auto capture and post processing tools are bundled. Should be all fixed now!
Apologies and thanks for the report!
1 Like
Thank you so much, everything works now! Loving the plugin so far 
1 Like
Hi, fantastic plugin, thanks for creating!
Big issue: I used the auto capture feature in my game and mid-capture it was ādenied script permissionsā when the prompt showed up. This resulted in my entire workspace being nuked & not restored after pressing āallowā on script permissions (seems like the plugin prematurely handled the prompt as an error, threw a āwarningā that permissions were denied when I was prompted for permission). Had to revert the version.
Please add a warning that this should be used in an empty place file or ensure the workspace is always restored properly (changehistoryservice?) or that this permissions error is handled properly.
Thanks!
1 Like
Iām so sorry about this! I will add a warning as a safety precaution.
I do run any of the āworkspace hidingā through a pcall and change history service, but obviously your case was not caught.
Iām not entirely sure how the script permissions prompt popped up mid-capture? That typically only happens when the user themselves prompts it or if the plugin is trying to insert scripts into your game. The plugin only ever tries to add a script to your game when you enable the binding feature. So assuming you didnāt do that, Iām not sure what wouldāve triggered this prompt? Did the models you were capturing contain scripts? Maybe cloning / reparenting your target model with scripts triggered the prompt?
I need to be able to reproduce this to fix it. The prompt is done externally from the plugin so it may be firing off the error outside of the pcall scope I have built to catch this kind of thing.
Edit: I can confirm this is caused by your capture targets having scripts in them!
1 Like
Appreciate it, no worries! In my case, I had a script in workspace so it prompted when attempting to restore the workspace, halting the restore. Looks like this happens both with scripts in workspace & scripts in the target model
1 Like