MSVCR120!memset+0x24
byondcore!DMFrame::DMFrame+0x49
byondcore!DMGraphic::operator=+0x8e
byondcore!DMIcon::operator=+0xa8
byondcore!DungClient::AutoReconnect_CIO+0x37a0
byondcore!DungClient::AutoReconnect_CIO+0x12a4
byondcore!DungClient::AutoReconnect_CIO+0x54ae
byondcore!DungClient::AutoReconnect_CIO+0x286
byondcore!LocalDB::HubToJS+0x149
byondcore!DungClient::AutoReconnect_CIO+0x191d3
byondcore!DungClient::AutoReconnect_CIO+0x21451
byondcore!DungClient::AutoReconnect_CIO+0x9f53
byondcore!DungClient::AutoReconnect_CIO+0x91a6
byondcore!DungClient::AutoReconnect_CIO+0x21451
byondcore!DungClient::AutoReconnect_CIO+0x17aba
byondcore!DungClient::AutoReconnect_CIO+0x21451
byondcore!DungClient::AutoReconnect_CIO+0x17aba
byondcore!DungClient::AutoReconnect_CIO+0x21451
byondcore!DungClient::AutoReconnect_CIO+0x17aba
byondcore!DungClient::AutoReconnect_CIO+0x21451
ID:2162674
Oct 21 2016, 9:31 am
|
|||||||||||||
| |||||||||||||
Oct 21 2016, 10:06 am
|
|
"511" is not a valid version number yet for any bug report; I need the exact specific build, especially with a crash dump.
|
Problem: 511.1344 isn't a real version. The 1344 build is actually 510.
Did you mean 511.1354? If so, I would recommend upgrading to 511.1360 as it's the most recent. It might not make a difference but it couldn't hurt. |
sorry yeah it was 1354, i'll update to 1360. Today isn't a good day for me apparently
|