Troubleshooting

Check ownership, active assets, and exposure before retuning the look. These are text walkthroughs; no editor UI screenshots are required.

Two Sky Rigs Are Fighting Over the Frame

Symptoms: The sky does not match the assigned look, light seems doubled, or fog remains after you change the preset.

Keep AAtmosSkyActor as the only sky/fog producer. Disable other sun, skylight, sky-atmosphere, cloud, and fog components, including those inside streamed level instances or a project's level-visuals actor. Selecting the intended actor does not stop other components from rendering.

Your own post-process volumes can also override exposure. Agentic Atmos deliberately places its own volumes below user-placed volumes, so yours win. Check them before changing sun intensity.

No Day Cycle Is Assigned

Symptoms: A plain lit sky appears instead of the expected authored look.

1. Read the sky actor's actual DayCycle assignment.
2. Assign /AgenticAtmosphere/DayCycles/DA_DayCycle_Default for a known starting point.
3. Confirm the clock is within a slot's coverage window.
4. Confirm that slot references the preset you are editing.

No cycle, or an uncovered hour, uses the actor's default layer. That fallback is intentional, not evidence of a failed renderer. See Day Cycle Asset.

An Edited Look Does Not Change the Viewport

The apply path skips unchanged state. Editing a preset underneath a paused clock may not change the watched inputs, so it can remain visually unchanged until explicitly refreshed.

Confirm the active slot points to the edited preset, then click Refresh Now (RefreshNow) on the sky actor. See Day Cycles.

Manual Time Changes Do Not Hold

Pause before setting time:

AT.Time.Pause 1
AT.Time.Set 12:00

If an external driver owns time, resuming the clock allows its next update to replace the manual value. Adjust that driver's time for a durable change. See Console Commands.

The Agent Toolsets Are Missing

The tools live in the editor-only AgenticAtmosphereToolsets module and require Epic's Experimental ToolsetRegistry engine plugin. Verify it is enabled, restart the editor, and rediscover the toolsets and argument schemas through the live MCP surface.

ToolsetRegistry is a required dependency, not an optional runtime switch. Do not look for these editor tools in a packaged game. See Agent Toolsets.

Ground Fog Is Invisible After Editing Terrain

Ground-fog banks follow a baked terrain height map. Any of the following invalidates it:

• Moving the bank or changing its footprint
• Changing bake resolution or trace bounds
• Changing the ground selection or exclusions
• Editing the terrain itself

A stale or invalid bank fails closed rather than showing a misleading result. Run Bake Terrain, confirm HasValidTerrainBake() and a nonzero valid-texel count, then save the bank's package. Baking is not saving.

Assigning a day cycle alone does not place ground-fog banks. Follow the full Ground Fog guide.

Shipped Content Is Missing from the Browser

Enable Show Plugin Content in the Content Browser's settings. Assets under /AgenticAtmosphere/ are hidden without it, including the day cycles, looks, weather types, and showcase map.

Atmos Tags Are Missing from the Picker

The plugin registers /AgenticAtmosphere/Core/Data/DT_AtmosphereTags at startup. A normal install does not require copying the table's rows into project configuration.

Verify the plugin is enabled and its content is available, restart the editor, then check the picker again. If the tags are still absent, include the relevant startup log when asking for support; do not assume an empty tag selection is equivalent to the intended tag.

The Frame Is Black or Blown Out

First check competing sky producers and user post-process overrides. Hold a known time and let exposure converge before judging the frame. Then follow Exposure to inspect camera response, metering, and the grade rather than compensating blindly with light intensity.

A Weather Name Does Not Produce the Expected Effect

Inspect the active weather type and its renderer. Names describe authored atmospheric states, not a guarantee of a renderer for every phenomenon. Lightning bolt VFX are unassigned; airborne dust is unfinished; hail and ash have no shipped implementations. See Weather for the supported effects and limits.

Need Help?

Ask in Discord. Include the Unreal Engine version, active day cycle and weather type, the time you tested, relevant log output, and a rendered frame from a rendering-capable editor. State whether the issue survives reopening the saved level.