wouldn’t this mean for every new descendant it loops through those 50k instances in workspace?
like 50000^50000??? This is INSANE??
Thats a lot… here’s how you could’ve done the script :
Tag all the conveyors, name the tag “Conveyors” or something then loop through that tag. No extra function is needed since it would add an extra rate(/s) I believe. Also, insitead of having a numbervalue on every conveyor part why don’t you set an attribute to it called “Speed”? This will make it less laggy as well. Here’s a script regarding everything I said :
local CollectionService = game:GetService("CollectionService")
for _, conveyor in pairs(CollectionService:GetTagged("Conveyor")) do
if conveyor:IsA("BasePart") and conveyor:GetAttribute("Speed") ~= nil then
conveyor.AssemblyLinearVelocity = (conveyor:GetAttribute("Speed") * conveyor.CFrame.LookVector)
end
end
Good idea! Will do
Ive joined one of my servers (had 1.1k playing yesterday and the datastore script was INSANE), kt had over 1k rate
Another friend also recommended collection service, I do not know how to tag parts tho. Could i also use this for all the kilbricks which are being handled by one for i,v in pairs(killbricks) if touched then kill player end end?
Also the 1k rate of the datastore script may be normal
2 ways you can add a tag with out using a script :
one way is to add a tag from properties of an instance
the other is to go to view section then click the icon “Tag” (Tag Editor)
Alright thanks! The “global datastore” which saves ALL the data of every player in the server has an average rate of 600. Is this fine?
I am not sure, Compare it to the other values, but it should be fine.
Don’t forget the new conveyors that might be added later.
CollectionService:GetInstanceAddedSignal("Conveyor"):Connect(function(conveyor)
local speed = conveyor:GetAttribute("Speed")
if conveyor:IsA("BasePart") and speed ~= nil then
conveyor.AssemblyLinearVelocity = speed * conveyor.CFrame.LookVector
end
end)
Have you looked at the microprofiler? And things like datastore usage won’t cause client lag.
The first thing I notice is that there is a lot of physics activity across all threads throughout a frame.
As a quick test, write a script that anchors everything in the game and see if performance improves. If it does, then you know that physics is your bottleneck.
Also another thing I noticed is that your ‘ViewportHandler’ script runs even when the shop is closed (if you’re on the crates tab), you can claw back some performance by fixing this.
Are you using any geometry queries like Raycasts, Blockcasts, Spherecasts, GetTouchingParts, GetPartsBoundsInBox, etc?
huuuuh??? I thought ive disabled this function whenever the viewport crates aren’t visible
thanks for the advice, what could I possibly do to fix all this?
You can start by checking if physics is the issue. Start a game and just anchor everything by doing the following in the command bar.
for _, Object in workspace:GetDescendants() do
if Object:IsA("BasePart") then
Object.Anchored = true
end
end
If performance improves then you know you’ll have to work on optimizing the physics.
alright. Where do I see the stuff you saw and where do I put this in without it being permanent. Im sure its a lot of physical activity because we have TONS TOOOONS of spinning platforms, moving platforms, falling platforms, particles and so on
This is the viewport handler:
for i, ViewportFrame in pairs(script.Parent:GetDescendants()) do
if ViewportFrame:IsA("ViewportFrame") and ViewportFrame:FindFirstChildWhichIsA("Model") then
local Model = ViewportFrame:FindFirstChildWhichIsA("Model")
Model.PrimaryPart.Anchored = true
Model:PivotTo(CFrame.new(Vector3.new(0,4,0)))
Model.Parent = ViewportFrame
local ViewportCamera = Instance.new("Camera")
ViewportCamera.Parent = ViewportFrame
ViewportFrame.CurrentCamera = ViewportCamera
ViewportCamera.CFrame = CFrame.lookAt(Vector3.new(0, 7, 4.8), Model.PrimaryPart.Position)
end
end
while task.wait() do
if script.Parent.Visible == true then
for i, Model in pairs(script.Parent:GetDescendants()) do
if Model.Parent:IsA("ViewportFrame") and Model:IsA("Model") then
Model:PivotTo(Model:GetPivot() * CFrame.Angles(0, math.rad(0.2), 0))
end
end
end
end
idk why this isn’t working 
People still complain about lag, ive implemented everything said. Still don’t know how to use micro profiler tho
If you have that many physical Constraints why not Tween some of them instead?
try using ContentProvider:PreloadAsync()
what this does is that it loads instances and asset ids and pauses the script until the loading is finished
you can use this in the loading screen, but i recommend adding a skip button when using it because it might take a while, especially on low internet
i dont want to sound like a broken record so sorry if this seems a bit annoying, but have you tried anchoring physics based parts that are far enough away from the player’s character? i think it should reduce the amount of lag at least a little since the solver shouldnt be doing much for those parts in particular, when the player gets close enough you could then unanchor them so they work properly again
Hi,
I tried that and it really didn’t produce any results. I followed the disabling a while loop when a certain frame is closed and that helped a lot. In the next update of the game I will enable content streaming, which will limit the render distance of the player. However, since I have a lot of local scripts that access the workspace (killbricks, spinners, cutscenes, checkpoints, etc.), I would have to use something like a “collectionservice” to tag the parts, because otherwise they wouldn’t exist for the local script and everything would break apart.
I’m not sure how to use a collection service yet, but I’ll look into it. Thanks for the advice tho, I appreciate every help!
oh, sorry to hear that
i hope you manage to fix the issue soon