MacroQuest64

I've seen a few other posts mentioning this but none seem to have an answer that works for me.

To begin with until the release of GoD I've been using MQ2 from the 25th of December. Performace was always decent...no real delay in my commands to my bots (I'm using genbot 8.8). I've got eq on 2 separate harddrive and the second install has everything turned off and on low settings.) The second instance could get bogged down but it was quick with my genbot commands... tell the bot to slow it starts casting in like 1 sec or less. I had tried later versions of MQ2 but I was getting really choppy and lagged response with the second window with later versions. I'm talking up to 6 seconds before the bot would start casting. Its like the bot falls asleep or something.. if I switch to that window the bot is still kinda slow but it does pickup some speend if I'm focused on that window.

Well anyways back to the point of this post... now with the release of GoD I've had to upgrade to the latest version of MQ2 and now that delay is back and I can't count on my bot for the most part..a delay of 6 seconds with slow could mean I'm splattered on the ground.

I'm not sure what is causing the delay but from what I can see it seems to be something added to MQ2 since the December 25th release since that was the last verion I had that didn't give me this delay. Is anyone else noticing this? Is there a setting I need to disable or enable or not compile? I'm a big moron when it comes to programming so I'm really lost.

I'm using the latest version of EQ Windows. The foreground window runs fine... its a little coppier than before but not bad but the background even when switched to is really sluggish.

My System if it matters
Athlon XP2500+
1GB DDR 3500 Memory
NForce2 Ultra Chipset

Like I said performance before wasn't fantastic with stuff like following but when I gave the bot a command it would start doing it right away but now its got 4 to 6 second delay.

Sorry if I missed info about this in another post but the only ones I've found mention it but never get resolved... maybe I'm just an idiot/


Craft

Not sure if its a MQ2 issue. According to EQW site there are known issues with the new EQ dx9 and EQW.

http://www.eqwindows.com/board/viewtopi ... hlight=dx9

Anyways, might check on their board and wait for a EQW dx9 update.

Bob

I was running a spellcheck sub and the memspell command was not working or the gem var was not returning the right value( as of 2/12/04 latestzip) may be me I dont know I just commented out the sub I did not like it much anyways
also it was just delaying check your code find out where its lagging

I just figured it was a MQ2 issue because I was experiencing this with any release since the Dec25th. I've played around a bit and it could be a EQwindows problem. If I switch between the 2 windows the macro picks up alot of speed. I seems the foreground window is hogging all the system resources and lagging out the background window which causes the delay... this is just from observing it since I've got no clue about code.

Craft

seems the foreground window is hogging all the system resources and lagging out the background window

You can use MQ2fps plugin to regulate foreground and background fps / cpu useage.

maybe you deleted the mq2fps.ini or the macroquest.ini after updating the latest build and cleared any preset values that you had tweaked.

Bob

Ok I still have my old MQ2 folder I'll check to see if the settings are different.

Craft

I have the EXACT same issue. I had done a search to find out more on this issue and lo and behold I found this thread. I too am having issues with all releases since Dec. 25. I am certain its a MQ issue and something was changed between Dec. 25th and the later releases....now if only we could find the problem heh.

You can use MQ2fps plugin to regulate foreground and background fps / cpu useage.

maybe you deleted the mq2fps.ini or the macroquest.ini after updating the latest build and cleared any preset values that you had tweaked.

Bob[/quote]

I have never changed either file for any performance tweaking in the past and am sure they are default settings still. Whenever I update to a newer release, I rename the old mq directory, create a new mq directory, then dump the compiled latest release into the empty dir, then copied over all my macros from the renamed old mq dir.

I've been noticing something similar with normal, full screen EQ. Little, split second pauses ever few seconds.

There is some speculation that this is caused by new server-side checks for speed hacking. Everything is lagging as the client and server cross check each other to make sure that you aren't hacking your speed.

Dunno if that is the case or not. I also want to check and see if we are using the DX9 dinput.h yet or not. Might want to try compiling with that and see what happens.

im not sure if anything serverside is causing the issue, as again, with the christmas release, pre GoD, it ran wonderful. With any release after, it ran like ass when running 2 eqw sessions and mq. i tested with the march 1st release, and its still runnin laggy as hell with 2 sessions of eqw. with the christmas release it NEVER ran laggy. everything since has...

Couple questions. Are you using any custom plugins? And if so, do any of those have anything in OnDrawHUD?

I found the source of my choppiness, a bit of badly structured code in OnDrawHUD. You have to be very careful with what you put there, or in OnPulse.

I am just using the default plugins. I have actually gone thru and did /plugin <name> unload one at a time til all but chatwnd was unloaded and still laggy as ever. Its very frustrating. This is on 2 seperate PCs as well. Also, a friend who runs it on a 2.8ghz P4 with all the new bells and whistles has the issue as well, altho not as severe as I on my P4 2.4ghz

Forgot to mention, it runs wonderful with a single session of EQ running. It is when you run 2 sessions that it hoses up. I am beginning to wonder if its due to a sharing conflict of some sort since both EQ instances would be utilizing the same MQ instance. Again tho, I am not sure why Christmas 2003 version had no issues, and everything since has...

PS thanks for the suggestions Mckorr

You realize you need to copy your EQ directory so that each instance of EQ and EQW are from seperate directories right?

Also, you should put a blank file called nosound.txt into one of the EQ directories.