Macro causing performance issues

[warlock45]

The idea behind an INC file is so you can put commonly used code for multple macros as I understand it, and it will get pulled when the macro first starts. From that point of view I would think there would be no/slight difference in pull a few large INC files VS pulling a lot of small ones, outside of additional lines of code to include and call the files of course.

Though I do know that the more battle spam you are showing the more lag you can generate. This gets worse when you are logging, and moreso when you are parsing. I recently went through this with a guildie whose log file was getting into multiple gigs.

Just thought I might mention that incase it was something you may not have looked in to, if you are using logs.

[ikill]

The strange thing is, the macro seems to run quickly enough. I don't notice a drop in responsiveness, the issue is actually EQ itself slowing down. It's very similar to an overtaxed video card. Frames get slightly choppy and it's difficult to move with precision. I suppose the macro slows down in relation to the slight dip in frame rate, but it's not really noticeable compared to the choppiness of the video. That's what's leading me to think it's something that's taxing MQ2 or EQ itself, like the new build is causing more overhead on the parser's side. I honestly don't know anything about what happens on MQ2's side of interpreting my macro, hence my random shots in the dark. I'll definitely play around with checking timing on different scripts, I'm sure it will be beneficial regardless.

Thanks again for all the help

Kill

[three-p-o]

Kill,

I would check what Warlock said. If you have logging on it can cause the same type of performance hit as every line of text logged initiates a new save to the log file.

3po

[caj]

Kill,

what OS is being used? Win XP, 7, 8?

if its XP your on your own (or the YoYo plan)

otherwise, it could be multiple reasons why eq is preforming badly. Certain firewalls will drag your system down and affect eq. (norton is a prime example) Too many back ground programs running. Defraging your HD, just to name a few.