DX Studio: Worldweaver’s 3D Engine and IDE, Its Features, and What Replaced It

DX Studio was a Windows tool for interactive 3D games and simulations, with editors, JavaScript and DirectX 9. Here's how it worked, what it cost, and what to use instead.

Flat illustration of one low-poly 3D scene connected to icons for an app, a browser, a document and linked gears, representing DX Studio's interactive 3D publishing options

DX Studio was a Windows tool for building interactive 3D applications, games and simulations. It combined a 3D engine, visual editors and JavaScript scripting in one package. The UK company Worldweaver began developing it in 2002 and released the first version in 2005. It found a following in education and among hobbyists, with a free edition alongside paid ones. Its last release was version 3.2, in December 2010, and it hasn’t been updated since.

This profile covers what DX Studio was, how it worked, its versions and editions, what was made with it, why it faded, and which tools do the same job today. Facts were checked against contemporary reviews, release reports and other sources in October 2026.

What Was DX Studio?

DX Studio was a proprietary 3D development environment for Windows from Worldweaver Ltd for building games, simulations and interactive presentations. It combined 2D and 3D editors, a DirectX 9.0c renderer and JavaScript scripting, and could publish to a standalone EXE, a web player plug-in or an embedded ActiveX control. Its final version, 3.2, was released in December 2010.

DX Studio at a glance

DeveloperWorldweaver Ltd, UK (founded 1996 by Chris Sterling)
DevelopmentStarted 2002; first release 2005
Final release3.2, December 1, 2010 (no updates since)
TypeProprietary 3D engine and IDE with 2D and 3D editors
ScriptingJavaScript; plug-in SDK in C++ and HLSL
GraphicsDirectX 9.0c with pixel and vertex shaders
PhysicsPhysX and Bullet support (from version 3.0)
Runs onWindows only
PublishingStandalone EXE, browser plug-in, ActiveX component (C++, C#, VB.Net, Office)
Editions (2009)Freeware (limited), Standard £175, Pro £375
UsersAbout 30,000; used in 20+ game education courses

A Short History of DX Studio

Worldweaver was founded in 1996 by Chris Sterling to make PC games and business mapping (GIS) software. Work on DX Studio began in 2002, and version 1 shipped in 2005 (Wikipedia’s DX Studio article).

The major releases built it from a presentation tool into a full development suite:

  • Version 2.0 (June 2007) added a full 3D model editor, so users could build projects from scratch instead of only importing models. It also brought a new lighting engine, post-processing effects, per-pixel bump, opacity and specular maps, COLLADA model support and an online library for sharing models, materials and scripts (Game Developer’s report).
  • Version 3.0 (2008–2009) added live 3D and 2D editors with real-time lighting, a terrain editor, a Firefox plug-in, support for the PhysX and Bullet physics libraries, and OGG video.
  • Versions 3.1 and 3.2 followed, with 3.2 on December 1, 2010, as the final release.

Reviewers liked it. Digital Arts and Computer Active! both rated version 3.0 at 4 out of 5 in 2008, praising its effects, real-time previews, ease of use and low price. Their main complaints were that web deployment needed a plug-in, there was no Mac support, and it relied on imported 3D models for serious work. Its user base grew to around 30,000.

How DX Studio Worked

A DX Studio project was a document: a set of 2D and 3D scenes described in XML, with textures, models, sounds and video packed into the same file using ZIP-compatible compression. Optional encryption protected the content. You built scenes by dragging and dropping in the editors, then added behaviour with JavaScript, which could control scenes, objects and media in real time.

Rendering used DirectX 9.0c, with pixel and vertex shaders. Built-in effects included lens flares, water ripples, particle systems, real-time shadows, 3D video projection (MPEG or AVI), 3D positioned sound, and post-processing such as bloom and sepia. Advanced users could write custom effects with a plug-in SDK in C++ and HLSL.

Finished documents could be delivered four ways:

  • A standalone EXE, a single redistributable file that checked the player’s PC and installed any DirectX update it needed.
  • The DX Studio Player in a web browser, through a plug-in.
  • An embedded ActiveX component in C++, C# or VB.Net applications, or in Microsoft Office.
  • External control of a running document from other software, through COM or a TCP/IP port.
One DX Studio document, four ways to ship it Every route ran on Windows and DirectX 9.0c, which is why DX Studio aged out with them. DX Studio document XML scenes ZIP-packed assets JavaScript logic DirectX 9.0c renderer Standalone EXE One redistributable file that installs DirectX if needed Web player plug-in Browser plug-in (including Firefox); a 2009 security flaw was fixed in 3.0.29.1 Embedded component ActiveX control for C++, C# and VB.Net apps and Office External control Other apps could drive a running document over COM or TCP/IP Sources: Wikipedia, DX Studio; Core Security advisory CORE-2009-0521 (CVE-2009-2011)
A DX Studio document could ship as a standalone EXE, through a browser plug-in, as an embedded ActiveX control, or under external control, but every route depended on Windows and DirectX 9.0c.

Editions and Pricing

DX Studio was proprietary, sold in tiers. In January 2009, MCV listed three editions (MCV’s tool focus):

EditionPrice (2009)What it included
FreewareFreeLimited: no networking, model export or shader effects, and caps on physics objects and meshes
Standard£175The full editor, without networking, the database client or player re-branding
Pro£375A full commercial licence and royalty-free publishing

Site licences were also available, and a Corporate Licence included the full source code of the player.

What Was Made with DX Studio?

DX Studio was used more for interactive presentations, training simulations and education than for commercial games. In 2009, Worldweaver said it was used in more than 20 game education courses worldwide, and a team in the 2008 Dare to be Digital student competition used it. Small free and indie games made with it include Ballistic Bonbon, a mouse-driven physics shooter and puzzle game, and iGrow Game, both listed on ModDB’s DX Studio engine page. No major commercial release is known to have used it.

Ballistic Bonbon gameplay screenshot, a mouse-driven physics shooter made with DX Studio
Ballistic Bonbon, a free physics shooter built with DX Studio.

Is DX Studio Part of DirectX? Is It Still Available?

It isn’t a Microsoft product. The “DX” refers to DirectX, the Microsoft graphics technology it was built on, but DX Studio was made and sold by Worldweaver, an independent UK company.

It’s no longer developed. Version 3.2 (December 2010) was the last release, and Worldweaver hasn’t updated it since. Copies still circulate on download archives, and some users report that it runs on newer versions of Windows, but it gets no fixes or support.

Don’t install its old web plug-in. In June 2009, Core Security reported a flaw in the DX Studio Player’s Firefox plug-in that could let a malicious web page run commands on a visitor’s computer. Worldweaver fixed it in version 3.0.29.1 (Core Security’s advisory, CVE-2009-2011). Modern browsers no longer support this kind of plug-in at all, but it’s a good reason to treat abandoned browser plug-ins with caution.

DX Studio Alternatives

The jobs DX Studio did, from 3D games to interactive presentations and training simulations, are handled today by actively developed tools:

  • Unity: a common modern choice for interactive 3D, training simulations and games for interactive 3D, training simulations and games, with an editor and C# scripting. See our Unity engine profile.
  • Godot: a free, open-source engine with a full editor and 2D and 3D tools. See our Godot engine profile.
  • Babylon.js: an open-source JavaScript 3D engine that runs in any modern browser with no plug-in, which is what DX Studio’s web player tried to do (Babylon.js’s website).
  • Panda3D: an open-source engine driven from Python, often used for simulations and research. See our Panda3D profile.

For more engines from the same era, see the retro and classic engines in our game engine directory.

Key Takeaways

  • DX Studio was a Windows 3D development environment from the UK company Worldweaver, released in 2005, with editors, a DirectX 9.0c renderer and JavaScript scripting.
  • It could publish to a standalone EXE, a web plug-in or an embedded ActiveX control, which made it popular for presentations, training and education.
  • It came in Freeware, Standard and Pro editions; in 2009 the paid editions cost £175 and £375.
  • It isn’t part of DirectX or a Microsoft product, despite the name.
  • Version 3.2 (December 2010) was the last release, and its old browser plug-in had a 2009 security flaw.
  • Unity, Godot, Babylon.js and Panda3D cover what it did today.

Conclusion

DX Studio made interactive 3D unusually accessible for its time, with editors, scripting and one-click publishing in a single affordable package. It was tied to Windows, DirectX 9 and browser plug-ins, and when those went out of date, it went with them. Its ideas live on in the engines that replaced it, which now run in the browser and across platforms without plug-ins.

For more engines across every genre, browse our game development hub.

Scroll to Top