[x3d-public] start timer at fraction 0 after scene loading

[John Carlson]

There's no issue with ProximitySensors, if you start the right sensors
that start character timers.

Leif73Final.x3dv:DEF Leif_ActivateSensor ProximitySensor { size 1000000
1000000 1000000 }
Leif73Final.x3dv:ROUTE Leif_ActivateSensor.enterTime TO
Leif_z100sTimer.startTime
Lily73Final.x3dv:DEF Lily_ActivateSensor ProximitySensor { size 1000000
1000000 1000000 }
Lily73Final.x3dv:ROUTE Lily_ActivateSensor.enterTime TO
Lily_z100sTimer.startTime
Tufani73Final.x3dv:DEF Tufani_ActivateSensor ProximitySensor { size 1000000
1000000 1000000 }
Tufani73Final.x3dv:ROUTE Tufani_ActivateSensor.enterTime TO
Tufani_z100sTimer.startTime

Above is what I do for individual characters. I don't know why they don't
transfer to the main scene.  Are ProximitySensors disabled because they are
Inlined?

Thanks!

John

On Fri, Sep 8, 2023 at 11:28 PM John Carlson <yottzumm at gmail.com> wrote:

>
> > That is my problem. getting that startTime.
>> Right, the common source for a startTime is TouchSensor,
>> ProximitySensor, timeTrigger.
>>
>
> I'm not sure about timeTrigger...could you please explain?  Wouldn't that
> require a TimeTrigger node that is triggered with a boolean event that
> comes ultimately from a set_fraction (0 I hope) event?  Where do you get
> the fraction but a Time-based sensor?
>
> I did experience some PreludeTimeSensor/JumpStart/JoeKickStart successes.
> I also experienced stuff starting right in the middle.
>
> I will work getting stuff into WS, already started this evening.
>
> John
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230909/1c79e796/attachment.html>