I haven't noticed any drastic change in performance after logging in today, but virtually the first thing I always do after a patch hits is to reset the Video Settings to their defaults, by pressing [X] in the corresponding menu. Then I set them back to ultra-high quality, and at my iMac's resolution of 2560x1440, I got the same FPS as before, as far as I was able to tell (20-25 FPS outdoors, but I won't probably use these settings on live later on).Yesterday's version of the 64bit Mac client ran beautifully (30+ fps), today's is running at an average of 5 fps. Altering graphics settings is having no effect - same on minimum and maximum settings.
I just posted this on the patch notes thread but I'm gonna shamelessly repeat it here:
Yesterday's version of the 64bit Mac client ran beautifully (30+ fps), today's is running at an average of 5 fps. Altering graphics settings is having no effect - same on minimum and maximum settings.
2.4Ghz i7 (quad core)
8Gb memory
GeForce GT 650M 1024Mb
Faulting application name: eso64.exe, version: 1.0.0.1, time stamp: 0x56b55b28 Faulting module name: eso64.exe, version: 1.0.0.1, time stamp: 0x56b55b28 Exception code: 0xc0000005 Fault offset: 0x0000000000912e53 Faulting process id: 0x2e58 Faulting application start time: 0x01d1638f35fb1fe4 Faulting application path: D :\Program Files (x86)\Zenimax Online\The Elder Scrolls Online PTS\game\client\eso64.exe Faulting module path: D :\Program Files (x86)\Zenimax Online\The Elder Scrolls Online PTS\game\client\eso64.exe Report Id: c8112328-f7e6-486d-8cb5-fc0efb331012 Faulting package full name: Faulting package-relative application ID:
Fault bucket 120408964937, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: eso64.exe P2: 1.0.0.1 P3: 56b55b28 P4: eso64.exe P5: 1.0.0.1 P6: 56b55b28 P7: c0000005 P8: 0000000000912e53 P9: P10: Attached files: C:\Users\Milos\AppData\Local\Temp\WERB189.tmp.WERInternalMetadata.xml C:\Windows\Temp\WERB5DF.tmp.csv C:\Users\Milos\AppData\Local\Temp\WERB5FE.tmp.appcompat.txt C:\ProgramData\Microsoft\Windows\WER\Temp\WERB61E.tmp.dmp C:\Users\Milos\AppData\Local\Temp\WERB63F.tmp.WERDataCollectionFailure.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_eso64.exe_50b2ea5ffb3dae2d3a20b356c3f9d220794b5f57_333209f0_2cb2b64b Analysis symbol: Rechecking for solution: 0 Report Id: 61675719-3018-46cd-944c-762af0faba1e Report Status: 4104 Hashed bucket: 60e38259453ab646da80bb1166002954
@Dagoth_Rac What's your DirectX version? Vista's standard DirectX 9 is no longer supported.Dagoth_Rac wrote: »Neither 32-bit nor 64-bit working on my Windows Vista machine and I have used PTS in the past. Both result in the standard ESO crash dialog box where you enter what you were doing and hit submit.
ZOS_GinaBruno wrote: »This is the official feedback thread for the 64-bit Client. Specific feedback that the team is looking for includes:
- If you used the 64-bit client, did you find it worked ok?
- Did you crash while using this client? If so, how often?
- Did you notice anything peculiar?
- Did you run into any issues when using /feedback or /bug?
- Do you have any other general feedback?
Version=1 EventType=APPCRASH EventTime=130995355326165912 ReportType=2 Consent=1 UploadTime=130995355326940218 ReportIdentifier=22e676e7-cf88-11e5-8d7c-5404a64de33e IntegratorReportIdentifier=13dac06f-20b3-4f7b-900a-92c8b8e321c5 NsAppName=eso64.exe Response.BucketId=60e38259453ab646da80bb1166002954 Response.BucketTable=4 Response.LegacyBucketId=120408964937 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=eso64.exe Sig[1].Name=Application Version Sig[1].Value=1.0.0.1 Sig[2].Name=Application Timestamp Sig[2].Value=56b55b28 Sig[3].Name=Fault Module Name Sig[3].Value=eso64.exe Sig[4].Name=Fault Module Version Sig[4].Value=1.0.0.1 Sig[5].Name=Fault Module Timestamp Sig[5].Value=56b55b28 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=0000000000912e53 DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.10586.2.0.0.768.101 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=972c DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=972cbf321beba0872c6ad37af43c68e6 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=185a DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=185a06e82a2ef5f7e55512c1ea4c1d24 UI[2]=C:\Program Files (x86)\Zenimax Online\The Elder Scrolls Online PTS\game\client\eso64.exe UI[3]=ESO has stopped working UI[4]=Windows can check online for a solution to the problem. UI[5]=Check online for a solution and close the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program
@Dagoth_Rac What's your DirectX version? Vista's standard DirectX 9 is no longer supported.Dagoth_Rac wrote: »Neither 32-bit nor 64-bit working on my Windows Vista machine and I have used PTS in the past. Both result in the standard ESO crash dialog box where you enter what you were doing and hit submit.
NewBlacksmurf wrote: »Eek I'm going to sit out this round on PTS. Waiting for consistent stability first.
Wow. Not sure if ppl joke about ZOS not testing stuff but this doesn't look good
NewBlacksmurf wrote: »Eek I'm going to sit out this round on PTS. Waiting for consistent stability first.
Wow. Not sure if ppl joke about ZOS not testing stuff but this doesn't look good
If you're truly looking for 'consistent stability', the PTS is not where you'll find it.
Hmm, interesting. I'm not sure what to suggest, really. I had thought the end of official support for Vista was tied to DirectX, but maybe there's more to it than that.Dagoth_Rac wrote: »@Enodoc@Dagoth_Rac What's your DirectX version? Vista's standard DirectX 9 is no longer supported.Dagoth_Rac wrote: »Neither 32-bit nor 64-bit working on my Windows Vista machine and I have used PTS in the past. Both result in the standard ESO crash dialog box where you enter what you were doing and hit submit.
Dual GTX 560 Ti with DirectX 11 on my Vista 64-bit machine. The 32-bit eso.exe crashes immediately, but I do get the ESO crash dialog box where it asks me to type in what was happening when I crashed. I just installed PTS on a Windows 7 64-bit machine with a single GTX 970, again DirectX 11. And again, 32-bit eso.exe crashes immediately with the standard ESO crash dialog box where it asks me to type in what was happening when I crashed. It does behave differently with eso64.exe. On Vista, eso64.exe is standard ESO crash. On Windows 7, eso64.exe is "0xc000007b" error.
KennanTheCold wrote: »I'm running on Windows 7 Ultimate, downloaded latest patch for PTS, and after hitting launch I get the standard crash dialog box from ESO, asking me to describe what I was doing at time of crash. This has happened for both the 32-bit and 64-bit version. Really hoping this will be solved soon, in the meantime i'm considering unistalling PTS and reinstalling it. Any thoughts on that?
ZOS_GinaBruno wrote: »We believe we've found the problem relating to an encryption issue, and will let you know when we'll be able to fix it as soon as we can. Still testing, though. Please stand by...
It's nice to know that the problem was found. I guess the fix is coming with next weeks patch? Or will it be pushed in a smaller incremental as soon as it's ready?
ZOS_GinaBruno wrote: »We believe we've found the problem relating to an encryption issue, and will let you know when we'll be able to fix it as soon as we can. Still testing, though. Please stand by...
It's nice to know that the problem was found. I guess the fix is coming with next weeks patch? Or will it be pushed in a smaller incremental as soon as it's ready?
ZOS_GinaBruno wrote: »b92303008rwb17_ESO wrote: »Excuse me if I ask a silly question, but how do I know if I downloaded the 64 bit client?
It automatically downloads when you patch.
ZOS_GinaBruno wrote: »ZOS_GinaBruno wrote: »We believe we've found the problem relating to an encryption issue, and will let you know when we'll be able to fix it as soon as we can. Still testing, though. Please stand by...
It's nice to know that the problem was found. I guess the fix is coming with next weeks patch? Or will it be pushed in a smaller incremental as soon as it's ready?
Yes, should be fixed with our incremental early next week. Unfortunately we cannot do another full patch before then, and it's not something that can be hotfixed.
ZOS_GinaBruno wrote: »Is @Xiana the only one that's been able to successfully launch the 64-bit client? Anyone else?