Jump to content

Movix

Pathfinder
  • Content Count

    5
  • Joined

  • Last visited

Everything posted by Movix

  1. Movix

    bug Tames falling through floors and boats

    Hi all, from what we investigated we think that it mostly happen on places where floor are stacked on each other, and it happend either in buildings on ground or on top of water
  2. Hello, in the couple of past week we lost serveral important animals (Elephant, Rhinos, Bears, ...) that glitched throught the ceilings and into floors. From what we investigated it seems to be the case everywhere where mobs are stored on top of stacked floors, and it mostly happen upon server restarts. Would be great to correct this as soon as possible because it's annoying to loose important mobs just because of buggy game mecanics and collision algorythms. btw. it also seems that NPC that you dismount while to close to walls just get stuck behind the walls.
  3. Movix

    Possible reason for fetch server info issue?

    Hello, Here what i learned so far. When you try to connect and hit a time out, try opening a web page. I occurs nealry each time i got a time out, my network stack is stuck. No webpage opens, as if i'm disconnected from internet. Curriously discord voice chat remains functional, but if i CTRL+R the reload fails. Only way to quickly repair the network stack is to close steam, disable the NIC and reenable it. Also if you wait long enough without doing t his the network starts working again. While not working the network seems ok, locally everything is working, zyxel router is showing no issues and no blocking anything, log is clean. At first look it seems like a DNS issue, but DNS server is working and all other PCs in the local network are just working fine. So what in the world is causing the network stack to freeze for new outgoing connexions on the PC that encountered an atlas timeout ? I'm still investigating, but so far it helped me to avoid clicking "reconnect" in atlas whilst the network was not working by checking simply to open a new web page. As long as your web page does not open it's not worth trying to connect Atals, it will simply not work and prevent the network from coming back.
  4. Movix

    Connection Lost/Timeout

    Hello, Here what i learned so far. When you try to connect and hit a time out, try opening a web page. I occurs nealry each time i got a time out, my network stack is stuck. No webpage opens, as if i'm disconnected from internet. Curriously discord voice chat remains functional, but if i CTRL+R the reload fails. Only way to quickly repair the network stack is to close steam, disable the NIC and reenable it. Also if you wait long enough without doing t his the network starts working again. While not working the network seems ok, locally everything is working, zyxel router is showing no issues and no blocking anything, log is clean. At first look it seems like a DNS issue, but DNS server is working and all other PCs in the local network are just working fine. So what in the world is causing the network stack to freeze for new outgoing connexions on the PC that encountered an atlas timeout ? I'm still investigating, but so far it helped me to avoid clicking "reconnect" in atlas whilst the network was not working by checking simply to open a new web page. As long as your web page does not open it's not worth trying to connect Atals, it will simply not work and prevent the network from coming back.
  5. Movix

    5.6 - Still Timing Out

    Hello, Here what i learned so far. When you try to connect and hit a time out, try opening a web page. I occurs nealry each time i got a time out, my network stack is stuck. No webpage opens, as if i'm disconnected from internet. Curriously discord voice chat remains functional, but if i CTRL+R the reload fails. Only way to quickly repair the network stack is to close steam, disable the NIC and reenable it. Also if you wait long enough without doing t his the network starts working again. While not working the network seems ok, locally everything is working, zyxel router is showing no issues and no blocking anything, log is clean. At first look it seems like a DNS issue, but DNS server is working and all other PCs in the local network are just working fine. So what in the world is causing the network stack to freeze for new outgoing connexions on the PC that encountered an atlas timeout ? I'm still investigating, but so far it helped me to avoid clicking "reconnect" in atlas whilst the network was not working by checking simply to open a new web page. As long as your web page does not open it's not worth trying to connect Atals, it will simply not work and prevent the network from coming back.
×