X3d examples

X3d examples DEFAULT
  42 X3D Models      X3D Model DescriptionsAllenDuttonAllen DuttonLaser scan by CyberwareAllenDuttonVillageAllen Dutton VillagePrimitive village. Move mouse over the hut roofs to see a demonstration of sensors and interpolatorsChairChairA chair for a room, modeled as a Prototype for reuse.Chess8LevelsChess 8 LevelsMulti-layered Chess Board in 3 dimensions.ComputerKeyboardComputer KeyboardA computer keyboard for the control panel in the CVN bridge control. The buttons animated to be pushed in when touched.DeadReckoningComparisonsDead Reckoning ComparisonsCompare different dead-reckoning algorithms to see relative effects of velocity and acceleration on animation smoothness.DeskDeskA reusable desk prototype - click on drawers to open/shut.DeskLampDesk LampA file decribing a desk lampDirtBikeDirt BikeSimple dirt bike model.DraggingSphereDragging SphereA sphere that drags its tail around a box in the XY-planeDuttonVillageDutton VillagePrimitive village. Move mouse over the hut roofs to see a demonstration of sensors and interpolatorsFishingLureFishing LureUnique fishing lure ("If it were any more real, I would actually be fishing"). Final project for introductory X3D course.FormulaOneRaceCarFormula One Race CarA FormulaOne Race Car running in a predefined pathHomeAquariumHome AquariumStudent project showing a small aquarium.HomeInCreteGreeceHome In Crete GreeceSomething Special My Home Villa In Crete GreeceIkeaBeadToyIkea Bead ToyX3D example Model of an ikea bead toy. It has intense extrusions and animationIkeaBenchIkea BenchX3D example Model of an Ikea BenchIkeaBlueChairIkea Blue ChairX3D example Model of an Ikea Blue ChairIkeaGreenChairIkea Green ChairX3D example Model of an Ikea Green ChairIkeaRockingHorseIkea Rocking HorseX3D example Model of an Ikea Rocking HorseIkeaTableIkea TableX3D example Model of an Ikea TableKeyboardEightyEightKeysKeyboard Eighty Eight KeysEight-eight key keyboard, extrapolated from VRML Sourcebook Figure 24.4, including animation of key movements coordinated with sounding of key when touched.LaetitiaLaetitiaRendered woman's body model, created using 3d Studio Max and then translated into X3D and VRML.LaetitiaSprintsLaetitia SprintsAn animation of human body modeled and animated in 3d Studio Max environment and then translated into x3d environment.LaetitiaWithDvdControllerLaetitia With Dvd ControllerAn animation of human body modeled and animated in 3d Studio Max environment and then translated into X3D environment. Instead of using 'mesh deformation' like in LaetitiaSprints.x3d (by using Character Studio's physique modifier), which was not modular and compact enough for x3d environment, I used this time 'segmented animation' approach: 1- At first we divided up the body into segments such as head, upperarm and forearm... 2- Then we linked each segment to a segment of biped skeleton such as head to bip-Head, forearm to bip-Forearm... (Biped is a pre-built skeleton structure in 3d Studion Max) 3- After that we could create the walking animation by using biped's animation features. 4- We hid all of the biped segments and then did some tweaks on the body at vertex level to fix the breaking points during the animation. 5- It was ready to be exported into VRML and then to be translated into x3d. To have it work properly in x3d environment, we had to add new routes connecting interpolators with nodes. (except all SCALE-INTERP's and some SCALE-ORI-INTERP's) 6- Then we had to fix the main position interpolator (Laetitia-POS-INTERP) by defining new keyValues. (Adding new translation values to its transform node doesn't help anything at all.) 7- Finally we deleted unnecessary interpolators from the file... After that we added DVDController and WaypointControler to have more control of the path she walks...LaserPrinterLaser PrinterHow a laser printer worksPinballTablePinball TableA pinball table with some ball animations.PlayRoomPlay RoomX3D example Model of a Play roomProjectileInterpolatorArenaProjectile Interpolator ArenaA projectile motion application which displays range and max height values accoding to Vi and theta inputs. Calculations for drag force with air density are also taken into account.ProjectileInterpolatorPrototypeProjectile Interpolator PrototypeA proto which simulates x-y plane projectile motion.ProjectileSliderBarPrototypeProjectile Slider Bar PrototypeA generic slider bar prototype. Colors, size of the bar and name are changable.PropellerControlPanelPropeller Control PanelController buttons and slider for a propeller.RoomRoomA simple room containing protoype instances for chair, desk lamp, wall clock, etc.StealthHeloStealth HeloA sort of Stealth Helo I designed and created.SweetHomeSweet HomeModel of one of the housing types in La Mesa Housing Area.The model is mostly in scale.SweetHomeFullDetailSweet Home Full DetailModel of one of the housing types in La Mesa Housing Area. The model is mostly in scale.this file contains the detailed version of the model.SweetHomeLowDetailSweet Home Low DetailModel of one of the housing types in La Mesa Housing Area. The model is mostly in scale.this file does not contain the detailes.TorchTorchExample torch using MovieTexture and flickering lights.TrebuchetTrebuchetWorking model of a 14th century Trebuchet Catapult.WallClockWall ClockA file describing a wall clockWallLampWall LampA reusable wall lamp: prototype using an inverted cone with embedded PointLight.WaterTowerWater TowerA simple water tower, produced as a MV4204 class project. Total height 25m.
Sours: https://www.web3d.org/x3d/content/examples/Basic/StudentProjects/
  24 X3D Models      X3D Model DescriptionsAnimatedViewpointRecorderExampleAnimated Viewpoint Recorder ExampleExample authoring use of AnimatedViewpointRecorder prototype. Each tour recording output goes to the console, where it must be cut/pasted for further use. See AnimatedViewpointRecorderSample for sample output.AnimatedViewpointRecorderPrototypeAnimated Viewpoint Recorder PrototypeRecord camera position and orientation as user navigates, then filter values and produce output, both into the console output window and as a replayable node group. Future work: further filtering.AnimatedViewpointRecorderSampleAnimated Viewpoint Recorder SampleExample output from AnimatedViewpointRecorderExample showing results from four separate, previously computed, animated viewpoint recordings.CoordinateAxesCoordinate AxesX Y Z axis arrows and labels in X3D coordinate system. See CoordinateAxesExample for use as an Inline coordinate-system reference frame.CoordinateAxesInlineExampleCoordinate Axes Inline ExampleX Y Z axis arrows and labels in X3D/VRML coordinate system. Shows use of CoordinateAxesVrml as Inline for coordinate-system reference frames.CoordinateAxesNSEWCoordinate Axes NSEWX Y Z axis arrows and labels in X3D coordinate system. See CoordinateAxesExample for use as an Inline coordinate-system reference frame.FilterExamplesFilter ExamplesContains examples for the prototypes defined in the FilterPrototypes.x3dFilterPrototypesFilter PrototypesContains prototypes that filter multiple values/events to extract a single value/event.GridsExampleGrids ExampleExample showing all three line grid authoring tools to enable precise measurement of objects in 3D space. Select axis labels to drag any plane and move along axis, click numbers to hide individual grids.GridsExamplePixelTextureGrids Example Pixel TextureImage converted from binary format into an X3D PixelTexture.GridXY_20x20FixedGrid XY 20x 20 FixedLine grid authoring tool to enable precise visual measurement of objects in 3D space - fixed position. Oriented along XY plane, size 20m by 20m, default block size 1m by 1m.GridXY_20x20MovableGrid XY 20x 20 MovableLine grid authoring tool for precise measurement in 3D space: drag plane to move along Z axis, click numbers to hide grid. Oriented along XY plane, size 20m by 20m, default block size 1m by 1m.GridXZ_20x20FixedGrid XZ 20x 20 FixedLine grid authoring tool to enable precise visual measurement of objects in 3D space - fixed position. Oriented along XZ plane, size 20m by 20m, default block size 1m by 1m.GridXZ_20x20MovableGrid XZ 20x 20 MovableLine grid authoring tool for precise measurement in 3D space: drag plane to move along Y axis, click numbers to hide grid. Oriented along XZ plane, size 20m by 20m, default block size 1m by 1m.GridXZExampleGrid XZExampleLine grid authoring tool to enable precise measurement of objects in 3D space - fixed position. Oriented along XZ plane, default size 20m by 20m, default block size 1m by 1m.GridXZPrototypeGrid XZPrototypeLine grid authoring tool to enable precise measurement of objects in 3D space - fixed position. Oriented along XZ plane, size 20m by 20m, default block size 1m by 1m.GridYZ_20x20FixedGrid YZ 20x 20 FixedLine grid authoring tool to enable precise visual measurement of objects in 3D space - fixed position. Oriented along YZ plane, size 20m by 20m, default block size 1m by 1m.GridYZ_20x20MovableGrid YZ 20x 20 MovableLine grid authoring tool for precise measurement in 3D space: drag plane to move along X axis, click numbers to hide grid. Oriented along YZ plane, size 20m by 20m, default block size 1m by 1m.PixelTextureNavyJackDontTreadOnMePixel Texture Navy Jack Dont Tread On MeImage converted from binary format into an X3D PixelTexture.PixelTextureTemplatePixel Texture TemplateImage converted from binary format into an X3D PixelTexture.SingleTypeConversionExampleSingle Type Conversion ExampleConverts from a single typed value to various other types of values.SingleTypeConversionPrototypeSingle Type Conversion PrototypeConverts from a single typed value to various other types of values.ViewPositionOrientationExampleView Position Orientation ExampleAs user navigates, display local position and orientation in the console output window. Various other output formats also available.ViewPositionOrientationPrototypeView Position Orientation PrototypeViewPositionOrientation prototype provides local position and orientation as user navigates, with optional console output

Official disclaimer: "Material contained herein is made available for the purpose of peer review and discussion and does not necessarily reflect the views of the Department of the Navy or the Department of Defense."

Sours: https://savage.nps.edu/Savage/Tools/Authoring/
  1. Mini winnie rv
  2. Common mustang problems
  3. Folding bus seat
  4. Fertility journey quotes
  37 X3D Models      X3D Model DescriptionsAlarmClockAlarm ClockSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.13.3 Alarm clockX3D encodings example: alarm clock plays chimes once each interval.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.13.3 Alarm clockChopperChopperSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.16 ChopperRotor node provides animation and serves as an ExternProtoDeclare example

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.16 ChopperChopperBodyChopper BodySpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.16 ChopperX3D encodings example: main body for Chopper example, used as an Inline to show scene composition.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.16 ChopperChopperRotorChopper RotorSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.16 ChopperX3D encodings example: spinning rotor (with replacable children) Prototype for Chopper example.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.16 ChopperClickToAnimateClick To AnimateSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.13.2 Click to animateX3D encodings example: click to animate a Box.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.13.2 Click to animateColorInterpolatorExampleColor Interpolator ExampleSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.12 Colour interpolatorX3D encodings example: ColorInterpolator demonstration modifies Material color.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.12 Colour interpolatorDirectionalLightExampleDirectional Light ExampleSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.9 Directional lightX3D encodings example: a DirectionalLight source illuminates only the objects in its enclosing grouping node. The light illuminates everything within this coordinate system, including the objects that precede it in the scene graph.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.9 Directional lightECMAScriptSaiAddDynamicRoutesECMAScript Sai Add Dynamic RoutesSpecification reference: X3D language bindings, ISO/IEC 19777-1, Part 1: ECMAScript, B.5 Add dynamic routesJava Scene Authoring Interface (JSAI) scene and source code example that show adding dynamic ROUTEs to a scene.

Specification reference: X3D language bindings, ISO/IEC 19777-1, Part 1: ECMAScript, B.5 Add dynamic routesECMAScriptSaiCreateNodesECMAScript Sai Create NodesSpecification reference: X3D language bindings, ISO/IEC 19777-1, Part 1: ECMAScript, B.3 Create nodesJava Scene Authoring Interface (JSAI) scene and source code example that show using createX3DFromString to create nodes.

Specification reference: X3D language bindings, ISO/IEC 19777-1, Part 1: ECMAScript, B.3 Create nodesECMAScriptSaiCreateNodesFromPrototypeECMAScript Sai Create Nodes From PrototypeSpecification reference: X3D language bindings, ISO/IEC 19777-1, Part 1: ECMAScript, B.6 Create nodes from a prototypeJava Scene Authoring Interface (JSAI) scene and source code example that show creation of nodes from a prototype.

Specification reference: X3D language bindings, ISO/IEC 19777-1, Part 1: ECMAScript, B.6 Create nodes from a prototypeECMAScriptSaiPerFrameNotificationECMAScript Sai Per Frame NotificationSpecification reference: X3D language bindings, ISO/IEC 19777-1, Part 1: ECMAScript, B.4 Per frame notificationJava Scene Authoring Interface (JSAI) scene and source code example that show how to use per frame notification to produce a frame rate annotation.

Specification reference: X3D language bindings, ISO/IEC 19777-1, Part 1: ECMAScript, B.4 Per frame notificationECMAScriptSaiTouchSensorIsOverEventECMAScript Sai Touch Sensor Is Over EventSpecification reference: X3D language bindings, ISO/IEC 19777-1, Part 1: ECMAScript, B.2 touchSensor isOver eventJava Scene Authoring Interface (JSAI) scene and source code example that demonstrate a scripted response to a TouchSensor isOver event by changing the color of a Box from blue to red.

Specification reference: X3D language bindings, ISO/IEC 19777-1, Part 1: ECMAScript, B.2 touchSensor isOver eventElevatorElevatorSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.18 ElevatorX3D encodings example: example of animating the camera by depicting an elevator to ease access to a multi-story building. For this example, a 2 story building is shown and it is assumed that the elevator is already at the ground floor. To go up, the user just steps onto the elevator platform. A ProximitySensor fires and starts the elevator up automatically. Additional features such as call buttons for outside the elevator, elevator doors, and floor selector buttons could be added to make the elevator easier to use.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.18 ElevatorExecutionModelExecution ModelSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.19 Execution modelX3D encodings example: execution model demonstrated. Click ball to see script-generated text appear.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.19 Execution modelExtrusionEdgeCasesExtrusion Edge CasesSpecification reference: X3D encodings, ISO/IEC 19775-1.4, Part 1: Architecture and base components, Clause 13 Geometry3D component, Topic 13.3.5 Extrusion, Section 13.3.5.4 Special casesScene incorporating extrusion edge cases

Specification reference: X3D encodings, ISO/IEC 19775-1.4, Part 1: Architecture and base components, Clause 13 Geometry3D component, Topic 13.3.5 Extrusion, Section 13.3.5.4 Special casesExtrusionFigureX3dSpecificationExtrusion Figure X3D SpecificationSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Figure 13.5 - Spine-aligned cross-section plane at a spine point.X3D Extrusion spine-aligned cross-section plane (SCP) at a spine point. Modeled after Figure 13.5 in X3D Specification.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Figure 13.5 - Spine-aligned cross-section plane at a spine point.GeometricPropertiesGeometric PropertiesSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.6 Geometric propertiesX3D encodings example: simple demonstration of geometric-property nodes.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.6 Geometric propertiesGuidedTourGuided TourSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.17 Guided tourX3D encodings example: provides control of the viewpoint through use of a script. This is useful for things such as guided tours, merry-go-round rides, and transportation devices such as buses and elevators. These next two examples show a couple of ways to use this feature. This example is a simple guided tour through the world. Upon entry, a guide orb hovers in front of the viewer. Click on this and a tour through the world begins. The orb follows the user around on his tour. A ProximitySensor ensures that the tour is started only if the user is close to the initial starting point. Note that this is done without scripts thanks to the touchTime output of the TouchSensor.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.17 Guided tourInstancingInstancingSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.3 Instancing (sharing)X3D encodings example: demonstrate reuse of content instances through DEF, USE.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.3 Instancing (sharing)JavaSaiAddDynamicRoutesJava Sai Add Dynamic RoutesSpecification reference: X3D language bindings, ISO/IEC 19777-2, Part 2: Java, D.5 Add dynamic routesJava Scene Authoring Interface (JSAI) scene and source code example that show adding dynamic ROUTEs to a scene.

Specification reference: X3D language bindings, ISO/IEC 19777-2, Part 2: Java, D.5 Add dynamic routesJavaSaiCreateNodesJava Sai Create NodesSpecification reference: X3D language bindings, ISO/IEC 19777-2, Part 2: Java, D.3 Create nodesJava Scene Authoring Interface (JSAI) scene and source code example that show using createX3DFromString to create nodes.

Specification reference: X3D language bindings, ISO/IEC 19777-2, Part 2: Java, D.3 Create nodesJavaSaiCreateNodesFromPrototypeJava Sai Create Nodes From PrototypeSpecification reference: X3D language bindings, ISO/IEC 19777-2, Part 2: Java, D.6 Create nodes from a prototypeJava Scene Authoring Interface (JSAI) scene and source code example that show creation of nodes from a prototype.

Specification reference: X3D language bindings, ISO/IEC 19777-2, Part 2: Java, D.6 Create nodes from a prototypeJavaSaiPerFrameNotificationJava Sai Per Frame NotificationSpecification reference: X3D language bindings, ISO/IEC 19777-2, Part 2: Java, D.4 Per frame notificationJava Scene Authoring Interface (JSAI) scene and source code example that show how to use per frame notification to produce a frame rate annotation.

Specification reference: X3D language bindings, ISO/IEC 19777-2, Part 2: Java, D.4 Per frame notificationJavaSaiTouchSensorIsOverEventJava Sai Touch Sensor Is Over EventSpecification reference: X3D language bindings, ISO/IEC 19777-2, Part 2: Java, D.2 TouchSensor isOver eventJava Scene Authoring Interface (JSAI) scene and source code example that demonstrate a scripted response to a TouchSensor isOver event by changing the color of a Box from blue to red.

Specification reference: X3D language bindings, ISO/IEC 19777-2, Part 2: Java, D.2 TouchSensor isOver eventLevelOfDetailLevel Of DetailSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.11 Level of detailX3D encodings example: LevelOfDetail demonstration.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.11 Level of detailPointSetExamplePoint Set ExampleSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.10 PointSetX3D encodings example: PointSet demonstration.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.10 PointSetPrototypePrototypeSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.4 Prototype exampleX3D encodings example: defining a Prototype, demonstration of IS/connect definitions.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.4 Prototype examplePrototypesPlusPrototypes PlusSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.7 Prototypes and alternate representationsX3D encodings example: using an externally defined prototype.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.7 Prototypes and alternate representationsRedSphereBlueBoxRed Sphere Blue BoxSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.2 Simple exampleX3D encodings example: show simple Shapes, including different Materials and geometry.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.2 Simple exampleRefractiveMaterialRefractive MaterialSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.7 Prototypes and alternate representationsX3D encodings example: create new node RefractiveMaterial for example PrototypesPlus.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.7 Prototypes and alternate representationsRobotRobotSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.15 RobotX3D encodings example: Robot. Seek or zoom in towards the robot to start a simple animation sequence. This scene demonstrates nested prototype instances

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.15 RobotRotorRotorSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.16 ChopperX3D specification example showing a spinning helicopter rotor that is used by the Chopper model.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.16 ChopperScriptingScriptingSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.5 Scripting exampleX3D encodings example: this Script node decides whether or not to open a bank vault given openVault and combinationEntered messages. To do this, it remembers whether or not the correct combination has been entered. The Script node combined with a Sphere, a TouchSensor and a Sound node to show how is works. When the pointing device is over the sphere, the combinationEntered eventIn of the Script is sent. Then, when the Sphere is touched (typically when the mouse button is pressed) the Script is sent the openVault eventIn. This generates the vaultUnlocked eventOut which starts a click sound.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.5 Scripting exampleShuttlesAndPendulumsShuttles And PendulumsSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.14 Shuttles and pendulumsX3D encodings example: animation of shuttle and pendulum prototype nodes.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, Annex C.14 Shuttles and pendulumsStringArrayEncodingExamplesString Array Encoding ExamplesSpecification reference: X3D encodings, ISO/IEC 19776-2 v3.3, Part 2: Classic VRML encoding, 5.15 SFString and MFStringDemonstrate simple X3D MFString (string array) encoding.

Specification reference: X3D encodings, ISO/IEC 19776-2 v3.3, Part 2: Classic VRML encoding, 5.15 SFString and MFStringTriangleStripSetFigureTriangle Strip Set FigureSpecification reference: X3D Abstract Specification, Part 1: Architecture and base components, Topic 11.4.14 TriangleStripSetX3D specification example for TriangleStripSet.

Specification reference: X3D Abstract Specification, Part 1: Architecture and base components, Topic 11.4.14 TriangleStripSetX3dHeaderPrototypeSyntaxExamples X3D Header Prototype Syntax ExamplesSpecification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, 4.3 XML file syntaxX3D scene header and prototype syntax examples. This example header indicates that the content is XML encoded, follows the Interactive Profile and explicitly lists additional necessary components. The X3D header may also contain additional semantic information. Used for specification EXAMPLE excerpts in 19776:1 XML Encoding.

Specification reference: X3D encodings, ISO/IEC 19776-1.3, Part 1: XML encoding, 4.3 XML file syntax
Sours: https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/index.html
Manual Mesh Bed Levelling - Free warped bed solution

X3D file structure

This article or section is a stub. It does not yet contain enough information to be considered a real article. In other words, it is a short or insufficient piece of information and requires additions.

Draft

1 Introduction

This is a short summary explaining the file structure of a X3D model. In order to understand "the message", you will need some knowledge about XML, in particular XML file structure, wellformedness and validity.

X3D is a modular standard and therefore the X3D file structure is defined through several ISO Specifications.

Combined, these specifications are then available in terms of three types of schemas: DTD, XML Schema (XSD) and Schematron

  • x3d-3.2.dtd. Can ensure proper parent-child element relations and attribute naming
  • x3d-3.2.xsd. In addition, can ensure proper type-checking of most attribute values.
  • X3D Schematron. For additional validation that can't be handled by XSD.

2 The X3D file structure

A X3D scene is defined by the contents of a URL (i.e. either an X3D file or some generator). This resource then can include additional elements with an Inline node.

X3D scene files have a common file structure:

  • File header (either XML, ClassicVRML, or Compressed Binary)
  • Start of the X3D root node including version and profile attributes
  • A head section with Component and Meta statements (both optional)
  • The X3D Scene graph and its child nodes
  • End of the X3D root node

We shall shortly describe these elements below. But before, let's have a look at the code of a simple exemple scene, HelloWorld.x3d, retrieved on oct. 2010 from Chapter 01 - Technical Overview at x3dgraphics.com/

Inserted XML comments identify the elements:

<?xml version="1.0" encoding="UTF-8"?><!-- -------------------- X3D header and X3D root node with profile declaration --><!DOCTYPE X3D PUBLIC "ISO//Web3D//DTD X3D 3.2//EN" "http://www.web3d.org/specifications/x3d-3.2.dtd"><X3Dprofile='Immersive'version='3.2'xmlns:xsd='http://www.w3.org/2001/XMLSchema-instance'xsd:noNamespaceSchemaLocation='http://www.web3d.org/specifications/x3d-3.2.xsd'><!-- -------------------- head section with included meta data --><head><metacontent='HelloWorld.x3d'name='title'/><metacontent='Simple X3D example'name='description'/><metacontent='30 October 2000'name='created'/><metacontent='7 August 2010'name='modified'/><metacontent='Don Brutzman'name='creator'/><metacontent='http://www.web3D.org'name='reference'/><metacontent='http://x3dGraphics.com'name='reference'/><metacontent='http://www.web3d.org/x3d/content/examples/HelloWorld.x3d'name='identifier'/><metacontent='http://www.web3d.org/x3d/content/examples/HelloWorldTall.png'name='image'/><metacontent='http://www.web3d.org/x3d/content/examples/license.html'name='license'/><metacontent='X3D-Edit 3.2, https://savage.nps.edu/X3D-Edit'name='generator'/></head><!-- -------------------- the X3D scene node with X3D nodes --><Scene><!-- Example scene to illustrate X3D nodes and fields (XML elements and attributes) --><Group><ViewpointcenterOfRotation='0 -1 0'description='Hello world!'position='0 -1 7'/><Transformrotation='0 1 0 3'><Shape><Sphere/><Appearance><MaterialdiffuseColor='0 0.5 1'/><ImageTextureurl='"earth-topo.png" "earth-topo.jpg" "earth-topo-small.gif" "http://www.web3d.org/x3d/content/examples/Basic/earth-topo.png" "http://www.web3d.org/x3d/content/examples/Basic/earth-topo.jpg" "http://www.web3d.org/x3d/content/examples/Basic/earth-topo-small.gif"'/></Appearance></Shape></Transform><Transformtranslation='0 -2 0'><Shape><Textstring='"Hello" "world!"'><FontStylejustify='"MIDDLE" "MIDDLE"'/></Text><Appearance><MaterialdiffuseColor='0.1 0.5 1'/></Appearance></Shape></Transform></Group></Scene><!-- -------------------- footer, closing X3D toot element --></X3D>

In case you don't have a X3D client for looking at this scene, it should render like this:

Hello World scene screen capture

More complex X3D scenes are usually split over several files. To include a scene one usually positions and scales the included object, e.g. like in the example fragment below taken from the Kelp Forest exhibit that can be found at x3dgraphics.com. Click on Kelp Forest Main to look at the scene, then play around with the viewpoints.

The following code can be found in the main file (KelpForestMain.x3d) and will load "Lucy the shark" from the first local or remote URL that the client can retrieve. As you can see, one also can load *.wrl files into *.X3D.

<Transform><Inlineurl='"SharkLucyLocale.x3d" "http://X3dGraphics.com/examples/X3dForWebAuthors/KelpForestExhibit/SharkLucyLocale.x3d" "SharkLucyLocale.wrl" "http://X3dGraphics.com/examples/X3dForWebAuthors/KelpForestExhibit/SharkLucyLocale.wrl"'/></Transform>

2.1 X3D file header and filename extensions

Since X3D has grown out of VRML it has both an XML and a VRML syntax. In addition, both formats can be delivered in compressed format.

The Header for X3D / XML needs an XML declartion and an optional DTD. The XML Schema (XSD) is declared in the root node which must include a version and a profile attribute.

<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE X3D PUBLIC "ISO//Web3D//DTD X3D 3.2//EN" "http://www.web3d.org/specifications/x3d-3.2.dtd"><X3Dprofile='Immersive'version='3.2'xmlns:xsd='http://www.w3.org/2001/XMLSchema-instance'xsd:noNamespaceSchemaLocation='http://www.web3d.org/specifications/x3d-3.2.xsd'>

As of october, there exist several final X3D versions:

  • version 3.0
  • version 3.1
  • version 3.2 (Version 3.2.2 was published in April 2005 and should be supported by most browsers)

To us, it is totally unclear where versions are defined and where one can find central information about support profiles and versions by various clients and other tools - Daniel K. Schneider 15:35, 5 October 2010 (CEST).

See below for more information about profiles and components

The following file extensions should be used for X3D contents:

X3D Encoding File Extension MIME Type
Classic VRML .x3dv model/x3d+vrml
XML .x3d model/x3d+xml
Binary .x3db model/x3d+binary

E.g. if you have an Apache server you could add the following lines to a *.conf file:

AddType model/x3d+xml .x3d AddType model/x3d+vrml .x3dv AddType model/x3d+binary .x3db AddEncoding gzip .x3dvz AddEncoding gzip .x3dbz

2.2 Profiles, components

X3D has a modular architecture that defines 4 to 6 baseline profiles (depending on the version) which are are predefined collections of components. Profiles are defined with XML attributes in the X3D root node or as VRML statements on top.

In addition, within the head section, authors can specify more precisely what components are needed. Components are predefined collections of nodes and match chapters in the specification. Each profile can be augmented by adding other components

Both the mandatory profile definition and the optional components statements tells the X3D browser what level of support is needed for run-time operation.

The 3.2 specification includes six profiles:

  • Core is just the core (probably not useful for authors)
  • Interchange is the basic profile for communicating between applications. It supports geometry, texturing, basic lighting, and animation
  • CADInterchange adds support for CADGeometry component nodes to Interchange Profile.
  • Interactive enables basic interaction with a 3D environment by adding various sensor nodes for user navigation and interaction (e.g., PlanseSensor, TouchSensor, etc.), enhanced timing, and additional lighting (Spotlight, PointLight).
  • Immersive enables full 3D graphics and interaction, including audio support, collision, fog, and scripting. Corresponds to the power of VRML 97 plus minor additions.
  • MPEG4Interactive
  • Full includes all defined nodes including NURBS, H-Anim (animated interactive Avatars) and GeoSpatial components.

X3D Baseline Profiles: Source: What is X3D?, retrieved 11:53, 26 August 2010 (UTC)

Examples of X3D profile declarations

