Have anyone played qw on a raspberry pi?

problems? fps? etc??? tell me if you have

Raspberry PI have a ARM processor. i doubt quakeworld is ported to arm at all. and guess it never will

WELCOME BACK SASSA!
you were missed =)

I thought it could be ran in ARM via some Linux OS :|

Just because it runs linux doesnt mean it runs quake. and it's afaik not ported to the architecture arm.

Several Quake engines have been ported to ARM. 3-4 at the very least.
FTEQW even runs on Android (which usually is ARM).

Yes I think almost every major client has made the effort trying it to run on Android. Doesn't sound too exciting to port it to the pi. It is more likely a matter of hardware availability and motivation..

Client is probably harder to get running than a server. I've run mvdsv on a network camera based on MIPS (ktx gave floating point exceptions)..

If you mean to run it on raspberry pi in linux it shouldn't (in theory) atleast be that big of a problem to make it "work" atleast, as long as you can compile for the target and have necessary libs available.

I thought this was a reply to "What did you have for dinner?".

Get your shiznits together sassa and get back into QW!

no1 have got it to work on android?

http://www.youtube.com/watch?v=alpIu9j4SRY

Well I think it is more like a feasability study at this time. Don't you agree hat controls on a phone or tablet are not suited for serious quaking as they are right now? I guess this renders the userbase to an absolute zero. Not much motivation for a developer to support this port..

From a technical point of view if you run Linux on the Pi all that should be required is to port the OpenGL calls to OpenGL ES. All other Linux API's should be supported.. I suppose? Software version might work right away..

Would be nice to spec games on the phone or tablet

Yes.. but that is what HTML5 and WebGL was meant for *cough* *cough*

Spectating should totally work with FTEQW. Input is an issue though

I will try this when I get a pi! It should get decent FPS (it plays quake 3 fine at 1920x1080, according to the old pre-release news), but a big issue is probably that it can only run at 60hz over HDMI....

There is a new model out also with more RAM and some other upgrades too. I saw a vid of q3 running on it. Looked good.

Yeah I recieved my Raspberry Pi Model B 512MB version this week. Haven't decided how much fun I'm gonna try to have with it yet

Running ezQuake on Raspberry Pi would unfortunately mean that most of the rendering code would need to be rewritten to more modern shader based rendering. ezQuake as a project would need this, even for desktop, so anyone reading this with OpenGL knowledge and the will to help, give me a PM instantly!

Hi everyone!
We have a port effort going on over at the Raspberry Pi forums.
The thread is available at:
http://www.raspberrypi.org/phpBB3/viewtopic.php?f=67&t=44447

And the github repo is over at:
https://github.com/welford/qurp

It's not ready for prime time or regular users yet, but anyone with some development skills is welcome to help.

Hi!

This definitly looks interesting! GLES is also always interesting. I'd recommend to base the work on a commonly used engine, preferably qw engine like ezQuake which would benefit both camps. I'm currently the only developer in the ezQuake camp and ezQuake really need an overhaul, especially in the gfx department. If it's possible to combine the work, make the client work nicely on RPi and at the same time get the client in a better shape, it would be awesome, especially since ezQuake is the client that the absolute majority uses in the Quakeworld scene.

There are also other clients out there, some have much cleaner/better code like Fodquake, but it currently lacks some features that players today take for granted. Other clients like FTE are much (i really mean much) more technically advanced and better, but has a focus that is not really "qw only".

So for some reason we are stuck with ezQuake and we currently lack QW developers. It would be awesome if you'd like to help out

eb compiled the mvdsv and ktx sources for rpi

We did some testing:
- with 7 players + 1 spec, cpu usage was around 80% with everyone spamming sng at dm3 outside
- in conclusion it will be enough for 2on2, not sure on a competitive 4on4 match.


some instructions for setting the server up:

AWESOME

quick update on this:

Spike has compiled FTE, both client AND server, for raspberry pi. links on http://wiki.quakeworld.nu/How_to_server

Also, old news buth worth mentioning imo: Spike has released a FTE port for android phones (FTEDroid). more info at http://wiki.quakeworld.nu/FTEDroid

Interesting... I have a Raspberry Pi sitting at home doing nothing...

too bad
* connect it to an external drive and u can sftp to it;
* setup a squid http proxy to bypass the company's security policy (access youtube and porntube at work)
* download torrents 24/7 with http gui
* setup qw server
* wake pcs on the lan with magic packet
* ...

or
* simple media player (xbmc)

How do I start 1 nquakeserver from boot on the raspberry ?

right now I do



in the Terminal

Are there a easy script to make somewhere?

Assuming you are running on debian (but I guess this applies to all other linux flavours as well) there is /etc/rc.local. Everything you put in there is run on startup. Put in a line like this:



Or something like that..

Weeell not really (about it applies to other linux flavours)

SysV init has initscripts in /etc/init.d/ and has /etc/rc.x/ folders for different runlevels. Normal runlevel is 3.

If you run Arch linux for instance on the Pi it's using systemd, which does work completely different (parallell startups @ boot etc). I'd recommend writing a proper .service file for systemd. Could probably help if you need it.

AFAIK &> is bashism, dunno about support in other shells.

Off topic: I'm using my Pi with Raspbmc and it works flawlessly as HTPC now adays.

There is no rc-local.service on Arch Linux?

systemd doesn't normally work with the old concept of runlevels. It uses what it calls targets, the equivalent of "normal desktop runlevel" would be multi-user.target on systemd. So if you have some service you want to start, you'd symlink (or systemctl enable will do that for you) the service file to (one of) the mult-user.target.wants folder(s) (Recommend reading about systemd if interested ).

If your service requires networking for instance, you need to specify this as a dependency in the service file. There are Before= and After= statements for instance, Requires=, Wants=, etc to specify dependencies. This is due to the nature of systemd; everything that can be started in parallell will be, but it requires that your dependencies are correct.

Was there ever an ezquake variant made for ARM or RPi in the end?

Raspberry Pi 5 is coming out in October and has a 2.4Ghz Quad-Core processor. Would be interesting to see how it oculd run games