NorthAlabamaStormChase V1 will likely take another year. It will be faster development but around basic features like HUD, probe tool, GIS mapping engine, etc. Tactical Mesoanalyst is intended to deliver a subset of the first-gen smorgasbord in the full resolution new engine. In fact I need to make sure it's a complementary or different focused product for now, but not replacement, and see what people prefer. Which is why first-gen is being kept around as long as there's demand. Besides the RadarHalo Polyradial Mosaic, I don't intend to progress to any of the other data you mentioned before maximizing the utility and features for the core competency of raster timeseries. I know it's a different and narrower focus but I really want to see if we can't make a highly simplified, optimized product for tactical/in-field realtime awareness and then once that product, Tactical Mesoanalyst, is finished, reevaluate where first-gen stands.
So thank you for bringing this up so I can clarify again, all those extra things, some of which are outside Tactical Mesoanalyst's scope, should not be expected soon. This winter will be about making the actual product features, abilities, tools, graphics/customization, settings/maps/organization, etc., feature-rich but within the context of the raster timeseries core engine and the special RadarHalo reflectivity mosaic. Those are novel things not found anywhere else, and I think it's best to start with the novel things. Since we're reducing the price I also can't afford mass cancellations presently of first-gen and/or add-ons to a less expensive product before gaining more traction in general, not to mention I do not want to create even the appearance of a finished product until it truly is, another reason I want to stay in the lane of "world's fastest and most optimized realtime visible satellite imagery and radar reflectivity viewer" for a while before adding more data. 3D terrain, 8x multimap, my ideas for map organization and styling, contour/particles in raster engine, etc - these are all core competency for features that we already have sufficient data engines for (Raster2 GOES-R streams) to start building.
So you're really looking at having to wait for V1 if your focus is on those regular aspects and not on the ultra optimized low-latency raw display of storm chasing geared live sensor data. The perfectionism and doing everything in compute shader for ultimate performance delayed this and I need to keep the course of slow perfectionism. But thank you for your patience.
