keep getting error 132 everytime I go into certain areas in the alpha, any fix to this?
keep getting error 132 everytime I go into certain areas in the alpha, any fix to this?
Having same error, anyone ?
It's caused by bad doodad's. Nothing you can do about it.
Also having this problem, I feel it might be a graphics issue, driver maybe, as it tends to be abundant in loading redone zones.
Also, Kalzor, a doodad isn't even a word. Its a slang term for a random gadget. What you are saying is that this problem is cause by bad random things and there is nothing we can do about it. Please don't spread false information, especially when you don't back it up and have no idea what you yourself is talking about.
(And it would be doodads, not doodad's.)
Does everyone else having this problem have a weak graphics card? If you have a strong one are you using completely updated drivers, ect?
i really do hope you know what kalzor is talking about Anmoi.... he saying that there a bad objects in game causing it to crash.
not to mention if you Model edit alot of the in game objects are in a file called doodads.. if memory serves me right.
Last edited by Srath47; 05-08-2010 at 05:24 PM.
i've noticed that it depends of the emu that you're using. With mangos i've explored some zones with no crashes. With the first sandbox i've got crashes in zones that worked ok with mangos.
But on thousand needles and tanaris i've experienced crashes with the two emus.
Hope it helps
I did not. I don't use broad senseless words to describe problems. Besides, that still isn't right.
What happens is entering certain areas will drastically drop frame-rates, create lag (On a closed connection lol), and as you go too far into the area you will get the ACCESS_VIOLATION critical error. What's to say that this isn't actually like you suggested a bad object? These are areas that other people are able to explore with easy and have posted pictures and videos of the same.
A good example is the new Stormwind bank and AH, both crash the alpha if you get too close by normal means; Deephome is also a good example because this is a place you can find an abundance of videos of exploration on but half of the area in those videos cause massive slowing and eventual crashing.
Did a bit of research as best I could on the ACCESS_VIOLATION error and, unless its caused by drastically different means in the alpha, it seems to accompany driver based errors, which would make sense for me in the least because of the graphics card that I do have, and the graphical quality of the pictures posted of these gray areas.
If you use the .go command to enter the area you can explore them just fine on any emu. it's just entering of a new zone or subzone that causes the error to surface. I suggest looking for a list of .go locations you can use to explore. IIRC there is a list or 2 in the sticky relating to the alpha in this forum.