My publisher tells me that my new book, 3D Studio MAX 3 R3: In Depth, will be available within the next week. If you're a MAX user, or a would-be MAX user, you might want to look over a sample chapter--and maybe even order the book at the same time.:)
In the past couple of lessons, we've been previewing the soon-to-be released Shout3D 1.0. This remarkable package (as I cannot repeat too often) allows developers to embed a realtime, interactive 3D rendering engine directly into a Web page, without any plug-ins. Shout3D uses a Java applet as the 3D player, and therefore makes use of the full programming power of the Java language to realize unlimited possibilities for user interactivity. I hope to have the final word on the release date of this important package in the near future.
Java programming, however, is not a skill that the average 3D artist (or even the average Web developer) is likely to have. Many interested people may well be impressed with Shout3D, but doubt (or even dismiss) their own ability to learn this toolset. Of course, a great deal can be done with Shout3D with very little programming, and, if no interactivity is required, no programming at all. But it's fair to say that solid commercial applications for 3D on the Internet depend on strong user interactivity, and this, of course, requires coding.
Keyframed animation in Shout3D is driven by a TimeSensor, a node right out of VRML. When the TimeSensor is started, the animation begins. At this point, we must distinguish between stopping and pausing the TimeSensor. If we pause the TimeSensor after it has started, we can unpause it to continue the animation. But if the animation is stopped, it can only be restarted from the beginning. Thus the toggle in this applet starts the animation, and then just pauses and unpauses it.
Let's take a look at the code.
|To Continue to Parts 2 and 3, Use Arrow Buttons||
Created: Oct. 12, 1999
Revised: Oct. 12, 1999