1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Bug Camera.concurrentlyTurnTo(Locateable a) Broken?

Discussion in 'Developer Support' started by AlexH666, Jun 8, 2016.

  1. AlexH666

    AlexH666 Χ Ξ Σ

    Joined:
    Apr 15, 2016
    Messages:
    379
    Likes Received:
    101
    The following seems to work:

    Code (Text):
    1. Camera.concurrentlyTurnTo(furnace, Random.nextDouble(0.300,0.600));
    But this will do nothing at all, won't even attempt to move the camera. (Should supposedly use player sense and adjust yaw/pitch itself)

    Code (Text):
    1. Camera.concurrentlyTurnTo(furnace);
    There doesn't seem to be any error in logs.

    Am I doing something wrong or is it actually broken?
     
    #1 AlexH666, Jun 8, 2016
    Last edited: Jun 8, 2016
  2. Arbiter

    Arbiter Mod Automation

    Joined:
    Jul 26, 2013
    Messages:
    2,937
    Likes Received:
    1,266
  3. frazboyz

    Joined:
    Nov 15, 2013
    Messages:
    339
    Likes Received:
    56
    Ummm Camera.turnTo is broken for me :p
     
  4. Cloud

    Cloud Engineer

    Joined:
    Jul 28, 2013
    Messages:
    2,777
    Likes Received:
    1,124
    Please provide additional information.
     
  5. AlexH666

    AlexH666 Χ Ξ Σ

    Joined:
    Apr 15, 2016
    Messages:
    379
    Likes Received:
    101
    I am trying to move the camera to a GameObject (in this case, a furnace).
    furnace = GameObjects.newQuery().names("Furnace").results().nearest();

    If I use Camera.concurrentlyTurnTo(furnace, manual pitch values); It works and moves the camera correctly to whatever values I set.
    If I use Camera.concurrentlyTurnTo(furnace); for it to automatically determine pitch it does nothing at all even if the furnace is not in view.

    -What I expect from it to:
    *Move the camera to gameobject.
    -What happens:
    *Nothing at all.
    -Was I able to manually fix this?
    *Yes, by manually inputting a pitch value.
    -RM Version:
    *Latest.
    -RS Version:
    *RS3.
    -Any error in logs?
    *None.

    I've been able to reproduce this all the time.

    What type of info do you need? I'm more than happy to provide it.
     
    #5 AlexH666, Jun 11, 2016
    Last edited: Jun 11, 2016
  6. Cloud

    Cloud Engineer

    Joined:
    Jul 28, 2013
    Messages:
    2,777
    Likes Received:
    1,124
    What does the dev kit say the yaw and pitch are when this happens?
    --- Double Post Merged, Jun 11, 2016, Original Post Date: Jun 11, 2016 ---
    And how many tiles away is the furnace?
     
  7. AlexH666

    AlexH666 Χ Ξ Σ

    Joined:
    Apr 15, 2016
    Messages:
    379
    Likes Received:
    101
    The furnace is 13 tiles away; can be easily seen when zoomed out.
    Pitch and yaw return valid values within range (0.568 and 83).

    Now that you mention distance, it seems like the camera does turn correctly when an object is close (tried 4 tiles away with a portable).
     
  8. frazboyz

    Joined:
    Nov 15, 2013
    Messages:
    339
    Likes Received:
    56
    I revoke my comment.
     
  9. Cloud

    Cloud Engineer

    Joined:
    Jul 28, 2013
    Messages:
    2,777
    Likes Received:
    1,124
    We don't currently have camera zoom hooked on rs3 so the algorithm was written conservatively for when you're fully zoomed it.
    --- Double Post Merged, Jun 29, 2016, Original Post Date: Jun 17, 2016 ---
    Calculated using linear regression on a data-set that must have been very fucked up looking back on it. Hmm how to approach this...
     
    AlexH666 likes this.

Share This Page

Loading...