Hi!

Hope I am in the right Thread to ask how much network bandwith will be used in 5-10-25-man Raids, or even in Wintergrasp. Using addons like Omen, Visualheal, Pallypower, DBM and some more. Have a feeling that lowest numbers are like 2-5 KB when not in instance, but can be 15-20 in raids, but how high can be the number in WG?

If someone know about the numbers with and without addons, and which ones are causing high network usage.

Thank you in advance,
Kobor

You can figure out that yourself if you are running Vista/7. Open the Task Manager, then start the Resource Monitor. There you have all the interesting info, just look for the network tab and check the traffic the wow task is using.

I want to make 2 remarks that may also take the form of questions.

- There's a possibility threaded optimization on nvidia SLI / core 2 duo systems may improve FPS on 25man fights if disabled on nvidia settings. Can anyone confirm or deny? (The reason I pursued this potential optimization is that it is certain that in Quake3 engines threaded optimization must by disabled in order to avoid severe FPS drops.)

- Running /reloadui before each fight may improve the probability of .exe crashes or disconnects. I suspect it may be related to memory leaks, possibly related to addons (even if they may not appear oversized on an in-game memory listing). Can anyone confirm or deny?

One way I got better overall performance was to upgrade my sound card.

It may not be intuitive but taking the load off your computer when it comes to processing sound can help it process the graphics. In my case, I bought a USB sound card (Soundblaster X-Fi Go!). It cost about $40 and is plug and play. WoW plays a lot smoother using this for me. You might also try doing into dxdiag, select the sound tab, and moving hardware sound acceleration down one notch at a time and then seeing if game performance improves. Basically, you are degrading the sound quality some and offloading sound processing to the USB card.

Recently, I went from playing on my laptop (slow, not gaming oriented) to my desktop (big, fast, built for gaming) and was getting really frustrated with an odd lag spike or slow down. Basically, every once in awhile my client would "lag" so that people were running in place and spells kept casting then it would do a high speed "catch up." I tried a bunch of stuff, updating video drivers, changing settings, reinstalling WoW, etc. Basically everything the WoW technical forum tells you to do.

In the end, I figured it out it had nothing to do with my video settings, card, ram, HDD, processor, client or anything. All of my troubles were coming from Windows wireless zone configuration (WZC). WZC is the stock windows wireless finding utility. It turns out, every 60 seconds or so, WZC does a search for wireless networks in range and with my wifi card (Linksys WMP54G) this causes a big lag spike every time it scans.

In order to fix this problem, I installed the Linksys wireless utility and disable the WZC (Admin Tools -> Services -> Wireless Zone Configuration -> Turn off and set to disable on start up)

I have had no problems with random lag spikes anymore and life has been good again. So in short, if you are getting weird lag spikes that cause the game to slow down then do a fast paced catch up where everything speeds up around you, try turning off your Wireless Zone Configuration in Windows.

Edit in response to below: I am using Windows XP. The services disabling of the WZC worked for me, but I did read about the stuff you were saying in regards to Vista.

Uzziel, are you running XP on that computer, or a later Windows OS?

I had the hardest time with the WLAN Autoconfig (the Vista equivalent of Wireless Zero) due to it being tied to regular wireless functionality and not easily disabled or overridden like WZC could be. There are command line tweaks that can fix it, but the best solution I found (short of switching to a wired connection) was a freeware utility called WLAN Optimizer (Home-WLAN Optimizer - Optimize wireless gaming, audio and video streaming...).

The easy way to tell if you have this particular issue is to open a command prompt and type "ping google.com -t" and observe the results. If WZC or WLAN Autoconfig is the culprit you should see a significant spike in the response time about once a minute.

/script ReloadUI()

Omen does not use the addon communication channel at all, every client gets the threatlist for his current target (and pretty much every other mob that at least someone in your raid has targeted)

I'm running Windows 7 and experiencing MapMem.cpp and M2Shared.cpp crashes. Has anyone found a fix/workaround for those under Windows 7?

I've tried deleting my WTF, and Interface folders and this error still happens. It seems like WoW goes up to 1.7 GB ram used and then -- usually after zoning, say from Storm Peaks to Icecrown -- it tries to page up to over 2 GB and then crashes.

