Odd. I’ve literally never experienced this bug. I’ll start using the headlight when I open studio to see if it replicates.
Do any errors appear at all?
Nope, no errors. It’s very odd, and I get that it’s a hard thing to fix.
Here’s a quick video showcasing my most common issue, which is where the part just doesn’t update to the camera position. It can start broken when I launch studio, but it can also break midway through.
1 Like
Thanks for the footage. Very odd. I’ll look into it when I get the chance.
Appreciate the report and I’ll let you know when I have a cause or a fix.
This is insane, specifically selection features and quick pivot. Even the minor details like auto wedge and headlamp are just cool things to have linked under the same plugin. It’s a shame some of these features aren’t already integrated into studio, I might have to buy this… 
2 Likes
Thanks for the feedback!
You definitely won’t regret buying it if you do. I’m always using it myself.
Sorry for the long wait. Finally looked into the issue and couldn’t really find anything wrong.
I did notice that to get the camera I do this
local camera = game.Workspace:FindFirstChildOfClass("Camera")
It could be possible that this returns nil upon first booting up studio so I added a repeat loop that constantly sets the variable until its no longer nil just as a fail safe. (Make sure to update the plugin to see this change. Lmk if the issue persists still if you can.)
However its worth noting that if this were the case there would probably be errors showing. Could it be possible that you have multiple camera instances parented to the workspace? Thats the only other alternative I can think of.
1 Like
Nahh I don’t. Pretty sure it’s a race condition caused by the camera instance not being loaded at the time the plugin runs. It nearly always works the second time I load my place for the day, probably because things are cached in memory and load faster.
I’ll let you know.
3 Likes
Aight, so that didn’t fix it for me. I went ahead and switched the logic for getting the camera to use the workspace property for current camera instead.
local camera = workspace.CurrentCamera
And in the script that activates the headlight I set the camera variable again just in case current camera has changed. That’s worked so far with my local plugin version of your plugin.
This is all rather confusing, but I believe that Roblox must be setting the CurrentCamera property sometime during the place loading, which deletes all previous camera instances. And sometimes, your plugin loads in before this happens, meaning you’ve got a reference to the previous camera.
I tested that and it doesn’t result in any errors because you still have a reference to the old camera instance, it’s just parented to nil and not in use.
2 Likes
5/10 plugins that you provided here, can be bought for free. So I don’t think its worth.
You would probably have made more selling each as their own product with good UI.
But keep up the good work.
3 Likes
Ahh this makes a lot of sense. I really appreciate you going out of your way to find a solution yourself. I will apply this solution later today. Thanks!
I’ll possibly have an event that checks when the camera is no longer parented to workspace then reset the variable whenever that happens.
3 Likes
New update 7/28/2024
Fixed issues where headlight and prop placing would break.
Big credit to @thebigkannye for finding the solution to this bug!
3 Likes
Hey thanks for reporting this issue I just fixed it.
I literally didn’t touch the plugin whatsoever so I find it super odd that it randomly flicked off sale.
Thanks for the report this is super weird. I’ll look into this.
1 Like
It appears to be back up now. I’m assuming there may have been a period where it had to go under review after being put on sale again. Again, thanks for reporting that to me.
1 Like
Maybe All developers is a bit of a stretch. As a programmer this is not something that directly appeals to me since it has a lot of Building/Modelling features.
In addition to this, people should not have to pay for updates of your service and Ideally, they should pay one price that includes future updates. Since future buyers may feel ripped off knowing that previous buyers have the same features although paying a lower price.
Also the price is quite high considering the following factors:
- The Toolbox does a lot of these features
- F3X is another popular Building tool that is Free.
I also really do not like the UI design. For the price it is, it seems very childish and not something people may see themselves using professionally (I.E. on front page games)
1 Like
I agree. I feel that it would feel more professional if the UI was more appealing and I feel like nothing here is really new to justify the nearly $20 price point.
1 Like
It’s not meant to be taken literal it’s more of a catchy title than anything. Obviously there will be devs that dont find use out of any of this plugins features.
I think its fair that if you bought the plugin while it lacked features you get some sort of reward for being in early. It’s also worth noting I’m not just gonna increase the price with every single update (and I haven’t) there would have to be an abundance of new content added before doing so. As it is right now I don’t have any plans to increase the price anytime soon.
This is false. But I am also not sure what ‘toolbox’ implies. Are you just referring to free models?
I personally haven’t used f3x but I do believe the features yoolurs builder offers and the features f3x offers have no overlap. F3X offers a completely different set of tools from what I’ve seen.
Admittedly I’ve probably lost out on tons of sales because of this lol. I have removed the images at the top a while ago but they are still present in the showcase. I initially didn’t take the plugin serious because I had only made it for personal use with no intentions to sell it. Once I did decide that I may as well list it for sale if I’m making it anyways I didn’t expect it to have much demand like it does now.
Regardless, front page game or not, it’s not like the players are going to see it. I do understand that UI like that can deter potential buyers though. If I ever decide to make a v3 I will definitely take into consideration the UI.
Thanks for the feedback! (you as well @Geolio9)
3 Likes
Respectfully this is a very, very surface level look into what this plugin has to offer
This does not match f3x and is infinitely more flexible than anything you get in toolbox
I’m not here to say the price is worth it (Competitively? I have no idea, subjectively? Fine to me) but that your factors don’t suggest the price is overwhelming.
'm exactly the genre of builder this plugin appeals to so thank you for this!
2 Likes