Been encountering a new error lately...

elseguard

https://ibb.co/f1WSwF

Never seen this error before, but it started earlier this week when I was just walking around in ren cen and it crashed and gave me that message. So I tried verifying the files and went to select the character I was playing on and it crashed again right when the loading bar reached 100 ingame. Tried that several more times, same result so I tried to log into another character instead and it worked fine.

Went back to the character it crashed on and it kept crashing. I took a break and played on another character and then tried the next day and never crashed. About 2 days later (today), had no problems and then all of a sudden it happens on a totally different character. Tried verifying and logging in again but now the error pops up right when the launcher is ready to start the game.

Im totally baffled since this has never happened in the whole time I have been with the game through multiple computers. Doing what the error advises and verifying seems to do nothing. Anyone else encountered this before?

nextnametaken

Corruption of your hard drive maybe? Re-download the assets?

Do you happen to have a your character costume saved? Maybe that file will reveal a corrupt costume piece, but it's probably local to your computer.

Unknown

This content has been removed.

pantagruel01

Note that the error message doesn't say what .hogg file is to blame, though you can often guess. Also that error message really should be changed, because force verify will not fix it unless you take further measures.

elseguard

I actually forgot to come back here and say it now seems to be fixed. I got home and tried removing my costume folder then verifying which didn't work, so I just decided to complete reinstall which worked and I have been just sort of testing it and putting it through the paces with character switching then playing for about 6 hours now and have had no problem.

Though I didn't see you guys info in time, I really appreciate it. I still wonder what would have caused this to happen in the first place.

pantagruel01

scarletthound4 said:

Though I didn't see you guys info in time, I really appreciate it. I still wonder what would have caused this to happen in the first place.

It's a modestly common thing; probably a wild pointer somewhere.

elseguard

I see. Very odd, like I said I never in like I think its been 6 years(?) since I first came to CO had that error happen. Oh well, thanks again for helping out.

markhawkman

basically you got corrupted data when patching. there are safeguards to stop this, but they really just make it less common.