Orxonox

hehe nice

thanks for the hint

if what x3n suggested doesn't help it might be neccessary to know which kind of graphics card (intel/nvidia/ati) you use and whether you use the opensource driver or a binary driver ?!

i guess 3d acceleration works on your system (check with glxinfo | grep render)?

looks nice so far
however after destroying the boxes the tutorial doesn't continue, does it?

what did you intend to continue with afterwards?

hm.. I'm not sure if i remember correctly (did some changes there once ago) but i thought that actually the radar should remain bound to the spaceship and not to the rocket, shouldn't it?

do you mean the steerable rocket or the self-seeking rocket ?

maybe it helps if you post some log files: in ${build directory}/log/ the files cegui.log, (maybe) ogre.log and orxonox.log

could be that there is a hint for this problem somewhere hidden in one of these files

hm... though ubuntu still recommends the 32bit version i'm always using the 64bit version of it. so this wouldn't be a problem for i guess 80% of the orxonox linux users. and we could still provide a gcc 32bit version of orxonox if ekopath's not available for 32bit. @clang: maybe we should compare t...

Just stumbled over this article. It is about the open-source release of a previously proprietary and multiple kUSD (per license) expensive compiler suite. In some tasks it outperforms GCC by a factor of more than two or three (not sure if I remember this correctly, but at least two ^^). I think we s...

nice, thanks a lot.

now we finally have to update our ubuntu packages (which i think are only available for 10.04 which is obviously more than a year old...)

i like the idea of this topic and i'm curious if it'll be used ...

i think in this use case fixed tags will be fine esp. if we might need some menu elements or sheets that know all/some tags and select/filter between them

hm, this sounds like a tough problem... x3n, what does ogre use internally for absolute position computation if not "normal" floats? i don't really understand why these internal floats should be any different than normal ones ?! why is it not possible to attach a world entity to a different scene, i...

what's on the x axxis for the first plots (plot 1, 3, 5)? tick time in ms ? (cause that wouldn't look reasonable for empty level 60ms without bots and 1.5ms with bots ?!)

wouldn't that be pre-processing too (e.g. the code for scale)?
or how do you differentiate post- and pre-processing? post and pre xmlport?

a quick view into /usr/share/icons lists the following resolutions:
- 8x8 ^^
- 16x16
- 20x20
- 22x22
- 24x24
- 32x32
- 48x48
- 64x64
- 72x72
- 96x96
- 128x128
- 256x256

However I guess that they're not all necessary ^^
Maybe Adi knows more about that.

about the authors files: maybe i authors file per directory is a bit too much (especially if we will use more directories than before). maybe we should put the authors files one (i.e. {metal, rock, ...}) or even two (i.e. in {billboard,texture,...}) layer(s) up ?!