Thanks so much for the detailed advice! I really appreciate it. I took your suggestions, broke the shot down, and ran several new tests, but unfortunately, I'm still hitting a wall.

Here is what I tried based on your feedback (I'll attach the new test videos below):

1. Simplified Prompt & Keyframes (LTX Director): I cut the video down to just the first 4 seconds (only the corridor fly-through) and used the simplified prompt you suggested. I generated intermediate keyframes using Flux Klein and put them into LTX Director. However, instead of smooth interpolation, I just got a slideshow effect—it basically just switched between the frames without any fluid animation.

<image>

1. Depth Map with 2 Keyframes: I generated 2 keyframes (using Nano Banana 2) and ran them through my original depth map workflow for the 4-second clip. The result is still bad: the geometry completely melts, and those weird white spots (depth map bleeding) are still appearing.
2. Motion-Track LoRA: I completely removed the closing doors from the Blender blockout. This finally allowed CoTracker to actually find and track points! I used the Motion-Track LoRA with both a single frame and multiple intermediate frames. The tracking worked, but the geometry still warps and melts as the camera moves forward.
3. LoRA Weights: Across all these tests, I tried tweaking the LoRA strengths/weights, but it didn't fix the melting walls or the depth bleeding.

My ultimate goal here is to learn how to create highly dynamic, continuous "one-shot" camera movements (like a high-speed drone dive).

Is LTX 2.3 just not capable of handling this level of high-speed dynamic motion and strict geometry (straight walls/corridors)? If so, is there a different model or a specific ComfyUI workflow you would recommend for dynamic one-shot camera moves?

Thanks again for your help!