Kitserver Pes 2011 Pc Download ((EXCLUSIVE))
Irta Boccanfuso
With XP and Vista, and now Windows 7 having more emphasis and enforcement of file ownership and different user rights, and promoting the use of "Standard User" accounts, i realized it was time to change the installation routine slightly, comparedto the previous versions of Kitserver. So, first new thing: you have a more traditional installernow, well it's just a self-extractable archive with some logos :) Run it, and it will ask youwhere you want your kitserver files extracted:
This was previously called setup.exe, but Windows thinks that anyapplication named setup.exe wants administrative access, even though the kitserver's setup actually doesn't. Also, the name "setup" was always slightly misleading, so i decided to rename it to more neutral - manager - because it manages the attachmentof kitserver to the game EXE files.
Now select the game executable (it should actually already be preselected). You canalso select your settings.exe (if say you wish to by-pass the quality checks, for example. Otherwise, it is not necessary). Once you select the files, click "Attach" button.What this does is it "connects" the kitserver to the game: now whenever you start the game (using that particular game EXE), the Kitserver DLLs will be loaded into memory. If all went well, you should see a picture like this:
If you decide that you don't want to use Kitserver any longer, run manager.exe again and click "Detach", and it will disconnect the kitserver from the game EXE. (This is useful when troubleshootingcrashes: you can always temporarily detach Kitserver from the game to verify that the gameruns fine without it. And then re-attach the Kitserver later).You can also install/remove Kitserveronly for one exe by setting the other one to "no action".
Now for one last step, before we can run the game with kitserver:
We need to make sure there exists a file called config.txt in thekitserver folder. If you're upgrading your Kitserver, then you might already have it in there,in which case the installation/upgrade is done. If not, then it's easy enough to create theconfig.txt file: just run the Kitserver's configuration tool, click "Save", and it will make the config.txt for you.
That's it. You're ready to launch the game.
REMEMBER: you need to start the game using the game EXE (pes2010.exe) in Kitserver2010 folder, because that is the one that has the kitserver attached to it.
Also, it is worth reminding that you can always temporarily detach the kitserver from the game exe, and then re-attach it back, by using the manager program (as described in 2.1 section above). This is useful when suddenly you get game crashes, and you are not sure whether Kitserver is at fault, orthere is some other reason.
So what you need to do is copy the new game EXE over to the Kitserver2010 folder, then run themanager.exe program and attach the kitserver to the new EXE. Assuming, of course, that Kitserversupports the new EXE, that's all there is to it. Now you can again start the game from Kitserver2010folder.
The kitserver manager.exe program can also be run without GUI - in a so-called batch or command-line mode. This can be useful, if kitserver is part of a bigger patch, which contains an installer, and typically the last step of the installer is to attach kitserver to the game EXE file. This can be accomplished by running the manager like this:
Kitserver uses a file called config.txt as its main configuration file. A lot of things are specified there, including which modulesto load, what settings those modules should use, and etc. Go to your kitserver folder and you should see a file called config-sample.txt. (I gave ita different name on purpose: so that those who upgrade their kitserver installation don't accidently overwrite their existing config.txt). If you aren'tupgrading then the chances are that you don't have an existing config.txt, in which case just rename (or copy) the sample config into config.txt (or run configuration tool, click "Save" and it will do the same thing). Otherwiseyou may want to compare the sample config with yours and see if you need to make changes to your config: such as add new modules in the [kload] section,for example.
The main configuration file for kitserver - config.txt - is located in thekitserver folder. If you don't have it there - re-read the end of Install section (2.1) above.Here is an example of what can be in config.txt:
The GDB contains a folder named uni, which is responsible for storingthe team kits (uniforms). The single most important file inside uni is called map.txt.This file tells kitserver where to find the kits for particular team. As you know, each team has a unique id - an integer number from 0 to 340. For every team in the GDB, you must specify in the map.txt where the kits for this team are. Here is an example:
Please note that the sample GDB (provided with kitserver) is just one possible way of organizing the teams and folders. It uses "EPL" folder to group all english teams, "National" - to group all nationalteams, and so for. You may find that you just prefer a flat list of folders - without theseextra groups. In that case, just modify the map.txt file accordingly, and createthe structure of folders that you prefer. That's the main advantage of having map.txt - theflexibility of kit organization.
You can see from map.txt above that in order to find a kit for team #23, the kitserver needs to go to the folder GDB\uni\National\Russia. This folder will contain all of the kits that areavailable to team #23. Inside it, you must create an individual folder for each kit. Like this:For players, 1st kit must have a folder name pa, 2nd - pb. Extra kits can have any folder names that start with letter "p". I found it useful to prefix all extra kits with px-. For example, px-redwhite. For the goalkeepers, 1st kit must be in the folderga, 2nd - in the gb. Extra kits can have any folder names that start with letter "g".
LOD-Mixer is the module that allows to fine-tune some aspects of PES2010 graphics engine.
Currently the following features are implemented: screen resolution and aspect ratio correction. All of these can be configured manually in kitserver's main configuration file (kitserver/config.txt), but you can also use Kitserver's configuration tool (config.exe).