Summary
In Parkour Spiral 2 (PlaceId 96596531231580), some players join and part of the map fails to render for them, while it renders fine for other players in the same server. The geometry is still there (collision works, players stand on and bump into it), it just does not draw. Manually clearing the Roblox asset cache fixes it for a player.
The failure varies per player
It is not one consistent symptom. Across different players I have seen three distinct modes: missing meshes with textures intact; meshes present but untextured (flat/gray); and almost nothing drawing at all. Meshes and textures fail independently, and the affected subset and severity differ per client.
Correct result, after clearing the cache:
Notes
- My map is built from a very large number of meshes, which may be relevant if this is load or delivery related.
- Re-uploading the affected meshes under new asset IDs did not fix it for already-affected players.
- It self-heals over time. I used to get it too but no longer, and once a player is past it, it seems impossible to trigger again.
- I could not reproduce it on demand (tried with vpn, clearing cache and fresh downloads from several regions, and forcing corrupt or failed assets locally; none reproduced it).
Hypothesis (uncertain)
Since the failing set is a variable subset of assets per client rather than one specific asset, and it self-heals, my best guess is an intermittent asset delivery/loading failure of recently-uploaded assets rather than corruption of a single asset. Clearing the cache forces a fresh fetch that succeeds. I could be wrong about the mechanism.
Impact
The impact is significant. I postponed the public launch of the experience because of this, and access is currently restricted to group members only until I know this is fixed.
Details
- Place: https://www.roblox.com/games/96596531231580
- Similar reports: Meshes not visible but still present and collidable and Assets randomly going invisible, but retaining collision information
Expected behavior
MeshParts should render for all players regardless of the state of an individual client’s asset cache. When a player is in this broken state, the only known fix is manually clearing the cache, which ordinary players will never do, so for them the experience is simply broken. I am not sure of the exact mechanism, so I am not prescribing a specific fix; the key point is that a client should not be able to get stuck rendering nothing for an asset that other clients render fine.



