Archive for August, 2011

Linux – Quake gameplay (Multiplayer) mode

Posted in Gaming by Shafkat Shahzad, M.Sc - Senior Technical Content Manager on August 27th, 2011

The article will provide a user with information on Quake gameplay’s multiplayer mode. As we are aware that Quake has two fundamental modes of gameplay:

- Single player
- Multiplayer

We have already discussed Quake gameplay’s single player mode in the previous article. Now, Let’s have a look at Quake gameplay’s multiplayer mode. In multiplayer mode, players on several computers connect to a server (which may be a dedicated machine or on one of the player’s computers), where they can play against each other. Typically in multiplayer mode, when a player dies then he/she can loses any items that were collected. This means that a user has to start collecting the items again. Similarly, items that have been picked up previously respawn after some time, and may be picked up again.

The most popular multiplayer modes are all forms of deathmatch. Deathmatch modes typically consist of either free-for-all, one-on-one duels, or organized teamplay with two or more players per team (or clan). Teamplay is also frequently played with one or another mod. Typically, no monsters are normally present, as they serve no purpose other than to get in the way and give away the player.

The gameplay in Quake was considered unique for its time because of the different ways the player can maneuver through the game. An example will further explain this. bunny hopping or strafe jumping can be used to move faster than normal, while rocket jumping enables the player to reach otherwise-inaccessible areas (or just move faster), at the cost of some self-damage. The player can start and stop moving suddenly, jump unnaturally high, and change direction while moving through the air. Many of these non-realistic behaviors contribute to Quake’s appeal. The nature of the gameplay is often fast and frenzied, and has become considerably faster over the years as players mastered advanced movement techniques.

As Quake did not include any automap, it also requires considerable knowledge of the sometimes confusingly-contorted maps (made more complex by the frequent use of teleporters) as well as careful planning in order to collect needed items and conserve health and ammunition. Strategies include regularly picking up items to prevent one’s opponent from having access to them and controlling certain critical areas of each level. Duels often take place with opponents mostly out of sight of each other, jockeying for position and carefully stocking up on items, with sudden changes in speed of play when one player or the other gains an advantage. Sound also plays a central role in keeping track of other players and even items in the game, so many players use headphones to give the clearest sound and directionality. Teamplay adds even more tactical layers, with different ways to communicate and cooperate.

IF a user has read the article then he/she would have gained knowledge about the Quake gameplay’s multiplayer mode.

Bookmark Us
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google
  • MisterWong
  • Netvouz
  • Reddit
  • Slashdot
  • Spurl
  • StumbleUpon
  • Technorati
  • Wists

Linux - Quake gameplay (Single player mode)

Posted in Gaming by Shafkat Shahzad, M.Sc - Senior Technical Content Manager on August 20th, 2011

The article will provide a user with information on Linux Quake gameplay in a single player mode. The game engine was developed for Quake, the Quake engine, popularized several major advances in the 3D game genre.

Quake has two fundamental modes of gameplay:
- Single player
- Multiplayer

In this article, we will look at Quake gameplay’s single player mode. In single-player mode, players explore and navigate to the exit of each level, facing many challenging monsters and a few secret areas along the way. Usually there are buttons to press or keys to collect in order to open doors before the exit can be reached. Once reaching the exit, the game takes the player to the next level.
Before the start level, there is a set of three pathways with easy, medium, and hard skill levels; in order to reach the Nightmare skill level (described in the game manual as so bad that it was hidden, so people won’t wander in by accident), the player must drop through the water before the Episode 4 entrance and jump into a secret passage.

Quake’s single-player campaign is organized into four individual episodes of about eight levels each (each including a secret level, one of which is a “low gravity” level Ziggurat Vertigo in Episode 1, Dimension of the Doomed that challenges the player’s abilities in a different way). As items are collected, they are carried to the next level, each usually more challenging than the last.

If the player dies, he must restart at the beginning of the level. However, games may be saved at any time. Upon completing each episode, the player is returned to the hub Start level, where he can then enter the next episode. Each episode starts the player from scratch, without any previously collected items. The ultimate objective at the end of an episode is to recover a magic rune.

If a user has read the article then he/she would have learnt about Linux Quake gameplay in a single mode.

