missonary lag issues, lag fixes Options

[Silver]

[holden_caulfield]

I've got a question about missionary lag:

Just d/l'ed the program, and it works fine except that lately, about 10 minutes into the game, the console will have some message like--Holden_Caulfield just tried to run wmiprse.exe or something to that effect. I don't know the exact file name, but it looks awfully similarly to the one I just mentioned.

From that point on the game will be mostly smooth (when there isn't much activity around me), but will hiccup and momentarily freeze when I see someone. And I can swear that my shooting is just slightly delayed. It's hard to tell because my reaction time is pretty slow to begin with . Anyway it's not my ping, which is usually under 70 (kickass server btw).

When I exit the game and look under "shutdown processes" using the missionary interface, I can't find the running program. I've done the basic stuff: set it to high priority, shielded the MOHAA and missionary files from my anti-virus, etc...

Any suggestions?

Thanks for your time fellas.

hc

[PISTOFFBAD]

Holden, this taken from a website I use.

Windows Management Instrumentation Provider Service first introduced in Windows XP, and then in Windows 2003. WMIPRVSE is a host process for WMI provider services. It is a new Windows architecture intended to eliminate the previous problems in Windows 2000 where the failure of a WMI provider service would make the whole WMI service fail as, then, WMI provider services were loaded in-process with the WMI Service (a new request to WMI would restart the WMI Service). With the new WMIPRVSE model, failure of a single WMI provider service affects that service only rather than the entire WMI Service. For the layman : this is an essential Windows XP/2003 service which will start whenever a specific piece of software requires its facilities.

Recommendation :
Essential – leave alone. Note that, as with SVCHOST, there may be more than one instance of WMIPRVSE running in your Task List : this is normal. Also, some users will never have witnessed the WMIPRVSE service running on their Windows XP/2003 PC, and then notice it running one day and every day thereafter : this is also normal and will in most cases be the result of some software having been installed (and installing WMI provider services) or the result of a Windows Update. Finally, as with SVCHOST, if you experience errors or excess CPU usage with WMIPRVSE, the problem will in almost all cases be with the WMI provider process that WMIPRVSE is hosting, not with WMIPRVSE itself, or you may have a hardware problem or incompatibility which is not yet at the "serious" stage – see if Microsoft’s Windows Update has WMI related fixes for your PC/Server; also, on a network, we have empirical evidence that poor network card drivers or chipsets on any part of the network may result in excessive CPU usage by WMIPRVSE.

[holden_caulfield]

I'll check it out. Thanks again.

[blk96gt]

One other thing you might want to check is to make sure you don't have any other programs running, like down in your system tray in the bottom right hand corner of hte screen. Also, before you start missionary, check to see how many processes you have running in the background by hitting ctrl-alt-delete and clicking on the processes tab. You can see a count in the bottom left hand corner of the screen. In my opinion you should never have more then about 20 processes running if you don't have any other programs running(ie web browser, instant messangers, etc.). I have 18 running when my computer is idle.

[holden_caulfield]

I'm retarded. For some reason my details were set to high, which was normally ok until my computer started up these apps on the side. I shut down a few processes I didn't need, set all the graphics to low, and haven't had a problem since. I appreciate the help though.

--hc

[holden_caulfield]

eck i lied. the problem is somewhat allayed, but it still won't shoot on time when there's fast/heavy activity. i'll keep tinkering as i go.