Jump to content
TrinityCore

James

Plebs
  • Posts

    6
  • Joined

  • Last visited

Posts posted by James

  1. Well, the error is generated with this code so I would guess you've got the extractors in the wrong place:

    ...

    This is the CMD script I use on XP without any problems, give it a shot:

    ...

    Hiya,

    Thanks for your suggestion.

    I have tried the CMD script, and it seems to produce the same error. The Map Extractor works perfectly, but when it reaches executing the vmap4extractor, it bugs up

    I do have the vmap files in my WoW WOTLK 3.3.5a folder, and it does indeed work on my other PC, so I think using the extractors on my other pc will temporarily fix the problem I'm having.

  2. Where was WoW installed on the old computer you copied from? I know Vista and Windows 7 can put file and folder permissions on stuff in certain folders and it's possible those copy from the old computer. If that happened you'd have to use the advanced permissions crap and take ownership. Just a thought.

    Thanks for the reply. My World of Warcraft was installed on a Windows XP system. All administrators/users (which is only 1 account on the pc) have full control/read/write permissions on the folder. I don't know what else I could say about this. I will be testing this on another PC with the same version of windows (64bit win 7)

    UPDATE: Just ran it from my other PC, same specs/software as this one and it seems to be working. No idea what is the problem

  3. You mentioned in your OP that you have both wow 3.3.5a and 4.x, did you run "wow.exe" from the 3.3.5a before using the extractors?

    When you run wow.exe from any version it overwrites registry entries that the extractors use so if you've played the 4.x client recently, run the 3.3.5a client and close it (you don't need to actually log in), then immediately run the extractors.

    Yes, I have recently run the 3.3.5a client build 12340 and have closed it multiple times. I haven't ran the 4.x client in a while.

  4. I did a clean WoW install a few days ago, clean Trinity build, install and patched to 3.3.5a. Ran WoW a couple times and then extracted vmaps according to the wiki and go no errors. That probably doesn't help you but I can say it worked for me.

    You could double check to make sure you don't have old extracted data sitting in your WoW folder from before since you copied your old WoW folder.

    Hiya, thanks for the input. I have already tried deleting Buildings/vmaps/maps folders, but it doesn't seem to solve anything.

    Open a command prompt and point it to the path where the BAT file is. Run the BAT file from the command prompt (instead of double-clicking it). This will allow you to see the errors that are generated because the window won't close when the extractor craps out.

    If the errors don't make sense to you, post them here.

    It seems to produce the same error - I have also ran the vmap4extractor.exe by command prompt, but the most it can make is just a folder and 1 wmo file in it.

    uhmy.png

    I also found by repeatedly opening the vmap4extractor.exe, most of the time it produces a random wmo file, ranging from 0 kb file size, up to 600kbs

  5. Hiya,

    I am having trouble with extracting and assembling my vmaps.

    It's pretty much the same as the error below:

    http://www.trinityco...lem-with-vmaps/

    OS: Windows 7 64bit

    Client: WoW 3.3.5a

    Compiler used to make the binaries: Visual C++ 2008 Express 32bit, no compile errors

    I have administrator privileges, I do indeed see the binaries making the folders in my World of Warcraft folder, and sometimes it adds 1 wmo file in the Buildings directory, so there must be no issue with admin privileges.

    I haven't got any registry keys assigned to WoW. It was taken off my old hard drive when I formatted and upgraded the OS.

    I also have a 4.0.6a client in another folder, but I doubt that is an issue, it also was taken off my old HD.

    Yes, the extractor/assembler are in my D:\World of Warcraft\ folder, which is 3.3.5a

    Map extractor works fine.

    I have used the batch file from the wiki and the following batch file:

    
    vmap4extractor.exe -d Data
    
    md vmaps
    
    vmap4assembler.exe Buildings vmaps  
    
    pause
    This is the output:
    
    D:\World of Warcraft>vmap4extractor.exe -d Data
    
    Extract V4.00 2012_02. Beginning work ....
    
    
    Game path: Data/
    
    Found locale 'enUS'
    
    
    Adding data files from locale directories.
    
    Scanning patch levels from data directory.
    
    Scanning patch levels from locale directories.
    
    Locale: enUS
    
    
    Opening Data/enUS/locale-enUS.MPQ
    
    Opening Data/enUS/expansion-locale-enUS.MPQ
    
    Opening Data/enUS/lichking-locale-enUS.MPQ
    
    Opening Data/common.MPQ
    
    Opening Data/common-2.MPQ
    
    Opening Data/expansion.MPQ
    
    Opening Data/lichking.MPQ
    
    Opening Data/patch.MPQ
    
    Opening Data/patch-2.MPQ
    
    Opening Data/patch-3.MPQ
    
    Opening Data/enUS/patch-enUS.MPQ
    
    Opening Data/enUS/patch-enUS-2.MPQ
    
    Opening Data/enUS/patch-enUS-3.MPQ
    
    Read LiquidType.dbc file...Done! (26 LiqTypes loaded)
    
    Extracting World\wmo\Dungeon\Azjol_Lowercity\Azjol_Lowercity.wmo
    
    
    D:\World of Warcraft>md vmaps
    
    
    D:\World of Warcraft>vmap4assembler.exe Buildings vmaps
    
    using Buildings as source directory and writing output to vmaps
    
    Could not read dir_bin file!
    
    exit with errors
    
    
    D:\World of Warcraft>pause
    
    Press any key to continue . . .
    
    

    From what I gather from this error, the map extractor is ending prematurely, and I have no idea why that is. The last time I had used the extractors was when TrinityCore was hosted on BitBucket, and on a 32bit windows xp OS. Is it because it's 32bit it's giving me this error?

    I also attempted trying a different emulator vmap extractor, of course not to use for tc2, but just for testing sake, and it also provided the same error. I have searched for this error, and most results came back with a wrong client version, so I don't know what's going on. I'll try later today to use the binaries on my other PC which also has win 7 64bit

    Any help would be appreciated.

    Thanks

×
×
  • Create New...