Free fps epassport software for linux

The Castle is a first-person shooter (FPS) style game in a dark fantasy setting. Your main weapon is a sword, so the fight is mostly short-range. 3 main levels included, packed with creatures, items and sounds.

Also a bonus level, from a well-known 3D game, will be available to you from "New Game" menu once you finish the main game (you can also switch to this level from the debug menu, if youre impatient).

Dreams Eternal project is a story-driven FPS game that is set in the dream world.

Dreams Eternal is an FPS game that focuses on a strong story line and puzzle solving. It is set in the dream world.

The very short summary of the story is that a scientific experiment went wrong and everybody is stuck in the dream world.

You have to end this experiment by hopping from dream to dream. In every dream you have to find clues to try to find out how the experiment can be aborted.

Games::Irrlicht is a Perl module that use the Irrlicht 3D Engine in Perl.

SYNOPSIS

package MyGame;
use strict;

use base Games::Irrlicht;

use Games::Irrlicht::Constants; get EDT_SOFTWARE etc

# override methods:

The Why

When building a game or screensaver displaying some continously running animation, a couple of basics need to be done to get a smooth animation and to care of copying with varying speeds of the system. Ideally, the animation displayed should be always the same, no matter how fast the system is.

This not only includes different systems (a PS/2 for instance would be slower than a 3 Ghz PC system), but also changes in the speed of the system over time, for instance when a background process uses some CPU time or the complexity of the scene changes.

In many old (especial DOS) games, like the famous Wing Commander series, the animation would be drawn simple as fast as the system could, meaning that if you would try to play such a game on a modern machine it we end before you had the chance to click a button, simple because it wizzes a couple 10,000 frames per second past your screen.

While it is quite simple to restrict the maximum framerate possible, care must be taken to not just "burn" surplus CPU cycles. Instead the application should free the CPU whenever possible and give other applications/thread a chance to run. This is especially important for low-priority applications like screensavers.

Games::Irrlicht makes this possible for you without you needing to worry about how this is done. It will restrict the frame rate to a possible maximum and tries to achive the average framerate as close as possible to this maximum.

Games::Irrlicht also monitors the average framerate and gives you access to this value, so that you can, for instance, adjust the scene complexity based on the current framerate. You can access the current framerate, averaged over the last second (1000 ms) by calling current_fps.

Frame-rate Independend Clock

Now that our application is drawing frames (via the method draw_frame, which you should override in a subclass), we need a method to decouple the animation speed from the framerate.
If we would simple put put an animation step every frame, we would get some sort of Death of the Fast Machine" effect ala Wing Commander. E.g. if the system manages only 10 FPS, the animation would be slower than when we do 60 FPS.

To achive this, SDL::App::FPS features a clock, which runs independed of the current frame rate (and actually, independend of the systems clock, but more on this in the next section).
You can access it via a call to current_time, and it will return the ticks e.g. the number of milliseconds elapsed since the start of the application.

To effectively decouple animation speed from FPS, get at each frame the current time, then move all objects (or animation sequences) according to their speed and display them at the location that matches the time at the start of the frame. See examples/ for an example on how to do this.

Note that it is better to draw all objects according to the time at the start of the frame, and not according to the time when you draw a particular object. Or in other words, treat the time like it is standing still when drawing a complete frame. Thus each frame becomes a snapshot in time, and you dont get nasty sideeffects like one object beeing always "behind" the others just because it gets drawn earlier.

Time Warp

Now that we have a constant animation speed independend from framerate or system speed, lets have some fun.

Since all our animation steps are coupled to the current time, we can play tricks with the current time.

The function time_warp lets you access a time warp factor. The default is 1.0, but you can set it to any value you like. If you set it, for instance to 0.5, the time will pass only half as fast as it used to be. This means instant slow motion! And when you really based all your animation on the current time, as you should, then it will really slow down your entire game to a crawl.

Likewise a time warp of 2 lets the time pass twice as fast. There are virtually no restrictions to the time warp.

For instance, a time warp greater than one lets the player pass boring moments in a game, for instance when you need to wait for certain events in a strategy game, like your factory beeing completed.

Try to press the left (fast forward), right (slow motion) and middle (normal) mousebuttons in the example application and watch the effect.

If you are very bored, press the b key and see that even negative time warps are possible...

Ramping Time Warp

