Scheduled Game Update 11.23.2010

We need alot more than that to know though. Dcing without summoning sounds like it could be a ton of other issues besides. Might just be a bug with auto pot? I have never suffered anything other than dcing at the point of summoning or after a body switch by the boss.

No way, I have a brand new desktop with decent specs, my download speed on speedtest.net is like 6.xx, and the only thing I use the computer is is for MS, I haven't even entered the product key in yet. I never lag anytime ever on it, I should not be dcing at simple things like Zak before it's even summoned. They did not [completely] fix W7 issues, except as CrystalUser said with the maximizing FPS or something.

No way, I have a brand new desktop with decent specs, my download speed on speedtest.net is like 6.xx, and the only thing I use the computer is is for MS, I haven't even entered the product key in yet. I never lag anytime ever on it, I should not be dcing at simple things like Zak before it's even summoned. They did not [completely] fix W7 issues, except as CrystalUser said with the maximizing FPS or something.

What happens exactly when you DC? Does the game just close itself immediately? Do monsters start going invisible and reappearing with lines? Do your menus do the same?

Graphics card specs? Also, try running the game on low graphics, if you are not doing so already. I really do not believe the OS is the root cause of the DC issues.

Unless MS works on W7 like it does on XP then:
[video=youtube;oH1rOL5hB9s]http://www.youtube.com/watch?v=oH1rOL5hB9s[/video]

Uhmmm. 2010 Hp desktop, 750 GB harddrive ram, 4 GB other RAM, 3.6 GHz processing speed. "ATI Radion HD 4200 Integrated Graphics" card, to which Fiel said was noob but was good enough to get the job done for only MS.

I've dced three times at major bosses, two Zaks and one Scarlion. At one Zak and the Scar I walked in and before the monster summoned, screen froze, and then Maple closed and I got a "Maplestory program is not responding" message. In the other Zak I got 3 TT's in after summoning Zak and then Maple closed and same "not responding" message showed up.

I always figured ATI and Windows 7 were a bad mix.

I always figured ATI and Windows 7 were a bad mix.

So is Nvidia and Vista in that case.

I am crossing my fingers hoping this works and that we will be able to boss again. It's literally been over eight months since I have successfully completed a zak fight.

A few things I noticed on my system (MacBook Pro 7,1)...

1. MS takes MUCH longer to load
2. Alt-tabbing is MUCH faster, and no longer seems to glitch
3. MS no longer makes audiodg.exe take insane amounts of CPU usage while alt-tabbed
4. MS crashed once upon CCing...that would be annoying
5. Window mode is MUCH less memory exhaustive (230MB vs. 360MB) and less CPU intensive compared to full screen (while alt-tabbed)

So far so good overall though...it seems that they are heading in the right direction.

But seriously... can't Nexon afford to buy a couple Win7 machines for their QA team?
Don't they have a standard "sanity check" script to run through?

How could they put out this abomination of a "compatibility improvement" patch, which had normal users crashing within minutes? How could they think it would work? Do they do no testing whatsoever?

And if for some reason they had to send it out without in-house testing, couldn't they do it in Tespia? While it's open? People would accept experimental versions and mass crashes there, much easier than in the production servers.
Or... is testing BB of so much higher priority that Nexon would rather crash the live servers, emergency maintenance and all, than lose Tespia uptime? That's just a wee bit ass-backwards... but this *is* Nexon, after all.

After the patch, the game takes forever to start up and I dc whenever i walk around a busy ch1 fm...hope they fix this before bigbang comes out :x

Well, here's a nice little issue.

All visual display for MapleStory breaks upon trying to go from Window mode back into full screen. v.v

Anyone else have this problem?

Anyone know how to get past the crashing at log in? I kinda need to be on today for something important. :<

But seriously... can't Nexon afford to buy a couple Win7 machines for their QA team?
Don't they have a standard "sanity check" script to run through?

How could they put out this abomination of a "compatibility improvement" patch, which had normal users crashing within minutes? How could they think it would work? Do they do no testing whatsoever?

And if for some reason they had to send it out without in-house testing, couldn't they do it in Tespia? While it's open? People would accept experimental versions and mass crashes there, much easier than in the production servers.
Or... is testing BB of so much higher priority that Nexon would rather crash the live servers, emergency maintenance and all, than lose Tespia uptime? That's just a wee bit ass-backwards... but this *is* Nexon, after all.

All the bugs I've seen in this thread (except busy ch1 obviously) are ones that I experienced in the Tespia client as well with Win 7 x64. I don't know what their excuse for updating was but it seems more like it's just an intermediate step on the way to the BB client.