That is exactly what happens - have you done any manual (or addon based) tweaking to the config.wtf? I had this problem when I upped my texture cache, and resetting to a default wtf and just using the in-game quality settings stopped it from happening to me entirely. Until Blizzard decides to do a LargeAddressAware or 64-bit WoW that is likely your only option.

I run on W7 with maxed out settings including manual tweaks like 1600 farclip and max texture cache, but the "2GB crash" only happens on very rare occasions and only when flying long distances coupled with leaving/going to Dalaran. My mods take less than 2 MiB, so they don't cause much issue.

If you're reaching 2GB with default settings and no mods, I'd say that's very strange.

There are some experimental changes to the graphical system in patch 3.3, I would recommend seeing how things work for you on the PTR, although personally, I find it's hard to replicate the packed Dalaran of a live high population server at peak times when all premades start in their home cities and people are in dungeons.

I using Apple Magic Mouse on Windows 7. But I found there are some problems when I use this mouse play WOW.

1). Some time right click will stop auto-run.
2). When I didn't use mouse few second. The mouse will "sleep" for save power I think. I have to click mouse to wake it up. But it will make mistake sometimes.

Anyone have the same problem?

For me the fix for this was resetting all the WoW folder permissions to give my user account full access. No idea why that helped, but it did. It's worth a try I'd say.

Tried changing permissions; still getting crashes

The only thing i would say is try to delete certain files/folders to cater to wow's "needs".
Other then that, idk man =/

Try this:

1 day after I installed Windows 7, my PC crashed when I was in WoW. Complete crash, only pressing the reset button worked. Since that day I was getting 1-5 crashes a day. I updated all drivers, scanned my PC, defragmented my drives. I tried running the game in compatibility modes, disabling desktop themes, prioritising WoW. I tried everything. I read hundered of pieces of info all over the internet. No one knew the solution. What repeated most times was that Soundblaster drivers suck big time and cause trouble. So I removed my X-Fi and switched to onboard sound.
Boom, no crashes for about a week. When I started to believe that I solved my problem, my PC started crashing again last week. This time, I couldn't stay online for more than 3 minutes before a crash. That did it for me. Since I read that many people experienced the same problem after installing W7, I decided to install XP. First day: great, no crashes.
And again, I thought my problem was over. The following day stripped me of my hope. I crashed in XP... And again 30 minutes later...
Now I started to suspect my HDD. W7 is on c:\, XP is on d:\, WoW is on d:\.
I reinstalled WoW, this time on another partition, e:\. I logged on yesterday at 6:40 p.m. and stayed online till 11:20 p.m. with no crashes at all. I ran a thorough check of my drives. I left the PC on overnight and checked in the morning - no reports of any bad sectors, whatever. Apparently my HDD is completely healthy. Which means I will start crashing again. And I still don't know the reason...

Magic Mouse is the latest version of mouse from Apple. I have turn off the bluetooth power manager and found the mouse not "sleep" anymore. But right click still stop auto-run when I use right click to change the direction.

Moving my View Distance slider to two notches from Max has stopped my crashes. A small price to pay until Blizzard releases 64-bit executable.

Actually, it didn't. It made them more rare, but didn't fix them.

However, if I don't run WoW in XP Compatibility mode, I don't get the memory crashes.

Instead, WoW runs smoothly -- until I tab out in a loading screen and then try to tab back in. Then it closes with no error message. This is on Win 7 64 pro, in Full Screen Windowed Mode. I have an nVidia GTX 260 and am using the latest drivers, 195.62.

How I can fix this so that I can tab back in and out freely while loading?

This probably isn't ideal for you, but have you tried windowed mode? Might "solve" your problem.

I'm running in Full Screen Windowed Mode -- i.e. Maximized Windowed Mode.

I think this might have to do with they way Windows7 treats programs that are not responding. If you run WoW in windowed (not maximized) mode with the title bar visible, you can see "(not responding)" being appended to the title when logging in with a character. If you then interact with WoW (ie clicking on it), Windows 7 just exits it. You might try to not send any inputs to WoW when it is loading.

I am experiencing regular disconnects when attending 25-man raids. Up to 4, yes four times on fights like Loatheb.

-I tried disabling all my addons
-I have disabled most of the combatlog
-I tried disabling WZC (As was mentioned in this thread, but I can't test it atm.)

Anybody here who has had the same issues, and maybe figured out a solution. I've searched high and low, but I can not find any solutions.