A saved VRML world is usually missing most of itself. The .wrl file, the plain-text heart of a 1990s virtual reality scene, survives in archives by the thousand, but it rarely arrived alone. The geometry it contains is real; everything that made it recognizable as a place was fetched from somewhere else.
The world shipped in pieces
A VRML scene listed its outside links in plain sight. Textures came through ImageTexture (Texture2 in the 1.0 days), sounds through AudioClip, and whole sub-scenes through Inline nodes — URLs the viewer hit at load time. The Library of Congress’s format description for the VRML family notes it was meant for a “distributed web environment,” hyperlinking out by design. The Castle example that floated through 1990s tutorials, built by Mike McCue at Paper Software, shipped castle.wrl with GIF textures and inlined pieces; a surviving copy kept at TECFA records that the original has since “disappeared from the Web.”
A VRML viewer therefore may need to retrieve an entire bundle of referenced resources before the scene looks complete. A lone .wrl can be a stage with its props absent.
The viewer was part of the appearance
Which plugin you had also set what you saw. Netscape’s Live3D read VRML 1.0 and added proprietary extensions such as animated textures, while SGI’s Cosmo Player pushed the newer 2.0/97 spec; worlds tuned for one ran fully only in it. Even ordinary files were hostage to interpretation. Relative links, plugin-specific behavior, and vendor extensions could change what appeared when the same world was opened in a different viewer.
Recovering an intelligible version
Recovery means reassembling the package and matching it to software. An open-source viewer such as FreeWRL, Xj3D, or view3dscene reads the plain-text geometry without complaint, but it can only fetch files that still exist. Textures stored beside the .wrl come back if they were gathered too; an Inline world renders as nothing when its URL has gone dark.
The limits of recovery
Even a complete file set hits viewer differences. NIST’s Digital Library of Mathematical Functions, which still offers VRML/X3D behind a WebGL display, reports that some browsers “are not capable of handling the complex files necessary for our visualizations” and that it found no viewer working consistently on Linux — which is why its modern default is WebGL instead.
What survives, what is gone
Geometry is the survivor: vertices, faces, and materials remain readable ASCII. Appearance and behavior are the casualties. A recovered world without its textures is gray shapes; without its plugin-era extensions, animation, sensors, and scripted touches are lost regardless of whether the code survived. The DLMF could move on; the old worlds have no successor runtime waiting for them. Only the pieces someone thought to keep still render.