Weather forecasts that match...

This is partly a suggestion and a frustration.

Two races in a row I had by far the quickest car. I set my car up for a dry race, since the whole week, forecast is dry. Then, when I want to click the qualifying results, I see it's a wet race. My car is on inters however, meaning +10 seconds in qualifying to those who started on full wets. Same in the race, I lose 10 seconds in the first lap, plus I have to make an extra pitstop. 

For what...? I understand the extra depth in gameplay but this makes it a lottery and just annoying for those caught out. 

When selecting advance strategy, if the weather is wet, it'll switch to those tires. So in your advanced strategy, you had chosen Intermediates.

If I have softs selected for all my stints, including the first one, but have the avanced set up for full wets in rain, then will it switch it automatically for me for qualifying?  Even if I have softs for the first stint?  If so, does it make a difference how  many laps I have it set to in advance to switch with ragards to qualifying?  Thank you for your time.  I am new so I am just trying to understand.

yes it changes it self if u had softs for the first stint to wet or inters

Oke, thanks.

But would that still make it a lottery? Cause it might be inter-weather when I fitted wet tyres, right? E.g. it's light rain, and my 'advanced strategy' puts me on full-wets. 

Meh - I'll just try to be online 30 minutes before the lock then. 

You'll be fine Jaap, if it rains it always goes to full wets. Trust me :)

Alright - learned another thing from you then :) thanks again!

Your driver will pit as soon as possible, but when it comes to them running out of fuel, they'll pit. But unless a recent update has fixed this, then even if it's monsoon weather, the advanced setup won't prevent your drivers pitting for Slicks if it's set up like that in your strategy. Then they'll pit again according to the advanced strategies for Wets and do this for as many stops you have planned. It is retarded.

I may be wrong but the issue mentioned by Ethan will be addressed in the next update.