esteel wrote:But sorry i have no idea about video editing

I first thought of building support for piping data directly to mplayer into the darkplaces engine, but then realized that this could probably be done by using a simple pipe. Now the next problem is that the DV format, to which mencoder could transform the yv12 output from nexuiz, only allows NTSC or PAL resolutions. ARGH! And it seems that Kino can only handle DV. Why not M-JPEG? That format is probably as simple as DV...
Ok, then I found out about the LiVES video editor for linux. It seems to be capable of handling MJPG or LJPG formats (the latter one improving hard disk space usage by a factor of 2.2+ over raw yv12), but has the disadvantage of converting every single frame into a preview jpeg file when opening the video file. That takes a LOT of time.
The next problem was that the file descriptors for the raw video dump are opened by nexuiz in a non-blocking mode. So, when writing to a pipe ("mknod ~/.nexuiz/data/video/dpvideo001.yv12 p"), the output is truncated -- probably after the first 64kb of every frame or so. Changing the code so that blocking writes are used (please commit that change to the nexuiz codebase in some way, maybe by using a cvar like cl_capturevideo_blocking), solved that problem. My solution is now to pipe raw yv12 video directly via a pipe into mencoder, which then writes the data to an avi using the loss-less LJPG compression.
An example script that creates the pipe node, starts the mencoder and nexuiz demo, and the corresponding ebuild file containing the code changes is available at
https://stier.dynu.com/~myportage/games-fps/nexuiz/.
BTW: I have added the nexuiz code to my LXR source code cross referencer at
https://stier.dynu.com/~lxr/nexuiz/source/.
Regarding the relief mapping: GeForce Ti4800SE is not OpenGL 2.0 compliant as far as I know... so that feature does not work here.
Yet another point: the vertical pixel size should be automatically set using the DPI information from the X org server. Usually, tvtime and other apps need that information, too. To make the nvidia driver work correctly, I had to set "UseEdidDpi" to "FALSE" and adjust the DisplaySize variable in xorg.conf. Many users have a bad display setup if this is not done automatically, because many TFTs have non-square pixels (4:3 format, but 1280x1024, ie. 5:4 resolution).