Roblox studio bad allocation10/25/2023 ![]() ![]() ![]() Mid-end computers can use a graphics level between 4 and 7, unless the game has many graphic intensive details. ![]() For low-end computers, a graphics level between 1 and 3 is recommended. In order to run games smoothly, computers with enough power can handle between 8 and 10, but they most likely require an external graphics processing unit, rather than internal graphics. ![]() If settings are a 10-level adjustable bar for the looks (and performance) of Roblox. Origin = Origin * CFrame.new(movedirection *1000,0,0) If math.fmod(timesthrough,15) = 0 and timesthrough ~= 0 then P.BrickColor = BrickColor.new("Cool yellow") Local p = Instance.new("Part",workspace.OceanFloors) Workspace.RegionParts:SetPrimaryPartCFrame(Origin) The error will also occur if you try to run any other code through the command bar after the initial error is returned. However, soon following the error messages studio will drop in frame rate dramatically and then proceed to promptly crash.ĮDIT: The reason this script is wrapped in a pcall function was an attempt to thwart the, at the time, unknown error, this still caused the bad allocation error to occur but without specificity to where the error was being returned from, the error is normally reported at the first line of the while loop. It seems to be client change based as other people in the team create were seemingly unaffected and were only able to see bits and pieces of the changes I made. For instance, I’m generating terrain with the following script, which works fine up until I generate a certain amount (unknown), similar to how Lito was trying to add a large map to the workspace. I’d like to mention as well, that it does not appear to be the script itself, this error generally occurs when the client makes a change to studio over a certain load. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |