Quake 2 linux ubuntu

В принципе это все, можно запускать игру. Для этого переходим в катлог, куда был распакован архив darkplacesengine20081004.zip и запускаем игру одним из следующих файлов:

Установка Quake 2

Из стабильно работающих на современных Linux-дистрибутивах портов можно выделить два — Yamagi Quake 2 и Quake 2 XP.

Первый из них почти ничем не отличается от ванильного Квейка 2 — добавлена поддержка архитектуры x86_64, переписана система сохранения игры. OpenGL-рендер использует SDL для инициализации и поддерживает большие разрешения экрана.

А вот Quake 2 XP — тут как раз много улучшений в графической части. Небольшая выдрежка из официального FAQ:

Quake2xp это графический порт оригинального Quake II использующий возможности новых видео карт nvidia и ati с поддержкой OpenGL 2.0, интегрированные решения на картах intel и sis НЕ ПОДДЕРЖИВАЮТСЯ! Порт может работать на последних интегрированных решениях от intel, но по причине общей тормознутости-обрезанности поддержка не осуществляется.

Готовых пакетовпод основные Linux-дистрибутивы (пока ещё) нет, так что придётся собирать из исходников — краткая инструкция по сборке Quake 2 XP — в этой сатье.

Установка Quake 3

Установка оригинального Quake 3 в Linux в целом не является сложной процедурой. Даже на современных 64-х разрядных дистрибутивах. Итак, приступим.

Для начала сходим на FTP-сервер id Software, и заберем оттуда последний апдейт Linux-версии Quake 3 Arena.

wget ftp://ftp.idsoftware.com/idstuff/quake3/linux/linuxq3apoint-1.32b-2.x86.ru

После этого присваиваем скачанному атрибут исполняемого а затем запускаем его::

chmod +x linuxq3apoint-1.32b-2.x86.run

./linuxq3apoint-1.32b-2.x86.run

Запускать необходимо с привелегиями суперпользовтеля (root), хотя если вы собираетесь ставить игру в свой домашний катлог — можно запустить и с правами обычного пользователя.

ВАЖНО: Для пользователей 64-х разрядных систем перед данным шагом необходимо установить 32-х разрядные библиотеки. Иначе установшик Quake 3 мягко вас пошлет, сославшись на некорректные версии библиотек. Так что ищите в репозитариях своего любимого дистрибутива пакет ia32-libs. И инталлятор Quake 3 запускайте командой:

linux32 ./linuxq3apoint-1.32b-2.x86.run

Программа установки задаст вам несколько вопросов насчет лицензии (принимаем ясное дело), пути установки игры, создания символической ссылки (оставляем по умолчанию /ur/local/bin/). Попросит также выбрать необходимые компоненты, вы можете не ставить файлы выделенного сервера, мода Team Arena, если не собираетесь их использовать.

После того как необходимые файлы будут скопированы, игра спросит — желаем ли мы запустить её. Откажемся, ведь у нас ещё нет самого главного файла — pak0.pk3. Копируем данный файл из того источника, в котором он у вас находится (папка на NTFS-разделе, оригинальный CD).Если игра была установлена не в домашний катлог, а к примеру в /usr/local/games/quake3/, то копирование выполняем от имени суперпользователя.

cp /path/to/filw/pak0.pk3 /usr/local/games/quake3/baseq3/pak0.pk3

И только пос этого запускаем игру, используя консольную команду quake3.

#1 | profile — 09 декабря 2008 в 12:39

альтернативой Darkplaces может стать квейкворлд версия
идете на сайт nquake.com и качаете линукс весию)

#2 | NIGHT [unreg] — 16 февраля 2009 в 01:40

Установил Q3 примерно так, как тут и описано.
Проблема, в игре нет звука.

#3 | Dvemer [unreg] — 10 мая 2009 в 14:48

to NIGNT
сначала надо получить доступ к /dev/dsp об этом написано в README-linux.txt (см в папке с игрой после установки)
если есть доступ к /dev/dsp , но нет звука, то надо сделать от рута что-то вроде echo «quake3.x86 0 0 direct» >/proc/asound/card0/pcm0p/oss

#4 | hatred [unreg] — 05 мая 2010 в 10:55

Если хав-ту все ещё поддерживается пара ремарков: группа icculus сделала и порт движка Q2: http://icculus.org/quake2/ не пробовал, хотя в AUR (пользовательский репозиторий дистрибутива ArchLinux, пользователем которого я являюсь) есть для него правила сборки. Сам же использовал порт проекта QuakeForge:
http://quakeforge.net, единственно, проект долгое время не подавал признаков жизни, сейчас вроде опять ожил, но актуальные версии только в исходниках и в svn, вчера буквально собрал компилятором gcc 4.5.0 для первого Quake. Для второго там подпроект Quake2Forge но в том же svn. Там же в SVN есть что-то для Quake3 (насколько мне известно, оно тоже теперь открыто). В свое время играл именно на этих движках: есть софтверный и OpenGL рендер, и различные варианты вывода графики: от fbdev (без иксов, хотя вроде только софтварный рендер будет) до sdl и glx.

