strange pathing problem

[Caseus]

After upgrading to the ax_peq database (which is absolutely incredible!), I have run into a pathing problem that has me mystified.

With my previous database (the official PEQ db with the AA modifications), mobs pathed normally. In my current database, mobs don't actually move, they blip instantly from waypoint to waypoint. This isn't the z-axis problem where mobs kinda bounce up and down as they're moving. The mobs don't actually move. Wandering mobs wander by blipping from waypoint to waypoint at high rates of speed. To make things more interesting, when a mob gets aggroed, it blips instantly on top of the player. If the player moves away, the mob blips on top of the player. Aggroing multiple mobs is pretty much guaranteed to give the puller a coronary.

I'm using the most recent version of EqEmu, so I probably need to make a modification to the database but I'm not sure where to start. I've never seen anything like this before. Any suggestions would be most appreciated!

[Angelox]

ax_peq21k was up to date/tested with EQEmu-0.7.0-988 - if you used EQEmu-0.7.0-989, I saw changes there to the database and haven't added/tried them out yet.
Pathing worked fine with me and EQEmu-0.7.0-988

[Caseus]

I was using EQEmu-0.7.0-989, so I rolled it back to EQEmu-0.7.0-988. It didn't fix the problem, but it was an excellent suggestion.

I'm sure there is nothing wong with the actual ax_peq database. As I mentioned privately, I wasn't able to do a fresh install of the db so I restored over my current database. I'm guessing that's where things went wonky. (The problem is usually 18 inches between the monitor and the chair.)

What table(s) in the db dictate movement? I'm guessing it's zone_points, though that might just be the waypoints. I have my old database backed up, along with the SQL files from the recently-released developer version of the PEQ db. I could use one of those to overwrite the movement table(s). Or do the maps dictate movement? I haven't changed my maps at all, and movement with the old database worked perfectly.

I'm also going to go back through the previous changelogs and see if there's something I need to add. I'm not sure that will solve the problem, as everything else works perfectly other than the insane movement, but it's worth a shot.

[Angelox]

All ax_peq21k has new, is fixes from the changelogs so it will work with 988. When I get time, I'll do 989 too.

Just to make sure, I downloaded EQEmu-0.7.0-988 and the ax_peq21k database, Installed on my "trusty" windows P3-500 MhZ machine. It all tested fine here, So there must be a problem on your side. Here's some things that come to mind (may or may not be your solution, just some ideas).

Lag; Maybe you got malware or a virus that's cause you to lag? try this;
http://eqemulator.net/forums/showpos...00&postcount=1
if you think you don't, try it anyway.

Are you running everything from the same machine with little memory? you might need at least a gig of memory for client, server, mysql on the same machine.

Did you restore the way I did with MySql-Admin?

You don't have anything running in the bacground, like messengers, av, etc.?

[Angelox]

I'm using mostly InnoDB tables, which tend to hog more memory- I have tested with my P3 - 500 and about 500Ram it worked fine. what maps to you use , mine or peq? have you tryed this in other zones with same results?

[Caseus]

Until yesterday I ran the original PEQ database with EQEmu-0.7.0-989. Pathing was perfect, pets worked fine. No lag problems. My system has a gig of RAM.

Yesterday, using MySql Admin, I restored the ax_peq database over top of my PEQ database. Mobs stopped pathing, pets stopped working completely.

Since nothing else in my system changed other than overwriting my database, I'm guessing something went wrong when I did the restore. The simplest thing to do would be to do a fresh install of ax_peq, but every time I try to restore it using MySql Admin, it fails immediately with the message, "cannot create table."

I could simply go back to the original PEQ database, but the ax_peq database is just freaking incredible.

[Caseus]

Originally Posted by Angelox

I'm using mostly InnoDB tables, which tend to hog more memory- I have tested with my P3 - 500 and about 500Ram it worked fine. what maps to you use , mine or peq? have you tryed this in other zones with same results?

I am using the PEQ maps. Do you have yours available for download? I didn't see them on the Rathe site.

The movement problem is in every zone I went to: the new zones like BoT and PoStorms, old zones like South Ro and Droga.

[Angelox]

some maps have changed, but not most of them, later I will post the maps I have.
Seems you need to make an ax_peq database aside your peq in MySql - try this;
With Mysql-Admin go to catalogs and right-click "create schema" , call it "ax_peq". Try and restore now. It may be it can't make the table becuause it needs to make the DB.
Be sure you have ax_peq pointed out in your eqemu_config.xml.
Also make sure you're doing this as root/admin on the same machine the MySql is (just to avoid any conflicts there).

[Caseus]

Originally Posted by Angelox

Seems you need to make an ax_peq database aside your peq in MySql - try this;
With Mysql-Admin go to catalogs and right-click "create schema" , call it "ax_peq". Try and restore now. It may be it can't make the table becuause it needs to make the DB.

I downloaded a fresh copy of ax_peq21k and then tried what you suggested, using the create schema to make a new database. The restore seemed to work fine. I migrated over all accounts and characters using the backup/restore options in MySql Admin, changed the xml file then loaded EqEmu up.

Everything worked perfectly. Pathing worked properly in every zone I tried. Pets worked perfectly. Even the AAs worked fine; I didn't have to source in the AA_Data.sql file. In my last db, tracking didn't work and mobs saw invis in Droga. Today, tracking worked perfectly without having to modify the trackable column in npc_types, and mobs don't see invis in Droga.

Thank you so much, Angelox!