Multi Theft Auto: Wiki - User contributions [en]

Resource:Race

2008-06-15T18:49:30Z

Mvol:

{{Resource page}}
__NOTOC__
The "race" gamemode organizes sprint or freeroam races for one or more players. It supports both maps from MTA:Race and maps in the MTA:SA DM map syntax that were created in the map editor.

==Ingame==
Playing race is quite straightforward. If there are checkpoints, drive from checkpoint to checkpoint and be the first to reach the finish line within the time. If there are no checkpoints, just drive around and have fun.

In races you may encounter three types of pickups which will have an effect on your vehicle:
*'''Repair pickups:''' this pickup looks like a wrench. If you drive over it, your vehicle will be restored to full health.
*'''Nitrous oxide pickups:''' a red NOS bottle. After you drive over one you can press the fire button (by default the left mouse button) to get a temporary speed boost.
*'''Vehicle change pickups:''' these display the name of a vehicle above them. As soon as you drive over a pickup your vehicle will be changed.

Lastly, if you get stuck during a race, you can enter the /kill command in the chatbox to kill yourself and respawn at the previous checkpoint.

==Installing maps==
===Installing maps in MTA:Race syntax===
Adding MTA:Race maps to your DM server is easy. All you have to do is place the file in a folder and add a meta.xml. No conversion is necessary.
*Go to the "resources" folder of your server installation (<SERVER>\mods\deathmatch\resources) and create a new folder. In order to keep with conventions, the folder name should be in the format "race-<mapname>", so if the map file is called "Dirtring.map" you might call the folder "race-dirtring".
*Copy the .map file into the new folder
*Create a meta.xml file in the new folder and paste the following text into it:
<div style="padding-left: 20px">
<syntaxhighlight lang="xml">
<meta>
<info type="map" gamemodes="race" name="" />
<race src=".map" />
</meta>
</syntaxhighlight>
</div>
*Enter the name of the map, for example "Dirtring", in the "name" attribute of the <info> node.
*Enter the name of the .map file in the "src" attribute of the <race> node, for example "Dirtring.map".
*Save the meta.xml.
*Add more maps if you wish. When you're done, /refresh your server resources.

===Installing maps in DM syntax===
If you created the map yourself in the MTA:SA DM map editor (not released at this point), everything will be in place and you only need to /refresh. If you downloaded the map, place it in your server "resources" folder and /refresh.

===Converting maps from Race syntax to DM syntax===
The MTA:SA DM map editor can only edit maps in the DM syntax. If you want to edit maps that are in MTA:Race syntax, you need to convert them.
*Make sure the map you want to convert is not in a zip file. If it is, create a folder with the same name as the zip file and extract the zip contents into it.
*Make sure race is started. Either have a race map running, or do /start race.
*Enter the command /convrace <map resource name>.
*The conversion process should be very quick. Once conversion is complete a message will appear.
The map file is overwritten with the converted version. If you want to keep the original file, make sure you have a backup.

==Map syntax==
===MTA:Race style syntax===
<syntaxhighlight lang="xml">
<map mod="race">
<meta>
<author>Author name</author>
<description>Map description</description>
<version>Map version number</version>
</meta>

<options>
<weather>Weather ID</weather>
<respawn>timelimit|none</respawn> 
<duration>Maximum race time in seconds. Default is 30 minutes</duration>
<time>hour:minute</time> 
<vehicleweapons>true|false</vehicleweapons> 
<ghostmode>true|false</ghostmode> 
<skins>cj|random|rangelist></skins> 

<respawntime>Time from death to respawn in seconds. Default is 5.</respawntime>
</options>


<spawnpoint>
<position>X Y Z</position>
<rotation>Angle in degrees. 0 = north, higher values go counter clockwise.</rotation>
<vehicle>Vehicle number</vehicle>

<paintjob>Paintjob ID, ranges from 0 to 3</paintjob>
<upgrades>Space separated list of vehicle upgrade numbers</upgrades>
</spawnpoint>


<checkpoint>
<position>X Y Z</position>
<size>Float. Higher values make the checkpoint marker bigger. Default is 2.25</size>
<color>R G B</color> 

<vehicle>Vehicle ID to change into when passing through this checkpoint</vehicle>
<paintjob>Paintjob ID, ranges from 0 to 3</paintjob>
<upgrades>Space separated list of vehicle upgrade numbers</upgrades>
</checkpoint>


<object>
<position>X Y Z</position>
<rotation>rotX rotY rotZ</rotation> 
<model>Model ID</model>
</object>


<pickup>
<position>X Y Z</position>
<type>repair|nitro|vehiclechange</type>

<vehicle>Vehicle ID to change into</vehicle>

<paintjob>paintjob ID</paintjob>
<upgrades>Space separated upgrade list</upgrades>
</pickup>
</map>
</syntaxhighlight>

The <skins> option can be "cj" (players are CJ in random clothes), "random" (players have random ped skins), or a range list. A range list is a space separated list of single numbers and ranges of numbers expressed as "start-end". For example:

<syntaxhighlight lang="lua">18 40-50 65-68 72 200</syntaxhighlight>

The skin of each player will be chosen at random from this list.

===MTA:SA DM style syntax===
====.map file====
<syntaxhighlight lang="xml">
<map mod="deathmatch">

<spawnpoint posX="X" posY="Y" posZ="Z" rotation="Rotation in degrees" vehicle="Vehicle ID" id="spawnpointID" [ paintjob="paintjob ID" upgrades="*comma*-separated list of upgrades" ] />


<checkpoint posX="X" posY="Y" posZ="Z" color="#FF0000" id="textual or numeric checkpoint ID" nextid="ID of checkpoint after this one" [ size="checkpoint size" vehicle="vehicle ID to change into" paintjob="paintjob ID" upgrades="comma-separated list of upgrades" ] />


<object posX="X" posY="Y" posZ="Z" rotX="in degrees" rotY="in degrees" rotZ="in degrees" model="model ID" id="objectID" />


<pickup posX="X" posY="Y" posZ="Z" type="repair|nitro|vehiclechange" id="pickupID" [ vehicle="vehicle ID" paintjob="paintjob ID" upgrades="comma-separated list of upgrades" ] />
</map>
</syntaxhighlight>

====meta.xml====
<syntaxhighlight lang="xml">
<meta>
<info type="map" gamemodes="race" name="Map name" author="Author name" description="Map description" version="Map version number"/>
<race src="Map file.map"/>
<settings>
<setting name="#optionName" value="optionValue"/>
...
</settings>
</meta>
</syntaxhighlight>
The <setting>s correspond to options in MTA:Race syntax. For example, <time>4:0</time> in MTA:Race syntax would correspond to <setting name="#time" value="4:0"/> in DM syntax.

==Events==
===onPlayerReachCheckpoint===
====Parameters====
<syntaxhighlight lang="lua">int checkpoint, int ms</syntaxhighlight>
*'''checkpoint:''' the number of the checkpoint the player went through. The first checkpoint has number 1.
*'''ms:''' time in milliseconds since the start of the race.

