[Three] extracting vmaps for 4.3.4

[tweex15]

It seems another user had this same issue but I didn't see an actual solution to create the vmaps:

http://community.getmangos.eu/index.php?topic=18557.msg148763#msg148763

I'm having the same issue as the vmapExtractor.exe will populate the buildings folder with 10k or so files, but won't touch the vmaps. (see attached screenshot.)

This time around I downloaded the 4.3.4 client from the torrents found in the FAQ section here. All commands run on Win8 cmd as administrator.

Is there a solution?

Thank you!

[attachment deleted by admin]

[madmax]

Hm,

All our servers at covenant-wow use enGB data and they are fully compatible with enUS clients.

For 4.3.4 I took the exe's dlls from a 4.3.4 torrent and then ran the wow regen program to download ll the data fresh from blizzard

[tweex15]

interesting, I ran my extractor on windows 7 and my vmaps is full, ran without problems, but I did have serious issues when I ran it with the enGB version thats floating in the torrents. I just pulled a fresh 4.3.4 enUS version using my original WOW dvd, then set the update using the how-to found in the stickies so now I have now have a enUS version that works fine, server installed and ran without issues (well one issue, but that was an issue of missing sql files from the git pull but was remedied quickly)

as for the no connect, make sure your conf (both mangos and realm config files) have the bindIP set to correct IP address also, and the realmd is configured, I at first thought it was a firewall issue also, spent several hours going through and trying various things only to find out it was a bindIP issue all the time, once those were set properly everything popped up and ran fine.

Well I tried the bind IP settings in the realmd and mangos conf files, unfortunately no dice for my game client

I turned up the logging on the realmd and the attached photo shows what pops up every time I hit Okay on the realm selection screen. It prints this twice for every click. Hopefully that tells something...

[attachment deleted by admin]

[lfxgroove]

@tweex15 have you changed the ip in the database aswell? It's located in realmd.realmlist and the field to change in that table is address

[Urlryn]

Not sure if this works the same in Windows as it does in linux, and assuming you are using Mysql.

Before you updated realmd.realmlist IP...did you stop the server. Update the realmd.realmlist IP to your Internal IP of the computer?

Then restart your mySQL? then restart your server. Be sure to set your BindIP in realmd.conf/mangosd.conf to your internal IP of the computer hosting the server.

If all that fails....firewall disabled?

Urlryn

[Svarr]

I have tried the bind IP once. Nobody could connect to the server after that.

I would retry it without bindIP (leaving it blank). If I recall it correctly you had "0.0.0.0" set in bind IP perhaps that was the issue all along? Couldn't it be that the server actually bound the IP to 0.0.0.0?

[lfxgroove]

@Svarr, binding to ip 0.0.0.0 should accept incoming connections to anywhere or how one would put it, ie: it should accept a connection if it came to 192.168.1.1 or 192.168.1.2 if those ip's go to the same server.

[tweex15]

@tweex15 have you changed the ip in the database aswell? It's located in realmd.realmlist and the field to change in that table is address

So I did what you said and changed the bindIP in the database, and when I tried from home it cruised right in to the character creation screen. Unfortunately I had to run to work so I didn't go any further, but I'm trying the client remotely and it's back to the same issue. I'll have to check when I get home to see if the home PC still works or not. Would be pretty random if it worked for just once and then not.

[Svarr]

@Svarr, binding to ip 0.0.0.0 should accept incoming connections to anywhere or how one would put it, ie: it should accept a connection if it came to 192.168.1.1 or 192.168.1.2 if those ip's go to the same server.

Alright, didn't know that. :

[tweex15]

Ok so I set the db and the conf back to 0.0.0.0 and the authentication is about instant now (used to take a few seconds) but still as soon as I hit Okay it instantly goes back to the realm select screen.

[lfxgroove]

What exact ip did you set it to in the db tweex, an internal one? Localhost? External? If you're running the server on the same machine as you are running wow you could set the address to 127.0.0.1, localhost or your internal ip that your router gives you, something along: 192.168.1.139 or so. If you want to connect from a computer connected to the same lan you would need to use the internal address given by your router, ie: 192.168.1.139 or so. If you're hosting externally you would need to set it to your external ip (whatismyip.com will help you finding that out) and then port forward the necessary ports to point at your computer hosting the server. Hope this is of any help!

Edit: The conf can be 0.0.0.0 but try changing what you have in the db

[tweex15]

What exact ip did you set it to in the db tweex, an internal one? Localhost? External? If you're running the server on the same machine as you are running wow you could set the address to 127.0.0.1, localhost or your internal ip that your router gives you, something along: 192.168.1.139 or so. If you want to connect from a computer connected to the same lan you would need to use the internal address given by your router, ie: 192.168.1.139 or so. If you're hosting externally you would need to set it to your external ip (whatismyip.com will help you finding that out) and then port forward the necessary ports to point at your computer hosting the server. Hope this is of any help!

