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

Invalid Yuki Location Issues

Discussion in 'Bug Reports' started by Kawaii Believe It, Jan 24, 2016.

?

Is anyone else experiencing issues with this new update?

  1. Nope, working like a charm

    0 vote(s)
    0.0%

  2. Yee ~ My gosh, help meh!

    1 vote(s)
    100.0%
Thread Status:
Not open for further replies.
  1. Kawaii Believe It

    Kawaii Believe It Active Member

    Joined:
    Jan 22, 2016
    Messages:
    237
    Likes Received:
    36
    Summary of Issue Encountered
    Location bugs between room changes
    Location bugs at elevation changes
    Location is bugging between Client-Server
    Plausible prop boundary changes

    Expected Result
    Smooth Client-Server communication of my HUD
    Improved communication with specific bones on the model

    Actual Result
    Random warps on map
    Client stuns for the server to remap my location
    Prop boundary changes
    HUD randomly flashes
    Server communication is causing a constant lag - Like the server keeps requesting information

    Steps to Reproduce
    Change your elevation
    Change locations
    Sprint/Change location of HUD

    Screenshots/Error(s) in Console (if applicable) of the Issue



    I would like to add the comment, that my client was fine about a day or two ago with no issues. I showed in the video that it is not a performance issue. Sorry for a lengthy video. Had to state some key points, get the warp to randomly occur, experiment to find probable cause. Even rejoining the server did not assist.
     
    Kawaii Believe It, Jan 24, 2016
    #1
  2. WinterPhoenix96

    WinterPhoenix96 Founder/Lead Developer Staff Member Founder/Lead Developer

    Joined:
    Dec 28, 2015
    Messages:
    472
    Likes Received:
    146
    The video you provided does not provide any evidence of the Location System acting abnormally. It may take longer than usual in some situations to switch your Location, but this is simply due to whatever amount of load the Server is under at that moment. The "pushing back," as you claim, is what's known as "Rubberbanding" and happens due to lag as well. However, the occurrence of rubberbanding was possible before the new Location System was deployed, thus making this report Invalid.
     
    WinterPhoenix96, Jan 24, 2016
    #2
Thread Status:
Not open for further replies.