[SOLVED] Error #132 0x007B31F8 read 0x00000010

Forum > Miscellaneous

<< < (2/2)

Vel:
I know this problem. Problem in "bugged chunks" in the adt. This problem causes only in Blizz Based ADT. Problem may be fixed via 010 hex editor.

how?

1) you need "check" (ingame) all chunks and then find problem areas (memory could not be read)
2) Manually find this chunks or chunk diapason in hex editor
3) in DetailID spawn flags (01101110101011 011010111011010 101110101011 101101010101 e.t.c) set all to 00000000000 0000000000000 00000000000000 00000000000000
4) then error on this chunk will be fixed.
-----------------
Ofc this is hardcore method, but I think - there is no other ways

full: http://imagr.eu/up/50c45da72b9655_example.png

Milly:
Thanks for the screenshot Vel. It's really helpful for people who haven't the slightest clue what they're doing. I'll take a look at it tomorrow or sometime. I've kinda come to terms with the fact that Blizzard ADTs are too much of a hassle and I've set my heart on a new project, using Steff's custommap1 preset. But either way this has been a great learning experience and thanks for all the help everyone.

Milly:
Update: I have tested and confirmed that this problem is caused by the Doodad Fixer when used on certain Blizzard ADT chunks. I can also confirm that Vel's method of fixing this problem works. However, if you use the Doodad Fixer again after fixing the chunks, it recreates the problem. Therefore I recommend that you wait until your Blizzard ADT project is completed before spending your time tediously fixing the problem in 010 Editor.

Navigation

[0] Message Index

[*] Previous page

Go to full version