Gnarlee

Still having this same issue without any resolve. I'm just living with it although it really makes the quality of game-play very bad. I wish I could find a solution to this. I am now using the latest release of MaNGOS 11774 with SD2 level 2255.

You will need to go into your realmd/account table and change the 'expansion' field to 2 for the account you are trying to use.

I have recreated the maps, vmaps and dbc files from a clean 3.3.5a client and still having the same problem. The data field in the .conf is set correctly to where the 3 folders exist on the hard drive. I get no server related line of sight or height errors and .gps says they are both enabled as well as the server output. Does anyone have any more helpful advice please? I'm starting to go bald pulling out my hair trying to get this working.

Nothing is recorded in Server.log when a creature was attacked or killed.

This doesn't happen on all creatures. Two examples I can give, the Frostmane Whelp that is in the entry way to the cave in, Coldridge Valley, when spawned, spawns above ground but as it walks it's waypoint, it will fall below the ground level and stay below ground level until killed. The female dwarf food vender that walks across the bridge as you come into Ironforge, if you click on her as she is on the bridge, she falls halfway through with just her head above ground.

vmap activated?

Yes

vmap.enableLOS = 1

vmap.enableHeight = 1

in mangosd.conf

I set up MaNGOS on a Debian 6 box last week and have been playing with it the past couple of days and have been having some issues with creatures spawning under/below the ground level or where creatures will fall through the ground at spots just wandering their waypoints or when aggroed or killed. I have vmaps created and in place and configured in the .conf file. The server output screen says height and line of sight is enabled. My apologies if this topic has been asked before but search didn't seem to find anything related. I've been pullng my hair out trying to figure out why this is happening. I've recompiled and resourced numerous times to see if I missed something or did something out of sequence but all yielded the same results. Is this something fixable on my side or a database/code issue?

MaNGOS 11712 + UDB 401 + ScriptDev2 for 11590+ and Acid 3.0.8.

see http://udb.no-ip.org/index.php/topic,12682.msg65238.html#msg65238

for the issue of the rotation being 90 degrees wrong the rotation2 needs fixed not the orientation field, at least that's what I found.

Either way this is a database issue not core

I was just curious as to how the OP fixed this issue as I was seeing the same behavior on my end as well. Thank you for your link to the udb forum. I hadn't as of yet registered with them as I've only had MaNGOS running a couple of days. It indeed turned out to be a database issue. Credit goes to bajaexplorer for the coordinates Antiroot for the rotation hint. Thank you very much.

Here was the fix I applied:

UPDATE `gameobject` SET `position_x`=-45.4007,`position_y`=2472.93,`position_z`=6.9886,`orientation`=1.5708,`rotation0`=0,`rotation1`=0,`rotation2`=0,`rotation3`=0 WHERE `guid`=18802;
UPDATE `gameobject` SET `position_x`=-45.4005,`position_y`=2492.79,`position_z`=6.9886,`orientation`=1.5708,`rotation0`=0,`rotation1`=0,`rotation2`=0,`rotation3`=0 WHERE `guid`=18803;
UPDATE `gameobject` SET `position_x`=4.52807,`position_y`=8.43529,`position_z`=7.01107,`orientation`=1.5708,`rotation0`=0,`rotation1`=0,`rotation2`=0,`rotation3`=0 WHERE `guid`=18804;
UPDATE `gameobject` SET `position_x`=4.58065,`position_y`=-11.3475,`position_z`=7.01107,`orientation`=1.5708,`rotation0`=0,`rotation1`=0,`rotation2`=0,`rotation3`=0 WHERE `guid`=18805;
UPDATE `gameobject` SET `position_x`=4.49883,`position_y`=28.2097,`position_z`=7.01107,`orientation`=-1.5708,`rotation0`=0,`rotation1`=0,`rotation2`=0,`rotation3`=0 WHERE `guid`=18806;
UPDATE `gameobject` SET `position_x`=-45.3934,`position_y`=2512.8,`position_z`=6.9886,`orientation`=1.5708,`rotation0`=0,`rotation1`=0,`rotation2`=0,`rotation3`=0 WHERE `guid`=18807;

I just did a Git Pull and a recompile this morning and the problem still persists for me with 11712 and UDB 401.

Could you be a little more specific on how to fix this issue please?