Vivaty Studio routing TimeSensor to TimeSensor in X3D
up vote
0
down vote
favorite
I am currently working on a simple X3D project, which is basically modeling the landing of a chopper.
I used TimeSensor to animate my chopper model, and an example of what I wrote is this:
<TimeSensor DEF='time1' cycleInterval='0.1' loop='true'></TimeSensor>
<OrientationInterpolator DEF='turn1' key='0 0.5 1' keyValue='1 0 0 0 1 0 0 1.046 1 0 0 2.093'></OrientationInterpolator>
<ROUTE fromNode='time1' fromField ='fraction_changed' toNode='turn1' toField='set_fraction'></ROUTE>
<ROUTE fromNode='turn1' fromField ='value_changed' toNode='rotorT' toField='set_rotation'></ROUTE>
I also got some auto-generated x3d stuff from my professor (he used Vivaty Studio), and interestingly I saw this:
<TimeSensor DEF='Wizard' cycleInterval='3.75000000' loop='true' startTime='-1'/>
<TimeSensor DEF='vizx_init' cycleInterval='.1' loop='true'/>
<ROUTE fromNode='vizx_init' fromField='cycleTime' toNode='Wizard' toField='startTime'/>
<ROUTE fromNode='vizx_init' fromField='cycleTime' toNode='vizx_init' toField='stopTime'/>
<ROUTE fromNode='Wizard' fromField='fraction_changed' toNode='Wizard_pos0' toField='set_fraction'/>
<ROUTE fromNode='Wizard_pos0' fromField='value_changed' toNode='dad_Group1' toField='set_translation'/>
It routes a timesensor to another timesensor, and also routes a timesensor to itself (vizx_init).
When I manually replace it with my style of having time sensor, my model still behaves the same way. Is there any point in having this overhead? What is the functionality of routing a timesensor to it self (line 5 in code block 2)?
visual-studio x3dom
add a comment |
up vote
0
down vote
favorite
I am currently working on a simple X3D project, which is basically modeling the landing of a chopper.
I used TimeSensor to animate my chopper model, and an example of what I wrote is this:
<TimeSensor DEF='time1' cycleInterval='0.1' loop='true'></TimeSensor>
<OrientationInterpolator DEF='turn1' key='0 0.5 1' keyValue='1 0 0 0 1 0 0 1.046 1 0 0 2.093'></OrientationInterpolator>
<ROUTE fromNode='time1' fromField ='fraction_changed' toNode='turn1' toField='set_fraction'></ROUTE>
<ROUTE fromNode='turn1' fromField ='value_changed' toNode='rotorT' toField='set_rotation'></ROUTE>
I also got some auto-generated x3d stuff from my professor (he used Vivaty Studio), and interestingly I saw this:
<TimeSensor DEF='Wizard' cycleInterval='3.75000000' loop='true' startTime='-1'/>
<TimeSensor DEF='vizx_init' cycleInterval='.1' loop='true'/>
<ROUTE fromNode='vizx_init' fromField='cycleTime' toNode='Wizard' toField='startTime'/>
<ROUTE fromNode='vizx_init' fromField='cycleTime' toNode='vizx_init' toField='stopTime'/>
<ROUTE fromNode='Wizard' fromField='fraction_changed' toNode='Wizard_pos0' toField='set_fraction'/>
<ROUTE fromNode='Wizard_pos0' fromField='value_changed' toNode='dad_Group1' toField='set_translation'/>
It routes a timesensor to another timesensor, and also routes a timesensor to itself (vizx_init).
When I manually replace it with my style of having time sensor, my model still behaves the same way. Is there any point in having this overhead? What is the functionality of routing a timesensor to it self (line 5 in code block 2)?
visual-studio x3dom
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am currently working on a simple X3D project, which is basically modeling the landing of a chopper.
I used TimeSensor to animate my chopper model, and an example of what I wrote is this:
<TimeSensor DEF='time1' cycleInterval='0.1' loop='true'></TimeSensor>
<OrientationInterpolator DEF='turn1' key='0 0.5 1' keyValue='1 0 0 0 1 0 0 1.046 1 0 0 2.093'></OrientationInterpolator>
<ROUTE fromNode='time1' fromField ='fraction_changed' toNode='turn1' toField='set_fraction'></ROUTE>
<ROUTE fromNode='turn1' fromField ='value_changed' toNode='rotorT' toField='set_rotation'></ROUTE>
I also got some auto-generated x3d stuff from my professor (he used Vivaty Studio), and interestingly I saw this:
<TimeSensor DEF='Wizard' cycleInterval='3.75000000' loop='true' startTime='-1'/>
<TimeSensor DEF='vizx_init' cycleInterval='.1' loop='true'/>
<ROUTE fromNode='vizx_init' fromField='cycleTime' toNode='Wizard' toField='startTime'/>
<ROUTE fromNode='vizx_init' fromField='cycleTime' toNode='vizx_init' toField='stopTime'/>
<ROUTE fromNode='Wizard' fromField='fraction_changed' toNode='Wizard_pos0' toField='set_fraction'/>
<ROUTE fromNode='Wizard_pos0' fromField='value_changed' toNode='dad_Group1' toField='set_translation'/>
It routes a timesensor to another timesensor, and also routes a timesensor to itself (vizx_init).
When I manually replace it with my style of having time sensor, my model still behaves the same way. Is there any point in having this overhead? What is the functionality of routing a timesensor to it self (line 5 in code block 2)?
visual-studio x3dom
I am currently working on a simple X3D project, which is basically modeling the landing of a chopper.
I used TimeSensor to animate my chopper model, and an example of what I wrote is this:
<TimeSensor DEF='time1' cycleInterval='0.1' loop='true'></TimeSensor>
<OrientationInterpolator DEF='turn1' key='0 0.5 1' keyValue='1 0 0 0 1 0 0 1.046 1 0 0 2.093'></OrientationInterpolator>
<ROUTE fromNode='time1' fromField ='fraction_changed' toNode='turn1' toField='set_fraction'></ROUTE>
<ROUTE fromNode='turn1' fromField ='value_changed' toNode='rotorT' toField='set_rotation'></ROUTE>
I also got some auto-generated x3d stuff from my professor (he used Vivaty Studio), and interestingly I saw this:
<TimeSensor DEF='Wizard' cycleInterval='3.75000000' loop='true' startTime='-1'/>
<TimeSensor DEF='vizx_init' cycleInterval='.1' loop='true'/>
<ROUTE fromNode='vizx_init' fromField='cycleTime' toNode='Wizard' toField='startTime'/>
<ROUTE fromNode='vizx_init' fromField='cycleTime' toNode='vizx_init' toField='stopTime'/>
<ROUTE fromNode='Wizard' fromField='fraction_changed' toNode='Wizard_pos0' toField='set_fraction'/>
<ROUTE fromNode='Wizard_pos0' fromField='value_changed' toNode='dad_Group1' toField='set_translation'/>
It routes a timesensor to another timesensor, and also routes a timesensor to itself (vizx_init).
When I manually replace it with my style of having time sensor, my model still behaves the same way. Is there any point in having this overhead? What is the functionality of routing a timesensor to it self (line 5 in code block 2)?
visual-studio x3dom
visual-studio x3dom
asked Nov 7 at 16:44
Keren Chen
11
11
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53194033%2fvivaty-studio-routing-timesensor-to-timesensor-in-x3d%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown