File size: 2,602 Bytes
11c70d1 e0ada71 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 | # PhysInOne Camera and Rendering Tools
This package contains the public camera-placement, Unreal Engine rendering, and
render-output post-processing tools for PhysInOne.
## Included tools
```text
data_processing/
βββ camera/
β βββ generate_static_cameras.py
β βββ generate_camera_sequence.py
βββ common/
β βββ paths.py
βββ render/
β βββ render_config.example.bat
β βββ render_levels_windows.bat
βββ postprocess/
β βββ exr_to_dataset.py
β βββ point_cloud.py
β βββ render_processor.py
βββ examples/
β βββ level_list.txt
βββ docs/
β βββ CAMERA_AND_RENDERING.md
βββ requirements-render.txt
```
Start with [docs/CAMERA_AND_RENDERING.md](docs/CAMERA_AND_RENDERING.md).
## Pipeline at a glance
1. Configure `BP_CameraTrajectory` in the target Unreal level.
2. Generate static cameras.
3. Generate or replace the moving camera and Level Sequence.
4. Render EXR passes with Unreal Engine Movie Render Queue.
5. Convert RGB EXRs to JPEG and depth/segmentation EXRs to NPZ.
6. Generate `points3d.ply` by back-projecting the first RGB/depth frame from
every static camera and merging the views.
The post-processing tools do **not** select validation views and do **not**
create or overwrite any `transforms_*.json` split file.
`CineCamera_Moving` is excluded from point-cloud generation.
## Requirements
- Unreal Engine 5.5.4 with the Python Editor Script Plugin enabled
- Windows for the supplied headless-render batch file
- Python 3.10 or newer for post-processing
- The PhysInOne Unreal project and its Movie Render Queue configuration assets
No access token or private credential is required by these local tools.
The public Movie Render Queue configuration assets are installed in the Unreal
project at `Content/PhysInOne/Scripts/`, corresponding to the virtual package
path `/Game/PhysInOne/Scripts/`. Keep that directory unchanged because the
Windows renderer refers to those package paths directly.
## Trajectory recording plugin
[Install and use PhysInOne Trajectory Recorder](https://huggingface.co/datasets/vLAR/PhysInOne/blob/main/Utils/data_processing/trajectory/README.md)
to capture a new Play/Simulate session with explicit world-space actor and
component poses. Version 1.1.0 includes a precompiled UE 5.5.4 Windows Editor
plugin, source, and validation/recovery helpers. This is separate from the
camera/rendering pipeline: it does not repair old trajectories or automatically
align new simulation samples with existing rendered images.
|