Instance.new() lag causing problem

[MightyYaso]

Hey, i would like to optimise my game and then i found this thread

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…

Does this also count for when creating decals, meshes, sounds and welds ? ?
thats what i mostly use with instance.new()

i wasnt able to find it in the orginal post only abou the valuves that someone tried it with intvalue and string and seems like there wasnt issues however what about decals and meshes

[MightyYaso]

also animations i forgot to ask animations too

[JarodOfOrbiter]

It’s everything and not too hard to fix. It should only effect you though if you create tons of new instances really quickly such as in a loop.

[VegetationBush (FartedWayTooHard)]

Anything in the explorer window is an instance (anything you can insert with the Instance.new function is an instance). Instances are just “objects”.

[jonbyte (Jon)]

Partially unrelated but there are some objects that are not Instances, like RBXScriptSignals.

[MightyYaso]

i mean i have a gun script and if you shoot a player really often it creates everytime decals using instance.new() to make blood patterns on the player

[FastKnight401]

Generally, it’s best to set all the properties before setting the Parent.

[MightyYaso]

ok i just done that, these old script are horrible

[legs_v (legs)]

Just don’t use the second arguement for Instance.new?

@MightyYaso

it creates everytime decals using instance.new() to make blood patterns

Just store it somewhere and then use :Clone()

[MightyYaso]

wait tahts it ?, Just not use the second argument on instance.new ?

[LocalWE (WilliApple)]

Yes, it is for everything. If you wanted to add a Part, do this instead:

local Part = Instance.new("Part")
Part.Parent = workspace

[jonbyte (Jon)]

I am pretty sure it’s fine to use the second argument IF you aren’t modifying any properties.

[FastKnight401]

That’s 1 case. Another case where you can use the second argument is when you are parenting it to part which either itself doesn’t have a parent or the has an ancestor that doesn’t have a parent (other than game), this is because you will still just be changing bytes inside the memory.

[TheBaconHero_101 (TheBaconHero)]

that post is from 2016 im pretty sure they fixed that

[MightyYaso]

i hope so.

Long storys short meaning ive removed the second argument if there was one and then set it last to parent and also if a CFrame wasnt determined i used CFrame.new() and if a size wasnt determined i also did Vector3.new()