The following project guidelines were provided to authors and list members.
CosmoPlayerPC/Netscape 3.01 on a Pentium 100, 32 MB RAM, 1GB HD
High Color, 800 x 600
It is the intention of the project that IrishSpace be viewable on any VRML browser, so no extensions will be used. These guidelines are the only other restrictions. However with the current state of VRML development, unless a target platform is chosen in advance, the fidelity of the final presentation cannot be ensured to the contributing authors and sponsors. All members of the VRML community are invited to test and comment on content and make suggestions where the content can be made more compliant with the VRML specification.
The following guidelines are suggested or strict. Suggested guidelines are just that: guidance for the author. Strict guidelines are project policies to ensure consistency, or to protect the content.
VRML 2.0 - no extensions. HTML 3.0 and above. All other notations per VRML specification except where used in frames. Since Netscape 3.01 is the target platform, use native handlers. Any others (e.g, QuickTime, avi) can be considered but a freeware plugin must be available for the Kerry Museum site.
Java can be considered, but VRMLScript is preferred. JavaScript is acceptable based on testing to ensure it works in the target platform.
Ages 9 to 12 (but if adults like it, that's Ok)
All submissions must contain a WorldInfo node stating authors and any sources. This is a strict guideline since VRML tools can strip comments. Any rights reserved by the submittor must be stated in the VRML node including intent to provide a public domain object.
Small objects (e.g, ships, space stations, etc.); 1 VRML unit/meter = 1 meter
Solar System and Celestial Objects: 1 VRML unit/meter = 10000 km
That would, for instance, make the Earth 1.2 units (diameter), and its distance from Sol as 15,000 units (therefore 1 Astonomical Unit = 15k)... Sol is 139 units, Jupiter 14 units and 78000 units away from the Sun. And Pluto at 589,000 units away with a size of .15.
The authors are free to use MovieTextures, sound files, etc. as long as they are *reasonable* in size. Performance is the key issue. If possible, IrishSpace will be produced in both a lo-fidelity version for distribution on the World Wide Web, but it will be hosted locally at the Kerry County Museum for the exhibit. This is to enable use of media that are too expensive to use on the Internet.
The objective is to present a Space Exhibit. The requirement is the theme as stated by John Griffin originally: a solar system and deep space flythrough. It is a fundamental of VRML that very complex models experience performance restrictions. The goal is to provide a piece that will "educate and entertain". It is expected that as the project proceeds to completion, we will all make adjustments for performance and consistency.
The following guidelines are established to ensure interoperation of the IrishSpace exhibit.
Each team is required to keep a protoPage. This is a framed web page which includes the current viewable state of the team's work. For VRML geometric files, this should be a VRML world (e.g, for planetary systems, spacecraft, etc.). Those providing code (eg., applets, scripts, proto nodes, etc.) should provide an index of these with anchors to the source.
It is suggested that a framed page be used to make quick navigation simpler. For geometric models, this is a good model of a VRML protopage (link deleted). For code, this is a good model of a code protopage (link deleted). Using common protopage models is not required, but it makes it easier for other team members to quickly locate objects for review and comment.
Planetary systems should be modeled with their moon and other orbital objects within the same file. Planetary systems may include man-made objects such as satellites, etc. See Paul Hoffman.
TBD
All possible effort should be made to share environment designs. For example, those building colonies and surfaces of worlds should try to share as much texture and terrain design as is practical.
Space navigation is via the JJ controls (see Dylan Brennan)
Authors are encouraged to succinctly comment their code so other project members can easily and quickly understand it. For VRML protos, this is highly encouraged. For VRML, good DEF naming practice should be followed. This is very helpful when following ROUTEs. These practices are particularly valuable during the integration phase. In other words, just do what a good programmer does by instinct.
For most sound files, 11025khz 8-bit, monaural wav files are preferred. If spatialization is used, ensure that the min/max settings are congruent with the object being modeled, and work inside a scene. Since some objects may be reused in several worlds, avoid scene-specific sounds that would prevent reuse of the object (e.g, narration). These will be added during integration if used. Ambient sounds are useful, but remember, space is a quiet place.
Maximize the use of sensors to initiate sounds, movie textures, and animations. These ensure the world is more efficient by not playing animations or sounds when they aren't in view or earshot, and they provide more realism. Avoid the technique of using startTime=0 to initiate sounds. Set Loop=FALSE unless the sound should always play in any scene in which the object may be inlined. Except for local ambient sounds, this should be seldom.
Graphics will be sized to 128 x 128 before sending to the FTP site. This reduces bandwidth requirements. If the target platform supports larger textures before the show, 256 x 256 textures will be accepted.
MPEGs should be sized such that they load and decompress quickly. See Dylan Brennan for guidelines and assistance.