NOTE: only the '''checkpoint''' argument is supplied, the '''ms''' is definitely NOT.

====Source====
The source is the player that reached the checkpoint.

===onPlayerPickUpRacePickup===
====Parameters====
<syntaxhighlight lang="lua">int/string pickupID</syntaxhighlight>
*'''pickupID:''' the number of the pickup in case of MTA:Race syntax (starting at 1), or the "id" attribute of the pickup in case of DM syntax.

====Source====
The source is the player that picked up the pickup.

==Element data==
These element data are set on each player:
*'''Race rank:''' the current position of the player in the race. 1 = first, 2 = second etc. Updated on a 1 second interval.
*'''race.checkpoint:''' the number of the checkpoint the player is ''heading for''. When the player spawns this number is 1, after he passed the first checkpoint it's 2, etc.
*'''race.finished:''' ''true'' if the player has finished, ''false'' if he's still racing.

SetElementVisibleTo

2008-01-20T20:56:17Z

Mvol:

__NOTOC__
{{Server function}}
{{Needs_Checking|Can an element only be visible to one element (and its children) at a time? If so, do we need clearElementVisibleTo? If not, surely we need to remove the root element before using this function?|[[User:EAi|EAi]]
}}
{{Needs_Checking|'''*''' I tried to make a blip visible to 1 player but it doesn't work unless I use getRootElement() [[User:Norby89|Norby89]] 10:20, 3 August 2007 (CDT)
}}
{{Needs_Checking|'''*''' I tried to hide a marker from 1 player but I have to make the marker especially visible to this player before (tested on DP2)
[[User:mvol|mvol]] 21:51, 20 January 2008 (CDT)
}}

This function can change an [[element]]'s [[visibility]]. This does not work with all entities - [[vehicle]]s, [[player]]s and [[object]]s are exempt. This is because these objects are required for accurate sync (they're physical objects). This function is particularily useful for changing the visibility of markers, radar blips and radar areas.

==Syntax==
<syntaxhighlight lang="lua">
bool setElementVisibleTo ( element theElement, element visibleTo, bool visible )
</syntaxhighlight>

===Required Arguments===
*'''theElement:''' The element you want to control the visibility of.
*'''visibleTo:''' The element you wish the element to be visible or invisible to. Any child elements that are players will also be able to see the element. See [[visibility]].
*'''visible:''' Whether you are making it visible or invisible to the player.

===Returns===
Returns ''true'' if the element's visibility was changed successfully, ''false'' otherwise, for example if you are trying to change the visibility of a vehicle, player or object.

==Example==
This example creates a marker and makes it only visibile to the player called 'someguy'.
<syntaxhighlight lang="lua">
-- Find the player called someguy
local someguy = getPlayerFromNick ( "someguy" )
-- If the player was found then
if ( someguy ) then
-- Get the player's position into the variables x, y and z
x, y, z = getElementPosition ( someguy )
-- Create a marker at the player's position
myMarker = createMarker ( x, y, z )
-- First off make the marker invisible to the whole dimension
setElementVisibleTo ( myMarker, getRootElement ( ), false )
-- Then make the marker visible again, but only to someguy
setElementVisibleTo ( myMarker, someguy, true )
end
</syntaxhighlight>

The following example show how to hide the marker on 'someguy' from 'anotherguy'
<syntaxhighlight lang="lua">
-- Find the player called someguy
local someguy = getPlayerFromNick ( "someguy" )
local anotherguy = getPlayerFromNick ( "anotherguy" )
-- If the player was found then
if ( someguy ) then
-- Get the player's position into the variables x, y and z
x, y, z = getElementPosition ( someguy )
-- Create a marker at the player's position
myMarker = createMarker ( x, y, z )
-- First off make the marker visible especially to 'anotherguy'
setElementVisibleTo ( myMarker, anotherguy, true )
-- Then hide it
setElementVisibleTo ( myMarker, anotherguy, false )
end
</syntaxhighlight>

==See Also==
{{Element_functions}}

Known Issues - FAQ

2008-01-09T16:17:27Z

Mvol: /* Client */

Post here your proposed Q&A, regarding the known problems with MTA:SA DM and their solutions, especially problems we're encountering now, that might be also encountered by users in the final release. You're also welcome to edit them grammar/style wise.

== Client ==

=== General ===
==== No chat response and black screen when in-game ====
* '''After connecting to a server, my chat doesn't seem to work and nothing seems to happen. I can only see a black screen, I'm not getting spawned but I can see other people.'''

This problem occurs due to the server-side packet size being set too high (close to the Ethernet maximum of 1500 bytes), resulting in the loss of all packets with this size somewhere on their way from the server to client (e.g. they are dropped by a switch, your local router, or your NIC), the above problems and possibly a ''Connection Lost'' message after a while.

{{Fixed|v1.0-dp2}}

==== Initial black screen/hanging GTA splash screens ====
* '''MTA shows a permanent black screen or hanging GTA splash screens.'''

It may be necessary that during/after the logo splash screens in Grand Theft Auto you have to give some input in order to skip the videos correctly. Try to click your left-mouse button a few times, or tapping a few keys.

* '''MTA shows a permanent black screen after the GTA splash screens (possibly with text in the bottom right corner).'''

