search

cmangos / issues

This repository is used as a centralized point for all issues regarding CMaNGOS.
179 stars 47 forks source link

MMAP:loadMap: .mmtile was built with generator v6, expected v7 #1854

Closed adellaci closed 5 years ago

adellaci commented 5 years ago

Current behavior: Extracted all the wow data files and moved them to share. Getting an error "ERROR:MMAP:loadMap: .mmtile was built with generator v6, expected v7.

Expected behavior: Not generator those errors

Steps to reproduce:

  1. Compile latest commit
  2. Extract new data files
  3. move them to share folder
  4. Start mangos

Client version: 3.3.5

Commit hash: dbae0142fc70a11f19d08293880194675d0b9bd3

Database version: 3dd330a2d5930cbd568e2aa3e1f23d22499d100f

Operating system:

hipejoe commented 5 years ago

I rebuilt the move maps, seems to work for me.

Phatcat commented 5 years ago

I rebuilt movemaps myself as well and had no issue. Are you sure you were running the latest version of the extractor cause it was indeed changed from v6 to v7 very recently. Here in fact; https://github.com/cmangos/mangos-wotlk/commit/6ec14a81cb6f5583c9be948e10f4450225f286c9

Try to delete the cache in cmake, then reconfigure from scratch, then make sure you also build the extractors by ticking off the box BUILD_EXTRACTORS, then configure again and generate, then try to rebuild and re-extract the resources again, all of them. I know it's a lengthy process but it should work.

adellaci commented 5 years ago

Thank you both for replying. I am unfamiliar how to clear the cmake cache. I always compile everything when doing so, and i delete my build directory every rtime

cmake /mangos/mangos-wotlk -DCMAKE_INSTALL_PREFIX=~/wow-servers/mangos-server-wotlk -DBUILD_EXTRACTORS=ON -DBUILD_PLAYERBOT=ON -DPCH=1 -DDEBUG=0 -DBUILD_RECASTDEMOMOD=ON

Then move the tools from the build directory to my wow data folder and issue the following

./ad -f 0 ./vmap_extractor ./vmap_assembler Buildings vmaps ./MoveMapGen8Core.sh 8

adellaci commented 5 years ago

I failed to do the extraction correctly the first time. I keep forgetting that i have to create the vmaps directory for the process to work right. Once i did that it worked correct. No more error

Phatcat commented 5 years ago

Then move the tools from the build directory to my wow data folder and issue the following ...

./ExtractResources.sh ain't working well for you?

adellaci commented 5 years ago

@Phatcat I have not tried ./ExtractResources.sh yet. I like running ad with the -f 0 option which increases the extraction detail, or it use too. I haven't check to see if it still creates larger files. Do you know the answer?

Phatcat commented 5 years ago

I honestly don't know, I always just use default everything really

adellaci commented 5 years ago

Thank you @Phatcat I'll take the time this weekend and run them both way and see if it still functions and report back here total files size, then check downstream in the process it it impacts also.

adellaci commented 5 years ago

I'll also track processing time. If there still a difference I'll look into making a change to ./ExtractResource.sh and submit it for approval.

adellaci commented 5 years ago

@Phatcat

[WotLK]

As you can see it did make a difference on the size of the maps files. It did not effect any of the others

./ad -f 0 54 secs ./vmap_extractor 1 min 16 sec ./vmap_assembler Buildings vmaps 12 secs ./MoveMapGen8Core.sh 46 mins 59 secs

Buildings 7460 files 307.7MB Cameras 14 files 34.8KB dbc 247 files 90.3MB maps 5744 files 522.2MB mmaps 4111 files 1.7GB vmaps 9876 files 588.3MB

./ad -f 1 41 secs ./vmap_extractor 1 min 4 sec ./vmap_assembler Buildings vmaps 13 secs ./MoveMapGen8Core.sh 46 mins 43 secs

Buildings 7460 files 307.7MB Cameras 14 files 34.8KB dbc 247 files 90.3MB maps 5744 files 254.7MB mmaps 4110 files 1.7GB vmaps 9876 files 588.3MB

Phatcat commented 5 years ago

I see, yea. Building time of vmaps and mmaps seem very similar even with almost double the size of the maps. Hmm..

Does it make a tangible difference in-game?

adellaci commented 5 years ago

@Phatcat What i can remember, it made a noticeable difference. I've been using './ad -f 0' for 7 or 8 years. I guess now that i have both sets of files, i can tested them both out.

datchannin commented 5 years ago

You can use additional option for vmap_extractor use "-l" I've added "-l" and "-f 0" to ExtractResources.sh and maps are extracted using .sh script.

image

For TBC: folder /vmaps without this option is near ~370 MB folder /vmaps with this option is near ~830 MB

adellaci commented 5 years ago

@datchannin

Do you know of any other options for the extractor tools? I'm rerunning and I'll post my file size chance

adellaci commented 5 years ago

@Phatcat @datchannin

[WotLK]

As you can see it did make a difference on the size of the maps files. It did not effect any of the others

./ad -f 0 54 secs ./vmap_extractor 1 min 16 sec ./vmap_assembler Buildings vmaps 12 secs ./MoveMapGen8Core.sh 46 mins 59 secs

Buildings 7460 files 307.7MB Cameras 14 files 34.8KB dbc 247 files 90.3MB maps 5744 files 522.2MB mmaps 4111 files 1.7GB vmaps 9876 files 588.3MB

./ad -f 1 41 secs ./vmap_extractor 1 min 4 sec ./vmap_assembler Buildings vmaps 13 secs ./MoveMapGen8Core.sh 46 mins 43 secs

Buildings 7460 files 307.7MB Cameras 14 files 34.8KB dbc 247 files 90.3MB maps 5744 files 254.7MB mmaps 4110 files 1.7GB vmaps 9876 files 588.3MB

./ad -f 1 ./vmap_extractor -l ./vmap_assembler Buildings vmaps ./MoveMapGen8Core.sh

Buildings 7460 files 596.4MB Cameras 14 files 34.8KB dbc 247 files 90.3MB maps 5745 files 524.2MB mmaps 4113 files 1.7GB vmaps 9890 files 1.3GB

datchannin commented 5 years ago

@adellaci , You have vmaps 9876 files 588.3MB without -l and vmaps 9890 files 1.3GB with -l. More than 50% increase. The same for me, for TBC.

I use only two option "-l" for vmaps and "-f 0" for maps. "-l" I used for check units movement from the water to the land. This one report: https://github.com/cmangos/issues/issues/1862