#how could i delete the loading thing
1 messages · Page 1 of 1 (latest)
That -1000 Y teleport usually happens when Roblox gets a bad physics correction because your client is driving movement without stable network ownership or a proper attachment setup, so the server “snaps” your character to a fallback position; it can also occur if your boost is being applied before the HumanoidRootPart is fully ready or if your velocity/LinearVelocity is using a broken or unanchored attachment, so the fix is to ensure the character is fully loaded, confirm HumanoidRootPart exists, set network ownership to the player before applying any forces, and make sure your boost direction is a clean normalized Vector3 with no Y corruption while avoiding mixing instant teleports with physics-based movement in the same frame.
alr
... maybe refrain from using chatgpt to answer people's help threads, ya?
this is most likely happening because you are teleporting the player outside of their streaming radius, which causes roblox to pause and wait for that area to stream in. i suggest looking into this for your teleport. you have a great animation already where you can hide this and give time for the replication to happen https://create.roblox.com/docs/reference/engine/classes/Player#AddReplicationFocus
https://create.roblox.com/docs/reference/engine/classes/Player#RemoveReplicationFocus
I fixed it, is there any way i can nullify all light for a cleaner transition(i use globalshadows being set to false but i have pointlights)
you can disable CastShadow on individual parts and meshes
but aside from that you can't really "nullify all light" short of doing it the hard way - referencing all nearby lights and .enabled=false on them (on the client)
but if turning off globalshadows does what you want, i suspect disabling castshadow is potentially a more desirable solution for you
Ik but is there any lagfree way to disable lightsources cuz my map is huge and it will lag if i do GetAllDescendants
you should almost never use getdescendants, or if you do, it is very carefully planned so it doesn't iterate too much
instead, consider using collectionservice which is streaming safe
Ok
instances that are streamed out will be removed from collectionservice and have the instanceremoved event called, so say the docs
so if you tag all lights, collectionservice will always only give you lights that are streamed in (careful to consider you're not also turning off lights in the area about to be streamed in)
collectionservice also gives you stuff outside of workspace so be mindful of that for templates; instance:isdescendantof(workspace) can be a quick check for that
or just .. don't give anything outside of workspace that tag
Alr
Imma research a bit tho
Do i have to make the tagging in a script or can i do it in studio
can do both