Jump to content

Forums Announcement

Read-Only Mode for Announcements & Changelogs

Dear Survivors, we'd like to inform you that this forum will transition to read-only mode. From now on, it will serve exclusively as a platform for official announcements and changelogs.

For all community discussions, debates, and engagement, we encourage you to join us on our social media platforms: Discord, Twitter/X, Facebook.

Thank you for being a valued part of our community. We look forward to connecting with you on our other channels!

Stay safe out there,
Your DayZ Team

Fifty (DayZ)

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Fifty (DayZ)

  • Rank
    On the Coast
  1. Hi, I've seen a number of posts about people being stuck on loading screens and then the inevitable (its an alpha, deal with it) posts, but I've got some new information that may help. Ive got 2 accounts, both through steam, and up until yesterday, both working perfectly. (in case you want to know, you can have 2 accounts through steam, which shares a common folder as long as you run the arma 2 through steam first before using something like six launcher as that will write over the reg files with the CD key from account 2 over account 1 and vice versa) Anyway, long story short, 1 account had a ghillie suit from 1.7.2 in his inv, but wasn't used due to the known bug. When 1.7.2.3 came out, I put it on with great success. Wandered around with some mates, killed a few things and then logged. When I logged on next, I was back where I had initially placed the ghillie on. I placed it on again and continued to have a blast and logout near the northwest corner of the map (still in trees). Since that last log in, I have been stuck on every load in screen for every sever. Now if I load up my second steam account (same base files minus the CD Key) No problems, can join any 1.7.2.3 server around. (common files at Beta 94876) As soon as I change back to the other account, then perma stuck on the loading screen. This makes me think its either server side or HIVE side and not a local problem. Maybe you guys could take a look at that?
×