Transitioning from Ray1.6 to Ray2/Ray3 for Video Generation

When transitioning from Ray1.6 to newer models, users may notice differences in camera stability and motion characteristics. Professional creators have successfully achieved results that match or exceed their Ray1.6 quality by using more specific prompting techniques and selecting the right model for their workflow.

Ray3 is the latest model with significantly improved camera control and stability—perfect for controlled camera movements and architectural work. Draft Mode is 5x faster and more cost-effective for iteration, making it ideal for professional workflows. Ray3 understands directive language exceptionally well.

Ray2 responds best to shorter, more directive prompts rather than the detailed instructional style that worked with Ray1.6. Less is often more - plus Ray2 can be used via API.

Ray2 Flash offers faster, more economical generations while maintaining good quality. Worth testing for specific use cases where speed and cost efficiency are priorities.

Example: Smooth Camera Push-In Movement

For achieving stable, professional camera movements like a smooth push-in through a room:

Pricing
Pricing Is very similar to Ray1.6 for Ray2Flash and Ray3 Draft

Working Examples

View a board with working examples showing the exact approach and results you can expect with each model:

Note: Ray3 Draft Mode provides easier workflow and more consistent results for this use case.

The transition from Ray1.6 doesn't require compromising on quality—it's about finding the right model and prompting approach for your specific workflow.

Happy Creating!
Chris Roebuck Luma AI – Customer Support - Education

Transitioning from Ray1.6 to newer models means learning a slightly different way of writing prompts to get the same smooth, stable camera movements you're used to. Step 1: Try Ray3 Draft Mode first—it's the newest model and understands what you want better than older versions, plus it's 5 times faster and cheaper for testing different ideas. Step 2: Write shorter, more direct prompts instead of long detailed instructions—for example, instead of saying "Generate a perfectly stable, professional push-in movement into the room. The camera should feel mounted on a tripod..." just say "locked viewpoint then very slow slow shallow smooth @Push_In exactly same empty room." Step 3: The @Push_In tag helps the AI understand you want that specific forward camera movement, and words like "locked viewpoint" tell it to stay stable without shaking. Step 4: If Ray3 Draft doesn't work perfectly, try Ray2 Flash which is faster and cheaper, or regular Ray2 which can also be used through the API if you're building automated workflows. Step 5: Look at the example board linked above to see exactly what these different prompts produce so you can copy the style that works—sometimes seeing the examples helps more than reading instructions. The main thing to remember is: less detailed explanation, more direct commands. Ray1.6 liked long instructions, but Ray2 and Ray3 prefer you to be brief and specific about what you want!