>Manage memory using FixedSize
>Can only set FixedSized upon mesh creation, so it can only ever be empty
Thanks Roblox
2 Likes
I was even hoping that one would be able to use this on publicly available meshes. Would there eventually be an update to deal with stuff like that?
That is good to hear! Thank you for the information. Good luck.
My entire project has now been rendered redundant because of this stupid permission change, we are on the same boat.
I also think your suggestions are really solid; Disabling asset publishing for sampled assets sounds like something roblox’s PR could get behind (maybe, i mean it is roblox after all)
but yeah, R.I.P. pixel world 
9 Likes
Hey, I’m the Image Editor plugin guy
I remember addressing the issue with the permissions change and I’ve been told my use case would be considered. Is there any chance we can see that happening next update? ( [Studio Beta] Major updates to in-experience Mesh & Image APIs - #109 by FGmm_r2 )
If the permission check to turn images into EditableImages could be lifted even if only in studio it would make the plugin I’m working on way more powerful while causing no harm I believe
^ Now that :DrawImageTransformed is added I could fix the whole plugin, I only need the studio publishing feature to release
9 Likes
Yes, there are plans to allow that, but didn’t make it in time for the initial release. There are plans to be able to ‘bake’ an EditableMesh into one that doesn’t affect the budget, and to have a maximum budget instead of fixed or 20,000 faces.
4 Likes
We’re looking into ways to open this up in the future. We know it’s annoying, it’s a requirement we added reluctantly, and we want to make this less restrictive longer-term.
These APIs are still a huge bump in creative power. The performance at a given fidelity is definitely higher. If you don’t care about framerate at all or if you squint hard enough it is technically equivalent, but it definitely makes creating content at runtime easier and more efficient. That’s the whole point!
For now, it is hopefully a more minor hurdle for a well-meaning developer like yourself than it would be for someone intent on using these APIs to create egregiously policy violating content.
11 Likes
Any ETA for skinned or testing with it? Maybe Early or Mid-2025?
It’s not a minor hurdle. Giving away super personal information isn’t a minor hurdle. It’s less like a small detour, and more like trying to drive around a supermassive blackhole. You aren’t deterring bad actors with this, you’re deterring good actors. Bad actors will find a way around this limitation, just like they did for everything else.
Imagine coming over from a different engine and being told, “This feature you had? Sorry bud, you’ll have to cough up your ID. Don’t want bad things to be made! Oh, you don’t feel safe giving up information that is THAT personal? Bugger off then, come back when you’ve lost the common sense.”
8 Likes
its more-so that the malicious people create a freemodel that creates horrible things, and then little timmy unknowingly adds it to his game
this is a very paranoid way of thinking, i dont care if they have my information because they delete it off their databases within a few hours. and please dont be one of those “they never actually delete your information and they sell it on the black market!!!” people, i dont personally like roblox’s practices but if they didnt delete it that would be illegal since they are telling you they are deleting it. you would not be giving informed consent to give them your ID, which is illegal, VERY illegal on a mass scale.
basically, roblox would be shut down by now if they didnt, i mean, they lost to a child in court, you really think they can beat those allegations without proof they delete it?
also, common sense would be considering this information and then verifying your age with your ID, since you know they delete the raw data and only store your date of birth for age verification, simple.
you verify your age and you get access to features locked behind age requirements, yep, seems pretty fair to me.
I must say, the fact that all security options are completely unrestricted apart from this, which requires ID verification and requires you to be the group owner is very confusing, it is definitely not the most dangerous option and things just as bad could be made using normal parts
1 Like
It would be cool to be able to set the FixedSize property after creation, or destroy the editablemesh without deleting it’s linked meshparts, it would be very useful in some cases where you only need to generate once, and never touch the mesh again.
Great point there! Now give a reason this needs to be locked behind ID verification. (If you don’t want timmy getting the malicious models made of meshes then he better not insert one made of parts, either. Maybe lock studio into ID verification?)
4 Likes
Hey, there is a bug whilst creating flat planes, I’m not sure if this is intended or not, but when creating a mesh with the same Y for every vertex the mesh just doesn’t load.
A fix for this issue will be included with v654.
5 Likes
It uses Fast-fourier Transform. As for the normal maps, unfortunately EditableImages can’t apply those atm (to my knowledge).
SurfaceAppearance support was added in the last update
Why doesn’t eMesh:GetAdjacentVertices(vertid) work? It returns an empty table.
Also with eMesh:FindClosestVertex(Vector3) it returns vertid 0. Is this getting a fix in the next version, or are they no longer supported?
editable meshes are a lot more dangerous because, while toolbox models ARE moderated, editable meshes are not yet moderated.
theres your reason
1 Like