Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/696480e2-8c90-8013-9d6f-6ccbd15d2db6
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Assistant: Yeah โ thatโs actually very likely the issue ๐ === Yeah โ thatโs actually very likely the issue ๐ Reflection problems almost always come from the blocks themselves, not the projectile or logic youโre testing. Here are the most common ways blocks cause reflection bugs, so you can check which one matches what youโre seeing: ===== If your reflect math uses the surface normal: ===== * Blocky / axis-aligned parts can give perfect 90ยฐ normals * Edges and corners can return unexpected normals * Some engines return (0,0,0) briefly on edge hits ๐ Symptom: * Projectile reflects at weird angles * Sometimes reflects straight back or sideways Fix ideas * Clamp or snap normals to axis directions * Ignore collisions where normal magnitude โ 0 * Add a small bias away from the surface before reflecting ===== If the projectile: ===== * Hits two faces at once * Or reflects and immediately re-collides ๐ Symptom: * Infinite bouncing * Projectile sticks to the wall * Direction flips repeatedly Fix ideas * Cooldown between reflections (even 1โ2 frames) * Move projectile slightly along reflected direction after impact * Disable collision for a split second after reflect ===== In Roblox especially: ===== * Union / Mesh / Scaled parts may have collision that doesnโt match visuals * Some parts are still treated as axis-aligned boxes ๐ Symptom: * Reflects before touching * Reflects off โairโ * Wrong angles on slanted-looking blocks Fix ideas * Enable CollisionFidelity = PreciseConvexDecomposition * Test with simple Parts first * Avoid scaled parts for reflection tests ===== If reflection is based on velocity directly: ===== * High speeds exaggerate errors * Floating-point drift builds up ๐ Symptom: * Reflections get worse over time * Angle slowly โdecaysโ Fix ideas * Normalize direction before reflect * Reapply speed after reflection ===== If the block has logic like: ===== * Touch events * Damage triggers * Force application ๐ Symptom: * Reflection logic fires twice * Direction changes inconsistently Fix ideas * Centralize reflect logic in ONE place * Ensure only projectile handles reflection ===== Try this: ===== # Replace all reflective blocks with plain default Parts # Axis-aligned, no scaling # Test reflection If it suddenly works โ 100% the blocks were the issue If you want, tell me: * Roblox or another engine? * Are these Parts, MeshParts, or Unions? * Raycast-based reflection or Touch events? I can pinpoint it fast once I know that.
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)