I have tested a Capture project on four different systems: MacBook Pro M1 Pro 16 GB RAM MacBook Pro M5 Pro 24 GB Unified Memory Gigabyte G5 MF Laptop Intel i5-12500H RTX 4050 Laptop 6 GB 64 GB RAM Desktop PC Ryzen 7 5700G RTX 3060 12 GB 16 GB RAM Test Conditions The exact same Capture project was tested, featuring: Multiple moving heads Pixel bars Haze/fog Beam effects Various resolution limits (720p to 1440p) Settings prioritized for either quality or FPS Additionally, I optimized the project by: Disabling "Throws Light" for pixel bars Disabling "Spill Lighting" Hiding unnecessary layers This had a significantly greater impact than expected. Results M1 Pro The M1 Pro is still usable for basic visualization, but performance drops sharply during scenes with haze and beams. Initially, it sometimes reached only 5–10 FPS. After optimization, it often achieved 40+ FPS. It remained the slowest machine when handling complex beam/haze scenes. M5 Pro The M5 Pro was the biggest surprise. It offered roughly double the performance of the M1 Pro. At 1080p with practical, real-world settings, it reached around 40 FPS. At 720p, it exceeded 50 FPS. Even with haze and beams, it often performed on par with the RTX 4050. Subjectively, it provided the smoothest and most pleasant visual experience. Gigabyte RTX 4050 This gaming laptop generally achieved the highest consistent frame rates—up to 60 FPS. It delivered very strong performance in Capture. However, it was always extremely loud; the fans would immediately ramp up to full speed. When running on battery power without a power adapter, performance drops significantly. RTX 3060 Desktop The system equipped with an RTX 3060 was significantly more competitive than expected, performing close to the M5 Pro, depending on the settings. Key Finding The most substantial performance gain resulted from optimizing the Capture project. Disabling the following features: "Throws Light" for pixel bars Spill lighting Unnecessary layers and objects ...led to an increase in FPS that was, in some cases, greater than the jump observed when moving from the M1 Pro to the M5 Pro. An interesting observation was the difference in how Capture behaves on macOS (Apple Silicon) versus Windows. On both MacBooks (M1 Pro and M5 Pro), the FPS increased significantly whenever there was movement: M5 Pro: Static: approx. 40–50 FPS Rapid camera movement or pan/tilt movements of the moving heads: increase to 120 FPS M1 Pro: Static: approx. 45 FPS Movement: up to approx. 90–100 FPS On the Windows laptop (with an RTX 4050) and the desktop PC, the opposite was observed: The FPS remained largely constant—or even dropped slightly—during camera pans and moving-head movements. It was particularly striking that, subjectively, the motion appeared smoothest on the M5 Pro, even though the static FPS values ​​were sometimes lower than those of the RTX 4050-equipped laptop. I do not have a technical explanation for this, but it appears that on the Mac, certain calculations are prioritized differently when movement occurs.