@Tyrant:
There are two factors: The BMS weather model and the weather data that WeatherGen produces. BMS models weather in (roughly) 9nm squares, so as you cross the boundaries, you might find yourself going from one set of weather parameters to a vastly different set, depending on how you have WeatherGen set up to produce weather (more on that in a second). Too, BMS changes the weather instantaneously at the times dictated by the WeatherMapsUpdates folder. So even if you’re not moving it can jump suddenly.
You can alleviate that in a few ways. To address time-based jumps, have the weather update more often, as it will change more frequently but in smaller ways. That’s the “step” parameter under “save weather package”. I use 15 minutes and haven’t seen any problems with it across many flights.
To address jumps between adjacent weather squares, you can increase the zoom under “Advanced”. This basically makes the weather patterns bigger, and therefore more slowly changing through space. Try values between 10 and 20 to see what you like.
Be aware that although I can’t really do anything about the chunkiness of the BMS weather model, BMS does do some smoothing/blending for things like cloud cover, so that plays into this all as well. Pressure, however, seems to change pretty close to instantaneously at region boundaries. And that’s sort of on me - the code currently produces weather that varies far too fast. I am working on improving it, but I have a lot of irons in the fire there and no ETA. A semi-fix for that is to change the min and max pressure settings and adjust the boundaries for the various weather types.
Hope that makes sense. If you’re still having trouble, post your weathergen settings file and I’ll take a look when I have a minute.
Thanks a lot Tyrant, this is the information I needed, you are most helpful. I will test your suggestions, I am certain that it will improve my (and maybe some others) experience with weathergen. All your work is highly appreciated.