
What does it do ?

2d clients always cause 100% CPU load even if "ideling".
More technically, (2d) OSI clients do busy waiting when they are not busy.
Taking away CPU cycles unnecassairily.
This patch reduces CPU load when the client does nothing.
(But doesn't eliminate busy waiting completely)
Important note: It does NOT (!!!) improve client performance.

It works for 2d clients only (because 3d clients dont have that bad habit).

Tested for 4.x clients, probably work with earlier clients as well.
Latest client at release time: 4.0.3e
Should also work for fututre clients, unless OSI changes their clients too much.

----------------------------------------------------

Usage:

Just start uo_lowcpu, it creates a new client called LOWCPU_2dclient.exe
with lowcpu patch inside.

Ya_muU2 & lowcpu patch:

Because Ya_muU2 doesn't recognice clients with lowcpu patch, do this to have a client
with lowcpu patch and multi uo capabilities.

a) start  Ya_muu2 first, patch the client
b) start  uo_lowcpu afterwards

LOWCPU_2dclient.exe is now a multi UO client with lowcpu patch

Ya_muU2 & lowcpu & UO_RIce

(if you dont know what UO_Rice is, you dont need that)

a) start Ya_muu2 frist, patch the client
b) start uo_lowcpu afterwards
c) rename osi client.exe to client.exee
d) rename LOWCPU_2dclient.exe to client.exe
e) start UO_rice
f) delete client.exe
g) rename client.exee to client.exe

NO_crypt_client.exe is now a multi uo, lowcpu, and nocrpyt client.
client.exe OSI client.

------------------------------------------

Removing lowcpu patch:

Usualy you don't need to undo it, because a seperate client is created,
leaving OSI client untouched.
The inlcuded tool undo_lowcpu.exe removes lowcpu patch from client.exe
Just in case you have renamed LOWCPU_2dclient.exe to client.exe, and need to remove it because OSI has patched
their client, and you dont have a backup of OSIs untouched client.

---------------------------------------------

Acks: Many Thanks to Sephiroth who send me a client with a lowpcu patch for a certain client.
It's a long story where this patch came from, but basicly it's unknown who has created it initially.
All I did is analysing it and creating a tool that can add it to any client.

