Results 1 to 2 of 2

Thread: lookat

  1. #1
    Junior Member
    Join Date
    Sep 2010
    Posts
    6

    lookat

    Node transform elements (<translate>, <rotate>, etc.) are composed in the order that they occur.
    If I understand correctly, for CAMERA instance, the INVERSE of the composed transformation should be applied.
    I tested this by sample DAE files from the model bank.
    But I think in the case of <lookat> transform, the INVERSE of <lookat> should not be used for camera.
    (I noticed this when I tested some files from Google 3D warehouse.)
    Is this thought correct?
    If so, I think that defining behavior of composed <lookat> and other transforms for camera is difficult.
    A <node> can contain both camera and geometries (and child nodes).
    Can I assume that <lookat> occurs solely for camera instance?

  2. #2
    Senior Member
    Join Date
    Aug 2004
    Location
    California
    Posts
    771

    Re: lookat

    The <instance_camera> and <lookat> elements are not special and have no exceptional rules. Treat them regularly with other transforms and instances.

    In general, all <node> elements in COLLADA should be processed consistently. There are no special cases.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •