[DiscordArchive] are you updating every particle?
[DiscordArchive] are you updating every particle?
Original source
What would cause an error 132 in the wow exe? I am using ARAC with the Worgen/Goblin (acore) and have done a file compare and merge for differences (to add worg/goblin to the ARAC setup). When i click on Worgen on the char select, i get the access violation 132 in the EXE ... when i click goblin, it jsut locks my wow up.
rektbyfaith
03-07-2022, 08:50 PM #11Archived author: AngryPenguinStudio • Posted: 2022-03-07T20:50:00.529000+00:00
Original source
What would cause an error 132 in the wow exe? I am using ARAC with the Worgen/Goblin (acore) and have done a file compare and merge for differences (to add worg/goblin to the ARAC setup). When i click on Worgen on the char select, i get the access violation 132 in the EXE ... when i click goblin, it jsut locks my wow up.
Original source
the error isn't what's interesting, it's what address it breaks at
rektbyfaith
03-07-2022, 08:50 PM #12Archived author: <o> • Posted: 2022-03-07T20:50:34.615000+00:00
Original source
the error isn't what's interesting, it's what address it breaks at
Original source
Try enabling windows compatibility mode for win7 on exe
rektbyfaith
03-07-2022, 08:50 PM #13Archived author: Xecc • Posted: 2022-03-07T20:50:53.368000+00:00
Original source
Try enabling windows compatibility mode for win7 on exe
Original source
testing this - i will post the error if that helps
rektbyfaith
03-07-2022, 08:51 PM #14Archived author: AngryPenguinStudio • Posted: 2022-03-07T20:51:45.036000+00:00
Original source
testing this - i will post the error if that helps
Original source
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:006DC86A
The instruction at "0x006DC86A" referenced memory at "0x00000004".
The memory could not be "read".
rektbyfaith
03-07-2022, 08:52 PM #15Archived author: AngryPenguinStudio • Posted: 2022-03-07T20:52:47.488000+00:00
Original source
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:006DC86A
The instruction at "0x006DC86A" referenced memory at "0x00000004".
The memory could not be "read".
Original source
No idea then, win7 mode fixed Error 132 for me, was not related to goblins tho
rektbyfaith
03-07-2022, 08:53 PM #16Archived author: Xecc • Posted: 2022-03-07T20:53:52.135000+00:00
Original source
No idea then, win7 mode fixed Error 132 for me, was not related to goblins tho
Original source
I agree, <@!160857905879449600> knows for sure
rektbyfaith
03-07-2022, 08:54 PM #17Archived author: Xecc • Posted: 2022-03-07T20:54:49.531000+00:00
Original source
I agree, <@!160857905879449600> knows for sure
Original source
132 is a generic error for almost all wow exceptions, it's common with custom stuff
rektbyfaith
03-07-2022, 08:59 PM #18Archived author: <o> • Posted: 2022-03-07T20:59:38.754000+00:00
Original source
132 is a generic error for almost all wow exceptions, it's common with custom stuff
Original source
as for your address i can't find anything related around it, but it's common for the game to crash if your character models are messed up in some way
rektbyfaith
03-07-2022, 09:01 PM #19Archived author: <o> • Posted: 2022-03-07T21:01:01.819000+00:00
Original source
as for your address i can't find anything related around it, but it's common for the game to crash if your character models are messed up in some way
rektbyfaith
03-07-2022, 09:02 PM #20Archived author: A2 • Posted: 2022-03-07T21:02:06.623000+00:00
Original source
![[Image: unknown.png?ex=690c640e&is=690b128e&hm=e...84c658e2b&]](https://cdn.discordapp.com/attachments/415944535718494208/950498603430998036/unknown.png?ex=690c640e&is=690b128e&hm=e19d556649130ab4543a0c689f954fe67d7f1b6dbde78ff0a93986b84c658e2b&)
1 Guest(s)
1 Guest(s)