<X3Dprofile='Immersive'version='3.2'xmlns:xsd='http://www.w3.org/2001/XMLSchema-instance'xsd:noNamespaceSchemaLocation='http://www.web3d.org/specifications/x3d-3.2.xsd'></X3D>
<X3Dprofile='Interactive'version='3.2'xmlns:xsd='http://www.w3.org/2001/XMLSchema-instance'xsd:noNamespaceSchemaLocation='http://www.web3d.org/specifications/x3d-3.2.xsd'></X3D>

Examples of X3D ClassicVRML profile declarations

PROFILE Immersive

Additional components with respect to the ones includes in the declared profile can be included in the had section as in the following Header Profile Component Meta Example (retrieved 15:35, 5 October 2010 (CEST)). The component tags raise the support level from Immersive profile to include other components included in the X3D 3.0 Full profile.

<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE X3D PUBLIC "ISO//Web3D//DTD X3D 3.1//EN" "http://www.web3d.org/specifications/x3d-3.1.dtd"><X3Dprofile='Immersive'version='3.1'xmlns:xsd='http://www.w3.org/2001/XMLSchema-instance'xsd:noNamespaceSchemaLocation=' http://www.web3d.org/specifications/x3d-3.1.xsd '><head><componentlevel='1'name='DIS'/><componentlevel='1'name='Geospatial'/><componentlevel='1'name='H-Anim'/><componentlevel='3'name='NURBS'/><!-- .... content deleted --></head></X3D>

2.3 Meta statements

Meta statements provide information about the X3D scene as a whole.

Information is provided as name-content pairs, for example

<meta content='30 October 2000' name='created'/> <meta content='Don Brutzman' name='creator'/> <meta content='done' name='status'/>

One can use any value in the name and content field, but there are some informal recommendations. This approach is thus very general and a wide variety of metadata can be represented. The X3D approach matches same approach used by HTML for regular hypertext web pages.

2.4 The X3D scene graph

Each X3D file only can include one X3D scene according to XML principles. In other words there must be a single root element.

At the content level, the same principle as for HTML applies. There can be only a single scene in the same way that in HTML there is only one body

A very minimalistic valid X3D file would look like this

<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE X3D PUBLIC "ISO//Web3D//DTD X3D 3.2//EN" "http://www.web3d.org/specifications/x3d-3.2.dtd"><X3Dprofile='Immersive'version='3.2'xmlns:xsd='http://www.w3.org/2001/XMLSchema-instance'xsd:noNamespaceSchemaLocation='http://www.web3d.org/specifications/x3d-3.2.xsd'><head></head><Scene><!-- Scene graph with a single red ball --><Shape><Sphereradius='2.0'/><Appearance><MaterialdiffuseColor='1.0 0.0 0.0'/></Appearance></Shape></Scene></X3D>

X3D (and other) scene graphs follow a model-centric approach to 3D that hierarchically defines geometry shape, appearance, position and orientation, etc. In other words, all parameters of interest (except some scripted behaviors) are defined declaratively.

In X3D, a graph has a root node and no loops, i.e. a directed acyclic graph (DAG). Most Computer Aided Design (CAD) models follow a similar approach.

In opposition, most narrative programming languages use an approach like "draw this triangle, that triangle, recompute", etc.

Read more on X3D shape and geometry

3 X3D ClassicVRML syntax

In our tutorials we shall not explain VRML syntax. See the VRML Primer and Tutorial we made over 10 years ago. We just point out that X3D/ClassicVRML is different from VRML1997, i.e. the ClassicVRML profile looks like VRML and uses the same syntax, but there are some changes between the last VRML standard (ISO/IEC 14772-1) and the new X3D-based ISO/IEC 19776-2. In particular, the scripting interface has been totally overhauled.

It is also important to understand the most X3D clients can render VRML 1997 (and the other way round if the VRML client is recent).

#X3D V3.2 utf8PROFILEImmersiveMETA"title""HelloWorld.x3d"META"description""Simple X3D example"META"created""30 October 2000"META"modified""7 August 2010"META"creator""Don Brutzman"META"reference""http://www.web3D.org"META"reference""http://x3dGraphics.com"META"identifier""http://www.web3d.org/x3d/content/examples/HelloWorld.x3d"META"image""http://www.web3d.org/x3d/content/examples/HelloWorldTall.png"META"license""http://www.web3d.org/x3d/content/examples/license.html"META"generator""X3D-Edit 3.2, https://savage.nps.edu/X3D-Edit"NavigationInfo{type["EXAMINE""ANY"]}###DefaultX3DNavigationInfo# Example scene to illustrate a single X3D node in VRMLClassic syntaxShape{geometrySphere{}appearanceAppearance{materialMaterial{diffuseColor00.51}}}

4 Links

Specification and Schema documentation
X3D Examples

5 Credits and Copyright modificiation

Sours: http://edutechwiki.unige.ch/en/X3D_file_structure

Examples x3d

Example Scenes

Every example from X3D: Extensible 3D Graphics for Web Authors is available for inspection, interaction, and download. The examples are grouped by the chapter where they appear. Additional examples are also included.

You can either browse all of the examples, download the examples archive, or browse individual chapters using the links below.

  1. Examples Table of Contents
  2. Chapter 1: Technical Overview (online chapter)
  3. Chapter 2: Geometry Nodes, Part 1: Primitives
  4. Chapter 3: Grouping Nodes
  5. Chapter 4: Viewing and Navigation
  6. Chapter 5: Appearance, Material, and Textures
  7. Chapter 6: Geometry Nodes, Part 2: Points, Lines, and Polygons
  8. Chapter 7: Event Animation and Interpolation
  9. Chapter 8: User Interactivity Nodes
  10. Chapter 9: Event Utilities and Scripting
  11. Chapter 10: Geometry Nodes, Part 3: Geometry2D Nodes
  12. Chapter 11: Lighting and Environment Nodes
  13. Chapter 12: Environmental Sensor and Sound Nodes
  14. Chapter 13: Geometry Nodes, Part 4: Triangles and Quadrilaterals
  15. Chapter 14: Creating Prototype Nodes
  16. Chapter 15: Metadata
  17. Kelp Forest Exhibit

Portions of this work are from the book,
X3D: 3D Graphics for Web Authors, by Don Brutzman and Leonard Daly, published by Morgan Kaufmann Publishers, Copyright 2007 Elsevier, Inc. All rights reserved.

Web site copyright © 2008-2017, Daly Realism and Don Brutzman

Sours: https://x3dgraphics.com/examples/index.php
X3D: Expanding Architectures for Efficient Video Recognition

What is a X3D file?

X3D is an XML based 3D graphics file format for presentation of 3D information. It is a modular standard and is defined through several ISO specifications. The format supports vector and raster graphics, transparency, lighting effects, and animation settings including rotations, fades, and swings. It became successor of VRML file format in 2001. X3D has the advantage of encoding colour information (unlike STL) that is used during printing the model on a colour 3D printer. The format features extensions to VRML, providing the capability to encode the scene using an XML syntax as well as the Open Inventor-like syntax of VRML97 or binary formatting.

The abstract specification for X3D (ISO/IEC 19775) was first approved by the ISO in 2004. The XML and ClassicVRML encodings for X3D (ISO/IEC 19776) were first approved in 2005.

X3D File Format

X3D scene files have a common file structure:

  • File header (either XML, ClassicVRML, or Compressed Binary)
  • Start of the X3D root node including version and profile attributes
  • A head section with Component and Meta statements (both optional)
  • The X3D Scene graph and its child nodes
  • End of the X3D root node

Example

References

See Also

Sours: https://docs.fileformat.com/3d/x3d/

You will also be interested:

This archive provides a wide variety of basic open-source examples that show how to design and build X3D models. Many of these scenes have been used for confirmation, development and testing of essential node capabilities in X3D.

  26 Directory Summaries   737 X3D Models Directory SummaryCAD Directory SummaryChemical Markup Language

Chemical Markup Language (CML)

Chemical Markup Language (CML) provides support for most chemistry including molecules, compounds, reactions, spectra, crystals and computational chemistry.

These examples show how to visualize Chemical Markup Language (CML) molecular definitions using previously designed X3D model prototypes by using an XSLT stylesheet transformations. This process is described in the paper "Stylesheet Transformations for Interactive Visualization: Towards a Web3D Chemistry Curricula," originally published in Proceedings of Web3D 2003 Symposium, St. Malo France, 9-12 March 2003, ACM Press.

 Directory Summarycourse
Becky's Road Overpass, sixth grade project

These scenes have been used in X3D course materials.

These are simple example scenes that are useful for teaching and course work. Some have been developed by students learning X3D. A much larger set of scenes and slidesets have been developed as the X3D for Web Authors Examples Archive.

 Directory Summarydevelopment
Additive Subtractive Light example

These scene examples support specification development, player implementations, and demonstration of exemplar X3D capabilities.

These scenes help to demonstrate trial technology and develop new nodes for the X3D Specifications. They support the efforts of the X3D Working Group.

 Directory SummaryDistributed Interactive Simulation

A supporting DIS chapter slideset is available online via X3dGraphics.com. Related work includes X3D-Edit DIS Support as well as the Open-DIS software library, which provides open-source implementations of DIS in C++, C#, Java, Objective-C and JavaScript.

Warning: the Distributed Interactive Simulation (DIS) component in not widely supported. Further work is welcome.

 Directory SummaryExperimental Binary Compression
Eight.x3d mesh model used for compression tests

Experimental Binary Compression algorithm models demonstrate the potential of geometric compression techniques.

These developmental examples illustrate how geometric compression based on text-based ASCII encodings might be integrated into X3D scenes via Prototype nodes that encapsulate Script processing. The file-size reduction technique Coding Polygon Meshes as Compressable ASCII by Martin Isenburg and Jack Snoeyink is documented in award-winning papers presented at the Web3D 2002 and 2003 Symposia. A Shout3D implementation demonstration is also available.

Further work on the X3D Compressed Binary Encoding (CBE) can be found at X3D Binary Compression Capabilities and Plans wiki page.

 Directory SummaryExternal Authoring Interface

Virtual Reality Modeling Language (VRML97)

VRML97 External Authoring Interface (EAI) was used to pass events from HTML scripts into VRML97 scene scripts.

These scripting examples illustrate how to use the original External Authoring Interface (EAI) in the VRML97 specification. It allows scripts placed in an external HTML page to communicate with a VRML97 scene, using either Java or ECMAScript .

These HTML scripting techniques were later unified with Script syntax inside the scene as the X3D Scene Authoring Interface (SAI).

 Directory SummaryFollowers
Follower algorithm

The X3D Followers component supports specialized linear interpolation for various data types to achieve smooth behavior animation.

These examples illustrate how to use Chaser and Damper nodes, which are defined in the Followers component of the X3D specification. Transitions are computed at run time to produce events that smoothly change from an initial value to a goal value.

 Directory SummaryGeospatial Directory SummaryLattice Xvl
Lattice technology

LatticeXvl was an experimental parametric geometry approach that was not adopted into the X3D standard. These nodes nevertheless demonstrate extensibility techniques for integrating new capabilities using X3D DOCTYPE (DTD). The Xvl nodes are merely experimental: not approved by the X3D Abstract Specification, not in the X3D XML Schema, and not in the X3D Unified Object Model (X3DUOM).

The LatticeXvl examples do show how Lattice technology from the XVL3D company was integratable as a commercial extension within X3D. This technique is repeatable. The extension approach to XML DTD validation has been maintained through each version of X3D, and is documented further in the actual X3D DTDs and Schemas.

 Directory SummaryMedical Directory SummaryNetworking
Network Rerouting over Alternate Routes

This directory includes several experiments with X3D Networking.

Long-running efforts have attempted to define and build a new NetworkSensor node for X3D. Although useful design progress was made by the X3D working group, this work did not reach closure because author-written implementations did not appear to be possible using X3D prototypes encapsulating sandbox-restricted JavaScript network access from within an HTML browser. Further implementation and evaluation work might someday be pursued using an X3D browser implementation.

Examples of additional networking techniques for X3D can also be added to this archive. Of related interest: the Distributed Interactive Simulation (DIS) examples in this archive, which include native X3D support for the IEEE Distributed Interactive Simulation (DIS) networking-protocol standard.

 Directory SummaryNURBS
Fred the Bunny

Non-Uniform Rational B-Spline (NURBS) provide a parametric mathematical model for generating and representing smooth curves and surfaces.

Non-Uniform Rational B-Spline (NURBS) provide a convenient and efficient manner to generate curved lines and surfaces which can be smooth at any viewing distance. Since these surfaces are generated parametrically, only a small amount of data need be provided for describing complex surfaces. These examples support the X3D NURBS component.

These capabilities hold significant potential value for use by the Computer Aided Design (CAD) and Medical working groups.
 Directory SummaryPoints

This directory includes experiments with extensions for X3D Points.

 Directory SummaryRigid Body Physics
Xj3D rigid-body car example

Rigid Body Physics modeling deals with objects as solid, unchangeable sets of mass having a velocity that can be connected together via various joint types that allow one body's motion to affect another.

These examples support the X3D Rigid Body Physics component for simple kinematics, first implemented by Xj3D.

Warning: the Rigid Body Physics component in not widely supported and these examples are insufficiently tested. Further work is welcome.

Of related interest: Distributed Interactive Simulation (DIS) examples.

 Directory SummaryScript Conformance Directory SummarySecurity Directory SummaryShaders

Shaders are special programs that interact directly with graphics hardware for special effects using light, darkness, and color within a model's appearance.

A programmable shader allows authors to directly specify how an object is rendered by providing a method of programmatically modifying sections of the rendering pipeline. This allows replacement of the traditional fixed-function graphics API pipeline to support visual effects that typically cannot be implemented using other node components in this standard.

These example scenes illustrate the X3D Programmable Shaders Component. Unfortunately, unlike X3D, shader languages are typically hardware-specific and not interoperable across different platforms. Mutually compatible X3D interfaces and syntax are defined for the OpenGL shading language (GLSL) binding, Microsoft high level shading language (HLSL) binding and the nVidia Cg shading language binding.

 Directory SummaryStudent Projects
Pinball Table Model

Student Projects are interesting and fun!

These are interesting scenes authored by X3D students who have taken the X3D for Web Authors Further contributions are welcome. Be sure to follow the X3D Scene Authoring Hints for reasonably consistent descriptions, metadata, layout and naming conventions within each model scene.

 Directory SummaryUnits

Yardsticks

Unit statements can redefine the base units of length/angle/force/mass values in an X3D scene from meters/radians/newtons/kilograms to other units of interest.

These examples demonstrate use of the X3D Units statements proposed for X3D version 3.3. Unit statements define conversion factors from default units in order to simplify the creation of content using minimal data translation. The original proposal provides further detail.

 Directory SummaryUniversal Media Materials
Universal Media

Universal Media Materials provide numerous complex Material values to simply scene authoring and improve geometry appearance.

These Universal Media examples provide a large suite of color-coordinated X3D/VRML Materials for easy usage by authors. Visual scenes are provided for browsing and selection from each collection. Entries can be copied directly or used via (internal or external) prototype declarations.

This library of materials is originally converted from SGI's Open Inventor material examples. Material library selections are also built into the X3D-Edit authoring tool. Example use is further explained in the X3D for Web Authors slideset Chapter 5 - Appearance Material Textures.

 Directory SummaryUniversal Media Panoramas
Universal Media

Universal Media Panoramas are texture-mapped high-resolution Background nodes.

These Universal Media examples provide a large suite of X3D/VRML Background nodes with customized images for easy author use. Visual scenes are provided for browsing and selection from each collection. Background nodes can be copied directly with multiple url site addresses included for each image texture in order to improve reliability.

Example use is further explained in the X3D for Web Authors slideset Chapter 11 - Lighting and Environment.

 Directory SummaryVolume Rendering Directory SummaryVRML 97 Specification

Virtual Reality Modeling Language (VRML97)

The VRML97 Specification was the second-generation predecessor specification that eventually led to the X3D Graphics International Standard, maintaining full compatibility with the X3D ClassicVRML Encoding.

Many 3D graphics systems support the Virtual Reality Modeling Language (VRML97). These scenes support the Examples section of the VRML97 specification.

The baseline source kept under version control is in form, and the autogenerated products include versions using the VRML97 file extension. These examples are maintained for historic reasons and interoperability testing. Backwards compatibility of scenes remains a significant strength of the X3D specification, which includes a fully interoperable ClassicVRML file encoding as well as numerous conversion and translation tools.

Historic predecessor document references include the VRML Script Node Authoring Interface proposal of 6 October 1996, and the Virtual Reality Modeling Language (VRML) 1.0 Specification of 26 May 1995.

 Directory SummaryWeb 3D Outreach
Web3D Consortium Logo

This directory collects models and scenes for outreach by the Web3D Consortium, the Standards Development Organization (SDO) that supports real-time graphics communication on the Web.

The Web3D Consortium is a nonprofit organization that develops and maintains the X3D, VRML, and H-Anim standards. These are 3D file formats and runtime specifications for the delivery and integration of interactive 3D data over networks.

Extensible 3D (X3D) Graphics (X3D) is the open, royalty-free, ISO-standard data language and run-time architecture for 3D graphics. It provides for real-time, interactive, animatable 3D objects displayed in a browser or other network connected or stand-alone display. The simple examples in this directory support the creation of outreach and marketing models for the Web3D Consortium and X3D Graphics. X3D Specification Logo
 Directory Summary X3D Specifications
Sours: https://www.web3d.org/x3d/content/examples/Basic/


661 662 663 664 665