Orxonox

maybe also additional levels for your gametype ?

nice, thanks a lot

looks cool

maybe you just have to be carefull that it won't look bulky in the end (after texturing) except if that's what you intend

afaik enet cannot use tcp

Is there a way to make collisionshapes visible? (The only way I know to detectem is to crash into them. that's not the smartest way...) if you are using sphere collision shapes you can attach a sphere mesh to the collision shape with the same size ^^ maybe we could implement such a feature into col...

hm... key is that they probably don't use enet. so if we wan't to be compatible to these protocols we cannot use enet for this communication part (i think this only concerns client->masterserver, right?) because enet also puts some stuff into the network packets ...

Hi At first thanks for your work. It is great to see people creating content for orxonox ;) wanted to test it today, but when trying to start the level the error LuaState: Cannot include file 'lastmanstandinghud.oxo' (not found). appeared in the console and the mainmenu background image stayed on th...

i think having a seperate executable would be much better: - this way you could still use any code of orxonox (even the IOConsole) - you could also use our enet bindings or some specific network classes - it would be possible to create a light orxonox package or src distribution with only the master...

is this problem now solved or does it still exist? cause the page on the wiki still says unsuccessful which doesn't look good ^^

if you will reuse parts of the orxonox network code it's probably the best to use enet (and thus udp) and send the information you require via a reliable packet (this would be samehow similar to tcp). you could probably create one/several new packet(s) and use orxonox::packet::Packet as base class i...

that's what i mean ^^ i would also put this linking file only into the pool and not the data_extern directory i think we have to clarify the different names for these folders: - when talking about the data pool i mean the directory which contains all content that was once created by us or our pps st...

I like the ideas of links, but I suppose it's never going to work because that list will always be outdated and incomplete anyway. (btw. we don't have any blender files in the data folder, just meshes) i don't think that these links will be quickly outdated: once you export a model you don't change...

i really got the pool and the data folder confused ...

what about putting meshes and blender files into one folder together with a model description file containing "links" to the material and texture files thus leaving textures and materials in a separate folder?!

maybe it would be better to keep material files, textures and meshes together for models as we already discussed earlier ?!

actually using "subdirectories" should be possible by configuring apache appropriately. We would have to use several copies of trac though. Don't think this is feasible