MacroQuest64

Ever since the latest patch and recompile of MQ, the more characters I have macroed, the higher the ping shoots up when I pull a mob into camp.

With too many characters macroed, the ping shoots up to 2k and disconnects the modem.


Suggestions?

I have seen some odd behavior with the data stream as well .... I am trying to debug the problem but I can't find the right breakpoint. I have dumped several segments of memory but all I have at this point is a best guess.

The basic symptom is that for no reason, the client starts sending and receiving mass of small packets, causing lag, spell gems do not refresh, doors don’t open.. etc. The problem is not network related as I will have 2 or 3 systems running at the same time and only one system displays this lag at a time. With or without the debugger loaded, but only when MQ is active. /unload halts the problem.

ok i had this same problem - heres how i fixed it.

make sure you have latest source.
compile a release version instead of debug and it should be good to go!



Flint

i am having the same problem. i have downloaded latest cvs and recompiled and still have the problem. i can have mq loaded with out probs but when i run my macros it gets laggy and i will end up with a disconnect.

Greetings Constructs,

I have a very similar problem. When I run macros with loops (yes they include doevents and delays), I experience extreme lag.

End of line...

Salutations,
Oooh... if we only get this lag while running macros, maybe it's some memcheck we haven't found...

Perhaps mem allocation issue..

In case i forgot /unload before logging out:

no macros run: eqgame.exe stays with around 5000 kB in memory
a simple mainloop macro: goes up to 55000 kB
a complex macro (mainloop, several subs with loops and branches and events...) uhoh.... last time i had 330 MB... that slowed thinks abit down...

How the heck did you get eqgame.exe down to 5 MB in memory? :) For me, eqgame takes up something close to 7 MB before getting into the game, and anywhere from 210 to 510 MB while playing, regardless of MQ or anything else running. Read: lots of graphics loaded. Just a thought as salt to the discussion. There very well may be a memory leak in MQ somewhere also.

Here's my experience with the situation. I dual or triple box almost every single time I play EverQuest, and so does my roommate. (We each play on a single computer running multiple instances of EQ, for clarification.) We run MQ and LEQM and EQW every single time we play. With or without actually running a macro, we have not noticed a) bloated executables b) excessive swapping/resource use c) any additional lag or link deaths.

I am not dismissing the problem out of hand, by any means. Just sharing my experiences since I dual-box a LOT.

EQJOE, that's the exact problem I'm having. Spellgems don't refresh, etc. I just got half my group killed on a mob because the mob enraged and none of the characters stopped attacking like they're supposed to due to lag.

This crazy ping started occuring as of the most recent 4-14 patch.

Any fixes yet?

Ok.. still working on it but I have given up on trying to debug the problem. I can't setup a breakpoint with any type of utilization condition and breaking to the debuger on memory access is not cutting it.

I am attempting to sniff the data on the wire by using a modified SEQ client (Thanks Mvern!) to see if the client/server is resending/requesting memory offset check packets at an unusual rate (which is what I suspect)

any updates to this problem?

After some quick tests, it appears that one byte sturct allignment build parameter is the fix. See DKAA's post in Devolopment:General.

my settings were already correct so that fix didn't help me. whats happening to me is now with the same .mac's i was using before, they lag. it's only after i start the mac that i have the problem. its the same on 3 diffrent machines.
if im in a high traffic zone it will lag me to ld but when i get to where i am going to use them (usually not crowded) and run them i will lag but stay connected.

Maybe it's your macros?

Put some delays in.

i finally got off my lazy rear and cleaned up my macros a bit (they were just a bunch from here thrown together). it did seem to help. i haven't tried yet in a crowded zone but will let you know.