← Back to the stories
Games Linux

GTA: San Andreas Original Disc on Linux: Video and Mouse Fixes

My original disc copy of GTA: San Andreas needed two fixes on Linux: one for video playback and one for the camera spinning. My fix at the time involved GStreamer dependencies and a different game executable.

Updated: 25 October 2026. This guide covers the classic Windows PC disc version through Wine, including a Wine entry managed in Lutris. The Definitive Edition uses a different game build and different fixes.

Check the executable before changing files

  1. Keep a backup of the installed game folder and your saves before adding patches. Keep the original executable and any DLLs you replace.
  2. Check the game version against the patch’s supported-build list. “Disc version” can cover an original release, a patched installation or a later reissue.
  3. Use the same Wine prefix and selected Wine runner for the installer, game and configuration tools. The prefix is the Windows environment containing drive_c; the game folder is the directory containing the executable.
  4. In Lutris, point the game entry at the installed game executable and use its directory as the working directory. Keep disc access configured in that prefix if your edition requests the disc.

The ReadMe included with SilentPatchSA Build 34.1 lists GTA SA 1.0, all versions, plus partial support for newsteam r2 and the Rockstar Games Launcher release. It does not list retail 1.01 or 2.0. Establish compatibility with those builds before following the patch steps below.

A helicopter flies above a suspension bridge at sunset in the classic GTA: San Andreas.
The classic PC game. Publisher screenshot from the original Steam listing; image: Rockstar Games. Source.

The 2019 Rockstar Games Launcher workaround

The GamingPH article from 2019 describes the Rockstar Games Launcher version. Its workaround adds a Steam gta-sa.exe and launches that file directly. It specifically tells readers to keep the launcher’s original gta_sa.exe.

Those filenames and instructions belong to that workaround. For a retail installation, start with the executable installed from your disc and choose patches that support its version.

Try SilentPatch on a supported build

SilentPatchSA is still maintained. The current release checked on 25 October 2026 is Build 34.1, released on 15 August 2026. Its documented mouse fixes include the mouse locking after leaving menus, unequal horizontal and vertical sensitivity, and in-car camera behaviour.

For the installation below, use the 32-bit dinput8 version of Ultimate ASI Loader. The classic game is a 32-bit application, so select the loader’s Win32 build even on a 64-bit Linux system.

  1. Download SilentPatchSA.zip from the official SilentPatch release. Extract SilentPatchSA.asi and SilentPatchSA.ini beside the game executable, and read the supplied ReadMe and configuration file.
  2. If you already have a working ASI loader, check its instructions and use that setup. Otherwise, get dinput8-Win32.zip from the Win32 links in Ultimate ASI Loader’s README and place its dinput8.dll beside the executable. Keep a backup if a file with that name is already present.
  3. Check that the DLL and patch files are in the actual executable directory, rather than an extra folder created when extracting the archives.
  4. Open Wine configuration for this game’s prefix. Under Libraries, add dinput8, edit it and select Native, then Builtin. Save the change.

Silent’s Wine setup instructions describe this override. “Native” tells Wine to load the Windows DLL supplied by the loader. You can also set it through the game entry’s environment variables:

VariableValue
WINEDLLOVERRIDESdinput8=n,b

Use either the prefix’s library setting or the environment-variable method. If the entry already has DLL overrides, add this one while keeping the existing entries. This value is for a loader named dinput8.dll; another proxy filename needs its corresponding override.

Wine configuration with dinput8 entered in the New override for library field.
The dinput8 entry field in Wine configuration. Generic example from Silent’s setup instructions; add the entry and select Native, then Builtin. Source.

Check GStreamer when a movie will not play

The startup logo and title movies are separate from the game’s rendered cutscenes. The community’s reimplementation of the classic PC startup code shows the movie-player path, while its cutscene manager handles game objects and animations.

GStreamer matters when Wine’s media path cannot decode a movie. Check the launch log for a missing plugin or decoder. Wine’s GStreamer code reports the required plugin set and whether that process needs 32-bit or 64-bit plugins. Match that requirement to the selected Wine build and runtime.

For a host Wine installation that uses the distribution’s GStreamer libraries, the official Ubuntu/Debian instructions include these runtime plugin packages:

sudo apt update
sudo apt install gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad gstreamer1.0-plugins-ugly gstreamer1.0-libav

That command installs the default package architecture. If Wine asks for 32-bit plugins, check the matching 32-bit packages for your distribution. A successful 64-bit media-player test does not check a 32-bit Wine media process. Managed or sandboxed runners may use their own library paths; check that runner’s dependencies before changing host packages.

Test the mouse, movies and normal play

  1. Check picture and sound in the startup movies, then start or load a game.
  2. Select keyboard-and-mouse controls when testing mouse input. Disconnect an unused controller to check whether its input is contributing to the camera movement.
  3. Look around on foot, open and close the pause menu, and test the mouse again.
  4. Enter a vehicle and check camera movement there too. Test an ordinary in-game cutscene separately from the startup movies.
  5. Save, close the game and reload the save. Begin with the in-game Frame Limiter enabled and a small set of patches, so changes are easier to compare.

SilentPatch also corrects the original limiter’s timing, changing its effective target from 25 to 30 FPS. The selected limiter and other installed mods affect the test conditions.

Collect a log if the problem remains

For a Lutris entry, add the following values in its environment-variable settings, reproduce the problem and inspect the game’s launch log:

VariableValue
WINEDEBUG+loaddll,+quartz,+winegstreamer
GST_DEBUG2

The DLL trace helps check whether the chosen loader and SilentPatchSA.asi were loaded. The media messages help identify missing decoder components. Keep the executable version, selected Wine runner, installed patches and exact point of failure with the log, then remove the temporary debug variables.

Sources and original references

Leave a Reply

Your email address will not be published. Required fields are marked *