2010-10-31, 07:18 AM
Stands to reason that if you're revamping your game, creating an all-new "Maple Story: The Next Generation", with new UI and screen resolution, you'd make it work right with current operating systems, doesn't it?
But yeah, this is Nexon we're talking about...
FWIW, I don't think it's an OS compatibility issue as such. It's poor programming in general. I've had the infamous "zakum winks in and out until you d/c" glitch happen on Windows XP, as well as other random glitches and disconnects. Nowhere near as bad as my friends using Vista or Windows 7, but enough to know it's not just the operating system.
It appears that MapleStory does bad things to graphic memory. Not sure what the English name is, in Hebrew we call it "memory smear", where you allocate X bytes but then write Y>X bytes of data, trampling memory locations that don't belong to you. These are some of the nastier bugs C++ allows you to make (don't get me wrong, I love C, but its power cuts both ways), and really hard to debug, because your process can be miles away before something tries to access the smeared locations for their legitimate use, and finds garbage there.
Vista and Windows 7 might just be more sensitive to these things, more likely to have something important just where Maple likes to encroach.
Anyway, Maple needs to be rewritten from the ground up. That dev blog intimated some rewriting of fundamentals has been done, but from what people are saying above, it's not enough.
But yeah, this is Nexon we're talking about...
FWIW, I don't think it's an OS compatibility issue as such. It's poor programming in general. I've had the infamous "zakum winks in and out until you d/c" glitch happen on Windows XP, as well as other random glitches and disconnects. Nowhere near as bad as my friends using Vista or Windows 7, but enough to know it's not just the operating system.
It appears that MapleStory does bad things to graphic memory. Not sure what the English name is, in Hebrew we call it "memory smear", where you allocate X bytes but then write Y>X bytes of data, trampling memory locations that don't belong to you. These are some of the nastier bugs C++ allows you to make (don't get me wrong, I love C, but its power cuts both ways), and really hard to debug, because your process can be miles away before something tries to access the smeared locations for their legitimate use, and finds garbage there.
Vista and Windows 7 might just be more sensitive to these things, more likely to have something important just where Maple likes to encroach.
Anyway, Maple needs to be rewritten from the ground up. That dev blog intimated some rewriting of fundamentals has been done, but from what people are saying above, it's not enough.