Released December 20, 2007.
TransGaming is pleased to announce the release of Cedega 6.0.5, codenamed Ektorp.
- Red Hat and Fedora Core: python >= 2.3, pygtk2 >= 2.6, gtk2 >= 2.6, wget, dbus-python
- SuSE: python >= 2.3, python-gtk >= 2.6, gtk2 >= 2.6, wget, dbus-1-python
- Mandriva: python >= 2.3, pygtk2.0 >= 2.6, pygtk2.0-libglade, gtk2 >= 2.6, wget, dbus-python
- Debian-Based Systems (Ubuntu, Lindows, Knoppix): libc6 >= 2.2.4-4, xlibmesa3 or libgl1, python >= 2.3, python-gtk2 >= 2.6, python-glade2, wget (python 2.4 and python2.4-dbus strongly recommended)
- Other (Gentoo, Slackware): x11, python >= 2.3, gtk2 >= 2.6, glade2, python gtk2 bindings and python dbus bindings, wget (exact package names vary by distro).
Recommended minimum hardware is
Due to superior Linux driver support, TransGaming recommends using a NVIDIA GeForce-class video card while gaming through Cedega. Pixel shaders are only available on NVIDIA FX class cards and above.
Cedega also works with ATI Radeon 8500 or better cards using the proprietary drivers available from ATI. We recommend using an ATI Radeon 9500 or higher card at a bare minimum, as ATI is no longer providing bugfixes for older cards. Please note that the ATI drivers may have bugs or be missing features in some core functionality, and may cause errors, graphical anomalies, or the game to simply not work with Cedega.
Other on-board video cards such as Intel and S3 video cards will run some games through Cedega, but many games will not run or may crash, due to bugs or missing functionality in the drivers.
Since Cedega is intended to run standard 32-bit Windows games, it is by nature a 32-bit application. When running Cedega on a 64-bit Linux system, an appropriate 32-bit compatibility environment must be available. Please see the documentation for your Linux distribution to learn more about running 32-bit applications on your system.
Additionally the following items may be of note:
There is ptrace bug in the Linux 2.6.9 and 2.6.10 kernels that may cause copy protection to fail. This bug has been resolved in the 2.6.11 kernel. TransGaming recommends avoiding the use of 2.6.9 and 2.6.10 kernels.
Exec-shield's non-executable stack feature is disabled for legacy
applications on most distributions. This is preferable, as Cedega (like
many other pieces of software) is treated as a legacy application with
respect to this feature, yet needs an executable stack. However, in
both Fedora Core 4 and Fedora Core 5 the non-executable stack feature is
enabled for legacy applications, and this can cause issues when running
Cedega. Users may experience a wide range of behaviour from texture and
geometry corruption to games failing to execute entirely.
The release of kernels 2111_FC4 and 2122_FC5 has resolved this issue and
TransGaming recommends all users upgrade to these kernels when using
Fedora Core. To test for this issue, run in a terminal window:
$ cat /proc/sys/kernel/exec-shield
Values of 2, 3, 6, 7, 10 or 11 will cause issues in legacy applications
including Cedega.
The 'targeted' profile for SELinux in Fedora Core 5, the default on this
distribution, has been modified so that it now targets user mode
applications. You must set SELinux to permissive mode by opening a
shell as root and typing:
$ setenforce 0
As of Cedega 4.3, there are no longer any compatability issues between prelink, the new VA layout and Cedega. These features can be left enabled and will work seamlessly with Cedega.
The version of mount that comes with some distributions now run with the noexec option unless otherwise specified. Running games from a partition mounted with noexec can cause an error = 21 message. This error can also be caused by trying to run games from FAT32 or NTFS partitions.
To fix this issue, edit the /etc/fstab and modify the partition line by removing the noexec option and adding the exec switch to the mount options. It is highly recommended that you do not run games from Windows partitions (such as FAT32 and NTFS).
For example:
change
/dev/hda1 / ext3 errors=remount-ro,no-exec,defaults 0 1
to
/dev/hda1 / ext3 errors=remount-ro,exec,defaults 0 1
If neither exec nor no-exec appears in the line it is recommended that you add exec to ensure that the partition can be used by Cedega.
To remount the partition run:
mount -o remount /
Some Linux distributions, including some older SuSE distributions and Mandriva 2007, may mount the Mac portion of a hybrid disc instead of the Windows portion, preventing Cedega from accessing the files necessary to complete a proper install under Cedega. Titles which may exhibit this automount problem include, but are not limited to; WarCraft III, Diablo II, World of Warcraft, and any of their expansions, as well as any other title which uses a hybrid Mac/Windows disc. We recommend that SuSE users upgrade to SuSE 10.2, which does not have this issue.
To work around the issue, unmount the disc, and manually remount the disc from the commandline specifying the 'iso9660' filesystem type. For example:
mount -t iso9660 /dev/hdc1
When compiling custom kernels there are some options that can cause compatibility problems with Cedega and Wine-based products.
The Memory Split option under CPU type and features must be left at the default 3/1 setting. Changing this option will result in incompatibility with Cedega, WineHQ, CrossOver and other applications.
Copy protection for a number of titles will not work if the Joliette File Extension option is not enabled.
There is currently an issue with Cedega and the NVIDIA 100.xx video drivers which results in upside-down
rendering when FBO and in-game anti-aliasing are enabled. To work around this issue, either disable
anti-aliasing or use an earlier driver version. We are working on a solution to the problem and it
will be made available in an upcoming release.
With the new NVIDIA drivers, ARGB GLX Visuals are enabled by default on sufficiently new X servers. These are
not compatible with Cedega and may result in an X error. You can work around the issue by running:
$ XLIB_SKIP_ARGB_VISUALS=1 cedega
or by setting AddARGBGLXVisuals to False in your xorg.conf file.
Mandriva 2007 does not allow regular users access to the X log file, which prevents the Cedega UI from autodetecting the amount of video ram your video card has. Many games have been known to fail if this value is incorrect. We recommend entering your Video Ram value manually in the System Hardware/Information dialog as a workaround.
TransGaming has seen some game-stopping instability with ATI cards using FireGL and/or DRI drivers running Cedega. Some games may not run at all, while others may require manual tweaks or experience graphical issues in-game.
Games which do not run at all include: Battlefield 2, Dungeon Siege II, Far Cry, Madden NFL 2005, Madden NFL 2006, Need for Speed Underground and Sacrifice.
The games Hitman Contracts, Battlefield 1942 and Battlefield Vietnam exhibit graphical corruption caused by a known issue in ARB_vertex_program.
TransGaming is continuing to work with ATI to improve support and we welcome all reports and your votes in the polls.
The OpenGL VBO and VAR extensions are used to speed up geometry data transfer to and from a video card. On NVIDIA cards, the VAR extension is preferred, though VBO is available. On ATI cards with the FireGL drivers, only VBO is available. While VBO should work on ATI cards for most games, there are still a number of titles which may exhibit problems, both in terms of graphical corruption and performance. For these titles you may simply disable the VBO option.
A number of users with ATI video cards on 64 bit machines do not receive accelerated 3D graphics with Cedega or will only receive a grey screen when starting some games (such as Half-Life 2/Counter Strike: Source). This issue is caused by an error in the ATI driver setup in the 32-bit compatibility environment.
To get working 3D acceleration with Cedega you need to setup the correct path for the LIBGL_DRIVERS_PATH environment variable. To do so run in a terminal:
$ export LIBGL_DRIVERS_PATH=/usr/lib32/modules/dri/:/usr/lib64/modules/dri
then launch Cedega from that terminal. Check your distribution documentation for the best method to set this permanently.
There is currently an incompatibility between the way DRI requires the OpenGL library to be loaded, and the how Cedega loads the OpenGL library, resulting in a fallback to indirect rendering. In order to work around this incompatibility it is necessary to preload the OpenGL library when using Cedega. This can be done by editing
~/.cedega/.winex_ver/<version>/bin/winex3
and adding the following line to it:
export LD_PRELOAD=/usr/lib/libGL.so
(Adapt this line as appropriate for where your actual libGL.so file is located.)
With the introduction of the 2.6 Linux kernel, drastic changes have been made in the behavior of process scheduling. Some distributions have taken advantage of this and optimized their schedulers to run certain applications better than others. Unfortunately, this means that some 2.6-based kernels may starve more 'aggressive' applications like Cedega at inopportune times, leading to stuttering movies, jerky framerate and/or random freezes.
Starting with Cedega 5.0, we include a user-mode scheduler to alleviate most of these problems by performing rescheduling of game processes manually. For most games, this will give users the performance they have come to expect with previous Linux kernels. Unfortunately, some games are not yet fully supported by this method. If you experience unusual behavior in any application, check the following section to see if the game has known conflicts with the Cedega scheduler. Additionally, some installers and patchers may run slower with the scheduler enabled. You can also disable the internal scheduler in the configuration profile for the title in question.
Also of note for those who have a multiprocessor or multicore system, the scheduler currently supports scheduling of only one CPU, so if you wish to use more than one core with Cedega, you will need to disable the scheduler completely. This is a known limitation which may be addressed in a future release.
When used with the Mozilla ActiveX control, Cedega can display HTML content in some on-line games. Some games use HTML content to display license agreements when starting the title. Please ensure you have correctly installed and activated the Mozilla control using the Cedega GUI Setup Wizard in order to view this content.
Regardless of whether or not the license agreements are displayed by these games, TransGaming Technologies Inc. will not be held liable for any failure or breach on your part of any 3rd party license agreement.
You are solely responsible for ensuring that you have read and will abide by any third party license agreements, regardless of the ability of the Cedega software to display such license agreements on your system.
- General Notes
- General Notes
- Play Notes
- General Notes
- Installation Notes
- Play Notes
- General Notes
- Play Notes
- General Notes
- Installation Notes
- Play Notes
- General Notes
- Only low detail mode is recommended, though users with high-end graphics cards may be able to use higher settings.
- You must have X set to 24 bit depth to play Battlefield 2142.
- ATI cards are not supported for this title. While the game should run, there are a number of severe graphical anamolies.
- Multiplayer play may not work on Punkbuster enabled servers. Our current efforts to increase support for Punkbuster means that users may be able to join some Punkbuster enabled servers. However, since Punkbuster is not fully supported this may result in warnings, being kicked from the server, or even local or GLOBAL BANS.
- Users may experience the occasional error message when quitting Battlefield 2142 complaining that the game is unable to unload a DLL. You may ignore this error or use the Stop button in Cedega to bypass this error.
- Installation Notes
- Play Notes
- General Notes
- Installation Notes
- Play Notes
- General Notes
- Play Notes
- General Notes
- Play Notes
- Installation Notes
[SOFTWARE\\Activision\\Call of Duty]
"InstallDrive"="D:"
"InstallPath"="C:\\Program Files\\Call Of Duty"
"Language"="1"
"Version"="1.1"
- Play Notes
- General Notes
- Installation Notes
- Play Notes
- General Notes
- Installation Notes
- General Notes
- Play Notes
- General Notes
- Installation Notes
- Play Notes
- General Notes
- Play Notes
- This title must be run in Windows 2000 compatibility mode.
- General Notes
- Installation Notes
- Play Notes
- Play Notes
- General Notes
- Installation Notes
- Play Notes
- General Notes
- Installation Notes
- Play Notes
- General Notes
- Installation Notes
- Play Notes
- This title should be run in Windows 2000 compatibility mode.
- General Notes
- Play Notes
- General Notes
- Play Notes
- Installation Notes
- Play Notes
- General Notes
- Play Notes
- General Notes
- Movies play with incorrect aspect ratio, and do not cover the full screen when non-power of two textures (NPOT) are unavailable.
- Attempting to skip the intro movies may cause a crash.
- Main menu background movie can be slow on some systems; we suggest disabling it in options.
- When Pixel Shaders are disabled, only the low detail level is supported.
- When Pixel Shaders are enabled, all detail settings are supported, except for Special Effects Quality which must be set to Low. In patch v1.3 and later, due to changes in the game's engine, only the low detail level is supported.
- Having the Texture Quality set to Medium may cause a crash on startup on some machines. Any other value for this setting should work.
- Fog may not be supported in certain detail settings (e.g. underwater fog, with pixel shaders enabled on low detail).
- v1.1 patch is unsupported due to installer issues; however, the v1.3 patch does install.
- When using the FarCryConfigurator with Cedega on the command line, make sure to run it with the --use-dos-cwd option pointing at your main Far Cry directory; otherwise, your config file will be created in the current directory and you'll need to copy it to your main Far Cry directory.
- This title may not start consistently with the v1.3 patch (and later). If Far Cry crashes in the middle of copy protection leaving processes running, don't despair! Try running Far Cry again, and then selecting Stop Running Games from within the Cedega GUI.
- Multiplayer hosting does not work.
- v1.3 patch may cause stripes/stretching on some textures.
- Some users may experience strange lighting or color changes during gameplay. Upgrading your video drivers may solve this issue.
- This title may not work on some distros. If you experience difficulties, please try a stock kernel.
- This game can be run with OpenGL rendering for improved performance. To do this, edit the system.cfg file in the Far Cry directory and use these options:
r_Driver = "OpenGL"
r_TexResolution = "0"
i_direct_input = "0"
Ensure you are using Cedega 5.0 or newer.
- Installation Notes
- Play Notes
- General Notes
- General Notes
- Play Notes
- General Notes
- Play Notes
- ATI users may experience incorrect textures or other graphical corruption while playing this title.
- If there are problems starting the game, deleting the file located in 'My Documents/GTA Vice City User Files/gta_vc.set' may help.
- Play Notes
- General Notes
- Play Notes
- General Notes
- Installation Notes
- Play Notes
- General Notes
- Play Notes
- General Notes
- Installation Notes
- Play Notes
- General Notes
- Play Notes
- General Notes
- Installation Notes
- This game must be installed in Windows 2000 compatibility mode.
- Play Notes
- This game must be run in Windows 2000 compatibility mode.
- Using Pixel Shaders 1.4 and Vertex Shaders/1.1 shaders is recommended. Using 2.0 shaders causes lighting issues on the players.
- ATI users should disable ARB_VBO for performance gains.
- ATI users should disable FBO for this game to avoid graphical anomalies.
- General Notes
- Installation Notes
- Play Notes
- Play Notes
- ATI users should be sure to disable ARB_VBO for this title
- General Notes
- Play Notes
- General Notes
- Play Notes
- General Notes
- Some users may experience severe sound issues with the Spearhead and Breakthrough expansion packs.
- Installation Notes
- Play Notes
- General Notes
- It is highly recommended that the 1.3 (or later) game patch is installed for best performance.
- Installation Notes
- Play Notes
- General Notes
- Installation Notes
- Users MUST choose to accept the installation of DirectX 9.0C to play this game. Please carefully read the associated EULA and only accept if you meet all DirectX license requirements.
- The installer needs to be run twice using the same Game Folder. The first time will install DirectX 9, and then prompt for a Windows reboot. It is safe to say Yes to this, it will not actually reboot your system. Just rerun the installer and be sure to select the same Game Folder in the Install dialog. This will install the actual game itself.
- The installer and patchers must be run in Windows XP compatibility mode.
- Play Notes
- General Notes
- Installation Notes
- Play Notes
- General Notes
- The auto patcher for early versions of this title will not work and you will have to manually download and install the lastest patch.
- Play Notes
- Play Notes
- General Notes
- General Notes
- Installation Notes
- The installer must be run in Windows 98 compatibility mode.
- Play Notes
- General Notes
- Installation Notes
- Play Notes
- General Notes
- General Notes
- Installation Notes
- The Run Directory option must be selected to install this game.
- Play Notes
- General Notes
- Play Notes
- General Notes
- General Notes
- Play Notes
- General Notes
- The mouse will not be usable unless you disable Hardware Mouse from the launcher configure screen.
- Installation Notes
- General Notes
- *** Steam ***
- If the vertical scrollbar is missing from the Steam Store window you can still scroll the page by using the arrow keys or the Page Up and Page Down keys.
- When using older versions of X-Windows, Steam may crash after login on some systems if there are too many .gcf files downloaded in the SteamApps directory. If this happens simply move aside some of the gcf files that you aren't currently using.
- When starting Source-engine based games there may be a message about detecting an unknown video card. Please ignore this and DO NOT select the option to upload the details to Valve.
- Occasionally, on startup of a Source-engine based game, you may see a message that the Steam Registry is in use by another process. To avoid this message, you should exit Steam, wait a few minutes, and then retry. Running a non-Source-Engine based title from Steam, then exiting and retrying the Source-Engine based title may also help.
- Steam may claim that the Steam Service is not running. If so do a search for Steam.dll. If it's anywhere but the steam directory, delete it. If it doesn't work, try mv ClientRegistry.blob ClientRegistry.blob.old
- Reinstalling Steam to a new Game Folder and copying over your game data files works around many Steam issues.
- Source Engine games do not auto-detect to DX9 level graphics capabilities automatically, however the game can be manually set to run in DX9 mode by passing '-dxlevel 90' as a launch parameter to the game, or by typing 'mat_dxlevel 90' on the in-game console.
- *** HALFLIFE 2: ***
- When installing Half-Life 2 from a DVD it may complain about missing instmsi.exe. If this error occurs, first install instmsi.exe from the Half-Life 2 DVD and then re-run the Half-Life 2 installer.
- For best performance make sure your system is configured to use at least 64MB of AGP Memory. See the section on AGP Memory for more details.
- The sound card must be available in Cedega to play this game.
- The fonts may appear distorted. Try running at a resolution of 1024x768 or higher to correct this issue. If you are licensed to use the Lucidia Console font, manually installing it will provide a more legible console font.
- Fonts are rendered more correctly if when running in win98 mode (instead of win2k or winxp).
- The first time the game is run, loading may take a long time.
- The intro movie when the GMan is talking may not show up correctly on some systems. Try passing in '-dxlevel 70' in the game options through the Steam game browser in order to see the movie in all cases.
- The developer/publisher movies are not played on startup.
- Some users may experience stutters in sound. If this occurs be sure that the Sound System is set to the correct setting for your sound card. Users may also wish to try decreasing the priority of the wineserver in the Overrides.
- The game may crash on exit.
- Some objects may become incorrectly lit during gameplay.
- Enabling Pixel Shaders 1.4 or higher (which also allows for pretty water) may cause drastic slowdowns for users with NVIDIA 5xxx class cards. We recommend using NVIDIA 6xxx class cards with Pixel Shaders 1.4 or above.
- Sound may not work for some onboard soundcards for this game.
- *** Counterstrike Source: ***
- To enable voice-chat, OSS users must enable the FullDuplex option and disable the UseMMap option.
- For best performance, make sure your system is configured to use at least 64MB of AGP Memory. See the section on AGP Memory for more details.
- The blocks in the video stress test will render with full effects only with Pixel Shader 1.4 (or higher) mode enabled.
- Enabling Pixel Shaders 1.4 or higher (which also allows for pretty water) may cause drastic slowdowns for users with NVIDIA 5xxx class cards. We recommend using NVIDIA 6xxx class cards with Pixel Shaders 1.4 or above.
- The fonts may appear distorted. Try running at a resolution of 1024x768 or higher to correct this issue.
- If you are licensed to use the Lucidia Console font, manually installing it will provide a more legible console font.
- Fonts are rendered more correctly if when running in win98 mode (instead of win2k or winxp).
- The sound card must be available in Cedega to play this game.
- Installation Notes
- Play Notes
- Steam startup and game patching are quicker if the scheduler is disabled. This has been done by default when using the correct GDDB profile. If you experience problems during gameplay try re-enabling the Scheduler. To do so right click the Steam shortcut, select Edit Settings for this Shortcut and set the scheduler to Default.
- Some users may experience Steam startup failures. Use the STOP button in the Cedega UI and restart Steam
- Quitting Steam may leave some errant Cedega processes open. We recommend users click the STOP button in the Cedega UI after quitting Steam.
- Some Steam games (such as Half-Life 2) may hang while updating. Stop or pause the update and restart it to complete the process.
- Steam may hang while updating. To recover from this stop or cancel the current update, use the STOP button in the Cedega UI and then restart Steam.
- ATI users should disable Pixel Shaders for Source games.
- General Notes
- *** Steam Notes ***
- If the vertical scrollbar is missing from the Steam Store window you can still scroll the page by using the arrow keys or the Page Up and Page Down keys.
- When using older versions of X-Windows, Steam may crash after login on some systems if there are too many .gcf files downloaded in the SteamApps directory. If this happens simply move aside some of the gcf files that you aren't currently using.
- When starting Source-engine based games there may be a message about detecting an unknown video card. Please ignore this and DO NOT select the option to upload the details to Valve.
- Occasionally, on startup of a Source-engine based game, you may see a message that the Steam Registry is in use by another process. To avoid this message, you should exit Steam, wait a few minutes, and then retry. Running a non-Source-Engine based title from Steam, then exiting and retrying the Source-Engine based title may also help.
- Steam may claim that the Steam Service is not running. If so do a search for Steam.dll. If it's anywhere but the steam directory, delete it. If it doesn't work, try mv ClientRegistry.blob ClientRegistry.blob.old
- Reinstalling Steam to a new Game Folder and copying over your game data files works around many Steam issues.
- *** Counter Strike: Condition Zero Notes ***
- Pushing the tab key may crash the game in single player mode.
- Installation Notes
- As of April 2007, the current Steam installer does not work because it is MSI-based. Please download and install SteamInstall.exe instead. You can find SteamInstall.exe in the forums at www.cedega.com/forums under Half-Life 2 & Valve Source Games. http://downloads.transgaming.com/files/SteamInstall.exe
- Play Notes
- Steam startup and game patching are quicker if the scheduler is disabled. This has been done by default when using the correct GDDB profile. If you experience problems during gameplay try re-enabling the Scheduler. To do so right click the Steam shortcut, select Edit Settings for this Shortcut and set the scheduler to Default.
- Some users may experience Steam startup failures. Use the STOP button in the Cedega UI and restart Steam
- Quitting Steam may leave some errant Cedega processes open. We recommend users click the STOP button in the Cedega UI after quitting Steam.
- Some Steam games (such as Half-Life 2) may hang while updating. Stop or pause the update and restart it to complete the process.
- Steam may hang while updating. To recover from this stop or cancel the current update, use the STOP button in the Cedega UI and then restart Steam.
- General Notes
- Play Notes
- Installation Notes
- Play Notes
- ATI users should disable ARB_VBO for this game for performance improvements.
- General Notes
- Installation Notes
- Play Notes
- General Notes
- Some third party addons will cause slowdowns and crashes. If you experience poor performance or crashes please remove any installed addons.
- As of April 19, 2005, the patcher for World of WarCraft requires that the Mozilla ActiveX Control be installed.
- This game may crash on exit.
- Installation Notes
- Play Notes
Please check the Cedega HOWTO for other common problems, installation procedures
and additional information. The Cedega HOWTO is available from the TransGaming
downloads area: http://www.transgaming.com/downloads.php