Update (September 16, 2004):

One bug that hasn't been fixed from Spazz3D to Vizx3d is the very  annoying excess texture bug. It occurs when a folder has about 100 potential textures (or more), the thumbnail option is in play, and the user visually surfs to the texture using the scroll bar function. As the user surfs to the near bottom of the thumbnailed textures, the program simply closes - no warning, no offer to save file, it just closes. An obvious workaround is to use the selectfile function and avoid the thumbnails.

Original story (September 5, 2004):

For the most part, the difference between 1.1 versions and 1.2 versions is fairly minor, a few corrected typos, a few fixed bugs, but nothing major, frequently nothing noticeable. And then the reviewers of the new Vizx3d 1.2 started to really look at it and noticed it's like a completely new piece of software. There are literally dozens of new features.

Vizx3d (which does both X3D and VRML effortlessly) is the beloved daughter program of Spazz3D. Spazz3D was the hands down favorite of VRMLists during the late 90's and early 00's. It is still used by most coders. Vizx3d opened the brave new world of XMLized VRML - X3D. X3D is expected to shortly overtake all other 3D formats, and because it's really XML with a fancy name, be transparently useable by surfers once browsers begin to handle XML better than currently.

Vizx3d 1.1 was the first version to suggest that it was more than just a new name for Spazz3D. It did many new things (multitexturing, movie textures) that were new to Web3D. Basically though, it was still just Spazz3D with great X3D support.

The new 1.2 version adds powerful features normally only seen in programs priced in the $700+ USD range. The most stunning of these was that it now imports (and exports) virtually any 3D format. Since the program doing the importing is for X3D export, importing another 3D format produces better results, think IDE. Standalone converters have their place, but they don't always do things nicely when X3D is the ultimate format.

The only bug the testers noticed was that when a file of sufficient complexity was imported, Vizx3d simply closed, no explanation. The old header bug in Vizx3d 1.0 and 1.1 is partially fixed, though you need to be online, the header only refers to the online DTD's, not a local copy.