VA Dynamics
About the project
VA-Dynamics, developed by VA-Design, is a GPU-native CFD project focused on building a local-first simulation stack for high-fidelity external aerodynamics for motorsport and aerospace-style use, without the usual long runtimes, fragmented toolchains, and slow iteration loops. The objective is not only to compute flow fields, but to compress the full time-to-decision cycle so engineers can test ideas more often, validate changes faster, and carry momentum through an entire development programme instead of waiting on the next run.
VA-Dynamics is built around two tightly integrated parts that are designed as one product pipeline rather than separate utilities. The first is VA-Dynamics, the main desktop application written in C++ that manages models, cases, domain settings, and solver orchestration while providing the working environment through navigation menus, a real-time viewport, live logs, and the explorer and properties panels. The second is VAWindSimSolver, shortened to VAWSS, a CUDA-accelerated solver designed to run purely on the client GPU so simulations execute locally with a workflow that stays fast, repeatable, and engineering-focused.
The Main Application handles the entire “Vendor” of the CFD loop, including case setup, model preparation, domain configuration, and run management. VAWSS handles the “compute half” of the loop, iterating the solution in the background while returning not just final results but the supporting outputs an engineer needs to trust a run, including coefficients, values, and history data that can be graphed and compared inside the application.
Mission and vision
Our mission is to build a fully GPU-native CFD solver that supports accelerated aerodynamic iteration while staying grounded in real physics, an engineering tool designed for decisions, not visuals-first output. This means performance is treated as a product feature only when it is paired with numerical discipline, predictable convergence behaviour, and transparent run reporting that makes results defensible.
We are also building the surrounding workflow so CFD becomes more approachable and practical for both companies and individual engineers. The aim is to keep case setup, models, meshing, boundary conditions, solver settings, and outputs in one place, shorten turnaround time by designing the solver for GPU-parallel execution from the start, and reduce dependency on external compute, queues, and specialist infrastructure by keeping the default path local.
The long-term vision is to bridge academic-level simulation intent with real-world usability. That means fewer steps between geometry and validated coefficients, fewer places where a run can silently fail, and a workflow that encourages iteration rather than punishing it.