A: No. ReplayCam captures supported mesh states, transforms, selections, viewport views and timed events as modeling data. It rebuilds a replay from that data, rather than storing screen video or relying only on re-executing keyboard shortcuts.

A: An additional ReplayCam session folder is saved alongside your Blender project. session.json stores timing and tracks; meshes.npz stores captured geometry. Editing decisions are stored separately in .rcedit files. ReplayCam does not add its replay objects, actions or session data to your project.

A: Yes. You can hide recorded steps, cut ranges, adjust playback speed and compress long pauses. These decisions affect the presentation and preserve the recording; they do not undo the operations in your model, and the resulting model state is kept. You can also omit undone branches. Step Density controls retained geometry steps and does not itself shorten the duration.

A: Yes. Choose Recorded View to follow a captured viewport or Orbit for an orbiting presentation. Choose Blender Original, Solid Flat, Clay or Wireframe, with mesh and cursor customization. Arbitrary scene cameras and material-texture or photorealistic render export are outside the current beta scope.

A: No. Video generation happens at export, so ReplayCam does not encode screen video while you model. Capture still uses CPU, memory and disk. Its cost depends on scene complexity, Geometry Rate, checkpoint saves and session length. Dense scenes can slow capture and use substantial storage.

A: New recordings preserve supported Object/Edit selections and historical Subdivision Surface settings, including levels and creases. Some preview combinations fall back to the base mesh with a warning; native export reconstructs supported Subdivision stacks. Other active modifier types and uncaptured custom normals can block export. Older recordings do not acquire missing historical data automatically.

A: Yes. Keep the original session and save different replay edits, then export them with different timing, cuts, appearance and supported view choices. Your .rcedit contains saved directing decisions such as timing, cuts, orbit parameters and appearance; select Recorded View or Orbit in the replay/export controls.

A: Yes. Recorded timestamps determine the timing. Speed 1, Max Pause 0 and no cuts preserve the captured pace within sampling and output frame-rate limits. Explicit recording pauses are excluded. Faster speed, compressed pauses and cuts create a shorter presentation.

A: It can recover the latest complete verified recovery checkpoint, not every action since that checkpoint. The current save system keeps two verified recovery copies. Save your Blender project normally and leave Blender open until the session reports Saved.

A: The beta focuses on mesh modeling in Object and Edit Mode. It does not capture the full Blender interface, gizmos, toolbars, complete Sculpt workflows, material nodes or textures. A recorded 2D cursor requires Recorded View and available captured positions. The 3D pointer is a separate presentation overlay.