WEATHER//ROOM
Rain, wind and clouds inside a familiar room: weather from a chosen place becomes a spatial experience, with a timeline reaching a day into the past and future
- Type
- Art experience
- Platforms
- Headsets · mobile · desktop
- Technology
- Meta Immersive Web SDK · three.js · Open-Meteo · MET Norway
- Updated
- 16 October 2026
Weather you can step inside
WEATHER//ROOM brings weather from a chosen place into the space around you. Rain leans into the wind, splashes and water appear on detected surfaces, and snow briefly settles where it lands. Clouds, haze and virtual light connect these layers into one atmosphere. During a storm, a spatial lightning bolt, a flash and rolling thunder respond to the same event.
In a headset, this adds to the real room you can still see rather than transporting you elsewhere. On an ordinary screen, it is a 3D preview with weather and time controls. It does not cool the air or physically simulate meteorology: the data becomes artistic material.
The room as medium
The point is not to put a little cloud on a table. It is to change how the whole room reads: open air becomes a place for rain, the table a place for its impact, the floor a base for water, and a moving hand the beginning of a brief weather event. You are inside what is happening rather than inspecting an object from outside.
One reference is Olafur Eliasson's The Weather Project, where light, mist and reflection work at the scale of the space and the people in it. For mixed reality at home, that is not a reason to obscure the view. Furniture and walkways should remain visible; the interface is there to adjust the experience, not take over the room.
Rain becomes convincing through a chain of causes rather than a particle count: falling, striking a surface, splashing and gathering water. Wind is legible in movement and bending precipitation, not just a number on a panel. Clouds change the upper volume and light; temperature and pressure belong to an artistic reading of weather, not a promise of a physically accurate environment. Shared light connects rain, snowflakes, air currents and water highlights so they do not look like unrelated effects.
What the app actually knows about the room
Showing an image of a table is not enough to make a drop hit it. The app needs surface information that the browser and device have agreed to supply:
- Surfaces and 3D geometry help distinguish levels, such as a table and the floor beneath it. A falling drop seeks the nearest suitable surface below it; water uses the lowest measured level.
- Testing an individual ray finds a particular point on a surface. A few such measurements help when geometry is incomplete, but do not amount to a full room scan.
- A depth image, when available, helps hide virtual rain behind a real object. That is a different task: hiding a drop behind a cupboard does not establish where it landed.
The surface map is approximate. Incomplete measurements can mistake furniture for the lowest base; unmeasured areas have no established contact with the room. Without surface data, an explicit preview volume remains, not an invented scan. Depth availability is not guaranteed either. Tracked hands have a separate virtual approximation of their shape to hide particles, while a field around the hand pushes rain and dust aside. This does not promise exact collisions with every finger.
How to open and try it
- Open WEATHER//ROOM in your browser. On a phone, expand the compact panel when you need more settings.
- Check the place and weather source on the panel. You can choose a city; the ordinary browser panel also accepts latitude and longitude. Automatic device or IP lookup can get the city wrong, so read the label rather than assuming this is the weather outside your window.
- For mixed reality, choose Enter AR if the button is available and respond to the browser's permission prompts. Quest 3 is the primary headset target; Android with WebXR AR is a secondary path. Without AR support, stay in the browser preview.
- Try the −24h ← NOW → +24h timeline. In the browser, use a mouse, touch or keyboard; −6h / +6h steps through time and NOW returns to the current hour. In XR, grab the knob with a hand or controller ray, or pinch the timeline strip.
- Turn Sandbox on to add your own event. A hand clap triggers thunder and lightning; with a controller, use a quick downward strike instead — do not hit the controllers together. A quick sideways sweep creates a gust. Thunder and gust buttons are available too.
Sandbox gestures are temporary: they do not rewrite the forecast or selected hour. In XR, move the panel or timeline using the bar revealed on hover beneath it; release it to park it for the rest of the session. Moving the timeline should not scrub time. RU / EN changes the interface language, not units or data sources. Browser audio first needs a user action; there is no sound when Web Audio is unavailable.
Where weather and time come from
Open-Meteo is tried first. If unavailable, the app tries MET Norway, then wttr.in; a labelled synthetic demo is used only if all three fail. The panel names the actual source. This matters because the services supply different information and are not equivalent in every respect.
The timeline spans a day before and after the present, but data coverage depends on the source. Open-Meteo supplies history and forecast; fallback services may not cover past hours, and wttr.in uses coarser three-hour blocks. Missing values display as --, not invented measurements. Outside the loaded series, beyond data appears: the app does not present the nearest known value as weather for another hour. Switching to MET Norway also changes the meaning of pressure: it is sea-level pressure rather than surface pressure.
Scrubbing reads the already loaded series without making a request for every movement. Time is stored as unambiguous UTC instants, so the browser timezone does not shift the selected hour. Background refresh is limited to one request per 15 minutes, with older data marked cached. A quiet scene may simply mean dry weather at the selected hour, not broken rain.
Platforms and the limits of verification
Quest 3 is the main target, not a guarantee of a fully known room. Surfaces, hand tracking and depth depend on permissions, the browser and available data. Android may expose fewer capabilities, with reduced effects provided for that path. In browsers without WebXR, including unsupported versions of Safari on iOS, it is AR entry that is unavailable: a flat 3D preview and on-screen panel are provided. That is not the same as verification on every phone.
The project documentation records individual runs on a real Quest 3: rain, the spatial panel and the timeline were observed over the room's passthrough view. That is not acceptance of the entire current version. The latest gesture and room-lifecycle checks, dated 13 October 2026, used IWER, a browser-based XR emulator, and controlled geometry fixtures. Phone controls were exercised at emulated screen sizes; WebKit startup was investigated separately.
Real room scans, hiding effects behind furniture, water contrast on different floors, device gestures, Android behaviour, comfort and frame pacing in the current version remain limits of verification. An emulator does not establish them. Fixing a problem in a test room does not mean it has already been rechecked in yours.
Implementation and sources
The experience uses the Meta Immersive Web SDK (IWSDK) and three.js; IWER supports development and XR emulation. Weather data is kept separate from brief events: light, lightning and audio receive a coordinated signal, while a gesture does not change the underlying measurements. This keeps the interface an instrument and the room the place where things happen.
This article was checked on 16 October 2026 against the project's “The room as medium” and app description and verification notes. Source code is available separately.