We're still looking at this internally, but are having a difficult time nailing down the exact problem (which is the main reason it didn't get fixed in today's patch), especially since it doesn't happen to everyone 100% of the time. We're continuing to investigate, though.Darkintellect wrote: »I'm also having this problem again as well as most in my guild. If we could get word on the issue Gina, we would be very appreciative. We know you guys have a lot on your plate so just an idea of what we could expect would be tremendous.
ZOS_GinaBruno wrote: »We're still looking at this internally, but are having a difficult time nailing down the exact problem (which is the main reason it didn't get fixed in today's patch), especially since it doesn't happen to everyone 100% of the time. We're continuing to investigate, though.
If you lose your markers, then login game, then try to move before EVERYTHING loads in you also lose them again.
ZOS_GinaBruno wrote: »We're still looking at this internally, but are having a difficult time nailing down the exact problem (which is the main reason it didn't get fixed in today's patch), especially since it doesn't happen to everyone 100% of the time. We're continuing to investigate, though.
ZOS_GinaBruno wrote: »We're still looking at this internally, but are having a difficult time nailing down the exact problem (which is the main reason it didn't get fixed in today's patch), especially since it doesn't happen to everyone 100% of the time. We're continuing to investigate, though.
Some specifics I have noticed that might help you out:
If my game lags out and disconnects, crashes out, or freezes up and has to be force closed, the next login my alliance indicators will vanish.
On one occasion, my game lagged out and had to be force closed, relogging lost me my indicators but was in the middle of a warzone and kept fighting anyway, lagged out and had to force close again, relogging brought the indicators back.
The work-around for this issue appears to be as follows:
If the indicators are missing, go into the interface menu and turn them to off
force close (alt+f4, NOT the Quit option in menu) the client and relog
after relogging, turn the indicators back on in the menu
It may be that the client is having some issues with saving/loading up the correct menu settings after a crash or force close, but not certain.
The biggest counter to this is the fact that the toggle cannot be simply turned on and off to bring indicators back, the only solution also involves closing the client completely.
Hope you guys can figure this out soon -- it is a terrible glitch in PvP and the new players to the game are going to be sent into Cyrodiil to experience it starting at level 10.
@ZOS_GinaBruno
ZOS_GinaBruno wrote: »We're still looking at this internally, but are having a difficult time nailing down the exact problem (which is the main reason it didn't get fixed in today's patch), especially since it doesn't happen to everyone 100% of the time. We're continuing to investigate, though.
ZOS_GinaBruno wrote: »Thanks so much for the extra information, guys. This definitely helps. We'll let you know whenever we have an update!
@ZOS_GinaBruno
It has something to do with UserSettings.txt. I don't know if the game 'caches' these settings, however, it seems that crashes, excessive loading screens, and sometimes death cause the bug to manifest. Twice I crashed last night, both times the bug occurred, and both times I had left the launcher open. (I believe there is a memory leak with your launcher.) I can play for hours without crashing if I remember to close the launcher.
That said, the best method I've found to resolve this bug with 100% success (so far) is to:
- Rename my UserSettings.txt to OLDUserSettings.txt
- Start the game and exit it properly.
- After closing the game, I delete the newly created UserSettings.Txt and rename OLDUserSettings.txt back.
- Restart the game and my alliance indicators and healthbars have returned.
(This allows me to retain all my settings, and fixes the bug.)
I've noticed that the game doesn't actually create the new UserSettings file until it actually closes... Which lends to my suspicions of it utilizing a cache. If that's the case, then the corruption is taking place with how it reads that cache. I'm guessing remnants of old (1.5) code not cleaned up to work in line with new (1.6/2.0) code.
Edit, Words, sentences, please send coffee. (Dunkins)