Meta Switched Off Its Worlds in June. Nobody Could Export Them — Now Read Your BIM Contract
Meta removed Horizon Worlds from Quest on 15 June 2026 and community worlds were never exported — $88B of Reality Labs losses later. What AEC teams should demand about open formats before signing.
Extended reality earns its keep in exactly the places nobody makes a keynote about. Surgeons at Johns Hopkins guide instruments with XR overlays because a floating vector beats a printed CT scan mid-operation. Vancouver International runs 3D simulations of passenger flow because a queue you can walk before it exists is cheaper than one you fix afterwards. The pattern is old and boring: a headset sticks when it answers a question someone was already asking. Hold that thought against what Meta switched off in June.
On 15 June 2026, Horizon Worlds stopped existing on Quest headsets. Meta had delisted it from the Quest Store on 31 March; Horizon Central, Events Arena and Bobber Bay went dark the same day, and the platform now survives as a mobile-only app. The bill is not in dispute: Reality Labs has absorbed roughly $88 billion in cumulative operating losses since the end of 2020, including $4.62 billion in the second quarter of this year alone, reported on 29 July. Kevin Brookshire’s 2023 GoodFirms post-mortem read the shape of it early — 11,000 layoffs, and John Carmack, the man who more or less taught the industry to render a 3D world in real time, walking out the door. Zuckerberg squashed the “we’re quitting the metaverse” rumours even as the company pivoted its whole vocabulary to generative AI. A $10 billion budget bought a room nobody booked.
Why did it land this way, when Snap’s decade-long Specs effort just re-anchored on Qualcomm’s Snapdragon XR silicon (PAZ covered that partnership in April) and Valve moved 103,000 Index units in a single quarter? Because Valve shipped Half-Life: Alyx first and the platform second. People had been begging for that game since 2006; the headset was the toll to enter, and they paid it gladly. Meta inverted the order — it built the world, then went looking for a reason anyone should live in it. The pandemic was the bet: Zuckerberg read remote-work-from-a-headset as the new normal and put every egg in it. Shared virtual worlds, though, are not new — EverQuest and World of Warcraft ran them thirty years ago, without a headset at the door.
←TODAY: Meta switches off its worlds after ~$88B in Reality Labs losses, while purposeful XR quietly saves lives in operating theatres. →3012: The interfaces that survive to the next century are the ones that solved a real desk problem, not the ones that promised a new world. Fulcrum: Adoption was never about the render quality — it was always about whether the file answered a question someone actually had.
Here is the translation to your desk. Every tool your practice adopts this quarter is either a Horizon Worlds or an Alyx. The new AI clash-checker, the fresh cloud round-trip, the parametric plugin the vendor demo made look inevitable — each one is a vision until it survives contact with the bricklayer. The test is not the sizzle reel. The test is whether it shortens the exact four hours you lose every week to a specific, nameable failure: the IFC that reimported with flipped normals, the schedule that didn’t map, the door tag that vanished on export.
And there is a longer risk hiding in the metaverse rubble. Meta’s own shutdown notice was explicit: community-built worlds would not be migrated or preserved. Years of volunteer world-building did not get sold, exported or archived — on 15 June it simply ceased to exist. That is the failure mode my generation learned to fear. The buildings that aged worst were not the ugly ones; they were the ones nobody could open because a proprietary format went silent. When you pick a stack, ask the one question that outlives the vendor: when the company disappears, can a 25-year-old still read the file? That is precisely why IFC — open, plain-text, un-compiled — is the most important language the AEC industry has shipped in a century. An IFC line like #42=IFCWALL('3vB2YO$...',#5,'Wall.01',$,$,#36,#40,$); is legible forever: #42 is the entity id, IFCWALL the class, the string is its permanent GUID, #5 points at ownership history, #36 at placement, #40 at geometry. Your Notepad already speaks it.
Atelier: The Büro adopting a new AI or XR tool this week should run it through one filter before signing — not “is it impressive” but “which recurring, timeable pain does it remove.” Your Monday move: pick the single tool your team is closest to buying and export a real project out of it, then try to reopen that export in anything else. If only the vendor’s own software can read it back, you have found a Horizon World, not an Alyx — negotiate an IFC or open-format guarantee into the contract before the pilot, not after.
Hack: Open a vendor’s export and read every wall yourself, without asking the vendor’s software for permission. IfcOpenShell parses the plain-text STEP file directly, so a model outlives whatever drew it.
import ifcopenshell
model = ifcopenshell.open("tender.ifc")
for w in model.by_type("IfcWall"):
print(w.GlobalId, w.Name)
Run it against any IFC you have. Every wall prints its GUID and name from raw text — no licence, no cloud, no login. That loop is the receipt that your data is yours: if it runs, a 25-year-old in 2051 can run it too. If your “BIM” tool can’t produce a file this loop reads, you don’t own a model — you’re renting a view of one. Export something today and try it before you renew anything.
Source: GoodFirms
SOURCE · ↗
PAZ Kaffi · multidisciplinary editorial, led by PAZ Academy