How fun it is to post to the gallery during such a blustery storm!

Following is an example of a Viewpoint scene with manipulating triggers contained to the inside of the scene. Use of Action Scripting was necessary and frequent.

We will modify this scene as we bring the 3D model to market as a plug-in to MS Flight Simulator. Experience it here, buy it, download, and fly it.

You will not see that "pretty pink" watermark because everything is functioning within strict adherence to the developer license.

An initial goal remains a keen one...to create product experiences which help sell product. In this example, the goal is not to establish two way communication in and out of the DOM or data capture...which would require a more expensive exchange.

In the next few days, I will offer up another example which stays within the Viewpoint Developers License agreement...it's an ecommerce site with a Viewpoint experience and a buy button which works...a modification from the Infinite Possibilities contest.
hth?
DavidR
http://www.rich3d.com/3D/RichMesser.html

Hi David,

I m sorry but you have not used ActionScript for this scene. Flash is only used as texture and Pre/post animator with not animation at all inside. The button are layer text, nothing more.

Yes it is a good exemple of what can be done with Webdevelopper license: Start and stop animation, move camera and play with hyperview.

Now tell me how to make a watch work (like mine for Tag Heuer or the Seiko sample from Viewpoint) without calling Javascript form MTX and without driving the scene from Javascript.

I have used 1 500 lines of Javascript code, Seiko used also a lot.

Hello ibob
Thanks for your response, it is perfect and succinct. I intermingled my use of Action Scripting to allow a more defining discussion. "huh?" you say...

My true aim with this example is to give a taste of what may be done with the new and un-improved Viewpoint Web Developer license. You suggested (and have shown) where it could be/should be...you are a master.
-------------
There are people in the community who think that Viewpoint has repealed the ability create interactive scenes (unless a high price is paid). The Yahoo investment board has people suggesting the sky is falling with this blunder (they should be more careful). I think it is important for everybody standing on the sidelines and following this to better understanding where the line in the sand is truly drawn...things are not that bad (even before Andrew's help making it even more reasonable, but don't stop Andrew! ibob and barnaby are right).

If we are going to move the needle, then first we must define where it is.
---------
There are three distinct focuses to consider;
1) The ability to interact within a scene...events triggering actions through specific scripting. ergo the Me109 example...
2) The ability to command and manipulate a scene from the HTML page defining it. Text, imagery/buttons, and Flash ActionScript triggers et al would be included here.
3) The ability to extract behavioral data based on interactions within a scene. If one digs deep enough into the true and current meaning of Rich Media...it is largely about behavioral data extracted from rich content. The Viewpoint CI product seems to fit well here...
-----
"
Events Versus Actions
Event refers to a use or system input, such as a cursor enter/exit or a mouse click. An action is something that is scripted to occur in the scene in response to an event."
(from Viewpoint Scene Interactors Ref. Guide Page 9)
---
Action Scripting in VET
Please note: the following code is an example from the *.mtx and was stripped of other content (e.g. making the cursor change when over the instance) for clarity. If you were to use this example in your own *.mtx, then place it after the Instances declarations and before the MTSTimelem components. An MTSAction should be always be placed above in the heirarchy of the XML/*.mtx file...and still before the MTSTimelem part of the scene structure.

[MTSAction Name="rudder_script" Type="Script" >
[MTSAssignProperty Event="MouseLeftClick" Target="MTSTimeElem.rudder_ANIM::trgr" Value="1" />
[/MTSAction>

[MTSInteractor Name="Rudder" NeverHandle="1" >
[Target Name="MTSInstance.Rudder" />
[MTSHandle Event="MouseLeftClick" Action="rudder_script" />
[/MTSInteractor>
---------------------------------
This is only a simple, slice of an example. Other actions that can be scripted include GetProperty and MTSPingURL.
------------------------
Without me being too far off base...
- The example here is a small example of the still available power and value with the Viewpoint Web Developer license (they don't pay me).
- The developer community has communicated in more technical terms with Andrew on the phorum a la ibob...which might allow for focus #2 noted above.
- Focus item #3 should be more expensive. I'm thinking Viewpoint might just be doing the right thing here...if item #2 is achieved.
--
So, ibob, can I show you how to re-create your beautiful Taghauer watches so interaction is contained with the Viewpoint scene? Maybe, probably not though...you really are a brilliant one.

Should full-fledge gaming (for example) or communication out of the scene be allowed under the web developer license?
It is somewhere in this answer that the line will be drawn...

I really
hth
DavidR

[This message was edited by DavidR on February 06, 2004 at 01:34 PM.]

I intend to send this post to the Federal Trade COmmission to investivgate whether Viewpoint misled me when I purchased Enliven Pro. If the developer license changed, I should have been informed. I bought Enliven Pro and it is JUNK!!!!!!! NO SUPPORT, NO REAL EXAMPLES, PRODUCT SALES DESCRIPTION MISLEADING.

I WANT MY MONEY BACK AND IF REFUSED, I WILL ESCALATE TO FEDERAL REGULATORS AND LEGAL AUTHORITIES.

wow...what is your real issue?

Mr/Ms BB

I repeat, WOW!

You've really been getting into the forums!

When I saw DavidRs' Messershmitt moved to the head of the Gallerys Forum I thought there had been an update.

The license agreement referenced here hasn't been mentioned except for this post since Enliven became public.

The potential of Enliven has really created a BANG for Viewpoint. As a marketing company possessing possibly the most advanced graphics engine created, I'm sure they're rethinking a lot. Come on, they're considering changing the corporate name considering the response generated by our input regarding Enliven, not to fail to mention the potential of morphing capability.

I had to work with Scene Builder and CLs' Poser for quite a while before even contacting the major graphics creation companies about the use of their content in Viewpoint. After doing so I was told there was no problem in using DAZ, CP, as well as others content. The public access to such content is going to result in significant issues.

IMnsHO, this technology is going to bring the internet to life. Enliven is, hopefully, going to be the "One Stop Shop" for getting it there. Enliven will be able to get it done, plus a whole lot more. Personally, if it could directly import .pz3, .cr2, .car, etc. files it would be,... Awesome.

Others have already created content with Enliven and are making money resulting from it.
Content I've created has been, somewhat, influencial in selling Viewpoint. So, the product we currently have is sufficient to produce content we can sell, so I really fail to see how it doesn't meet any production requirements that we might have.

As for expectations!
Expectations are presumptions, lacking fact.
Have you posted to the forums before? Posted to the Wish List? Submitted a bug report? I would really love to see what creations, or WIPs, have inspired such passion?

Hark! Viewpoint!

Behold, what passion thy creation hath wrought?

This message has been edited. Last edited by: lauramb,