Edit: The conf can be 0.0.0.0 but try changing what you have in the db

Hmm I don't have a static IP on my connection, I just use dyndns. But 0.0.0.0 in the db won't work?

[Urlryn]

Not sure anybody asked yet.....

Have you configured your port forwarding in your router/cable modem/firewall?

forwarding port 80 to the server hosting your wow web page setup (if ya have one)

forwarding port 8085 to the wow server....This is the Mangos world server port. (So players can enter your realm)

forwarding port 3724 to the wow server....This is the realm server port (so players can see the realms in the realmlist)

Hosting to the outside....this is going off when i used to host a server...so my information maybe wrong now.

I thought you needed to change the realmd/mangosd conf files to be your public IP address. ( ipchicken.com will show you this)

Though leaving it like they said to 0.0.0.0 sounds like it should work.

Urlryn

[tweex15]

Not sure anybody asked yet.....

Have you configured your port forwarding in your router/cable modem/firewall?

forwarding port 80 to the server hosting your wow web page setup (if ya have one)

forwarding port 8085 to the wow server....This is the Mangos world server port. (So players can enter your realm)

forwarding port 3724 to the wow server....This is the realm server port (so players can see the realms in the realmlist)

Hosting to the outside....this is going off when i used to host a server...so my information maybe wrong now.

I thought you needed to change the realmd/mangosd conf files to be your public IP address. ( ipchicken.com will show you this)

Though leaving it like they said to 0.0.0.0 sounds like it should work.

Urlryn

Yes I did forward those ports in my router. I can 'see' the realmlist which is a good sign, and my realmd console log shows me authenticating, but that's about as far as get.

[tweex15]

Not sure if this means anything to anyone but I've tested a few different IPs for the realmlist IP in the DB.

-If I set it to 0.0.0.0 and click Okay on the realmlist I get put back to the same screen instantly

-If I set it to the server's IP and click Okay on the realmlist it freezes the client for a good 15 seconds then throws me back.

-If I set it to the stock 127.0.0.1 and click Okay on the realmlist I get a 1-2 second freeze and same result.

A bit strange that these variables are affecting the client like that. Now if I can find what I'm doing wrong so it'll actually let me in, I'd be golden.

[lfxgroove]

Hm, lets start over i'd say, from which computer are you connecting, and where is your server located? Internal/external? And let the bindIp in the config file stay with 0.0.0.0 that should suffice

Also, if possible, start by having wow and the server on the same computer, then you don't need to change the address in the db or anything, that should work out of the box, does it?

[tweex15]

Hm, lets start over i'd say, from which computer are you connecting, and where is your server located? Internal/external? And let the bindIp in the config file stay with 0.0.0.0 that should suffice

Also, if possible, start by having wow and the server on the same computer, then you don't need to change the address in the db or anything, that should work out of the box, does it?

It appears that internal network works good. My server is on another box in the house, and my main PC with WoW client connects to it via IP. My config file is still set to 0.0.0.0 and the db IP is now set to the internal IP of the server box. Ports are forwarded, just doesn't want to hook up externally.

[lfxgroove]

Ah, so connecting in the internal network works well as it should in your current setup. When you're connecting from external you would probably have to set the address to your external ip and connect to the external ip from your internal network aswell iirc.

[bels]

Ah, so connecting in the internal network works well as it should in your current setup. When you're connecting from external you would probably have to set the address to your external ip and connect to the external ip from your internal network aswell iirc.

This is correct. If you have your ports forwarded in your firewall correctly this works fine. I am running a Three server this way.

[lfxgroove]

Thanks for the confirmation bels!

[tweex15]

This is correct. If you have your ports forwarded in your firewall correctly this works fine. I am running a Three server this way.

This is interesting. So the "address" field in the realmlist table needs to be changed to my dyndns hostname? I could put IP but that's bound to change as it's not static. I thought I tried hostname yesterday with no luck.

[tweex15]

For what it's worth I did try my IP address and externally IT WORKS. Now if I can get it to work with hostname instead ... small victories at this point I guess.

[lfxgroove]

What happens when you use your hostname instead in the address field?

[tweex15]

What happens when you use your hostname instead in the address field?

The same issue as before, with a good 5-10 second freeze in the game when I hit OK on the realm select screen.

[Hikari]

As you can read in different topics the Cataclysm client reuquires mandatory an IP address. Hostname doesn't work.

You can try to implement this work around from shlainn into your RealmList.cpp and see if it works afterwards.

[Merlinium]

Hm,

All our servers at covenant-wow use enGB data and they are fully compatible with enUS clients.

For 4.3.4 I took the exe's dlls from a 4.3.4 torrent and then ran the wow regen program to download ll the data fresh from blizzard

I was referring to an issue I had running the extractor on a enGB version, but then again, I didn't pull fresh content from bliz servers like i did with enUS version.