I have done some observations on the recent crashing problems and noticed some pretty important things; 1. When a crash happens its exactly the same as the "buff running out change channel" crash. 2. The crash is very specific, its not a regular CTD, instead you get disconnected first before your maple client closes. 3. I've noticed something very intresting with Onyx Apples which might give a clue to where the problem originates: - When Appling before a moment where you would need to change grapics (ex HT spawn, Zakum, Krex 2nd eye spawn) the gfx bugs that you would normally avoid by changing gfx will still appear. I managed to get through the gfx bugs by changing settings every 10 seconds untill my apple ran out. Now heres the intresting thing; After my apple ran out , ALL the gfx bugs had disappeared. I managed to reproduce this issue 3/3 attempts (since its kind of hard for me to test this issue without messing up my daily boss runs). - The Onyx Apple buff often does not disappear while your damage does decrease back to its original number. So my guess is that if there was something changed to the way buffs are handled OR something that has been changed in the WZ files causing cirtain timers to become different. That being said, it does not explain why VMware and regular clients suddently received so many compatibility problems. Perhaps a cirtain wz file has exceeded its maximum capacity for cirtain OS compatiblity settings, causing a bunch of null-references for the game? Darius
http://pasteboard.co/1mtqh1sN.png heres a screen shot of one of my many crash errors i was doing nothing besides training (usually crash occours when i jump
The errors you're posting are related to updating your wz info or simply getting the pointer error due to not running in win 98 compatibility (which I do not recommend)
