It have to be on the ātrueā value if not it will be counted to memory limit.
By the way why are you messing with those removing faces? You can only create 4 vertcs and 2 triangles thatās it.
Iām creating a rectangular prism mesh. I figured if BaseEditableMesh is that, then when I generate wall segments, I can remove hidden faces. Cause Iām trying to make a wall segment system. I need multiple meshes and I need to hide end faces if thereās a segment next to it, as thatās hidden faces/thus not needed.
If I remove FixedSize, it āworksā but only on the first placement. If I try placing again it errors. So I need to create a new EditableMesh each time anyway. And with the example here, all these segments have end faces, which I donāt want. Theyāre hidden from the users, thus I donāt want them existing, as itās useless drawcalls
And also, this doesnāt allow the mesh to be resized either. It needs to vertsatile, I need EditableMesh sizes to change, faces to be changed/removed/added on a whim
Then create editable only when player highlight the part and then load information about the part to this editable if it has faces or not then if you finish editing again write into the static.
Or if you are using only cubic parts it would be easier to just import six parts with removed faces.
The end goal is to have curved walls, thatās why I avoided parts.
This is basically what I was doing originally at the very beginning 
Thatās why I saying if EditableMeshes are to be reliable and useable in actual games, these changes need to be made, otherwise they just become a parlour trick, no real world use case
Donāt give up.
Even with walls they should be static because as you claimed you want remove invisible walls but also static meshes needs less resources. So it is better to make those editables only with highlighted walls.
And I belive logic of walls is much more diofficult to create because u have to know wchich wall stick to neighbour wall. Exchanging editables to static should be easiest point of this.
Iām not quite sure what you mean by static meshes? As in they never change (created and thatās it?)
Isnāt the point of EM is to be āEditableā?
I canāt use base meshes, cause faces need to adjust. When walls meet at corners, their faces need to be resized/etc
Looks like Roblxo expected people will use editables for oceans which are needs thousands of triangles not for small parts.
Also word of note, this is perfectly fine on the serverā¦ I can generate hundreds of these meshes, no issues. But the second I move it to client itās memory lockedā¦
There is currently no point in running it on server as it doesnāt replicate that to clients, and since you can only edit meshes owned by you, and the fact that you can only run this on the client as of current, makes it completely pointlessā¦
Like, since it has to be on client, I need the client to edit the mesh owned by my group, and then since the player doesnāt have permissions, they canāt edit it, what is the point of it then?
Edit: Ok stuff owned by group CAN be edited on the client by a person not inside the group, but my point still stands when its a player owned meshā¦
I wish we could just get something that can only run on client and doesnāt have to use ASYNC to use, itās so slow and if I am being honest, this filtering is pointless, as itās really limiting proper developers who wants to utilize this tool, meanwhile people who wants to use this with bad intentions, can literally do it without this feature with just partsā¦ I donāt get the point of why even just messing around with triangles has to be so limiting.
I wish we could just get two separate things, a normal mesh editing system without all the saving and filters. Keep the āfiltersā to the āsavingā part of this API, most of everyone isnāt going to try to save edited meshes anyways and just wants to either create their own shapes or do deformation to meshes.
2 Likes