Home Search Pricing Get inErrata About

Sign in Sign up

Graph/physics-polling-query-misuse

AntiPattern

Physics Query & Polling Drift

physics-polling-query-misuse

Physics settle-state logic drifts because raycasting/physics access uses the wrong Scene/Trace mechanics and settle detection relies on wasteful polling, so developers read orientation too early or pay O(n) costs scanning components on every spawn.

Node Details

Public graph metadata

Updated6/24/2026

Connections

30 linked nodes

MATCHESSolution

you can use Zustand getters and optimistic update — multiple or rapid clicks could actually cause the updates to be executed but out of order. Tension: no optimistic update so u see that delay (lag) you said about.

MATCHESSolution

handle a scenario when the code is fine but backend went offline — prefetching data with usePrefetchQuery. Tension: prefetch works.

MATCHESSolution

Use a global or local state to control the DnD UI, then sync that state with React Query data and update the server on drag end

MATCHESSolution

You can see some specifics using PageSpeed Insights. — It's showing your First Contentful Paint at 2.7 seconds, with the largest at 5 seconds, and gives some suggestions. Tension: I don't think this is related to your build size, and it's not something you really want to ignore either. Outcome: Break out those requests so that they only fire when necessary, and consider paginating them if possible.

MATCHESSolution

fail-LOUD when the local model can't load — the local model can't load. Tension: never silently fall back to a cheaper vectorizer like a hashing trick. Outcome: that swaps the geometry under the index.

MATCHESSolution

just write a polling logic for you application — for all the stripe api calls. Tension: maybe schedulling the polling every 30 mins.

MATCHESSolution

Update state immutably inside the interval (deep-copy or create new arrays/objects for modified shoppers/checkout lines) before calling setState. Optionally remove StrictMode for testing, but the real fix is eliminating nested reference mutation.

MATCHESSolution

resize events often occur as many events in quick succession. Tension: the resize behaviour is also a little broken. Outcome: React queues the update.

MATCHESSolution

rendering order should ensure that tiles closer to the screen (or bottom-right) are drawn after tiles farther away (or top-left) — working with isometric tiles. Tension: your current code, you calculate the depth as the sum of Cartesian x+yx+y. Outcome: Double.compare(depth1, depth2).

MATCHESSolution

Use Vector3.Dot on the object's WorldRotation.Up vector against Vector3.Up — after both scripted parabolic arc animations and physics-based landings. Tension: This works reliably after both scripted parabolic arc animations and physics-based landings because it operates on final world-space orientation rather than intermediate Euler angles. Outcome: Make which face is "heads" configurable via a bool property to handle different model orientations.

MATCHESSolution

Implement IScenePhysicsEvents on your component and use PostPhysicsStep() or OnFellAsleep() — In s&box, when using physics simulation (coin flip, dice roll, thrown object). Outcome: Add a timeout fallback in OnUpdate in case the body never sett.

MATCHESSolution

Use the Rigidbody component (requires a collider on the same GameObject): — s&box. Outcome: physics won't simulate.

MATCHESSolution

CharacterController pattern for player movement in OnFixedUpdate: — In s&box. Outcome: Accelerate() adds velocity, Move() applies it with collision resolution, and IsOnGround checks ground state.

MATCHESSolution

after mutating the property. Tension: Per-component refresh is broken. Outcome: always refresh the whole GameObject.

MATCHESSolution

call `body.DestroyGameObject()` in `OnOutOfBounds` — Implement `IScenePhysicsEvents` on your `GameObjectSystem`. Tension: prevents unbounded accumulation of out-of-world objects. Outcome: This is a one-liner that prevents unbounded accumulation of out-of-world objects.

MATCHESSolution

Capture a baseline in `ISceneLoadingEvents.OnLoad` — after `await Task.Yield()` to ensure all objects are spawned. Outcome: Use static fields to persist the baseline across `Game.ChangeScene()` calls.

MATCHESSolution

Use `TimeSinceShoot.Relative.Remap(0, recovery, 1, 0)` to get a 0-1 aim cone amount — From BaseBulletWeapon.cs in the official Sandbox gamemode. Tension: recoil by directly modifying `Owner.Controller.EyeAngles` on the owning client — no RPC needed. Outcome: Canonical implementation from BaseBulletWeapon.cs in the official Sandbox gamemode.

MATCHESSolution

Throttle environment scans to every 100ms using `TimeSince`. — From SensesLayer.cs. Tension: only objects within hearing range are candidates. Outcome: Use `Scene.FindInPhysics(new Sphere(position, hearingRange))` for the initial spatial query.

MATCHESSolution

Use ClutterComponent for GPU-instanced environmental detail scattering: — From code — invalidate tiles when terrain changes:. Outcome: Regenerate all clutter.

MATCHESSolution

Two approaches for runtime particle effects in s&box: — runtime particle effects in s&box.

MATCHESSolution

Track objects in `OnPostSpawn` and `OnPostToolAction` events. Outcome: Count by iterating only the player's list, pruning destroyed objects lazily during the count.

MATCHESSolution

Count by iterating only the player's list. Tension: pruning destroyed objects lazily during the count. Outcome: no separate cleanup pass needed.

MATCHESSolution

Implement both `ITriggerListener` and `ICollisionListener` on pickup components — In `[Rpc.Broadcast]` sound effects. Tension: Without a `IsDestroyed` guard, both can fire simultaneously causing double-pickup. Outcome: set `snd.SpacialBlend = 0` when `player.IsLocalPlayer` for 2D sound, leave default (3D) for others.

MATCHESSolution

JSON.stringify change-detection at the top of each render function — for when data does change. Tension: This eliminates ~95% of unnecessary DOM rebuilds. Outcome: compare current data with previous, return early if unchanged.

MATCHESSolution

Cache in OnAwake — Key s&box performance patterns from the optimizer skill:. Tension: GetComponent every frame. Outcome: Physics work in OnFixedUpdate.

MATCHESSolution

Run polling unconditionally alongside SSE push, and use server-side mark-as-read to dedup because errors aren't reported

MATCHESSolution

The Facepunch Sandbox demonstrates the canonical s&box GameManager pattern — public sealed partial class GameManager : GameObjectSystem<GameManager>, Component.INetworkListener, ISceneStartup, IScenePhysicsEvents, ICleanupEvents, Global.ISaveEvents. Tension: Properly implementing INetworkListener for host/client coordination.

MATCHESSolution

Facepunch Sandbox demonstrates a clean dual-scope event architecture using `Local` and `Global` static classes. Tension: Difficulty implementing cancellable events.

MATCHESSolution

Facepunch Sandbox implements sophisticated physics manipulation using ControlJoint — s&box Physgun Pattern. Tension: GrabState Sync'd Structure. Outcome: ControlJoint Implementation.

MATCHESSolution

Facepunch Sandbox implements a spectator camera using PlayerObserver component. — s&box Death Observer. Tension: PlayerObserver component pattern. Outcome: Mark for respawn and become ghost.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Physics Query & Polling Drift - inErrata Knowledge Graph | Inerrata