A very simple fix..

I think an in-house weather system is on the cards, as the real life weather is just too static. This suggestion (OP) gave me some ideas about implementing a daily weather pattern for each track. But I'd like to have it such that there can always be a sudden change of conditions in every race, that's part of what makes it exciting.

There's a lot more to consider as a developer. As a user the problem is "it's too cold too often, so hijack the temperature".

As a dev it's... "how am I going to work that in to the forecast text we import directly from the weather service? Do I scrap those forecasts? Will people miss them? Do I need to write a new forecast engine then? How will I write a weather engine that can be forecast a week in advance and change weekly? What happens at the point the weather changes? Is everyone doing setups before the change for a race happening after it going to be confused? Will the races at that time every week suddenly change from 30 degrees to 10 degrees and screw up everyone's strategies once a week? Do I keep the real weather conditions and inject a fake temperature? How many people will post saying the weather is "broken" if I do that? How much effort needs to be spent educating people before they know it's intentional? Will we have to stop saying we use real weather? Will all of this drain time from our other projects?". That's just off the top of my head. As you can see, a very simple update can have a number of complicated factors behind it.

But having said all that, I still want to do something about this soon. I'd like to change to an in-house weather system, but may have to reach some kind of compromise in the meantime. Keep the suggestions coming, they help spark ideas. :) Several have come from this thread and it will influence the design of our final weather system.

Perhaps I wasn't clear enough. The technical challenge of just changing the temperature is the simplest thing anyone could possibly do. And that's all a player has to consider, "just change the temperature! It's only a variable!". Of course, but it's not that simple in reality.

I tried to point out all the other things related to changing that number which we have to consider as devs. Like changing it for races in 1 weeks time, and how that will affect their forecasts, which are currently text we get from a weather service, as one example. Do we scrap that forecast or hack it in to the forecast with some kind of ugly string search? Both are poor solutions. Essentially, if we're going to forcibly change this number, we need to write a new weather engine with a new forecast system etc. We probably need to announce that we're not using real weather any more and a whole bunch of other things.

If all we had to do was change numbers life would be much easier. :P

We are going to come up with the simplest solution to this as quickly as possible. I pointed it out to explain to people why we don't just slap on what seem like obvious fixes all the time. Things that look so easy when the only consideration is "change this number" from an outside perspective. There are often so many factors beyond the obvious fix that get impacted, that a small change becomes a big consideration.

I have gotten some ideas from this thread though, including your last post. It's not always what people say directly that is the idea, sometimes it just makes you think about that idea, then another one comes off of it. I feel a lot closer to a solution actually having read these posts. They've spawned quite a few creative ideas of ways to manipulate the data we have and come up with a new weather system. Sometimes when you say "just change that number", it's so obvious it's actually the last thing you think of. It got me thinking... I probably can do something with the data we already have, and manipulate it to generate random, but consistent climates for each track that are realistic.