Maintenance for the week of December 16:
• PC/Mac: No maintenance – December 16
• NA megaservers for patch maintenance – December 17, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• EU megaservers for patch maintenance – December 17, 9:00 UTC (4:00AM EST) - 17:00 UTC (12:00PM EST)
• PC/Mac: No maintenance – December 16
• NA megaservers for patch maintenance – December 17, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• EU megaservers for patch maintenance – December 17, 9:00 UTC (4:00AM EST) - 17:00 UTC (12:00PM EST)
The issues on the North American megaservers have been resolved at this time. If you continue to experience difficulties at login, please restart your client. Thank you for your patience!
CTD on launch of eso.exe!
KitLightning
✭✭✭✭
ESO_Launcher states "PLAY"!
No corrupt file traced in report.txt file!
Ticket submitted
Files eso0204.dat to eso0215.dat have value of 14 bytes (ie. 0 byte). Removing these files and forcing a validation of the builds integrity will process the files recreation in the build, yet the patching of the build will stop at 113Mb left and any transfer on the drive stops!
Removed all new files and rebooting to verify the build outside the ESO_Launcher, which has been flawed beyond the ages of god-knows-when. Using a defragment software on the ESO build exclusively only to discover that the eso.exe was corrupt. Thank you Game Consultant for yet again not finding a corrupted file. eso.exe renamed with .bck afterwards. Redid the process of validating the build, then repair, download and lastly patching. ESO_Launcher states "PLAY" so we look at the .dat files which still reads 14 bytes. Since I tend to be forgetfull I hit PLAY and it runs!
A question for @ZOS_GinaBruno or whomever it may be, since Support are fond of their auto-replies yet voiding the ticket as is. Are the mentioned eso204-215.dat files missing content?
No corrupt file traced in report.txt file!
Ticket submitted
Files eso0204.dat to eso0215.dat have value of 14 bytes (ie. 0 byte). Removing these files and forcing a validation of the builds integrity will process the files recreation in the build, yet the patching of the build will stop at 113Mb left and any transfer on the drive stops!
Removed all new files and rebooting to verify the build outside the ESO_Launcher, which has been flawed beyond the ages of god-knows-when. Using a defragment software on the ESO build exclusively only to discover that the eso.exe was corrupt. Thank you Game Consultant for yet again not finding a corrupted file. eso.exe renamed with .bck afterwards. Redid the process of validating the build, then repair, download and lastly patching. ESO_Launcher states "PLAY" so we look at the .dat files which still reads 14 bytes. Since I tend to be forgetfull I hit PLAY and it runs!
A question for @ZOS_GinaBruno or whomever it may be, since Support are fond of their auto-replies yet voiding the ticket as is. Are the mentioned eso204-215.dat files missing content?
"I'd rather be insane in a sane world, than sane in an insane world!" ~Me
MechWarrior: Living Legends – Total conversion modification for Crysis Wars.
kitlightning.deviantart
Warning - This is a spoiler and looking at it for too long may cause irrecoverable eyesight issues.
◔̯◔
◔̯◔
MechWarrior: Living Legends – Total conversion modification for Crysis Wars.
kitlightning.deviantart
0