Greedy Mesh Module Release

[gianfragolo]

Greedy Mesh module

GreedyMesh - Roblox

Today i decided to open-source of this Greedy Mesh module; a powerful resource that allows to improve performance by reducing the part count with a bit of math. This is mainly used for procedural generation, because in this process a lot of unnecessary parts are created resulting in frame drops and overall lag. However this can be used in others scenarios.

Instruction

1 : Insert the module in “Replicated Storage”.
2 : Add a script in “ServerScriptService” and type:

module.new(targetFolder, outputFolderName)

targetFolder = The folder that you want to greedy mesh: can also be a model i guess.
outputFolderName = Optional, the name of the folder the result of the greedy mesh will be parented to.

Thats it, lemme know if there’s any bugs!

A special thanks to @Elttob and Haloblox2000

[Katrist]

I believe you forgot to replace workspace[“3D Done”] and workspace.Planet.

I could be wrong, but just letting you know.

You should also be setting .Parent last for extra performance:

PSA: Don't use Instance.new() with parent argument

I’ve discovered a pretty bad performance issue in one of top games that has to do with Instance.new and wanted to write about this, since this is not obvious unless you know the system inside out. Tthere are several ways to create a ROBLOX object in Lua: local obj = Instance.new(‘type’); fill obj fields local obj = Instance.new(‘type’, parent); fill obj fields local obj = util.Create(‘type’, { field1 = value1, … }) If you care at all about performance, please only use the first option - I wi…

Good resource though, after you fix some of these bugs I’ll try it out.

[gianfragolo]

Ohh i feel so dumb forgetting about this, thank you so much! Ill make sure that its fixed!

here’s the updated version.

Greedy Mesh V0.1 - Roblox

[Pichercacher]

In what way can this improve the part count of a game? How does it exactly work?

[ZerroxShiot (Zerrox)]

Greedy Meshing Algorithm - Roblox Scripting Tutorial

[gianfragolo]

Didn’t now about this… my module is pretty useless then…

[gianfragolo]

By substituting a lots of small parts at the same height, for example, with only one big part

[Pichercacher]

Ohhh I see… That’s a very clever way of optimizing!

[Magus_ArtStudios]

That algorithm is a very good optimization for removing unnessary polygons!

[Katrist]

I believe you forgot about this too:

[gianfragolo]

Thanks for the feedback ill update the module right now!

[gianfragolo]

Everyone thanks for the feedbacks! I fixed every major bug. Now the module is fully working. Also if the color of parts is random, don’t worry: go to the line 157 and change v.BrickColor to any color you want.