Oolite Bulletins

Commander McLane wrote:

Thus my question: wouldn't it make a lot more sense to contact one of the current developers?

*face-palm*
Yes it would, are you one? By any chance?

Check the links at the bottom of the main board index page: the Developers have a blue link.

Cheers!

Sorry, but a clarifying note please. Is the memory problem a cpu memory problem or a hard drive problem?

Isn't the R Pi supposed to be not only very cheap (I found a listing for $35, thought article posted on forum previously said 12 euro or something), but also modular. If it is modular, it's been a while since I read the article, then wouldn't it include usb ports, looks like it has a usb or two; if so couldn't we just put Oolite on a memory stick (or an external drive connected via usb)?

I assume anyone using one would have a usb drive or two to store their work. Then you would only need to list where they could find Oolite on the web in a document file on the R Pi or better yet, if you could offer a usb drive (or knew one was being issued to each student already) to each student with a copy of Oolite preloaded.

I realized that doesn't solve the graphics engine conversion, but that would solve issues cutting the textures down. Cutting the textures down seems like a bad idea as it would interfere with oxp compability, oxps would have to be separated into versions with reduced pixel textures for the R Pi and ones with textures for win and linux pcs and macs. The pc (or standard) textures would not run on the R Pi copy of Oolite being too big or at least looking out of place alongside standard R Pi textures, and R Pi downsized textures would look funny on regular computer versions of Oolite being too small and low quality compared to regular textures.

Finally, wouldn't there be a problem in that the R Pi is designed to hook into tv screens. The users would probably use a regular computer screen most of the time, but if one of them were to use a tv screen, say a student was allowed to take his home..., then the game would look even worse than it would on a PC with reduced textures as the screen would be bigger.

Commander Wilmot wrote:

Sorry, but a clarifying note please. Is the memory problem a cpu memory problem or a hard drive problem?

It's the memory used by the CPU and GPU. Nothing to do with any external storage. Model A has 256Mb RAM, one USB port and no Ethernet (network connection). Model B has 512Mb RAM, 2 USB port and an Ethernet port. That memory is shared by the GPU.

Ah, thank you. That is a problem.

Firstly I'd like to get involved in the project, although I'm a busy chap and don't get too much time to cut code (outside of work). I can bring 20+ years experience to the party, I'm used to collaborative dev environments and have used most source code repositories in the past (SVN or Git are the main 'free' ones). I know a fiar bit about continuous integration techniques (i.e. the build server processes). My coding expertise is mainly in basic,c# fair bit of .net

IIRC the guru's identified the Open GL issue as the biggie (and it was mooted at the time that oolite would probably go down the ES route eventually anyway), so any effort put into it now will pay dividends later when merged back into the trunk.

I'd like the rpi version to work in RiscOS, but don't know if there's a c++ (free or cheap) for it?
What's the footprint when oolite is running with all the candy?