The Meshing Bottleneck.

Traditional FEM/CAE pipelines often spend major time on volumetric meshing & geometry repair: fragile, memory-heavy, hard to parallelize.

WoSX aims to make physics simulation more like rendering: embarrassingly parallel, localized & free of volume meshes.

@Colonthreee No different than on the CPU.

For any random walk, the next walk location is picked uniformly on the sphere. More advanced estimators do essentially the same.

The PDE solution can be evaluated at fixed or random sets of points in the domain -- depends on the application.

“Rendering” Physics.

WoSX uses Walk on Spheres-style random walks to solve Laplace, Poisson, and screened Poisson problems with Dirichlet, Neumann, and Robin boundary conditions.

Estimate physical fields only where needed, using boundary queries via BVHs or SDFs.

Exterior Potential Flow: idealized flow around arbitrary geometry, inspected locally on a slice plane

This is a setting where generating a volume mesh is not just inconvenient—the exterior domain has infinite extent

Interactive Electrostatics: Electric potential and field magnitude computed on-the-fly for a moving micro-electronic comb drive

Bypassing the volume-meshing step entirely allows for real-time feedback during geometric articulation

WoSX includes several engineering-inspired demo applications, with more on the way

View-dependent Thermal Analysis: Steady-state heat conduction on a Mars Rover. WoSX effortlessly handles the raw, unoptimized asset (millions of triangles), evaluating the field only where needed

On the GPU, WoSX reduces warp divergence in its Monte Carlo random-walk solvers using dynamic load balancing through a persistent-threads implementation.

PDEs and boundary conditions are written in Slang (https://shader-slang.org), natively supporting CUDA, Vulkan, and Direct3D.

WoSX aims to be for MC physics what PBRT (https://www.pbrt.org) is for rendering: clear, inspectable, extensible software researchers & engineers can build on

It currently targets steady-state problems, not general multiphysics—but more features are under active development!

@rohansawhney1 How is the sampling done on the GPU, and are those fixed amounts samples?

@Colonthreee Checkout this tutorial for more details: https://rohan-sawhney.github.io/mcgp-resources/