2010-10-31, 04:15 PM
I agree with some of the previous posters about this dcing issue is got to do the age old dcing issue in zakum (where it would flash and disappear starting at the body), which is writing to out of bound memory. This on going "bug" was minor when the only version of windows is XP, but as Microsoft tighten up windows to make it "more stable" starting with Vista (also the same with Win7), the detection of processes accessing memory outside of the process's allocated data space has gotten more stringent to protect processes from corrupting system data areas to prevent BSOD, it now will terminate the (bad) processes a lot more than XP, hence the dcing issue we are seeing. It has nothing to do with "compatibility issues", all to do with memory over run bugs.
I don't agree with having to completely re-write Maple client, as it is highly unlikely and its a very big task, and if Nexon don't track down those bugs but to just re-write another client, there is no saying they won't create the similar problem, just with different codes. Also with such a big coding project there bound to introduce other bugs. The best thing to do is try to track down those bugs and fix them, which I think thats what Nexon's intended to do with the eTracer (but they need to make it work a lot better, as it doesn't trigger most of the time when the client DCs).
I don't agree with having to completely re-write Maple client, as it is highly unlikely and its a very big task, and if Nexon don't track down those bugs but to just re-write another client, there is no saying they won't create the similar problem, just with different codes. Also with such a big coding project there bound to introduce other bugs. The best thing to do is try to track down those bugs and fix them, which I think thats what Nexon's intended to do with the eTracer (but they need to make it work a lot better, as it doesn't trigger most of the time when the client DCs).