Troubleshooting

Fixes for the most common oxide-weather problems — startup, flickering weather, regions, seasons and snow, storms and blackouts, the tablet app and alerts, real-world weather, admin tools, settings and integrations.

Common problems with oxide-weather and how to fix them. Work down each list from the top — the first fix is the most likely one.

Most problems leave a clue in the server console (the window, or txAdmin's live console, where your server prints its messages). Lines from this resource look like [WARN][oxide-weather][...]. See Console lines worth knowing for what each one means.

Startup Problems

Weather and Time Problems

Region Problems

Season, Temperature and Snow Problems

Storm, Lightning and Blackout Problems

Weather App and Alert Problems

Real-World Weather Problems

Admin Tool Problems

Settings Problems

Problems for Other Resources

Performance

General Debugging

Check the conditions where you stand

/weather inspect

One line telling you the region, the weather, the rain amount, the temperature, whether you are under cover, and the road wetness and ice at your feet. This is the fastest way to prove or disprove almost anything on this page.

Check what is scheduled

/weather forecast
/weather front list
/weather blackout list
/weather season

Console lines worth knowing

oxide-weather writes to your server console through o-link's logger, tagged with a level, the resource and a category.

LineMeaning
[INFO][oxide-weather][lifecycle] Weather synchronization readyThe resource started correctly
[INFO][oxide-weather][persistence] Weather simulation restored from SQL.The saved world was loaded
[INFO][oxide-weather][weather] Weather changedA normal weather change
[INFO][oxide-weather][fronts] Weather front spawnedA storm was created
[INFO][oxide-weather][admin] ...An admin made a change. The data shows who
[INFO][oxide-weather][zones] ...A region was created, changed or deleted in the zone editor. The data shows who
[INFO][oxide-weather][command] ...The reply to a command run from the server console
[INFO][oxide-weather][broadcast] ...The public forecast and alerts were recalculated
[INFO][oxide-weather][realworld] ...The real-world mirror found its location, took over the weather or handed it back
[WARN][oxide-weather][realworld] Real-world weather update failedAn Open-Meteo request failed. The cached forecast keeps playing. See Real-world weather problems
[ERROR][oxide-weather][realworld] Real-world location not found. Check the Location settingOpen-Meteo has no place by the configured name
[ERROR][oxide-weather][bridge] ...A change requested through o-link failed with an error. The data shows the method and the calling resource
[WARN][oxide-weather][config] ...A config value was unusable and a default was substituted
[WARN][oxide-weather][settings] Invalid saved setting; using factory defaultA saved setting was out of range and was repaired
[WARN][oxide-weather][permissions] Rejected setter from untrusted resourceA resource tried to change the weather without being on the trusted list
[ERROR][oxide-weather][persistence] Weather state could not be loaded...The database could not be reached, or the table could not be created. See The weather never loads
[ERROR][oxide-weather][persistence] Saved weather state does not match the current settings...A restart-only setting conflicted with the saved world, so it was backed up and the world started fresh. See My regions and weather reset after a restart
[ERROR][oxide-weather][persistence] Weather checkpoint could not be saved...A save failed. It will be retried

There is no separate debug switch to turn on. If you want more detail than this, the level filter lives in o-link's logging configuration.

Prove a feature works end to end

/weather set thunder            -- everyone should see a storm
/weather front spawn            -- a moving cell should appear in /weather front list
/weather time 3 0               -- everyone's clock should read 03:00
/weather blackout on            -- the lights should go out
/weather season winter          -- snow should become possible
/weather inspect                -- read back what the server thinks

Start from a clean state

If something is badly wrong and you want to rule out corrupted saved data:

Stop the resource: stop oxide-weather.
In your database manager, delete the row in oxide_weather_state whose state_key matches your simulation key (global unless you changed it).
Optionally, delete every row in oxide_settings where resource is oxide-weather to reset settings too.
Start it again: start oxide-weather.

This deletes any regions you drew in /weather zones. Note down what you want to keep first.

Getting Help

If nothing here solves it:

  1. Note the exact console lines around the problem, including the [WARN] and [ERROR] ones.
  2. Run /weather inspect where the problem happens and note the output.
  3. Note your framework (QBCore, QBX or ESX), your o-link version from o-link/fxmanifest.lua, and your oxide-weather version from oxide-weather/fxmanifest.lua.
  4. Note whether any other weather or time resource is running.
  5. Contact Oxide Studios support with all of the above.

Please do not edit any file inside oxide-weather other than the config files in shared/, the language files in locales/, and the SQL files in sql/. Everything else is packaged and cannot be edited. If a fix needs a code change, support will tell you or ship an update.