Now, setting the time war to factor of N is nice, but sometimes you want to make dramatic effects, like slowly freezing the time into ultra slow motion or speeding it up again.

For this, ramp_time_warp can be used. You give it a time warp factor you want to reach, and a time (based on real time, not the warped, but you can of course change this). Over the course of the time you specified, the time warp factor will be adapted until it reaches the new value. This means it is possible to slowly speeding up or down.

You can also check whether the time warp is constant or currently ramping by using time_is_ramping. When a ramp is in effect, call ramp_time_warp without arguments to get the current parameters. See below for details.

The example application uses the ramping effect instead instant time warp.

Event handlers

This section describes events as external events that typically happen due to user intervention.
Such events are keypresses, mouse movement, mouse button presses, or just the flipping of the power switch. Of course the last event cannot be handled in a sane way by our framework.

All the events are checked and handled by Games::Irrlicht automatically. The event QUIT (which denotes that the application should shut down) is also carried out automatically. If you want to do some tidying up when this happens, override the method quit_handler.

The event checking and handling is done at the start of each frame. This means no event will happen while you draw the current frame. Well, it will happen, but the action caused by that event will delayed until the next frame starts. This simplifies the frame drawing routine tremendously, since you know that your world will be static until the next frame.

zstar Networked 3D project is a free 3D networked application platform.
zstar (z*) Networked 3D project is an extensible, distributed system for 3D application and game development, consisting of an abstract game client (similar in concept to the one that xpilot uses) and a game server to which players connect to play games against other players or alone.
This framework should be suitable for FPS, VR, MUDs, or any application that requires 3D and networking.
Enhancements:
- Added java interfaces for camera/object messages
- Added walk system
- Added ac3d/sgi rgb loading
- Bug fixes
- Bug fixes on the chat
- Added texture cache and object cache.
- Mipmaps are now in for voodoo users.