This can be related to a lack of support for DirectX or video card features, on your system, which are needed to run the dynamically rendered menu. This dynamic menu is enabled by default. Try disabling the dynamic menu by downloading the adjusted [http://www.mtasa.com/files/coreconfig.xml coreconfig.xml] file and placing it in our ''GTA San Andreas\MTA'' directory (overwriting any existing files).

==== Halt after MTA splash screen ====
* '''Nothing happens after the 'Stop playing with yourself' splash screen'''

If you use nVidia GeForce, try turning off nView Desktop Manager before starting MTA.

Also try deleting GTA San Andreas settings file ("gta_sa.set") in "Documents\GTA San Andreas User Files" folder

==== Crash after MTA splash screen ====
* '''MTA crashes after the 'Stop playing with yourself' logo. Both single player and the MTA: Race ran fine before.'''

Try downloading the latest DirectX Runtime files from [http://www.microsoft.com/downloads/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&DisplayLang=en Microsoft]. Also check in Task Manager, if gta_sa.exe process isn't already running.

If you run at any substandard resolutions (e.g. 960x720), try to change your resolution to a commonly supported one (e.g. 640×480, 800×600, 1024×768, 1152×864, 1280×1024) by launching Grand Theft Auto: San Andreas in normal mode, setting the new resolution and exiting.

==== Assertion in CMainMenu.cpp line 106 upon launching MTASA ====
* '''I'm getting an assertion in CMainMenu.cpp (line 106) after I have launched MTASA. I'm able to ignore it, but then game crashes after I try to connect to a server.'''

This is likely caused by GTASA or MTASA being installed in a path that contains non-ASCII characters (eg. Cyrillic, Polish, Japanese) in it.

To resolve this, you need to uninstall MTASA and GTASA, then install them in such paths that don't contain such characters.

==== Controls not working ====
* '''My controls don't seem to work as they should.'''

Try using the 'copygtacontrols' command in the console.

==== Incorrect models ====
* '''Woman model's breasts look awkward ingame / I'm seeing odd, spider-like shaped player models.'''

This is caused by the way GTA handles player stats. To fix this, be sure to set both fat and muscles player stats to 0, when you're changing player skin.

==== Incorrect drive-by functionality ====
* '''Drivebys arent working as they should'''

Drivebys are handled by script, and will change depending on the loaded gamemode.

==== Unsaved settings ====
* '''My MTA setting(s) didn't get saved (...) I crashed.'''

First, configure the MTA the way you want to, then exit the game and launch it again. Settings should get saved. Alternatively, try removing the coreconfig.xml file, then configure it and quit the game.

==== Gamepad support ====
* '''MTA doesnt recognise my gamepad'''

This is a known issue - MTA's keybinds system does not support direct input. As an alternative, [http://xpadder.com/ XPadder] can be used. This emulates joypad buttons as keyboard/mouse so that it can be used in MTA. Please refer to [http://forum.mtasa.com/viewtopic.php?f=87&t=21167 this forum topic] for a brief guide on how to use XPadder.

==== Sky flickering ====
* '''My screen/sky flickers when weather or sky effects are enabled.

MTA:SA DM uses a new text rendering system from race, which is much more efficient in terms of FPS. However, this can cause conflicts within the game, particularly with ATI based cards. To fix this, bring up the console with ¬(tilde), and type the command '''ceguitext 1'''. This reverts the rendering method to that of Race. All glitches should no longer happen, at the cost of lower FPS.

====Invalid serial number====
This seems to happen randomly to a few people. The best way to fix this is to install without a serial number at all (choose the bottom option on the MTA accounts page of the installer). We'll be looking into fixing this as soon as possible.

You can also try to login into your account on [http://mtabeta.com/ www.mtabeta.com], there you can read your serial number. Then open "
HKEY_LOCAL_MACHINE/SOFTWARE/Multi Theft Auto: San Andreas/" in your registry. There you have to create the string "Username" with your username as value, and the string "Serial" with your serial number as value.

==== 'Network module could not be located' ====
*'''I am getting 'Network module could not be located' error message upon launching MTA:SA DM

Copy the file 'net.dll' from your GTA:SA/mta directory into your GTA:SA directory, overwriting existing files.

=== Windows Vista®-related ===

==== Crash on launch ====
* '''I've successfully upgraded from MTA Race to MTASA DM on Vista, but it seems to crash on launch.

Go to your Program Files\MTA San Andreas\mods\race directory, and rename client.dll to something else.

==== Crash on connect ====
* '''I seem to crash whenever I connect to a server just before I go in-game on Vista'''

This seems to be an issue with the Microsoft DirectX April 2006 SDK Redistributable DLL file (d3dx9_30.dll) when running in compatibility mode. Please make sure that compatibility mode is competely turned off for '''both''' your GTA_SA.exe and Multi Theft Auto.exe executables.

==== Invalid serial error ====
* '''MTASA DM installer complains about wrong serial provided. I'm running it for the first time.

You need to run the installer with Administrator privileges. To do so, right click on the installer executable, choose 'Properties', go into 'Compatibility' tab and tick the check box on the last field.

Some have found that setting compatibility to Windows XP/2000 have fixed the problem.

If User Account Control is disabled, you might need to enable it and run the installer with admin privileges (like said above) in order to install MTA:SA DM.

==== Clock manipulation error ====
* '''I am getting 'Clock manipulation detected!' error message upon launching MTA:SA DM

Further info coming soon.

==== Halt on launch ====
* '''When I launch MTA:SA DM, nothing happens (GTA_SA.exe is running but not loading up)

Run MTA:SA DM with Administrator privileges. To do this, right click on the installer executable, choose 'Properties', go into 'Compatibility' tab and tick the check box on the last field and try again.

==== General GTA problems ====
* '''I have unexplainable GTA problems or crashes'''

Make sure your computer as well as your GTA install meet the [[Deathmatch_Client_Manual#System_requirements|minimum requirements]] and that you are not running in any 98/2000/XP/2003 compatibility modes.

Also try the solutions from these pages:
* http://www.gtaforums.com/index.php?showtopic=273549&view=findpost&p=4537502
* http://pullmonkey.com/2007/4/30/how-i-got-gta-san-andreas-to-work-with-a-crappy-os-vista

== Server ==

=== General ===
==== Fatal error 3 ====
* '''I'm getting ''Fatal Error 3'' whenever I connect to my server'''

This error happens when the server you are trying to connect to is unable to provide you the required downloads, because it does not have http downloading enabled. Be sure to set the '''httpdownload''' configuration tag in your configuration to '''1'''.
==== Download error 9: Error downloading requested files ====
* '''I'm getting ''Download Error 9: Error downloading requested files'' whenever I connect to my server'''

This error happens when the server you are trying to connect to is unable to provide you with a valid link. This results in a 404 (Not found) HTTP error and an error at your end.

* If you are running the built-in server ('''httpserver''' is set to '''1''' and '''httpdownloadurl''' is empty), make sure that your HTTP server is accessible (you can try to access it by using a browser) for everyone.

* If you have configured an external web server ('''httpdownloadurl''' is set to your custom URL), make sure that your HTTP is accessible and make sure you have read the [[Deathmatch_Server_Manual#Configuring_an_external_web_server | Configuring an external web server]] guide.

==== Crashing when banning a player ====
The banPlayer script function will crash. Avoid using it. You can modify the xml file manually instead. This will be fixed in the next release.

{{Fixed|v1.0-dp2}}

=== Windows-related ===
No known reported issues.

=== Linux-related ===
==== libcurl.so.<version>: cannot open shared object file ====
* '''My dedicated server gives a ''libcurl.so.<version>: cannot open shared object file'' error on startup''' (where <version> is to be replaced with 3 or 4)

This means one of the dynamic dependencies (libcurl, CURL) needed in order to run the server cannot be found on your server.

<ul>
<li>If your server reports that it cannot find '''libcurl.so.4''', it's most likely due to an old version of libcurl that is installed on your system. You can either choose to upgrade libcurl to the latest version (check out your distribution package manager, or download/compile/install from the [http://curl.haxx.se/ CURL website]), or you can choose to pick another Linux build (e.g. the Generic Linux build, which contains a statically linked version of the library).
</li>

<li>If your server reports that it cannot find '''libcurl.so.3''', libcurl is either not installed on your system, you are running an outdated version or you are running a newer version of libcurl (and downloaded a build that relied on the old version).
<ul>
<li>If '''libcurl.so.4''' is present on your system (e.g. in /usr/lib), it means you have a newer version than the one required and you can most likely solve the problem by creating a symbolic to libcurl.so.3:
<pre>$ ln -s /usr/lib/libcurl.so.4 /usr/lib/libcurl.so.3</pre>
</li>
<li>If '''libcurl.so.2''' is present on your system (e.g. in /usr/lib), it means you have an older version and you can solve the problem by installing the most recent version of libcurl. This should be done through your package manager (check your distribution's documentation), or no such manager is present, by manually compiling and installing the latest CURL source from the [http://curl.haxx.se/ CURL website]).
</li>
<li>If libcurl is not present on your system, see how to install libcurl by reading the instructions above.</li>
</ul>
</li>
</ul>

{{Fixed|v1.0-dp2}}

==== ERROR: Couldn't find meta.xml ====
* '''My dedicated server console reports one of the following errors''':
* ERROR: Couldn't find meta.xml file for resource '.'
* ERROR: Couldn't find meta.xml file for resource '..'

This is a minor (visual) issue with the directory handling code in the Linux server. The server tries to read the . and .. operators that are available in every directory, resulting in an error. You can safely ignore this issue.

{{Fixed|v1.0-dp2}}

==== ERROR: Could not parse 'settings.xml' file ====
* ''''My dedicated server reports the ''ERROR: Could not parse 'settings.xml' file (Invalid file). Starting with an empty settings registry.'' error.

This is because a default settings.xml file isn't shipped with the server. After this error is encountered, the server should be automatically created by the server. To be sure that the creation was successful, and that you have appropriate rights to the file, you can execute the following commands:

<pre>/mtasa_server_directory/mods/deathmatch $ touch settings.xml
/mtasa_server_directory/mods/deathmatch $ chmod 755 settings.xml</pre>

Please note that the word '''settings''' here doesn't reflect your server configuration, but rather the scriptable [[Settings system]].

{{Fixed|v1.0-dp2}}

Known Issues - FAQ

2008-01-09T16:16:03Z

Mvol: /* Client */

Post here your proposed Q&A, regarding the known problems with MTA:SA DM and their solutions, especially problems we're encountering now, that might be also encountered by users in the final release. You're also welcome to edit them grammar/style wise.

== Client ==

=== General ===
==== No chat response and black screen when in-game ====
* '''After connecting to a server, my chat doesn't seem to work and nothing seems to happen. I can only see a black screen, I'm not getting spawned but I can see other people.'''

This problem occurs due to the server-side packet size being set too high (close to the Ethernet maximum of 1500 bytes), resulting in the loss of all packets with this size somewhere on their way from the server to client (e.g. they are dropped by a switch, your local router, or your NIC), the above problems and possibly a ''Connection Lost'' message after a while.

{{Fixed|v1.0-dp2}}

==== Initial black screen/hanging GTA splash screens ====
* '''MTA shows a permanent black screen or hanging GTA splash screens.'''

It may be necessary that during/after the logo splash screens in Grand Theft Auto you have to give some input in order to skip the videos correctly. Try to click your left-mouse button a few times, or tapping a few keys.

* '''MTA shows a permanent black screen after the GTA splash screens (possibly with text in the bottom right corner).'''

This can be related to a lack of support for DirectX or video card features, on your system, which are needed to run the dynamically rendered menu. This dynamic menu is enabled by default. Try disabling the dynamic menu by downloading the adjusted [http://www.mtasa.com/files/coreconfig.xml coreconfig.xml] file and placing it in our ''GTA San Andreas\MTA'' directory (overwriting any existing files).

==== Halt after MTA splash screen ====
* '''Nothing happens after the 'Stop playing with yourself' splash screen'''

If you use nVidia GeForce, try turning off nView Desktop Manager before starting MTA.

Also try deleting GTA San Andreas settings file ("gta_sa.set") in "Documents\GTA San Andreas User Files" folder

==== Crash after MTA splash screen ====
* '''MTA crashes after the 'Stop playing with yourself' logo. Both single player and the MTA: Race ran fine before.'''

Try downloading the latest DirectX Runtime files from [http://www.microsoft.com/downloads/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&DisplayLang=en Microsoft]. Also check in Task Manager, if gta_sa.exe process isn't already running.

If you run at any substandard resolutions (e.g. 960x720), try to change your resolution to a commonly supported one (e.g. 640×480, 800×600, 1024×768, 1152×864, 1280×1024) by launching Grand Theft Auto: San Andreas in normal mode, setting the new resolution and exiting.

==== Assertion in CMainMenu.cpp line 106 upon launching MTASA ====
* '''I'm getting an assertion in CMainMenu.cpp (line 106) after I have launched MTASA. I'm able to ignore it, but then game crashes after I try to connect to a server.'''

This is likely caused by GTASA or MTASA being installed in a path that contains non-ASCII characters (eg. Cyrillic, Polish, Japanese) in it.

To resolve this, you need to uninstall MTASA and GTASA, then install them in such paths that don't contain such characters.

==== Controls not working ====
* '''My controls don't seem to work as they should.'''

Try using the 'copygtacontrols' command in the console.

==== Incorrect models ====
* '''Woman model's breasts look awkward ingame / I'm seeing odd, spider-like shaped player models.'''

This is caused by the way GTA handles player stats. To fix this, be sure to set both fat and muscles player stats to 0, when you're changing player skin.

==== Incorrect drive-by functionality ====
* '''Drivebys arent working as they should'''

Drivebys are handled by script, and will change depending on the loaded gamemode.

==== Unsaved settings ====
* '''My MTA setting(s) didn't get saved (...) I crashed.'''

First, configure the MTA the way you want to, then exit the game and launch it again. Settings should get saved. Alternatively, try removing the coreconfig.xml file, then configure it and quit the game.

==== Gamepad support ====
* '''MTA doesnt recognise my gamepad'''

This is a known issue - MTA's keybinds system does not support direct input. As an alternative, [http://xpadder.com/ XPadder] can be used. This emulates joypad buttons as keyboard/mouse so that it can be used in MTA. Please refer to [http://forum.mtasa.com/viewtopic.php?f=87&t=21167 this forum topic] for a brief guide on how to use XPadder.

==== Sky flickering ====
* '''My screen/sky flickers when weather or sky effects are enabled.

MTA:SA DM uses a new text rendering system from race, which is much more efficient in terms of FPS. However, this can cause conflicts within the game, particularly with ATI based cards. To fix this, bring up the console with ¬(tilde), and type the command '''ceguitext 1'''. This reverts the rendering method to that of Race. All glitches should no longer happen, at the cost of lower FPS.

====Invalid serial number====
This seems to happen randomly to a few people. The best way to fix this is to install without a serial number at all (choose the bottom option on the MTA accounts page of the installer). We'll be looking into fixing this as soon as possible.

You can also try to login into your account on [http://mtabeta.com/ www.mtabeta.com], there you can read your serial number. Then open "
HKEY_LOCAL_MACHINE/SOFTWARE/Multi Theft Auto: San Andreas/" in your registry. There you have to create the string "Username" with your username as value, and the string "Serial" with your serial number as value.

=== Windows Vista®-related ===

==== Crash on launch ====
* '''I've successfully upgraded from MTA Race to MTASA DM on Vista, but it seems to crash on launch.

Go to your Program Files\MTA San Andreas\mods\race directory, and rename client.dll to something else.

==== Crash on connect ====
* '''I seem to crash whenever I connect to a server just before I go in-game on Vista'''

This seems to be an issue with the Microsoft DirectX April 2006 SDK Redistributable DLL file (d3dx9_30.dll) when running in compatibility mode. Please make sure that compatibility mode is competely turned off for '''both''' your GTA_SA.exe and Multi Theft Auto.exe executables.

==== Invalid serial error ====
* '''MTASA DM installer complains about wrong serial provided. I'm running it for the first time.

You need to run the installer with Administrator privileges. To do so, right click on the installer executable, choose 'Properties', go into 'Compatibility' tab and tick the check box on the last field.

Some have found that setting compatibility to Windows XP/2000 have fixed the problem.

If User Account Control is disabled, you might need to enable it and run the installer with admin privileges (like said above) in order to install MTA:SA DM.

==== Clock manipulation error ====
* '''I am getting 'Clock manipulation detected!' error message upon launching MTA:SA DM

Further info coming soon.

==== Halt on launch ====
* '''When I launch MTA:SA DM, nothing happens (GTA_SA.exe is running but not loading up)

Run MTA:SA DM with Administrator privileges. To do this, right click on the installer executable, choose 'Properties', go into 'Compatibility' tab and tick the check box on the last field and try again.

==== 'Network module could not be located' ====
*'''I am getting 'Network module could not be located' error message upon launching MTA:SA DM

Copy the file 'net.dll' from your GTA:SA/mta directory into your GTA:SA directory, overwriting existing files.

==== General GTA problems ====
* '''I have unexplainable GTA problems or crashes'''

Make sure your computer as well as your GTA install meet the [[Deathmatch_Client_Manual#System_requirements|minimum requirements]] and that you are not running in any 98/2000/XP/2003 compatibility modes.

Also try the solutions from these pages:
* http://www.gtaforums.com/index.php?showtopic=273549&view=findpost&p=4537502
* http://pullmonkey.com/2007/4/30/how-i-got-gta-san-andreas-to-work-with-a-crappy-os-vista

== Server ==

=== General ===
==== Fatal error 3 ====
* '''I'm getting ''Fatal Error 3'' whenever I connect to my server'''

This error happens when the server you are trying to connect to is unable to provide you the required downloads, because it does not have http downloading enabled. Be sure to set the '''httpdownload''' configuration tag in your configuration to '''1'''.
==== Download error 9: Error downloading requested files ====
* '''I'm getting ''Download Error 9: Error downloading requested files'' whenever I connect to my server'''

This error happens when the server you are trying to connect to is unable to provide you with a valid link. This results in a 404 (Not found) HTTP error and an error at your end.

* If you are running the built-in server ('''httpserver''' is set to '''1''' and '''httpdownloadurl''' is empty), make sure that your HTTP server is accessible (you can try to access it by using a browser) for everyone.

* If you have configured an external web server ('''httpdownloadurl''' is set to your custom URL), make sure that your HTTP is accessible and make sure you have read the [[Deathmatch_Server_Manual#Configuring_an_external_web_server | Configuring an external web server]] guide.

==== Crashing when banning a player ====
The banPlayer script function will crash. Avoid using it. You can modify the xml file manually instead. This will be fixed in the next release.

{{Fixed|v1.0-dp2}}

=== Windows-related ===
No known reported issues.

=== Linux-related ===
==== libcurl.so.<version>: cannot open shared object file ====
* '''My dedicated server gives a ''libcurl.so.<version>: cannot open shared object file'' error on startup''' (where <version> is to be replaced with 3 or 4)

This means one of the dynamic dependencies (libcurl, CURL) needed in order to run the server cannot be found on your server.

<ul>
<li>If your server reports that it cannot find '''libcurl.so.4''', it's most likely due to an old version of libcurl that is installed on your system. You can either choose to upgrade libcurl to the latest version (check out your distribution package manager, or download/compile/install from the [http://curl.haxx.se/ CURL website]), or you can choose to pick another Linux build (e.g. the Generic Linux build, which contains a statically linked version of the library).
</li>

<li>If your server reports that it cannot find '''libcurl.so.3''', libcurl is either not installed on your system, you are running an outdated version or you are running a newer version of libcurl (and downloaded a build that relied on the old version).
<ul>
<li>If '''libcurl.so.4''' is present on your system (e.g. in /usr/lib), it means you have a newer version than the one required and you can most likely solve the problem by creating a symbolic to libcurl.so.3:
<pre>$ ln -s /usr/lib/libcurl.so.4 /usr/lib/libcurl.so.3</pre>
</li>
<li>If '''libcurl.so.2''' is present on your system (e.g. in /usr/lib), it means you have an older version and you can solve the problem by installing the most recent version of libcurl. This should be done through your package manager (check your distribution's documentation), or no such manager is present, by manually compiling and installing the latest CURL source from the [http://curl.haxx.se/ CURL website]).
</li>
<li>If libcurl is not present on your system, see how to install libcurl by reading the instructions above.</li>
</ul>
</li>
</ul>

{{Fixed|v1.0-dp2}}

==== ERROR: Couldn't find meta.xml ====
* '''My dedicated server console reports one of the following errors''':
* ERROR: Couldn't find meta.xml file for resource '.'
* ERROR: Couldn't find meta.xml file for resource '..'

This is a minor (visual) issue with the directory handling code in the Linux server. The server tries to read the . and .. operators that are available in every directory, resulting in an error. You can safely ignore this issue.

{{Fixed|v1.0-dp2}}

==== ERROR: Could not parse 'settings.xml' file ====
* ''''My dedicated server reports the ''ERROR: Could not parse 'settings.xml' file (Invalid file). Starting with an empty settings registry.'' error.

This is because a default settings.xml file isn't shipped with the server. After this error is encountered, the server should be automatically created by the server. To be sure that the creation was successful, and that you have appropriate rights to the file, you can execute the following commands:

<pre>/mtasa_server_directory/mods/deathmatch $ touch settings.xml
/mtasa_server_directory/mods/deathmatch $ chmod 755 settings.xml</pre>

Please note that the word '''settings''' here doesn't reflect your server configuration, but rather the scriptable [[Settings system]].

{{Fixed|v1.0-dp2}}

Known Issues - FAQ

2008-01-06T14:18:58Z

Mvol: /* Invalid serial number */

Post here your proposed Q&A, regarding the known problems with MTA:SA DM and their solutions, especially problems we're encountering now, that might be also encountered by users in the final release. You're also welcome to edit them grammar/style wise.

== Client ==

=== General ===
==== No chat response and black screen when in-game ====
* '''After connecting to a server, my chat doesn't seem to work and nothing seems to happen. I can only see a black screen, I'm not getting spawned but I can see other people.'''

This problem occurs due to the server-side packet size being set too high (close to the Ethernet maximum of 1500 bytes), resulting in the loss of all packets with this size somewhere on their way from the server to client (e.g. they are dropped by a switch, your local router, or your NIC), the above problems and possibly a ''Connection Lost'' message after a while.

{{Fixed|v1.0-dp2}}

==== Initial black screen/hanging GTA splash screens ====
* '''MTA shows a permanent black screen or hanging GTA splash screens.'''

It may be necessary that during/after the logo splash screens in Grand Theft Auto you have to give some input in order to skip the videos correctly. Try to click your left-mouse button a few times, or tapping a few keys.

* '''MTA shows a permanent black screen after the GTA splash screens (possibly with text in the bottom right corner).'''

This can be related to a lack of support for DirectX or video card features, on your system, which are needed to run the dynamically rendered menu. This dynamic menu is enabled by default. Try disabling the dynamic menu by downloading the adjusted [http://www.mtasa.com/files/coreconfig.xml coreconfig.xml] file and placing it in our ''GTA San Andreas\MTA'' directory (overwriting any existing files).

==== Halt after MTA splash screen ====
* '''Nothing happens after the 'Stop playing with yourself' splash screen'''

If you use nVidia GeForce, try turning off nView Desktop Manager before starting MTA.

Also try deleting GTA San Andreas settings file ("gta_sa.set") in "Documents\GTA San Andreas User Files" folder

==== Crash after MTA splash screen ====
* '''MTA crashes after the 'Stop playing with yourself' logo. Both single player and the MTA: Race ran fine before.'''

Try downloading the latest DirectX Runtime files from [http://www.microsoft.com/downloads/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&DisplayLang=en Microsoft]. Also check in Task Manager, if gta_sa.exe process isn't already running.

If you run at any substandard resolutions (e.g. 960x720), try to change your resolution to a commonly supported one (e.g. 640×480, 800×600, 1024×768, 1152×864, 1280×1024) by launching Grand Theft Auto: San Andreas in normal mode, setting the new resolution and exiting.

==== Controls not working ====
* '''My controls don't seem to work as they should.'''

Try using the 'copygtacontrols' command in the console.

==== Incorrect models ====
* '''Woman model's breasts look awkward ingame / I'm seeing odd, spider-like shaped player models.'''

This is caused by the way GTA handles player stats. To fix this, be sure to set both fat and muscles player stats to 0, when you're changing player skin.

==== Incorrect drive-by functionality ====
* '''Drivebys arent working as they should'''

Drivebys are handled by script, and will change depending on the loaded gamemode.

==== Unsaved settings ====
* '''My MTA setting(s) didn't get saved (...) I crashed.'''

First, configure the MTA the way you want to, then exit the game and launch it again. Settings should get saved. Alternatively, try removing the coreconfig.xml file, then configure it and quit the game.

==== Gamepad support ====
* '''MTA doesnt recognise my gamepad'''

This is a known issue - MTA's keybinds system does not support direct input. As an alternative, [http://xpadder.com/ XPadder] can be used. This emulates joypad buttons as keyboard/mouse so that it can be used in MTA.

==== Sky flickering ====
* '''My screen/sky flickers when weather or sky effects are enabled.

MTA:SA DM uses a new text rendering system from race, which is much more efficient in terms of FPS. However, this can cause conflicts within the game, particularly with ATI based cards. To fix this, bring up the console with ¬(tilde), and type the command '''ceguitext 1'''. This reverts the rendering method to that of Race. All glitches should no longer happen, at the cost of lower FPS.

====Invalid serial number====
This seems to happen randomly to a few people. The best way to fix this is to install without a serial number at all (choose the bottom option on the MTA accounts page of the installer). We'll be looking into fixing this as soon as possible.

You can also try to login into your account on [http://mtabeta.com/ www.mtabeta.com], there you can read your serial number. Then open "
HKEY_LOCAL_MACHINE/SOFTWARE/Multi Theft Auto: San Andreas/" in your registry. There you have to create the string "Username" with your username as value, and the string "Serial" with your serial number as value.

=== Windows Vista®-related ===

==== Crash on launch ====
* '''I've successfully upgraded from MTA Race to MTASA DM on Vista, but it seems to crash on launch.

Go to your Program Files\MTA San Andreas\mods\race directory, and rename client.dll to something else.

==== Crash on connect ====
* '''I seem to crash whenever I connect to a server just before I go in-game on Vista'''

This seems to be an issue with the Microsoft DirectX April 2006 SDK Redistributable DLL file (d3dx9_30.dll) when running in compatibility mode. Please make sure that compatibility mode is competely turned off for '''both''' your GTA_SA.exe and Multi Theft Auto.exe executables.

==== Invalid serial error ====
* '''MTASA DM installer complains about wrong serial provided. I'm running it for the first time.

You need to run the installer with Administrator privileges. To do so, right click on the installer executable, choose 'Properties', go into 'Compatibility' tab and tick the check box on the last field.

Some have found that setting compatibility to Windows XP/2000 have fixed the problem.

If User Account Control is disabled, you might need to enable it and run the installer with admin privileges (like said above) in order to install MTA:SA DM.

==== Clock manipulation error ====
* '''I am getting 'Clock manipulation detected!' error message upon launching MTA:SA DM

Further info coming soon.

==== Halt on launch ====
* '''When I launch MTA:SA DM, nothing happens (GTA_SA.exe is running but not loading up)

Run MTA:SA DM with Administrator privileges. To do this, right click on the installer executable, choose 'Properties', go into 'Compatibility' tab and tick the check box on the last field and try again.

==== General GTA problems ====
* '''I have unexplainable GTA problems or crashes'''

Make sure your computer as well as your GTA install meet the [[Deathmatch_Client_Manual#System_requirements|minimum requirements]] and that you are not running in any 98/2000/XP/2003 compatibility modes.

Also try the solutions from these pages:
* http://www.gtaforums.com/index.php?showtopic=273549&view=findpost&p=4537502
* http://pullmonkey.com/2007/4/30/how-i-got-gta-san-andreas-to-work-with-a-crappy-os-vista

== Server ==

=== General ===
==== Fatal error 3 ====
* '''I'm getting ''Fatal Error 3'' whenever I connect to my server'''

This error happens when the server you are trying to connect to is unable to provide you the required downloads, because it does not have http downloading enabled. Be sure to set the '''httpdownload''' configuration tag in your configuration to '''1'''.
==== Download error 9: Error downloading requested files ====
* '''I'm getting ''Download Error 9: Error downloading requested files'' whenever I connect to my server'''

This error happens when the server you are trying to connect to is unable to provide you with a valid link. This results in a 404 (Not found) HTTP error and an error at your end.

* If you are running the built-in server ('''httpserver''' is set to '''1''' and '''httpdownloadurl''' is empty), make sure that your HTTP server is accessible (you can try to access it by using a browser) for everyone.

* If you have configured an external web server ('''httpdownloadurl''' is set to your custom URL), make sure that your HTTP is accessible and make sure you have read the [[Deathmatch_Server_Manual#Configuring_an_external_web_server | Configuring an external web server]] guide.

==== Crashing when banning a player ====
The banPlayer script function will crash. Avoid using it. You can modify the xml file manually instead. This will be fixed in the next release.

{{Fixed|v1.0-dp2}}

=== Windows-related ===
No known reported issues.

=== Linux-related ===
==== libcurl.so.<version>: cannot open shared object file ====
* '''My dedicated server gives a ''libcurl.so.<version>: cannot open shared object file'' error on startup''' (where <version> is to be replaced with 3 or 4)

This means one of the dynamic dependencies (libcurl, CURL) needed in order to run the server cannot be found on your server.

<ul>
<li>If your server reports that it cannot find '''libcurl.so.4''', it's most likely due to an old version of libcurl that is installed on your system. You can either choose to upgrade libcurl to the latest version (check out your distribution package manager, or download/compile/install from the [http://curl.haxx.se/ CURL website]), or you can choose to pick another Linux build (e.g. the Generic Linux build, which contains a statically linked version of the library).
</li>

<li>If your server reports that it cannot find '''libcurl.so.3''', libcurl is either not installed on your system, you are running an outdated version or you are running a newer version of libcurl (and downloaded a build that relied on the old version).
<ul>
<li>If '''libcurl.so.4''' is present on your system (e.g. in /usr/lib), it means you have a newer version than the one required and you can most likely solve the problem by creating a symbolic to libcurl.so.3:
<pre>$ ln -s /usr/lib/libcurl.so.4 /usr/lib/libcurl.so.3</pre>
</li>
<li>If '''libcurl.so.2''' is present on your system (e.g. in /usr/lib), it means you have an older version and you can solve the problem by installing the most recent version of libcurl. This should be done through your package manager (check your distribution's documentation), or no such manager is present, by manually compiling and installing the latest CURL source from the [http://curl.haxx.se/ CURL website]).
</li>
<li>If libcurl is not present on your system, see how to install libcurl by reading the instructions above.</li>
</ul>
</li>
</ul>

{{Fixed|v1.0-dp2}}

==== ERROR: Couldn't find meta.xml ====
* '''My dedicated server console reports one of the following errors''':
* ERROR: Couldn't find meta.xml file for resource '.'
* ERROR: Couldn't find meta.xml file for resource '..'

This is a minor (visual) issue with the directory handling code in the Linux server. The server tries to read the . and .. operators that are available in every directory, resulting in an error. You can safely ignore this issue.

{{Fixed|v1.0-dp2}}

==== ERROR: Could not parse 'settings.xml' file ====
* ''''My dedicated server reports the ''ERROR: Could not parse 'settings.xml' file (Invalid file). Starting with an empty settings registry.'' error.

This is because a default settings.xml file isn't shipped with the server. After this error is encountered, the server should be automatically created by the server. To be sure that the creation was successful, and that you have appropriate rights to the file, you can execute the following commands:

<pre>/mtasa_server_directory/mods/deathmatch $ touch settings.xml
/mtasa_server_directory/mods/deathmatch $ chmod 755 settings.xml</pre>

Please note that the word '''settings''' here doesn't reflect your server configuration, but rather the scriptable [[Settings system]].

{{Fixed|v1.0-dp2}}

Known Issues - FAQ

2008-01-06T14:18:24Z

Mvol: /* General */

Post here your proposed Q&A, regarding the known problems with MTA:SA DM and their solutions, especially problems we're encountering now, that might be also encountered by users in the final release. You're also welcome to edit them grammar/style wise.

== Client ==

=== General ===
==== No chat response and black screen when in-game ====
* '''After connecting to a server, my chat doesn't seem to work and nothing seems to happen. I can only see a black screen, I'm not getting spawned but I can see other people.'''

This problem occurs due to the server-side packet size being set too high (close to the Ethernet maximum of 1500 bytes), resulting in the loss of all packets with this size somewhere on their way from the server to client (e.g. they are dropped by a switch, your local router, or your NIC), the above problems and possibly a ''Connection Lost'' message after a while.

{{Fixed|v1.0-dp2}}

==== Initial black screen/hanging GTA splash screens ====
* '''MTA shows a permanent black screen or hanging GTA splash screens.'''

It may be necessary that during/after the logo splash screens in Grand Theft Auto you have to give some input in order to skip the videos correctly. Try to click your left-mouse button a few times, or tapping a few keys.

* '''MTA shows a permanent black screen after the GTA splash screens (possibly with text in the bottom right corner).'''

This can be related to a lack of support for DirectX or video card features, on your system, which are needed to run the dynamically rendered menu. This dynamic menu is enabled by default. Try disabling the dynamic menu by downloading the adjusted [http://www.mtasa.com/files/coreconfig.xml coreconfig.xml] file and placing it in our ''GTA San Andreas\MTA'' directory (overwriting any existing files).

==== Halt after MTA splash screen ====
* '''Nothing happens after the 'Stop playing with yourself' splash screen'''

If you use nVidia GeForce, try turning off nView Desktop Manager before starting MTA.

Also try deleting GTA San Andreas settings file ("gta_sa.set") in "Documents\GTA San Andreas User Files" folder

==== Crash after MTA splash screen ====
* '''MTA crashes after the 'Stop playing with yourself' logo. Both single player and the MTA: Race ran fine before.'''

Try downloading the latest DirectX Runtime files from [http://www.microsoft.com/downloads/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&DisplayLang=en Microsoft]. Also check in Task Manager, if gta_sa.exe process isn't already running.

If you run at any substandard resolutions (e.g. 960x720), try to change your resolution to a commonly supported one (e.g. 640×480, 800×600, 1024×768, 1152×864, 1280×1024) by launching Grand Theft Auto: San Andreas in normal mode, setting the new resolution and exiting.

==== Controls not working ====
* '''My controls don't seem to work as they should.'''

Try using the 'copygtacontrols' command in the console.

==== Incorrect models ====
* '''Woman model's breasts look awkward ingame / I'm seeing odd, spider-like shaped player models.'''

This is caused by the way GTA handles player stats. To fix this, be sure to set both fat and muscles player stats to 0, when you're changing player skin.

==== Incorrect drive-by functionality ====
* '''Drivebys arent working as they should'''

Drivebys are handled by script, and will change depending on the loaded gamemode.

==== Unsaved settings ====
* '''My MTA setting(s) didn't get saved (...) I crashed.'''

First, configure the MTA the way you want to, then exit the game and launch it again. Settings should get saved. Alternatively, try removing the coreconfig.xml file, then configure it and quit the game.

==== Gamepad support ====
* '''MTA doesnt recognise my gamepad'''

This is a known issue - MTA's keybinds system does not support direct input. As an alternative, [http://xpadder.com/ XPadder] can be used. This emulates joypad buttons as keyboard/mouse so that it can be used in MTA.

==== Sky flickering ====
* '''My screen/sky flickers when weather or sky effects are enabled.

MTA:SA DM uses a new text rendering system from race, which is much more efficient in terms of FPS. However, this can cause conflicts within the game, particularly with ATI based cards. To fix this, bring up the console with ¬(tilde), and type the command '''ceguitext 1'''. This reverts the rendering method to that of Race. All glitches should no longer happen, at the cost of lower FPS.

====Invalid serial number====
This seems to happen randomly to a few people. The best way to fix this is to install without a serial number at all (choose the bottom option on the MTA accounts page of the installer). We'll be looking into fixing this as soon as possible.
You can also try to login into your account on [http://mtabeta.com/], there you can read your serial number. Then open "
HKEY_LOCAL_MACHINE/SOFTWARE/Multi Theft Auto: San Andreas/" in your registry. There you have to create the string "Username" with your username as value, and the string "Serial" with your serial number as value.

=== Windows Vista®-related ===

==== Crash on launch ====
* '''I've successfully upgraded from MTA Race to MTASA DM on Vista, but it seems to crash on launch.

Go to your Program Files\MTA San Andreas\mods\race directory, and rename client.dll to something else.

==== Crash on connect ====
* '''I seem to crash whenever I connect to a server just before I go in-game on Vista'''

This seems to be an issue with the Microsoft DirectX April 2006 SDK Redistributable DLL file (d3dx9_30.dll) when running in compatibility mode. Please make sure that compatibility mode is competely turned off for '''both''' your GTA_SA.exe and Multi Theft Auto.exe executables.

==== Invalid serial error ====
* '''MTASA DM installer complains about wrong serial provided. I'm running it for the first time.

You need to run the installer with Administrator privileges. To do so, right click on the installer executable, choose 'Properties', go into 'Compatibility' tab and tick the check box on the last field.

Some have found that setting compatibility to Windows XP/2000 have fixed the problem.

If User Account Control is disabled, you might need to enable it and run the installer with admin privileges (like said above) in order to install MTA:SA DM.

==== Clock manipulation error ====
* '''I am getting 'Clock manipulation detected!' error message upon launching MTA:SA DM

Further info coming soon.

==== Halt on launch ====
* '''When I launch MTA:SA DM, nothing happens (GTA_SA.exe is running but not loading up)

Run MTA:SA DM with Administrator privileges. To do this, right click on the installer executable, choose 'Properties', go into 'Compatibility' tab and tick the check box on the last field and try again.

==== General GTA problems ====
* '''I have unexplainable GTA problems or crashes'''

Make sure your computer as well as your GTA install meet the [[Deathmatch_Client_Manual#System_requirements|minimum requirements]] and that you are not running in any 98/2000/XP/2003 compatibility modes.

Also try the solutions from these pages:
* http://www.gtaforums.com/index.php?showtopic=273549&view=findpost&p=4537502
* http://pullmonkey.com/2007/4/30/how-i-got-gta-san-andreas-to-work-with-a-crappy-os-vista

== Server ==

=== General ===
==== Fatal error 3 ====
* '''I'm getting ''Fatal Error 3'' whenever I connect to my server'''

This error happens when the server you are trying to connect to is unable to provide you the required downloads, because it does not have http downloading enabled. Be sure to set the '''httpdownload''' configuration tag in your configuration to '''1'''.
==== Download error 9: Error downloading requested files ====
* '''I'm getting ''Download Error 9: Error downloading requested files'' whenever I connect to my server'''

This error happens when the server you are trying to connect to is unable to provide you with a valid link. This results in a 404 (Not found) HTTP error and an error at your end.

* If you are running the built-in server ('''httpserver''' is set to '''1''' and '''httpdownloadurl''' is empty), make sure that your HTTP server is accessible (you can try to access it by using a browser) for everyone.

* If you have configured an external web server ('''httpdownloadurl''' is set to your custom URL), make sure that your HTTP is accessible and make sure you have read the [[Deathmatch_Server_Manual#Configuring_an_external_web_server | Configuring an external web server]] guide.

==== Crashing when banning a player ====
The banPlayer script function will crash. Avoid using it. You can modify the xml file manually instead. This will be fixed in the next release.

{{Fixed|v1.0-dp2}}

=== Windows-related ===
No known reported issues.

=== Linux-related ===
==== libcurl.so.<version>: cannot open shared object file ====
* '''My dedicated server gives a ''libcurl.so.<version>: cannot open shared object file'' error on startup''' (where <version> is to be replaced with 3 or 4)

This means one of the dynamic dependencies (libcurl, CURL) needed in order to run the server cannot be found on your server.

<ul>
<li>If your server reports that it cannot find '''libcurl.so.4''', it's most likely due to an old version of libcurl that is installed on your system. You can either choose to upgrade libcurl to the latest version (check out your distribution package manager, or download/compile/install from the [http://curl.haxx.se/ CURL website]), or you can choose to pick another Linux build (e.g. the Generic Linux build, which contains a statically linked version of the library).
</li>

<li>If your server reports that it cannot find '''libcurl.so.3''', libcurl is either not installed on your system, you are running an outdated version or you are running a newer version of libcurl (and downloaded a build that relied on the old version).
<ul>
<li>If '''libcurl.so.4''' is present on your system (e.g. in /usr/lib), it means you have a newer version than the one required and you can most likely solve the problem by creating a symbolic to libcurl.so.3:
<pre>$ ln -s /usr/lib/libcurl.so.4 /usr/lib/libcurl.so.3</pre>
</li>
<li>If '''libcurl.so.2''' is present on your system (e.g. in /usr/lib), it means you have an older version and you can solve the problem by installing the most recent version of libcurl. This should be done through your package manager (check your distribution's documentation), or no such manager is present, by manually compiling and installing the latest CURL source from the [http://curl.haxx.se/ CURL website]).
</li>
<li>If libcurl is not present on your system, see how to install libcurl by reading the instructions above.</li>
</ul>
</li>
</ul>

{{Fixed|v1.0-dp2}}

==== ERROR: Couldn't find meta.xml ====
* '''My dedicated server console reports one of the following errors''':
* ERROR: Couldn't find meta.xml file for resource '.'
* ERROR: Couldn't find meta.xml file for resource '..'

This is a minor (visual) issue with the directory handling code in the Linux server. The server tries to read the . and .. operators that are available in every directory, resulting in an error. You can safely ignore this issue.

{{Fixed|v1.0-dp2}}

==== ERROR: Could not parse 'settings.xml' file ====
* ''''My dedicated server reports the ''ERROR: Could not parse 'settings.xml' file (Invalid file). Starting with an empty settings registry.'' error.

This is because a default settings.xml file isn't shipped with the server. After this error is encountered, the server should be automatically created by the server. To be sure that the creation was successful, and that you have appropriate rights to the file, you can execute the following commands:

<pre>/mtasa_server_directory/mods/deathmatch $ touch settings.xml
/mtasa_server_directory/mods/deathmatch $ chmod 755 settings.xml</pre>

Please note that the word '''settings''' here doesn't reflect your server configuration, but rather the scriptable [[Settings system]].

{{Fixed|v1.0-dp2}}