How to Generate Rain, Smoke and Weather in AI Vertical Drama Without Breaking Continuity
A rain scene. Eleven shots. The wide shows a steady downpour, the close up shows a light drizzle, and the reverse shows dry pavement. Every shot passed review on its own. Together they read as three different nights. This is the most common way weather fails in AI vertical drama, and it rarely gets caught until the edit, when the scene is assembled and the viewer would see the seams immediately.
Weather is one of the strongest tools a vertical drama has. Rain on a window during a breakup. Smoke drifting across a warehouse confrontation. Fog that hides who is standing at the end of the pier. These are images the format leans on because they carry emotion in a single frame on a phone screen. They are also the images most likely to drift, because generators treat weather as texture rather than as a fixed property of the world. The fix is not a better prompt. The fix is a production method that treats weather as something the team decides once and then holds.
1. Why Weather Breaks Continuity Faster Than Anything Else
A face has a reference. A wardrobe has a reference. A location has a reference library. Weather usually has nothing. It lives as a few words in a prompt, and every generator interprets those words fresh each time. Heavy rain in one session can mean a curtain of water. In the next it can mean visible droplets with a dry background. The model is not wrong. It was never told what heavy meant for this scene.
Weather also touches everything else in the frame. Rain changes the reflectivity of the floor, the darkness of fabric, the shape of hair, the light falling on skin. Smoke changes contrast, depth, colour temperature and how far the eye can travel into the background. So when weather drifts, it does not drift alone. It pulls lighting, wardrobe and set dressing out of alignment with it. One inconsistent value becomes five visible problems.
The third factor is volume. A 70 episode series can carry dozens of weather scenes, generated by several operators across many sessions. Without a shared definition, each operator brings their own picture of what the storm looks like. The drift is not a skill problem. It is a missing document.
2. Treat Weather as a Character With Its Own Reference Sheet
The most reliable shift is conceptual. Weather gets the same treatment as a recurring character. It has a name, a reference image set, a short written description and a list of the visual properties that must not change. Rain in the alley outside the club becomes a defined asset, not a phrase.
A useful weather reference sheet holds a small number of approved frames that show the weather at the intended intensity, ideally in the actual location and lighting of the scene. It holds a written description in plain physical terms: droplet size, direction, density, whether rain is falling in the foreground, midground or both. It holds a note on what the weather does to surfaces and people. Wet asphalt with sharp reflections. Hair darkened and flattened. Shoulders of the coat visibly soaked. These are the things a reviewer checks.
This sheet sits alongside the character and location references in the series bible. When the team builds a continuity bible, weather states should be listed as entries in their own right, so that a scene in episode 12 and a callback scene in episode 48 can share the same storm. The point is simple. If it can be seen, it can drift, and if it can drift, it needs a reference.
3. Lock the Weather State Per Scene, Not Per Shot
Teams often write weather into each shot prompt independently. That is how a scene ends up with three intensities. The better practice is to decide the weather state at scene level, before any shot is generated, and to carry that single state into every shot in the scene without variation.
What a Weather Ledger Entry Contains
A weather ledger is a short record kept per scene. It does not need to be complex. It needs to be read by every operator who touches the scene. Each entry should hold the following:
Scene and episode reference, plus the location reference it belongs to
Weather type and intensity in physical terms, with the approved reference frame attached
Direction of travel for rain, smoke or wind, relative to the camera axis
State of surfaces and people, written as visible facts
Whether the weather changes during the scene, and on which beat
That last line matters. Weather can change within a scene for dramatic reasons. Rain can start as a character walks out. Smoke can clear as a reveal lands. When this is intended, the ledger records the change as a beat, with a before state and an after state. Then the shots on each side of the beat are generated against the correct state. Intended change is storytelling. Unrecorded change is a continuity error.
Holding Direction Across Reverse Angles
Direction is the property most often lost. Rain falling left to right in the wide must fall right to left in the reverse if the camera has crossed to the other side, and left to right again if it has not. Smoke drifting toward the door must keep drifting toward the door from every angle. Operators should write direction relative to fixed elements of the set, not relative to the frame, because frame left changes with every angle and the door does not.
4. Writing Weather Into the Prompt Without Letting It Take Over
Weather words are heavy. They can dominate a prompt and pull the generator toward a stock storm image that ignores the character, the performance and the composition. The aim is to describe weather precisely while keeping it subordinate to the subject of the shot.
In practice that means a consistent prompt order. Subject and action come first, then framing, then the environment, then weather, then light. Weather placed after the location and before lighting tends to be applied to the space rather than replacing it. Weather placed first tends to become the image. The exact structure varies by generator, but the principle holds across tools: the scene is about a person, and the weather describes the world that person is in.
Language should be physical and repeatable. Avoid mood words such as dramatic, moody or intense, because they invite the model to invent. Prefer measurable descriptions: fine steady rain falling at a slight angle, visible streaks in the foreground, wet reflective pavement, no puddle splash. Then reuse that exact phrase for every shot in the scene. A shared phrase is the prompt equivalent of a reference frame. It removes interpretation.
Using Reference Frames as the Anchor
Where the generator accepts image references, the approved weather frame should travel with every shot in the scene, alongside the character and location references. If reference slots are limited, a frame that shows the location already in the correct weather is the most efficient choice, because it carries both. This is also where a reusable location library pays off. A location captured once in dry conditions and once in the scene weather gives operators a clean anchor for each state.
5. Rain Specifically: Surfaces, Faces and Wet Wardrobe
Rain is the weather vertical drama uses most, and it carries the most secondary detail. The rain itself is rarely what breaks. What breaks is everything rain touches.
Surfaces
Wet ground reflects. Those reflections carry light sources, signage and the shapes of people. In a tight vertical frame the floor is often a large part of the image, so a wet floor in one shot and a matte floor in the next is immediately visible. The ledger should say whether the ground is wet, whether there are standing puddles, and what the reflections should broadly show. Operators then check this at review, shot by shot.
Faces and Hair
Rain on a face has to be readable at phone size without obscuring the performance. Droplets that are too large or too numerous distract from the eyes, and in vertical drama the eyes carry the scene. A useful rule is to define facial wetness separately from rain intensity. Heavy rain in the world, light visible wetness on the skin, hair darkened and sitting closer to the head. Hair is a strong continuity signal. Dry volume in one shot and soaked strands in the next is the sort of detail viewers notice without knowing why.
Wardrobe
Wet fabric darkens and clings. A character who has been standing in rain for a full scene should not have a dry jacket in the final close up. Wardrobe wetness also accumulates over time, which means a long rain scene may need two or three wardrobe states recorded in the ledger. The same discipline applies here as with any costume change: the state is defined, referenced and reviewed, not left to the generator.
6. Smoke, Fog and Haze: Density as a Continuity Value
Smoke and fog fail differently from rain. They are less about particles and more about density, which changes how far the eye can see and how much contrast survives. One shot with a light haze and the next with thick fog will cut together badly even if both look good alone.
The solution is to treat density as a value. The ledger should state how far into the frame the background remains readable. Background clearly visible with soft contrast. Background shapes visible, detail lost. Background gone beyond a few metres. These descriptions are easy for operators to apply and easy for reviewers to check against each other.
Smoke also has motion and source. A fire, a vent, a cigarette, a smoke machine at a club. The source should be consistent and, where it is in frame, visible in the wide so the close ups make sense. Smoke drifting with no source reads as an effect rather than as part of the world. Haze, by contrast, should feel ambient and even. A good haze shot is one where the viewer does not think about haze at all, only about the light.
Faces in Smoke and Fog
Low contrast environments can soften faces until they lose definition. This is the same risk teams face in night exteriors, where identity can disappear into shadow. The method is similar: keep a dedicated light on the face that sits in front of the haze, and keep the density lower in the foreground than in the background. The face stays readable, the world stays atmospheric.
7. When to Add Weather in Post Instead
Not every weather effect should be generated into the shot. Some are better added in compositing, after the performance and continuity of the base shot are locked. The decision depends on how much the weather interacts with the subject.
Rain falling in the distance, light drifting haze, snow passing in front of a window: these sit largely on top of the image and can be added consistently in post across a full scene. Rain running down a face, a character walking through thick smoke, a coat soaked through: these interact with the subject and are better generated in shot, against a locked reference.
A hybrid approach often works best. Generate the base shot with the surface and wardrobe effects of weather, so the world looks wet or smoky, and add the falling or drifting element in post so its intensity and direction are identical across every shot. This separates the part that is hard to hold, the moving element, from the part that is hard to fake, the interaction. For a broader view of how scenes stay coherent, the principles of continuity in fiction apply as much to atmosphere as they do to plot.
Reviewing a Weather Scene
Review should happen at scene level, with every shot laid side by side in cut order. Individual shot review will always pass shots that fail as a sequence. The reviewer checks intensity, direction, surface state, facial wetness, wardrobe state and density against the ledger, then watches the scene as an assembled cut. Any shot that breaks the state goes back with a specific note naming the property that drifted and the reference it should match.
Axis AI Studios Perspective
Weather scenes are where a series either holds together or quietly comes apart. Audiences do not notice correct weather. They notice wrong weather, even when they cannot name it. That is why Axis AI Studios treats weather the same way it treats faces, locations and wardrobe: as a defined, referenced state that every operator works against, recorded per scene and reviewed as a sequence.
This is the kind of detail that separates a series a platform can put on its homepage from one that needs fixing after delivery. The method is not complicated. It is consistent. Weather references in the bible. A ledger per scene. A fixed prompt order. A clear decision on what is generated and what is composited. Review in cut order, not shot by shot.
For platforms, brands and media companies commissioning AI vertical drama, the question worth asking any production partner is how weather is defined and held across a scene. The answer says a great deal about how everything else is held too. To talk through a series that leans on rain, smoke or atmosphere, write to business@axisaistudios.com.
FAQ
Can AI generators hold the same rain intensity across a full scene?
They can when the intensity is defined once and reused. A fixed physical description, the same reference frame in every shot, and scene level review keep intensity stable. Left to separate prompts per shot, intensity will vary.
Is it better to generate rain in shot or add it in post?
It depends on interaction. Rain that touches the subject, such as wet faces and soaked wardrobe, is better generated in shot. Falling rain in the background or midground is often more consistent when added in post across the whole scene.
How do you keep faces readable in smoke or fog scenes?
Keep the haze lighter in the foreground than in the background, and keep a defined light on the face. Record a density value in the scene ledger so every shot uses the same visibility, then review the shots side by side.
Further Reading
For teams setting up the document that weather states belong in, the guide to building a vertical drama continuity bible covers how to track visual states across 70 episodes without drift.
For scenes where atmosphere meets low light, the method for generating night exteriors without losing faces to shadow covers how to keep identity readable when contrast drops.
For operators who need a clean anchor for each weather state, the walkthrough on building a reusable location library covers how to capture and reuse locations so they stay consistent across a series.

Let's set
the new standard together.
If you're working on something, we'd like to hear about it.
