ID:2256388
 
BYOND Version:511
Operating System:Windows 10 Home
Web Browser:Chrome 58.0.3029.110
Applies to:Dream Seeker
Status: Open

Issue hasn't been assigned a status value.
Descriptive Problem Summary: When a client connects with dreamseeker 511, they crash immeditally or after a few seconds. This does not occur in 510, only 511. No runtime is generated and DD runs as if nothing happened.

Numbered Steps to Reproduce Problem: Connect to the game in 511, and crash. Hostfiles will be sent to Lummox through pager.

Does the problem occur:
Every time? Or how often? Yes
In other games? No
In other user accounts? Yes
On other computers? Some are getting it, some aren't.

When does the problem NOT occur?

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.) anything before 511 is fine


Workarounds: downgrade to 510

A number of players reported that they don't have this issue. Only a few do. Here's specs of my computer, which is suffering from it:
Radeon Software Version - 16.6
Radeon Software Edition - Crimson
Graphics Chipset - AMD Radeon(TM) R5 Graphics
Memory Size - 512 MB
Memory Type - DDR4
Core Clock - 720 MHz
Windows Version - Windows 10 (64 bit)
System Memory - 16 GB
CPU Type - AMD A10-9600P RADEON R5, 10 COMPUTE CORES 4C+6G


Here's the spec of another player that isn't having any issues with 511:

http://prntscr.com/fi3mt0
https://gyazo.com/597fc9b71b00e980875d36f0bfbabc73


I need crash details from the Windows event viewer for whoever has the issue, which would include the offset where it happened, and also what version was being run.
Info report:

Fault bucket 108962632721, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dreamseeker.exe
P2: 5.0.511.1384
P3: 591d1347
P4: atidxx32.dll
P5: 8.17.10.682
P6: 57aa802e
P7: c0000005
P8: 0006ff71
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6CD8.tmp.WERInt ernalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ dreamseeker.exe_8074908cdcb562b2e61c8bf544433b3569da226e_e75 0c2fb_0c8ca647

Analysis symbol:
Rechecking for solution: 0
Report Id: f91a2daf-c924-448d-9362-d04af0bc64ce
Report Status: 1
Hashed bucket: bfaefff229d4549489c2889fd6ded00d


Error Report
Faulting application name: dreamseeker.exe, version: 5.0.511.1384, time stamp: 0x591d1347
Faulting module name: atidxx32.dll, version: 8.17.10.682, time stamp: 0x57aa802e
Exception code: 0xc0000005
Fault offset: 0x0006ff71
Faulting process id: 0x2ca4
Faulting application start time: 0x01d2e289dbdb42b0
Faulting application path: C:\Users\User\Desktop\byond\bin\dreamseeker.exe
Faulting module path: C:\windows\SYSTEM32\atidxx32.dll
Report Id: f91a2daf-c924-448d-9362-d04af0bc64ce
Faulting package full name:
Faulting package-relative application ID:

Seems to be happening in the ATI driver, have you recently updated it? If not, you could try that and making sure DirectX is fully updated as well.
So, after trying to update the drivers, the whole AMD graphics card stopped working, and at that stage, the game worked. However, after fixing the graphics card driver it stopped again. The drivers are updated after the fix, but game doesn't run.
That would indicate an issue with the latest version of the driver, you may want to forward along some details to ATI.