-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ Map & Vmap & Mmaps ] Extractors problem #302
Comments
use tools with correct command-structure: mapextractor.exe |
Map & DBC ExtractorLoading enGB locale MPQs Detected locale: enGB Extracting dbc files... after this will be close automaticly .. without any errors :( |
u need a original client with have complete data structure, |
Downloading .. whatever Thanks because of answering <3 |
sry me , can u give me download links instead of clientDownloader? |
this has copyright .. is not allowed.. look at google.. look there at RePack.. there are some forums from outside EU where you can find all finished extracted tools or completed links to client |
I don't have any problem with the extractors are in google drive, but with my own compiled can't do it :( I don't think it's cause of client |
none have changed the extractor tools past 3(?) years.. |
nothing works for me |
first debugging of the tools. i receive a buffer to small in StormLib.. |
I don't know how should compile on 64bit i just do the normal way and will be compile on 32bit |
same failure in 32 bit.. both on same place.. it's a function inside the stormlib code, copying a string in memory.. reading on google about this failure show that the behavior of the strcpy command has no memory security alerts.. but new compiler wrapping such security to the command. |
after the last commit, I did compile for again but nothing changes :( |
Confirmed with using self compiled extractors in release x64. Used full enUS client with all folders. |
Hi there.
after running mapextractor.exe on my client's folder after typing extracting dbc files.
closed! without any errors. any supports?
The text was updated successfully, but these errors were encountered: