Hello,

I tried watching the DH QTV streams today and yesterday, but both times (and after several /qtvreconnects) the streams were corrupted.
For the first second I saw (choppy) action, but after that it screws up, often placing the player outside the world, the ping increases to 999, the gameclock counts seconds as minutes etc.
I tried using vanilla config, no difference. Occasionally after that the view will jump to another position or angle, but it generally does nothing, no activity of any sort. The console is left at "Downloading skins/locktar.pcx"

I'm not sure what the problem is, I can play online fine and everything
I'm using 2.0-1 stable, package from AUR (Arch Linux repository)..

Anyone had anything like this before?

EDIT: It also crashed a few times when I /qtvreconnected, but I haven't managed to reproduce it to get an error code/message.

Does this happen on the quakeworld.fi QTV as well? Because it might just have been the DH one lagging

I have seen increasing reports of Arch Linux users who have problems playing MVD demos and receiving QTV streams.

It might be helpful to know which version of EZQuake is being used (32/64bit). Also if non Arch Linux users experience the same. It might be a problem specifically related to that particular linux distribution then.

EDIT:
I have just checked the Arch Linux install receipt from their repository. From what I can see is that they delete the EZQuake distributed binaries and instead compile their own binary from the source code. They also statically link to our provided libraries which leaves me completely puzzled why they consider recompiling the binary.

Can you try extracting and running the original binary found in the official EZQuake package?

I set Opera to open qtv links with /path/ezquake-gl.glx
That is "ezQuake 2.0 stable, 2678". Installed manually (not through AUR).

Absolutely no problems, I tried several from quakeworld.tv

I'm running 32 bit.

Apparently it's only the Arch build, because someone in IRC (forgot your name, sorry :S) said that the latest alphas/betas on the EZQuake site work fine.

Guess the maintainer should be alerted then.

I have the same problem and iirc I compiled the 2.0 binary myself, without the use of AUR. The 2.1 nightly build works perfectly fine though.

2.1 Nightly compiled by yourself or precompiled? AUR does not do much. So if you compile it yourself and it won't work thats about to be expected. If 2.1 precompiled works this is a complete different story. I guess Arch Linux GCC compiler is buggy or somehow incompatible with the EZQuake source tree in it current state.

I just compiled from svn and it shows the problems. Log: http://pastebin.com/pastebin.php?dl=m17eb64ab
Same with 2.0 stable compiled by myself. Log: http://pastebin.com/pastebin.php?dl=m198b1afd

Linux distros tend to come with two versions of gcc nowadays...
It doesn't help that many distros are released using experimental versions of gcc.

I have the same issue with build 3288 (from ezQuake website) and Ubuntu. Older versions have run smoothly with QTV and so does the latest nightly build (2011-03-09-13d3146-ezquake.7z). Naturally this 2.2 beta is not allowed in EQL...

What happens is when I connect to a QTV stream I get a couple of frames before it hangs (as if connection was lost).

I'm running Ubuntu 32bit on my HTPC and solved the problem QTV problem by using this:
http://sourceforge.net/projects/ezquake/files/beta/2.1-b1/ezquake_linux32_2.1_beta_1b.tar.gz/download

I think it had something to do with 32bit binaries which were compiled with gcc version 4.4.4. If you want to know the specifics, ask dimman.

#ezquake: