Don’t use unions to reduce part count! I’ve been building for around a year now and I’ve learnt a few things. When I started I used to union parts together thinking it would magically reduce the lag within the game, but it really doesn’t… There are many ways to reduce the lag within a game especially for high brick count, a good way is to counter this is by using teleports and having the other side of the tele far away from the general build, this reduces the render roblox has to do for running the game.
The post title seemed like a question, for your future posts here, you should title your posts that showcase what not to do, as the solution, “Don’t use unions to reduce part count”.
Using Unions to reduce parts with a question mark would imply it being a question, but I can see your confusion, me and a fellow dev made a city for Skilled Force the city on its on has over 100k parts the boarder has 10k and theres other parts you can go to using tp
Boarder isn’t connected to the city I suggested to Crushed that we publish the game with the boarder in a separate game and it teleports you to the main city game however we’re using a tp
Oh uh, didn’t know this… been using this technique since unions came out. I’m guessing its ok if I try to make a gun that is like 50 parts into a 2 part union gun. Welcome to the forums btw!
Although having buildings spread out across your place will reduce lag, it also causes some other undesired behaviour. As you head further and further away from the null point or origin (0, 0, 0) lots more rounding point errors occur and this can cause some weird effects with controls and rendering, other players can seem like they’re sinking into the ground.
This may not affect you hugely, but it’s always a good idea to build close to the origin. Instead of teleporting players, you could make something to spawn different areas in, this way the unused buildings won’t have to be rendered whatsoever.
Hey! I know about the render-trick but I am sometimes afraid I am putting the builds too far away than necessary.
How many studs should the builds be apart from each others?
For clarification @MarcusDeving and @VelbyDogg, moving things far from the origin is not recommended to help reduce lag as that has negative side effects (as General_Scripter says very well).
There are many other options you can use that do not harm UX. The best being to optimize your builds, removing redundancies and taking advantage of instancing with parts or meshes (preferably not Unions since they’re messy and have redundancies themselves).
You can’t just fill your place with over 100k objects and expect it to run on all platforms without some kind of loading system and serious optimizations.
Message me if you need more help with building best practices.
I don’t really have a set amount of studs you should separate the builds however do it until you feel its far enough, don’t separate them too much tho.
I still would not recommend using distance to solve your optimization problems. That’s hardly a band-aid solution to the much larger issue of an unoptimized game.
If you need help, DM me. I’m more than happy to guide you through best practices in optimization.
They shouldn’t be used to attempt to reduce lag period they’ll cause more lag than anything best way is to reduce part count or not using free models as some can be bugged
As far as I’m aware, the unions themselves take longer to load, but improve overall performance, that is until the player comes into contact with them, unions with CanCollide on cause more lag, the reason for this can be seen if you go into studio settings, and under physics, turn on ShowDecompositionGeometry and then change the CollisionFidelity, you can see the actual area the player can collide with; gives a little insight to when you unions 4 parts in a square and you can magically hit something invisible in the corner.
At least, this is what I’ve gathered using them, and asking people about them so far.
