Orxonox

Actually I prefer to put documentation into the code instead of the wiki. It's less likely to get out of date if you put it in the code. It's also the first place where a real developer looks. ;) Nice to see that you're project makes some progress. [x] created a class [x] created insulting messages ...

I'd like to put the following topics on the agenda: I'd like to tell you a little bit about (unit-)testing in general and give you a small practical example of how this can be done in Orxonox I like Jo's suggestion to talk about past and future work on Orxonox. I would like to cover the framework de...

Well, of course you can have a singleton, you can have anything, you're developers. :) The question is more like "Is a singleton a suitable solution to our problem" and "does it fit into the existing design". On a side note: try to not use singletons if possible. But before you start thinking about ...

The Meeting is also a place to present something: a cool new feature that was added since the last meeting; a new concept or development technique that you learned and want to share with us; or simply a scene from another game that you like. You may also pick some code examples and show us where you...

The issue is fixed in trunk. Please update with SVN. If you already created a branch, merge r9703 from trunk to your branch or create a new branch (or ask an assistant to help you)

Thanks for testing. I compared boost versions from 1.47 up to 1.54 and noticed that we only have to change the version number in the preprocessor statement to fix the issue (boost versions 1.48 and 1.49 were affected).

http://www.orxonox.net/changeset/9703

In this case you're probably right, it's better to bypass OIS and use WiiCpp. It shouldn't be too hard to inject some events into Orxonox' input system. Just look at how OIS events are handled, then do the same with your WiiMote events. Just try to find the part of the code which "translates" OIS ev...

OIS is indeed designed to use input events on the OS-level. And I guess your WiiMote will produces those events if you install an appropriate driver. I don't know if you need WiiCpp for that... The latest (well, it's from 2010) release of OIS (1.3) contains sources for the WiiMote on Windows. See th...

Currently we expect that everyone who signed up in the doodle poll will join our meeting (8 people). Other people that want to join please respond to this thread or send a message to me or beni. If you signed up in the doodle poll and changed your mind (i.e. you don't want to come) please let us kno...

I tried to reproduce the error on my machine. I get the exact same error when I remove my data_extern directory. So I guess this is the problem. What's inside your data_extern directory? Does it look like this: data_extern.png Or maybe you executed cmake before you checked out data_extern. In this c...

Hi Nowic Have a look at src/libraries/core/CorePrereqs.h between lines 266 and 318. There we make some forward declarations of some important classes in the boost namespace, including 'path' (for your version of boost this is probably on line 296 and 300). Even though it shouldn't, these may collide...

An input device doesn't have to cover all features. You can play Orxonox with a gamepad which acts like a combination of mouse and keyboard, but with less buttons. If you need more buttons, you can still use the keyboard. The same holds for the WiiMote. Just use the keyboard if necessary. After all,...

The input system was designed and implemented by Reto but I'm not sure if he's still reading this forum. I cannot answer all your questions off the top of my head but I'll try to find some answers soon. So far I can tell you only a few things: We use OIS as an external library for input handling. OI...

Hi Atlaun

Did you check out the data_extern repository?

URL: https://svn.orxonox.net/game/data/trunk
Checkout directory: c:\<msys-homedir>\data_extern

Ensure that you have a directory structure like this:

Nice!

And thanks for the hint, I think I accidentally deleted OpenAL32.dll together with Ogre & co. I will add it again to the dependencies.