LTX 2.5 NSFW Clothing Physics Prompting Guide (2026)

Key Takeaways

• "Flowing dress" is not a physics description. Believable clothing movement needs fabric type, a motion driver, and an anchor point written as three separate clauses.
• Vague adjectives produce inconsistent results; naming the fabric's actual physical properties (stiff vs. drapey, heavy vs. light) gives the model something concrete to work from.
• LTX 2.5 is not callable on Siray yet — support is planned. The structures below are carried over from LTX 2.3, which is live today, so they are a starting point to re-verify against 2.5 rather than measured 2.5 behaviour.

Safety boundary: Everything below assumes adult (18+) subjects only. These prompt structures must not be used to generate content involving minors or any depiction resembling a minor. "Uncensored" describes content filtering, not a suspension of law, consent, or platform policy — see the compliance statement at the end of this guide.

Status (2026-08-12): LTX 2.5 is not callable on Siray today; Siray support is planned. There is no published endpoint name, price, or capability sheet for it yet, and this guide deliberately does not print resolutions, durations, or frame rates — the ones documented for LTX 2.3 describe that endpoint's configuration on Siray, not a property of the model series. Confirm parameters against the endpoint's own reference when it goes live.

Why Clothing Physics Prompts Fail

Most clothing-physics prompts fail for one reason: they describe the garment at rest, not what makes it move. "A flowing silk dress" says nothing about what force acts on it, where it is anchored, or how stiff versus drapey the material behaves. Video models respond far better when those pieces are separated explicitly, the same way the general LTX 2.3 NSFW prompt guide breaks shots into scene, action, and camera layers. This guide applies that layered approach specifically to fabric and clothing motion.

The Three Clothing-Physics Layers

Fabric type

Controls: how the material behaves under motion — stiffness, weight, how it catches light and holds a shape.

How to describe it: name the actual fabric and its physical property, not just its color or style. "Stiff structured denim that holds its shape" reads differently to the model than "soft draping silk that clings and ripples."

Mini example: heavy raw denim, stiff, holds sharp folds, minimal drape

Motion driver

Controls: what force is making the fabric move in the first place — without a stated driver, the model defaults to near-static cloth.

How to describe it: name the source of motion explicitly — a turn, a step, a gust, a sit-down — rather than just saying the fabric "flows."

Mini example: fabric responds to a slow half-turn toward camera, hem lifting slightly with the motion

Anchor & fit

Controls: where the garment is tight to the body versus loose enough to move independently — this is what keeps clothing physics from looking like a disconnected overlay.

How to describe it: call out the specific anchor points (waist, shoulders, one strap) and where the fabric is free to drape or swing.

Mini example: fitted at the waist, loose through the skirt, hem swings freely below the knee

Combined Example — Text-to-Video

Subject: an adult woman, mid-20s in appearance, standing in a softly lit roomFabric type: lightweight satin, drapey, catches light with subtle sheenMotion driver: slow half-turn toward camera, arms relaxed at sidesAnchor & fit: fitted at the shoulders, loose through the body, hem swaying with the turnCamera: medium shot, static, eye-levelNegative: stiff or frozen fabric, clipping through the body, warped folds

Combined Example — Image-to-Video

image: <source image URL>Fabric type: structured cotton, moderate stiffness, holds folds but not rigidMotion driver: gentle walking motion, camera trailing from behindAnchor & fit: fitted through the waist, skirt panel swinging with each stepNegative: fabric clipping through legs, unnatural stretching, static hem during motion

Both blocks are prompt content only. Request parameters belong to whatever endpoint you send them to — fill those from its own reference rather than copying them between model versions.

Fixing the Two Most Common Failures

If fabric looks stiff and lifeless even when described as flowing, the prompt is almost always missing a motion driver — name the specific action causing the movement instead of relying on the fabric adjective alone. If fabric clips through the body or looks disconnected, the anchor & fit layer is too vague — name the exact point where the garment is tight, then describe the free-hanging part separately.

FAQ

Can I use LTX 2.5 on Siray right now?

Not yet. Siray support is planned, with no announced date. LTX 2.3 is live today and is what these structures were written against.

Does LTX 2.5 support real cloth simulation like a game engine?

No video generation model does — they respond to language, not to a physics solver. Describing fabric properties and motion explicitly gets closer to realistic-looking results, but it is pattern-matched generation, not simulated physics.

Will these prompts still work on LTX 2.5?

The layered structure should carry over, because it describes fabric behaviour rather than one model's syntax. How strongly 2.5 responds to each layer is unmeasured until the endpoint is live, so treat the examples as a baseline to test, not a tuned recipe.

Putting It Together

Clothing physics prompts break down into three layers: what the fabric is made of, what's making it move, and where it's anchored to the body. Write each one explicitly instead of reaching for a single flowing adjective, and the model has something concrete to work from instead of guessing.

Create a Siray account and test these layered prompts on the LTX endpoints that are live today — one API key, ready for LTX 2.5 the day it lands.

Safety statement: Siray requires all generated content to depict adults only (18+) and rejects any output involving minors, with zero tolerance for CSAM in any form. "Uncensored" describes relaxed content filtering — it does not override the law, consent requirements, intellectual-property rights, platform rules, or the safety boundaries described above.