Free cube software for linux

Mcube project is a 4x4x4 Rubiks Cube solver.
Mcube solves 4x4x4 Rubiks Cubes. It is platform independent and supports both a pipable console-only format and a graphical format.
CGI version:
First finished release of mcube Solves 4x4x4 rubiks cube via a CGI web-based environment. The cube class can be used in other programs as well.
Command-line version:
This is the command-line version of the 4x4x4 solver. The algorithm is identical to the normal (CGI) version. Use this if you like do-it-yourself console programs.
Enhancements:
- Fixed concise() bug not updating mov[] correctly.
- Added "input page" generator on output page, for easier debugging.

xmms-cube is a port of the Winamp plugin in_cube. xmms-cube plugin allows you to play Gamecube streamed audio files.
Supported types include:
- DSP
- GCM
- HPS
- IDSP
- SPT
- SPD
- MSS
- MPDSP
- ISH,
- YMF
- ADX
- ADX
- RSD
- RSP
- AST
- AFC

PDFCube renders PDF presentations with special 3D effects (the omnipresent rotating cube and 5 predefined zoom animations). The project adds eye-candy to your PDF presentations, even Latex, Beamer and Prosper ones.

Right now you get a 3D cube transition pressing "c" and you can zoom on 5 areas with "h", "j", "k", "l" and "z" keys or simply switching pages with double buffering (no redrawing is visible) and with full anti-alias.

If you want to program your cube transitions in advance give the page you want the transition at on the command line this way (0 means between page 1 and page 2, rudimental but will change soon):

$ pdfcube file.pdf 0 5 10

Rotating cube transition is of great effect when put on a big projection screen, so be moderate! One or two cube transitions done when changing argument can help understanding that you are switching to a new part of the presentation. On the other hand using cube transition on every page can give seasickness to your audience.

Youll need an OpenGL DRI enabled Xorg. GPL ATI 9250 driver is OK, ive not tested other cards.

This is alpha software (and right now its a quick hack too), but once you manage to get it working its fairly stable and usable.

Magic Cube 4D project is a four-dimensional Rubiks Cube.

MagicCube4D is a fully functional four-dimensional analog of Rubiks cube. The image above shows the puzzle in its solved state. Click on it for a simple resizable applet version that you can interact with to get a feeling for how it works. Download the full-featured application below and try to solve it. Please read the FAQ for a more complete description of the puzzle. If the Java applet or application fail to start you may need to install a Java virtual machine. Click here for a current one.

Don Hatch and Melinda Green have developed it on and off over several years. Jay Berkenbilt has recently joined us to help with Linux support and source control. Don and Jay were the first to have solved the puzzle making extensive use of the move macro facility in the UNIX version. Roice Nelson became the first person to solve the puzzle without using macros. For his solution, he extended Philip Marshalls 3D "Ultimate Solution to Rubiks Cube".

You can learn Roices solution if you dont feel like trying to solve it yourself first. Using his techniques, Roice and others have continued to find ever shorter solutions so that the record currently recovered by Roice required only 334 twists! You can find documentation of these and other milestones on the MagicCube4D Hall Of Fame page. If you solve it with or without reading the solution, send us your log file and well list you in the MagicCube4D hall of fame too!

The mathematically inclined may be interested to know that the number of possible states for the 4D cube is exactly

(24!x32!)/2 x 16!/2 x 2^23 x (3!)^31 x 3 x(4!/2)^15 x 4

which can also be expressed as

32! 24! 16! 2^22 6^32 12^15

rubix project is a Rubiks cube system for Linux.

It runs under X11.

The program will auto-load "rubix.dat" which is created when you save the current game, so you can continue from where you stopped. (it has to be in the same directory, you can run rubix -l saved_game.dat to change this default).

Run "rubix -h" to have the commands during the game.

Have fun with this.

PS: If you have a method to solve the Rubiks cube, send it to me !
If you did a program that solve it, by any mean, send it to me too !

PPS: This program demonstrates the definite superiority of the "select" approach compared to the multi-threaded one. (Yes it does ! :))

Installing

Then just do "make", all should be alright. If not, dont hesitate to contact the author.

Run "rubix -h" to see how to use the program at runtime.

Its a simple idea: implement Conways Game of Life using boolean logic operations (and, or, not, xor); do so by blits, thus running a Life game in every bitplane in parallel.

Currently 2 implementations are available: a proof-of-concept (with a life-covered 3d cube!) one in Python (with Numeric/pygame) and a useful one in C (X-Windows screensaver, potentially accelerated).

Rubiclox project is a Rubiks clock implementation.

Rubik is the creator of the Rubiks cube. There is a rubiks cube implementation too if you want to play with it. The clock is much easier than the cube, though.

This program works under Linux/X-Window. It may work on other OSes than linux, too, but they must be posix I guess. Well, try to build it on your system and send me reports if it worked or not.

The goal is to have all the clocks pointing to 12 oclock, in both sides of the
game. You can achieve other figures too, if you like, but the primary purpose
is all the clock on 12.

Volumevis displays pixel-based 3-dimensional datasets. 3-D pixel datasets mostly come from 3-D computer tomography (CT) and magnetic resonance (MR) images. These datasets usually come in the form of a set of 2-D picture files each being a slice of the 3D dataset.
To be displayed by volumevis, the files have to be ordered with identical names except for a number somwhere in the name corresponding to the slice number. Most image formats (jpg, tiff, dicom, etc ..) are supported.
Volumevis is a tool for visualizing 3D dimensional pixel-based datasets. Most computer 3D visualization in the world is with surfaced-based visualization. This is true for most 3D games, CAD tool, etc.
By stating it simply, surface-based rendering works by dividing a predefined surface into small triangles, and then sending those triangles along with their color to graphicscard to be rendered. For example,if you want to render a sphere in 3D, you would create a surface of the sphere, divide it into triangles, send the triangles to the graphics card, which would then turn the triangles into pixels and displaythem.
The unfortunate side-effect of this is, that if you happen to cut the sphere, or go inside it, you will see that its in fact hollow. Also, you cannot see any of the details that might be inside of the sphere.
Volume visualization is the equivalent in 3D of displaying a photo in 2D. The surface 3D visualizations on the other hand, are the equivalent of reducing a photo to a representation of lines (such as the outlines of people and houses) and drawing the lines on screen. Obviously a lot of information goes lost in the line representation.
The visualization works like this. In openGL (a graphics programming API), all fragments (3D equivalent of pixels) have an alpha value. The alpha value corresponds to the opacity of the fragment. If the fragment has a small alpha value, it will be easy to see through it and see the fragments behind it.
If the alpha value is high, the fragments behind it will be obscured. A 3D dataset is simply a block of data in the shape of a cube. Somewhere in the image there is an object which is white or grey. All the other places in the image are black. To render the object, all the pixels which are black are assigned and alpha value of 0 (meaning they are transparent). Therefore we dont see the black pixels.
The fragments belonging to the object are white and have an alpha value higher than zero. Therefore its not possible to see through them, and we perceive the location of the object fragment to be the surface of the object. Depending on the alpha value of the fragment, we might also be able to see some of the fragments behind it a bit (see inside the object).
At the moment, Volumevis only supports black/white images (which is fine for most CT and MRI datasets).
Enhancements:
- A bug with slice loading of textures which are not a power of two was fixed.
- Movie recording, cropping, and file saving for slices were fixed.
- Various feature improvements were made.