FakeNES project is a portable, Open Source NES emulator which is written mostly in pure C, while using the Allegro library for multi-platform capabilities.
Currently supported systems are Windows 9x/2000/Me/XP, 32-bit DOS, Linux, FreeBSD, QNX, BeOS, and Mac OS X. However, it should run on any system that Allegro supports. This includes, but is not limited to: any version of Windows released after 1995, any 32-bit DOS compatible, and many POSIX compliant systems and UNIX clones such as Linux, FreeBSD, QNX, BeOS, and Mac OS X.
Configuration
FakeNES uses a standard configuration system similar to that used by many DOS, Windows, and UNIX applications.
Each item in the configuration file that is not surrounded by square brackets ([ and ]) defines an element or key.
The equal sign (=) is used to assign a value to that element.
Items which are surrounded by brackets are called headers. Headers define a section or group of related elements.
Comments are delimeted by the pound (#) sign and are ignored by the configuration file parser.
At this time, command-line options are not supported. However, you may supply the name of an NES ROM file that you would like to load on the command-line instead of loading it from the GUI.
Input engine
Currently, FakeNES supports two different keyboard layouts on a single keyboard, and up to two (2) joystick-like devices such as joypads. Each device may be assigned to any player, you can even assign a single device to multiple players.
All configuration of the controls is done in the configuration file, under the [input] header. You can assign a specific device to each player by modifying the player_#_device elements (replace # with the associated player number).
The following values are permitted:
0: No input (disables all input for this player).
1: Keyboard layout #1
2: Keyboard layout #2
There are two (2) configurable keyboard layouts which are present on the same keyboard, and may define overlapping keys without conflicts. Modifying the key1_scancodes and key2_scancodes elements allow you to customize the key mappings for each layout.
Note that due to portability reasons, FakeNES does not accept standard IBM scancodes. Instead, you need to supply a sequence of 8 integer scancodes as defined by the Allegro multimedia library.
The order in which the scancodes are applied is very important, and corresponds to the associated NES standard controller buttons: A, B, Select, Start, Up, Down, Left, and Right. If a complete sequence of 8 scancodes cannot be found, then the defaults will be used.
For layout #1, they are X, Z, Tab, and Enter, respectively, combined with the arrow keys for directional control.
3: Joystick device #1
4: Joystick device #2
Core timing
FakeNES contains an automatic speed throttling system. By modifying the frame_skip_min and frame_skip_max elements under the [timing] header in the configuration file, you can toggle speed cap and set the parameters for frame skipping.
Frame skipping is a technique that allows the emulation to run much faster, at the cost of fewer frames-per-second (FPS) being rendered, which results in more latent or choppy gameplay.
Speed capping effectively limits the maximum amount of FPS to be rendered to match that of the NES itself, which keeps the emulation from running too fast on fast processors or when frame skipping is being used.
frame_skip_min defines the least amount of frames to be skipped, setting it to zero (0) effectively disables minimum frame skipping and enables the speed capping mechanism.
frame_skip_max defines the highest allowable amount of frames to be skipped. FakeNES will never skip more frames than is defined by this element, even if full speed is not obtained.
Setting frame_skip_min and frame_skip_max to equal values effectively sets a fixed amount of frames to be skipped.
If the speed cap is enabled, you can use the fast forward key to surpass the speed cap and skip frame_skip_max frames as long as the key is being held down. By default, the fast forward key is defined as the tilde key above the Tab key on most keyboards.
The machine_type element allows you to select which standard is to be used by the speed throttling system and sound/graphics engines. Set it to zero (0) for NTSC or one (1) for PAL. There are not many PAL NES games, and many of them should run fine in NTSC mode. Only modify this element if you have problems.
Enhancements:
- AUDIO: Fixed all while() loops in the APU to never be truely infinite (thus preventing hard lock-ups), removed a previous hack that was added to get around such a thing.
- AUDIO: Implemented a new ExSound API.
- AUDIO: Added full save state support to VRC6 Sound and MMC5 Sound.
- AUDIO: Rreduced default audio buffer length from 6 to 4 frames to reduce latency.
- AUDIO: Added in mixing of MMC5s digital audio channel (untested).
- CODE: Moved a bunch of code out of gui.c and into the GUI header files.
- CODE: Various code edits.
- DOCS: Updated docs.
- GUI: Added a GUI menu to configure the audio buffer length.
- GUI: Added a GUI menu to configure video buffer size.
- GUI: Enabled double buffered GUI while in OpenGL mode.
- GUI: Added custom drawing code for the sl_radiobox object.
- GUI: Cleaned up the Help->About dialog and added loomsoft under Special thanks to.
- GUI: Added more splitters to the Audio and Video menus to better group submenus.
- GUI: Added a Close button to the Help->Shortcuts dialog.
- GUI: Hide some menus when their respective features arent available for whatever reason.
- GUI: Made sl_frame object behave properly in a double buffered environment.
- GUI: Removed extended video resolutions, since if anyone wants to actually use any of the obscure things, they can set them manually via the configuration file.
- INPUT: Overhauled input system and input configuration system.
- MISC: Fixed a cosmetic bug where the enabled flag of CPU patches were written to the *.fpt file with the value of 2 instead of 1 when enabled.
- VIDEO: Added (buggy) OpenGL support.
- VIDEO: Added support for a screen buffer smaller or larger than the actual screen (it will be scaled to fit).
- VIDEO: Set all bitmaps to NULL after destroying them in video_exit(), fixes various problems.
- VIDEO: Improved the operation of video_blit().
- VIDEO: Improved efficiency of HQ4X slightly by removing extra assertions.
- VIDEO: Added size checking to the Normal and Stretched blitters.
- VIDEO: Changed blitter error message.

MPEG::Info is a basic MPEG bitstream attribute parser.

SYNOPSIS

use strict;
use MPEG::Info;

my $video = MPEG::Info->new( -file => $filename );
$video->probe();

print $file->type; ## MPEG

## Audio information
print $file->acodec; ## MPEG Layer 1/2
print $file->acodecraw; ## 80
print $file->achans; ## 1
print $file->arate; ## 128000 (bits/sec)
print $file->astreams ## 1

## Video information
printf "%0.2f", $file->fps ## 29.97
print $file->height ## 240
print $file->width ## 352
print $file->vstreams ## 1
print $file->vcodec ## MPEG1
print $file->vframes ## 529
print $file->vrate ## 1000000 (bits/sec)

The Moving Picture Experts Group (MPEG) is a working group in charge of the development of standards for coded representation of digital audio and video.
MPEG audio and video clips are ubiquitous but using Perl to programmatically collect information about these bitstreams has to date been a kludge at best.

This module parses the raw bitstreams and extracts information from the packet headers. It supports Audio, Video, and System (multiplexed audio and video) packets so it can be used on nearly every MPEG you encounter.