vehicle.setPostion(x,y,z) don't work properly in latest API version 0.8.1

  • Hi.


    The short story:


    In old API version (0.7.0.3) vehicle.setPosition(x,y,z) work very well (when i was on rowboat at position 0,91,0 for example and move to 100,91,100, i got on right place with a very small deviance from desired position), but in latest API version this is unusable :( . For example i am on a rowboat and wanted to go to 100,91,100 from position 0,91,0 and bad surprise ... i landed at 4.8,91,4.8, very very far away from wanted location ...

    I think something changed between this versions.


    This is the start position (almost 0,90,0):

    and landed here after vehicle.setPosition(100,91,100):


    red51 Can you look at this issue?

    Thx.



    The Long story:


    In version 0.7.0.3 i wrote a plugin for a ferry travel route when in am in a boat. All was based on vehicle.setPosition with a player inside and some background threads who move vehicle along a predefined points of a route. Except some glitch at players animation, all worked flawless. But after update of latest version of game (not sure if Seasons update or Steam Update) plugin stop working properly. After some debug i isolate culprit at function vehicle.setPosition who not work anymore like in the past .


    PS:


    Some video from test area ... when plugin worked ...


    https://www.youtube.com/watch?v=Lo2Nqf6M-mk


    https://www.youtube.com/watch?v=deWG06sSY08

  • BUT YOU CAN JUST DISASSEMBLE THE BOAT, MOVE WHERE YOU NEED TO AND ASSEMBLE THE BOAT.

    Я даю всем полное право использовать мои чертежи

    I give everyone the full right to use my drawings

  • BUT YOU CAN JUST DISASSEMBLE THE BOAT, MOVE WHERE YOU NEED TO AND ASSEMBLE THE BOAT.

    This is not the point. The idea is to make a automatically routes where a rowboat move from point A to point B. And for this we have API vehicle.setPosition(...) which in latest version move to point C not B like before.

  • Sorry for responding so late! I took a closer look at this issue and it seems that the game overwrites the new position too quickly with the current position, resulting in the behaviour you're seeing... I will fix that with the next update :)

Participate now!

Don’t have an account yet? Create a new account now and be part of our community!