eliteo Robert, thank you very much. Yes, I do intend to tackle 3D volume rendering after finishing the base raster display engine, probably around early next year. The V6P Prototype in the first-generation product does give you a sense of what I am shooting for in terms of high-framerate, low-latency, fluid, and interactive 3D graphics. The cluttered, outdated infrastructure of the 2015-era app made it very difficult to move forward in that codebase.
The new codebase is highly inspiring to work on, because I see everything that you do in terms of the promise of what's possible. I am currently experimenting with a general framework for raster data display that can render parameters to the 3D terrain textures themselves, to achieve the "draping" effect necessary for correct display of 2D parameters on 3D terrain, and which can default to traditional flat projections at a fixed height. There is a lot of predevelopment work like this which has precluded new amazing screenshots since in early April I got the screenspace-extruded terrain-projected vector line engine working well.
Actually I have spent most of my time in the last month working on the web architecture, both for data ingest and real-time client-server interaction. Everything will be "server push" based using WebSocket over regular HTTP/S network port. WSV3 Server will instantly notify all WSV3 Client instances when, say, a new National Radar frame hits. Actually, the client will update the server in real-time about what data products the user has selected, and the server will push only messages updating those products. This model eliminates traditional wasteful client-side polling. Other web functionality I intend is automatic seamless cross-device usage with synchronized settings/maps, and some sort of content sharing system instead of using a forum to post custom styles, palettes, and what not.
I should have some new screenshots this summer and look forward to incorporating any of your feedback.