Dismiss Notice
This Section is READ ONLY - All Posts Are Archived

[Known]Players are not seeing each other in the proper locations

Discussion in 'Release 37 Bug Forum' started by Datendrache, Dec 15, 2016.

Thread Status:
Not open for further replies.
  1. Datendrache

    Datendrache Avatar

    Messages:
    321
    Likes Received:
    1,466
    Trophy Points:
    55
    Gender:
    Male
    Title: Players are not seeing each other in the proper locations

    Reproduction Rate: 50%+

    Blocker? (Yes/No/Partial) Yes

    Details: Players cannot interact with each other or see each other in the same zone.

    Steps to Reproduce:

    1) Form a party with multiple players

    2) Enter an instance for a particular area (for example, Vertas Pass)

    3) Have players go to the center

    4) Have players identify the people they see

    5) Observe: A number of players will not be visible to other players.

    6) Observe: Some players may appear to be running in place in other parts of the map

    Additional: If you interact with a “running” player such as Trade, the window will open and close.

    Additional: Partying isn’t required.

    Additional: Easy to observe in Owl's Head where many players are able to be seen running in place at the same time.

    User Specs:

    AMD 8350 w/Geforce 970, Windows 8.1, 16 GB RAM, SotA Release 520.

    Bug Category: Players

    [​IMG]
     
    Last edited: Dec 15, 2016
  2. Attenwood

    Attenwood Portalarian Emeritus Dev Emeritus

    Messages:
    6,910
    Likes Received:
    5,863
    Trophy Points:
    153
    Believe this is tied to an issue that is currently being reported tied to the game not updating the positions properly for non-master players. We have a ticket created for this, which we hope to address as quickly as possiblee. Thank you for the additional details!
     
    Gaelis and Roycestein Kaelstrom like this.
  3. Attenwood

    Attenwood Portalarian Emeritus Dev Emeritus

    Messages:
    6,910
    Likes Received:
    5,863
    Trophy Points:
    153
    Bug: 38620
     
    Roycestein Kaelstrom likes this.
  4. Ancev

    Ancev Avatar

    Messages:
    1,150
    Likes Received:
    1,956
    Trophy Points:
    113
    Seeing some strange occurrences with mobs and PvP as well. invisible mobs and players that will kill you, can't see them on the screen but they can see you apparently. In one case a skeleton kept attacking me even as my avatar was exiting the zone.. and the spawn point of the skeleton was in the middle of DR near the lich area.
     
  5. zcundizmond

    zcundizmond Avatar

    Messages:
    1
    Likes Received:
    10
    Trophy Points:
    3
    What you just described with DRW is my life right now.
     
    Roycestein Kaelstrom likes this.
  6. null2

    null2 Avatar

    Messages:
    373
    Likes Received:
    1,152
    Trophy Points:
    55
    It appears to me that mobs will attack a person if they think it is in range. They think people are in range because of desync issues between the master (/whoismaster) and the person getting attacked. So if you die and res at an ankh half the map away, but the person /whoismaster is seeing you res and run into a wall near some mobs. Those mobs will see you as well and kick your butt even though you are halfway across the map.
     
    Roycestein Kaelstrom likes this.
  7. Widsith [MGT]

    Widsith [MGT] Avatar

    Messages:
    714
    Likes Received:
    646
    Trophy Points:
    93
    Yup, we ran into this in a siege scene (outside Upper Fortus) last night. I had rez'ed at an ankh and was still getting my butt kicked by a lich halfway across the scene. We brought in some more help, and there were at least 3 separate desync'ed sets of us at times. Using a ladder up to / down from one of the in-scene walls appeared to force some sort of resync. Might be a good weekend to go mining...
     
  8. Vallo Frostbane

    Vallo Frostbane Avatar

    Messages:
    1,756
    Likes Received:
    3,572
    Trophy Points:
    113
    I hope they fix this before the holiday.. real gamebreaker.
     
Thread Status:
Not open for further replies.