Syntax problem: Apply rotation

That did the trick!

On to the next one

Best regards,

Jakob

Hi Kees,

Seing that my problem had a rotational centre at (x,y,z)=(0,0,0), I just commented out the "CENTRE" command.

I will give it a go when I get a moment for extra curricular activities

BR,

Jakob

...Some time after;

I've finally gotten to testing whether or not changing the centre of rotation using the CENTRE command has any effect - and it seems that the change does nothing. BTW - I am in 9.4.

Alas, I now have a derived problem. In defining a rotation, one applies it to the whole model, imposing a rotation around a predefined axis. Due to gravitational loading, such an axis is not a correct way of describing the rotation of my model (it will cause an instability). I have attempted to describe this better in the figure below (EDIT: Cannot upload picture for some reason).

Fig. 1 shows a structure without gravitational loading. Fig. 2 shows the structure as it should be - with gravity applied.

In Fig. 3 i propose a way of rotating the structure by only imposing a rotation on two dummy volumes.

Any inputs on how to solve this problem?

Thanks!

Best regards,

Jakob<br /><br />Post edited by: Jakob Andersen, at: 2010/03/22 12:00

Had to go to Windows to get the upload function to work - Here is the figure mentioned above:

sorry, I should add something useful in a general sense too:
The &quot;properties&quot; of a timeline, like _x or _rotation, are not really handled as properties in the other senses of actionscript. For example, say I have a constructor:
function someObject(name){
this.name=name;}
If the constructor is &quot;called&quot; using the &quot;new&quot; keyword,
myPlate=new someObject(&quot;empty&quot;);
then the object &quot;myPlate&quot; has the property, &quot;name&quot;, which is accessed in actionscript as:
myPlate.name
Now, one can access the &quot;properties&quot; of a MovieClip object in the same manner, just as you have, by specifying the path and property identifier, as in:
_root.myMovieClip._rotation
and this is legal syntax. However,
It appears that the actual script processing of this type of access to movieClip properties actually amounts to a &quot;call&quot; to getProperty or setProperty. The result is, until actionscript processing changes with some rev or new release, that this:
_root.myMovieClip._rotation=50;
takes &quot;longer&quot; to execute than does:
setProperty(_root.myMovieClip,_rotation,50);
In a normal setting, this difference in execution times won't have any impact on the presentation. If, however, the presentation contains enough processing requirement to threaten degradation of the frame rate, then small execution time differences between methods of access might be critical to maintaining the frame rate.
Hope that adds something other than just a code fix.