Skip to content
TheChatArchiveThe Chat Archive
o3-2025-04-16· OpenAIHugging Face LMArena Human Preference 140K

the fog does not follow the cameras angles only its look postion to the horizion pretty…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Kimikimi-k2-0711-preview’s answer.
  1. User

    the fog does not follow the cameras angles only its look postion to the horizion pretty much, another thing is the beams/fog gets pushed back when moving until i stop moving

  2. Assistant

    Hey 👋 – I think I understand the symptoms, but I’m missing a couple of key details.
    Before I shoot in the dark, could you quickly tell me:

    1. Which engine / tool are you working in? (Unity, Unreal, Godot, Roblox, a custom engine, etc.)
    2. What kind of fog/beam solution are you using?
      • Built-in linear or exponential fog?
      • A post-processing effect (screen-space / global fog)?
      • A volumetric-fog component / plugin?
      • A particle system with billboard sprites?
    3. Do the objects that represent the fog or beams live in Local Space (move with the camera) or World Space (stay put in the environment)?
    4. Are you using any kind of temporal reprojection / motion-vector based effect?

    Even without that info, here are the two most common causes of the “fog follows camera yaw but not pitch” and “beams get pushed back while moving” problems:

    ────────────────────────────────────────

    1. The fog is calculated in view-space instead of world-space ──────────────────────────────────────── Symptoms
      • Rotating around the vertical axis (yaw) looks OK because the horizon line stays level.
      • Looking up/down or translating the camera makes the fog appear to “slide” or detach from the scene.

    Why it happens
    A lot of simple fog shaders do something like this:

    float depth = i.viewSpacePos.z;          // <- view-space, not world-space
    float fogFactor = exp(-_Density * depth);
    

    Because depth is measured from the camera, the fog effectively lives in the camera’s space; as soon as the camera moves, the fog moves with it.

    Typical fixes
    • Rewrite/replace the fog so it uses world-space positions:

    float3 worldPos = i.worldPos;
    float dist = distance(_WorldSpaceCameraPos, worldPos);
    float fogFactor = exp(-_Density * dist);
    

    • If you’re using Unity’s built-in GlobalFog image effect, enable the “Distance” and “Height” options so it samples world-space depth.
    • In Unreal, use Exponential Height Fog or Volumetric Fog (they’re world-space by default) instead of the legacy post-process fog.

    ──────────────────────────────────────── 2. The fog / beams are particles or meshes that are being simulated in “Local Space” ──────────────────────────────────────── Symptoms
    • While you walk forward the beams seem to rush away; they only stay still when you stop moving.
    • If you temporarily un-parent the particle system from the camera, everything lines up.

    Why it happens
    In most engines, a particle system can be set to simulate in Local, World, or Custom space. In Local space the particles inherit the parent’s transform every frame, so any translation of the parent will drag the fog with it.

    Typical fixes
    Unity
    Particle System → Main → Simulation Space → set to World or Custom.
    Unreal
    Niagara → System Settings → Emitter Update → “Local Space” off.
    Godot
    Particles → “Local Coords” unchecked.
    Roblox
    For Beams or ParticleEmitters, make sure the Part → Anchored = true / not welded to the camera.

    ──────────────────────────────────────── Extra notes for specific engines (in case one rings a bell) ──────────────────────────────────────── Unity
    • If the issue only appears while the camera is moving and you’re using the HDRP’s Volumetric Fog, lower “Volumetric Fog History Blend” (< 0.85) or disable Temporal Anti-Aliasing; TAA re-projections can smear volumetrics in motion.
    Unreal Engine
    • “Beams move while you move” is often just TAA history lag. Try r.TemporalAASamples 4 or disable TAA to test.
    • For Volumetric Fog being pushed back, adjust r.VolumetricFog.HistoryWeight (0.9 → 0.6) or set r.VolumetricFog.GridPixelSize smaller so the grid follows the camera more tightly.
    Godot
    • The built-in Fog has a “Depth Begin” / “Depth End” that are camera-relative. For world-space you need an environment override or a custom shader.
    Roblox
    • Setting Beam.FaceCamera = true on a wedge-shaped part can cause the “slide” effect; leave it false and orient the beam part manually.

    ──────────────────────────────────────── Quick experiment you can try right now ────────────────────────────────────────

    1. Pause the game/sim in the editor.
    2. While paused, drag the camera a few meters sideways.
      • If the fog moves with the camera → it’s view-space or Local-space.
      • If the fog stays put but “pops” when you un-pause → it’s likely a temporal reprojection artifact.

    ──────────────────────────────────────── Next step ──────────────────────────────────────── Let me know which platform you’re on and which of the two cases above matches what you’re seeing, and I can give you exact code / inspector settings to fix it. Screenshots or a short clip help a ton, too!

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.