Modcraft - The community dedicated to quality WoW modding!

Wrath of the Lich King Modding => Miscellaneous => Topic started by: tehrob on March 24, 2014, 01:17:49 pm

Title: [SOLVED] vmap4extractor crash (Trinity / Custom map)
Post by: tehrob on March 24, 2014, 01:17:49 pm
Hey guys,

i got a problem at extracting vmaps...
For 2 Weeks i was able to extract vmaps from my Custom maps without any Problems.
I didn't modified the extracter, it worked out of the box.

Since a Week when i try to extract vmaps, the vmap4extractor crashes while processing my map.
There is no crash dump or some error message, even in debug mode. Nothing.
I reextracted dbcs and maps too, and maps are working.

(http://imagr.eu/up/533023146672d_Screen_Shot_03-24-14_at_01.19_PM.PNG)

The code where it crashes:

vmapexport.cpp
http://pastebin.com/fYRFbyBA (http://pastebin.com/fYRFbyBA" onclick="window.open(this.href);return false;)

After the crash the vmapassembler is creating some of my Tiles of the Map to working Vmaps.


I have two Versions of this Map.

The First Version is for enUS Client, its for a friend of mine. With enUS edited DBCs etc..
This Version works perfectly, i can extract the vmaps without Problems.

The Second Version is only for me and for deDE Client.
It has edited dbcs for deDE Client with same entrys as the enUS Version.
The difference is, i added in this Version some more ADTs lately. And only with this extra ADTs,
the extractor is crashing.

Any Ideas how to figure out whats happened?

EDIT:
i noticed the Problem details Message ^^^

Problem signature:
   Problem Event Name: APPCRASH
   Application Name: vmap4extractor.exe
   Application Version: 0.0.0.0
   Application Timestamp: 5326f301
   Fault Module Name: MSVCR120.dll
   Fault Module Version: 12.0.21005.1
   Fault Module Timestamp: 524f7ce6
   Exception Code: c0000005
   Exception Offset: 0000f20c
   OS Version: 6.3.9600.2.0.0.768.101
   Locale ID: 2057
   Additional Information 1: 5861
   Additional Information 2: 5861822e1919d7c014bbb064c64908b2
   Additional Information 3: 01d7
   Additional Information 4: 01d7340064827245f2249cd1f1a7c264
Title: Re: [QUESTION] vmap4extractor crash (Trinity / Custom map)
Post by: Ascathos on March 25, 2014, 01:40:14 pm
Replace

 //sprintf(id_filename,"%02u %02u %03u",x,y,map_ids.id);//!!!!!!!!!

with

 sprintf(id_filename,"%02u %02u %03u",x,y,map_ids.id);//!!!!!!!!!


Run again
Title: Re: [QUESTION] vmap4extractor crash (Trinity / Custom map)
Post by: tehrob on March 25, 2014, 01:44:05 pm
Quote from: "Ascathos"
Replace

 //sprintf(id_filename,"%02u %02u %03u",x,y,map_ids.id);//!!!!!!!!!

with

 sprintf(id_filename,"%02u %02u %03u",x,y,map_ids.id);//!!!!!!!!!


Run again
Hey, thanks to your answer :)

Wil try it.
Title: Re: [QUESTION] vmap4extractor crash (Trinity / Custom map)
Post by: Ascathos on March 25, 2014, 01:50:45 pm
Note, that is merely an uncommenting to see at which file it breaks.
Title: Re: [QUESTION] vmap4extractor crash (Trinity / Custom map)
Post by: tehrob on March 25, 2014, 01:53:50 pm
Quote from: "Ascathos"
Note, that is merely an uncommenting to see at which file it breaks.

Nothing changed :(, no extra output with filenames...
Title: Re: [QUESTION] vmap4extractor crash (Trinity / Custom map)
Post by: Ascathos on March 25, 2014, 02:11:10 pm
Did you originally extract the DBCs with enUS or deDE ?
Title: Re: [QUESTION] vmap4extractor crash (Trinity / Custom map)
Post by: tehrob on March 25, 2014, 02:36:51 pm
Quote from: "Ascathos"
Did you originally extract the DBCs with enUS or deDE ?

I have two Versions of this Map.


The First Version is for enUS Client, its for a friend of mine. With enUS edited DBCs etc..
This Version works perfectly, i can extract the vmaps without Problems.

The Second Version is only for me and for deDE Client.
It has edited dbcs for deDE Client with same entrys as the enUS Version.
The difference is, i added in this Version some more ADTs lately. And only with this extra ADTs,
the extractor is crashing.
Title: Re: [QUESTION] vmap4extractor crash (Trinity / Custom map)
Post by: tehrob on March 26, 2014, 01:42:40 pm
/solved

The new ADTs had a unclean height difference to the old ADTs. Seems like the vmapextractor doesnt like that.
Thanks for all who had a look at this :)