It’s displaying this message on the output everytime I press play on studio.
I’m not sure what it means and I tried searching for answers, but didn’t find any.
Sorry, I don’t know what more to say. I’m really not familiar with this message and don’t know what it’s talking about.
Just noticed that there are different messages later on.
You should provide Studio logs as mentioned in How to post a Bug Report
It’s really long, do I just post the entire thing in text?
Hi! Please don’t post your logs publicly as they might contain sensitive information. Instead, message this group if you feel they’d be helpful: Logs / crash dumps / other bug files - Developer Forum | Roblox
In this case, reproduction steps to cause the error to occur would be the most useful if it’s possible for you to pinpoint, as mentioned in the link from @QuackBack
Thank you. I’ll try to pinpoint it.
I could not find much information, expect for the fact that it might have to do with the module posted here: New Problem With Room Generation Code
It does seem to uncanchor a bunch of RoomPlacements and there’s not much else I noticed and I don’t know if I can pinpoint exactly what is causing that.
But if it is necessary, I’ll just change the code one by one to see if I can find what part of it causes the bug.
Or it could be a problem with this camera local script right here: local Players = game:GetService(“Players”)
local Workspace = game:GetService(“Workspace”)
local RunService = game:GetService(“RunService”)
local CurrentCamera = Workspace.CurrentCamera
Players.LocalPlayer.CharacterAdded:Wait()
local Character = Players.LocalPlayer.Character
RunService.RenderStepped:Connect(function()
CurrentCamera.CameraType = Enum.CameraType.Scriptable
CurrentCamera.CFrame = Workspace:WaitForChild("CameraPosition").CFrame
local OriginalPartPosition = Workspace:FindFirstChild("CameraPosition").CFrame
Workspace:FindFirstChild("CameraPosition").Position = Character.Head.Position+Vector3.new(0, 35, -25)
end)
You can provide the place file if it only occurs in that place upon starting a playtest
The bug is not happening anymore, probably had to do with the module I was messing with. But I could be wrong.
Are you using WaitForChild(“ModuleName”)?