Bookmark Us
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google
  • MisterWong
  • Netvouz
  • Reddit
  • Slashdot
  • Spurl
  • StumbleUpon
  • Technorati
  • Wists

Linux - SerialICE

Posted in Software by Shafkat Shahzad, M.Sc - Senior Technical Content Manager on August 13th, 2011

The article will provide a user with information on SerialICE. SerialICE is a QEMU-based firmware debugging tool running system firmware inside of QEMU while accessing real hardware through a serial connection to a host system. This can be used as a cheap replacement for hardware ICEs.

Please note that following information provides a user with the incomplete support for less frequently-used architectures:
• As of 2011 only supports the traditional BIOS boot model for the guest OSes, no UEFI boot model support yet on x86-64 systems
• Few special device drivers (graphics, sound, IO) for guests are available, thus there is quite a large overhead for multimedia applications. For example, a Cirrus Logic graphics chip and various popular sound cards (ES1370, Sound Blaster 16, Gravis Ultrasound and AdLib) are emulated, but they do not take advantage of hardware acceleration on the host system. Recently a virtual video device compatible with the VMWare video driver has been added, however it does not support any scaled video or 3D features.
• QEMU only supports SDL or Cocoa libraries for video output, in addition to VNC for networked operation.
• Runs significantly more slowly than alternatives on PCs without hardware CPU virtualization, rendering virtualization of modern or visual systems sometimes unusably slow

If a user has read article then he/she would have learnt about SerialICE.

Bookmark Us
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google
  • MisterWong
  • Netvouz
  • Reddit
  • Slashdot
  • Spurl
  • StumbleUpon
  • Technorati
  • Wists

QEMU - virtualbox, XEN-HVM , Win4Lin and Win4Lin Pro Desktop

Posted in Software by Shafkat Shahzad, M.Sc - Senior Technical Content Manager on August 6th, 2011

The article will provide a user with information on virtualbox, XEN-HVM , Win4Lin and Win4Lin Pro Desktop

VirtualBox
VirtualBox uses some of QEMU’s virtual hardware devices and has a built-in dynamic recompiler that is based on QEMU. As with KQEMU, it runs nearly all guest code natively on the host via the VMM (Virtual Machine Manager), and uses the recompiler only for special situations as a fallback mechanism (this holds true for guest code that executes in real mode and some other rare scenarios at runtime). In addition, VirtualBox goes through a lot of code analysis and patching via a built-in disassembler to reduce usage of the recompiler to a minimum. VirtualBox is open-source software under the GPL, except for a number of enterprise features, and standard user features like USB 2.0.

Xen-HVM
The Xen virtual machine monitor can run in HVM (hardware virtual machine) mode, using Intel VT-x or AMD-V hardware x86 virtualization extensions. This means that instead of paravirtualized devices, a real set of virtual hardware is exposed to the domU to use real device drivers to talk to.
QEMU includes several components: CPU emulators, emulated devices, generic devices, machine descriptions, user interface, and a debugger. The emulated devices and generic devices in QEMU make up its device models for I/O virtualization.

Xen-HVM has device emulation based on the QEMU project to provide I/O virtualization to the VMs. Hardware is emulated via a patched QEMU device model (qemu-dm) daemon running as a backend in dom0. This means that the virtualized machines see as hardware: a PIIX3 IDE (with some rudimentary PIIX4 capabilities), Cirrus Logic or plain VGA emulated video, RTL8139 or NE2000 network emulation, PAE, and somewhat limited ACPI and APIC support and no SCSI emulation.

KVM
KVM (Kernel Virtual Machine) is a Linux kernel module that allows a user space program access to the hardware virtualization features of various processors, with which QEMU is able to offer virtualization for x86, PowerPC, and S/390 guests. When the target architecture is the same as the host architecture, QEMU can make use of KVM particular features, such as acceleration.

Win4Lin Pro Desktop
Win4Lin Pro Desktop is based on a tuned version of QEMU and KQEMU and it hosts NT-versions of Windows.

If a user has read this article then he/she would have learnt about virtualbox, XEN-HVM , Win4Lin and Win4Lin Pro Desktop.

Bookmark Us
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google
  • MisterWong
  • Netvouz
  • Reddit
  • Slashdot
  • Spurl
  • StumbleUpon
  • Technorati
  • Wists