In this video, I showcase Ray Tracer Version 4 and a major leap forward in software ray tracing performance inside the legacy PlayBASIC runtime.

This demo explores how smarter data structures and batching techniques can dramatically outperform traditional brute-force ray tracing, even without GPU acceleration, threading, or native compilation. Everything you see here is running entirely in pure software on a 10-year-old laptop.

🚀 What’s New in Ray Tracer v4?

- Introduction of PBS (Potential Visibility Set) mode

- Massive reduction in ray–object intersection tests

- Scene subdivision to limit per-pixel ray checks

- Shadows handled via optimized secondary ray lists

- Smooth performance with hundreds to thousands of spheres

- Real-time experimentation with object counts and resolution

Instead of testing every ray against every object, the engine now pre-filters intersection candidates, ensuring each pixel only checks against a small, relevant subset of objects. This simple design shift results in orders-of-magnitude performance improvements.



💡 Why This Matters

- Demonstrates how algorithmic design beats brute force

- Shows what’s possible in pure CPU-based ray tracing

- Ideal for learning ray intersection testing, spatial partitioning, and optimization strategies

- Highlights PlayBASIC’s continued flexibility as a learning and experimentation platform


This isn’t a physically accurate renderer, it’s a ray intersection engine designed to explore performance limits and engine design patterns. And the results are honestly surprising!

Like, subscribe, and share if you enjoy deep-dives into PlayBASIC internals and low-level rendering techniques.

Onwards and upwards.