Hi all. Apple has bought Darksky. They're not going to accept new signups to the API and it will stop working at the end of 2021 https://blog.darksky.net/
Hi. The program stopped to receive weather data and always show "webquerry failed" status. What can be the problem? I changed nothing before it stopped work.
Hi guys, I am new at this and I will really appreciate it if you can help me. I downloaded the file "rf2WeatherPluginV1.11b.zip" but I can't find the files that CORTI says in his tutorial >>> -rF2GeoData.xml , rf2WeatherClient.exe and Ionic.Zlib.dll <<< Is there another link where i can download those files? Thankyou
Thankyou Corti. I had downloaded it before but these files did not appear, probably because I had not logged. Now I made the loggin, downloaded again and everything ok.
V1.12a As DarkSky locked creation for new API keys, I added ClimaCell was added (https://www.climacell.co/weather-api/pricing/ for the free key). Thx @Corti for the hint with the available API Also some changes to openweathermap api response interpretation (however the api is weak anyway) Edit: added (again) a minor rain trigger threshold in V1.12a.
Thanks for the new update, always appreciated. I have found an issue that when using the new UI, you must be in the game first and then go to Windows to access Dedicated Server and the Weather plugin. I always start the weather client first then I go into the Dedicated Server options to host the game but when using the new UI it doesn't connect - it sees the track but normally when you finalise the session (add/remove AI) it says connected and away you go. Using the old UI, I would start the weather client, then go via the old UI to setup/host the game and on the final step add/remove AI it would say connected and then ingame the weather client works perfectly. I am assuming it doesn't working because the game is already running and the client must push through stuff to the open exe? Anyway around this do you think? It is definately a result of the limitation of the new UI no question.
You should use the UUID to control whether you want to connect to the dedi or your game. Start the dedi by a link or ingame command line with a different player profile. That means a 2nd player folder, e.g. player2. In this dedi profile folder, set in the multiplayer.json the UUID different for the weather plugin than for your rf2 driver player folder. Then connect to the right uuid. In case you want only control weather via a dedi but not for offline practise I would switch off the weather plugin for your driver profile.
Thanks Stefan, I might have to do some homework on the link/command line but what you said makes sense and I understand your logic.
As a workaround with one profile only (imo not recommended anyway) you could try: Disable plugin in the custompluginvar json by text editor Start rf2 Enable plugin in editor, save Start dedi (Disable again, save) That could work..
Thanks so much Stefan - I can confirm that Option 2 works perfectly. (disable/enable the custompluginvar). I don't think I need more than one player profile (???) but the solution you provided was easy to do and worked a charm.
What is the best API? OpenWeatherMap or ClimaCell? DarkSky does not accept new members and Wunderground I cannot generate API.
I updated to V1.13. For climacell I use now every 10min a forecast poll. For rolling in clouds, this allows me to start getting them in when forecast says rain in next 40 minutes. I just observed a happening rain situation in germany. Climacell reported 33% clouds (which is almost clear sky in rf2) even close to a beginning rain area. But with the forecast the plugin was able to roll in a cloud cover IN TIME (as it takes ~20minutes to get them in) so the visual change to rain was less sudden (as rf2 blends in an additional cloud layer with rain which allways makes for some kind of sudden change).