|
Forum > Miscellaneous
ERROR #132 - An actual way to fix it. (Build 12340)
<< < (4/8) > >>
ruffo91:
ERROR #132 (0x85100084) Fatal Exception
Program: C:UsersRubenDesktopWoW SaronWowejecutable.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:004DFEDD
The instruction at "0x004DFEDD" referenced memory at "0xBE860A92".
The memory could not be "written".
This error appears when I am in the character creation screen, I used a converted version of Pandaren model and Worgen, when Im in a different race like Felorc for example and I select the Pandaren race the crash appear but if I enter in Character creation screen and the Pandaren race is default selected no problem appears.
schlumpf:
--- Quote from: "ruffo91" ---ERROR #132 (0x85100084) Fatal Exception
Program: C:UsersRubenDesktopWoW SaronWowejecutable.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:004DFEDD
The instruction at "0x004DFEDD" referenced memory at "0xBE860A92".
The memory could not be "written".
This error appears when I am in the character creation screen, I used a converted version of Pandaren model and Worgen, when Im in a different race like Felorc for example and I select the Pandaren race the crash appear but if I enter in Character creation screen and the Pandaren race is default selected no problem appears.
--- End quote ---
Races are hard coded. Selecting death knights will also crash most likely. Only reusing existing races will correctly work. Also, do not change internal names for them. Same for classes. Every non-existing race/class is a potential crash.
ruffo91:
Okay, thanks for your reply Im trying to fix it cause just 2 races crash me the client and I have 24, I think that the problem is in CharacterSections.dbc or in the model so not totally sure. If I'll fix it I'll tell you how. Thank you.
Mjollna:
Hi everyone, long time no see :)
I don't know if that can help someone in the future, but I've solved a #132 labeled 0x85100084.
I had created a custom m2, and when launching the game with that model it crashed. I realized I had forgotten to add a dummy "stand" anim in the mdl before converting from mdlvis to m2.
After that, no more error. It might be very specific, but maybe someone will face this case again some day.
MR. Farrare:
--- Quote from: "Mjollna" ---Hi everyone, long time no see :)
I don't know if that can help someone in the future, but I've solved a #132 labeled 0x85100084.
I had created a custom m2, and when launching the game with that model it crashed. I realized I had forgotten to add a dummy "stand" anim in the mdl before converting from mdlvis to m2.
After that, no more error. It might be very specific, but maybe someone will face this case again some day.
--- End quote ---
thank you you blossom gorgues princess!!!! just kidding thank you for this info Mjollna :D
and its really nice to see you back legend
Navigation
[0] Message Index
[#] Next page
[*] Previous page
|