#5 | DOOMer — 05 мая 2010 в 14:35

Про QuakeForge я слышал, и Q2Forge пытался собирать (через PKGBUILD bp того же AUR-а)/ Yj yjhvfkmyj jy e vtyz yt pfd`kcz? r cj;fktyb./

p.s А можешь написать небольшой обзор Quake Forge (не процесс сборки, а описание того что из себя порт представаляет)?

#6 | Квакер [unreg] — 15 сентября 2011 в 22:06

люди подскажите где скачать/как сделать самому читы для Quake 3 в Arch Linux (для Linux)

#7 | LumazeR [unreg] — 19 марта 2012 в 19:13

Спасибо за инструкцию

#8 | викор [unreg] — 06 января 2013 в 22:40

С празником! Подскожите как новечку как можно бес проблем устанавить игрушку

Источник

Quake 2 linux ubuntu

To install Quake 2 with a native build on Linux[Ubuntu], deployed via the Yamagi sourceport, go with the following — first, basing off the PC-CD game version:

open the Terminal [yep, ere we go], have the CD already mounted and execute:

where «» is a direct filestructure location of the mounted Quake 2 CD that you have. For example, in my case: /media/ms/QUAKE4_SPEC_ED/, which would make it look like that in the end — all in one line:

If you were installing anything with the Synaptic Package Manager beforehand, remember to have it closed when doing stuff in the Terminal.

Samewise logic goes with Steam or GoG data, where instead of giving a path to the CD, you give path to the proper local directory as a source.

The procedure will create a .DEB format installation file directly in the place where the Terminal has been opened, so mind for it to be easily accessible and writable location, such as your «Downloads» place. Furthermore, keep the file, as it is the only compact way of removing the game if you wanted to — open it and an option to uninstall will pop up.

In case you only wanted to build the installator without installing the game, right after the game-data-packager opening argument, change the first switch from -i to -n.

To run the game, check out the «Games» section in your desktop menu for the icon, alternatively, within the Terminal, simply execute quake2.

I post it here hoping for the advanced users to clear out misconceptions if possible.

In order to get classic Quake music and enhanced Quake 2 textures, proceed with the following; open the file browser and in the commandline of the file browser, execute:

If anything pops up, a directory containing Quake 2 files, we are good to go further:

Download THIS [drive.google.com] package, extract it anywhere suitable — preferably on the desktop or in «Downloads» section to avoid any mishaps — then open the Terminal in the same location where the extracted folders are — and execute the following in the Terminal:

Having done that, you are good to go. Credits to the contributors of MODdb.

Mind that in order to remove the game laterwise, you will need to manually erase these extra added folders, preferably before the uninstaller is initiated.

Analogous procedure goes for the expansion packs, albeit if you had it all installed on the specified source location, they probably already have been handled. Just in case, names for the installator, are: q2rogue and q2xatrix, to replace the thusfar given quake2. Adjust the path if necessary.

To play the expansion packs, search for the icons within «Games» section of your desktop menu, alternatively open the Terminal and execute:

where «» is either rogue for Ground Zero campaign or xatrix for Reckoning campaign.

If you have the expansion packs installed, mind the basic game .DEB installer, upon starting will tell that it has stopped providing some database. In this scenario, it is needed to run the other related .DEB files first, if the point is to commence with uninstallation.

For the multiplayer, it is operational. In order to get the multiplayer on, visit THIS [q2servers.com] website, write down IP addresses of the most populated servers, then open Quake 2, hit Multiplayer section, then Join network, afterwards go Address book and type in the addresses of interest respectively into distinct lines. Refresh the primary list to see server names and details. Remember to quit Quake 2 via the menu to save changes.

I have a question though, if I run the following in the Terminal:

If you would like to add the Zaero campaign or any other Yamagi compatible mod to your arsenal of missions, we need to refer back to the already mentioned location:

First, download the Zaero from MODdb portal, link HERE. There are also other mission packs available, you may want to look around.

Second, extract the downloaded files, so that they are contained within a folder named zaero.

Third, copy the folder to the specified location, which takes what follows. In definitive majority of cases, I imagine, you will notice the inability to simply drag and drop the folder where you need it. That is because Quake 2 data has been stored in a rigid protected zone on your system. It is possible to override this boundary, using the Terminal.

Therefore, open the Terminal in the same location where you can see the zaero folder — or navigate the Terminal spotpoint to where it is required — then execute:

The moved folder should appear next to our main baseq2 directory.

To have the mod go, execute in the Terminal, regardless of location:

Similar procedure applies to any mod. Name of the mod equals name of the folder it is in.

To remove a mod, open the Terminal where the designated folder is located, then execute:

Careful, the system will not ask twice and the removal is permanent. If you want the system to prompt you every step to be taken, change v to i, making the line as follows:

I was speculating on how to run Yamagi Quake2 on Linux without the game-data-packager runtime conditions, which is a secondary — if not a tertiary — program added to the deal. I have manually downloaded latest Yamagi build from the pkgs.org website — exact link HERE [pkgs.org] .

Having installed, I found the starter file in /usr/lib/yamagi-quake2/ location. Having put it at least once to run through the Terminal, a hidden .yq2 folder was created in my local user data. There, into the baseq2 pocket, I moved the proprietary .PAK files, along with any other assets that usually I find necessary or useful to running Quake2. The base game run fine. The problem appeared with expansion packs. The maps loaded fine, but they were empty — devoid of any enemies, regardless of difficulty level. Then it hit me — it must the case of .DLL files or their .SO equivalents on Linux.

These files must contain the pathways, enabling the game to read the exclusive, custom data for any expansion, I suppose. These files were missing. This could be fixed easy with downloading further two adequate packages from the same website, but other questions have arisen. Namely, the questions addressing the mods.

Having tried the downloadable Zaero mission pack, I realized that even though enemies are present, certain assets are missing, particularly those assets which are exclusive to the Zaero. This is when I understood that mods build under WindowsOS is not an easy case on Linux, at least in Quake2 engine. I am uncertain of how does it work for other classic games of iD Software, such as Doom or Quake, but I believe the ones that feature universal .PAK files and lack elements recognized as WindowsOS specific, will run properly.

Unfortunately, with Doom^3, this must be the reason why the mods were unrecognized the latest time I have tried to mount them, even though following analogous procedure gave positive results for Quake2, albeit only to a degree complete, as now I have learned.

I feel it is proper to point out that Yamagi has the most tidy package I have seen. It installs and uninstalls clean, leaves no mess.

But, regarding Doom^3, unnecessarily it is that fault with the mods is at the .DLL or .SO side. Actually, this is even unlikely, for the mod I tried to run does not feature such any, at least to my discernment. Perhaps I should also try out placing the Doom^3 mods in a temporary folder, such as I did this time running Quake2.

I thought, let me try again, still considering usage of any superfluous software an unnecessary balast. I have gone pkgs.org and downloaded the following packages for the base game — links HERE [pkgs.org] and HERE [pkgs.org] . Having installed these in only available order, I have further downloaded the packages for expansion packs — mind these are in .RPM format, but worry not, it is even better for the cause — links HERE [pkgs.org] and HERE [pkgs.org] . Mind there are various versions of packages. Scroll through distributions to possibly find the latest.

Having the base client installed — while the expansion packs not yet — I have gone to /usr/lib/yamagi-quake2/ in my file manager, opened the Terminal at that location and through the Terminal, told quake2 to go. It refused to, understandably, but something has already changed. Yamagi has created a hidden .yq2 folder in my user files area.

Having displayed hidden folders, I entered the .yq2 directory and pasted from my original Quake2 build all the .PAK files — as well as players folder and perhaps the maps.lst entity — placing them in respective baseq2 location within the .yq2. Afterwards, I have browsed both the installers for expansion packs — note I opened them as archives, not having the RPM package manager installed on my system. In there, I eventually browsed out the game.SO file and copied it respectively to a manually created, separate rogue folder or xatrix folder — depending on the expansion pack — placed parallelly to the original baseq2 directory.

Then I copied the .PAK file of each expansion pack from their original builds, placing it in adequate rogue or xatrix directory.

If you want to have the cinematics, mind also the videos folder each time.

Finally, I have downloaded and placed all contents of my homemade patch in the already mentioned baseq2 directory, for upgraded textures and original NIN music, which does wonders to experience of gameplay, especially in Quake 2. Link HERE [drive.google.com] .

The .SO files necessary for the expansion packs to run, were remotely found in external packages, easy to pick out and copy without further installs.

The last step is to create a launcher file, specifying /usr/lib/yamagi-quake2/quake2 as target command for the base game, while /usr/lib/yamagi-quake2/quake2 +set game xatrix or /usr/lib/yamagi-quake2/quake2 +set game rogue for the expansion pack.

What I wonder about is why the package maintainer cannot create an easy to go extract-copy-paste type of build, such as the one Quakespasm for the original Quake has.

Источник