Why is everyone itterating ContentProvider:PreloadAsync({obj})

[Myukov (richardotr)]

What I do

local ww = workspace:GetDescendants()
ContentProvider:PreloadAsync(ww)

What everyone else does

local ww = workspace:GetDescenants()
for i = 1, #ww, 1 do
      ContentProvider:PreloadAsync({ww[i] })
      -- maybe ui bbar
end

you’re generating a new list just to load 1 object.

[RickAstll3y]

Both of them are unnecessary.

How to properly use ContentProvider:PreloadAsync()?

I don’t know why you think this. Async functions in Roblox purely mean that they can and likely always will cause a yield in your code, wrapping them in a pcall doesn’t make a difference afaik and afaik probably will (at least until recently) just slow down your code. Can you explain why wrapping Async functions in a pcall makes sense? Examples of async functions in Roblox: Instance:WaitForChild() Event:Wait() HttpService:RequestAsync() ContentProvider:PreloadAsync() Again, afaik these fun…

[12345koip]

The reason for that is so people can detect when individual assets have been loaded, especially useful in loading screens to display the amount of assets loaded.

[Myukov (richardotr)]

correct me if im wrong but it loads significant slower and… theres zero scenario when i want to know # of assets loaded. I just need a bool : loaded or not loaded

i will mark this as the solution but im not satisfied ;(

[12345koip]

Yes, it might load a little slower, but probably not too noticeable depending on memory usage at runtime.

Although you may not have a use for it, others such as me prefer to display the amount of assets loaded. I don’t think this system has any other use than that, though…

so for yours you would just preload the entire thing. Let me know if you have any further questions.

[RickAstll3y]

local n = 0
ContentProvider:PreloadAsync(ww, function(assetId, assetFetchStatus)
    n += 1
end)