Oolite Bulletins

*Whips out the flame proof underwear and a fire extinguisher*

"unwashed masses"

I'm saying nothing about the linux userbase at all... however you never see gentoo and soap in the same place at the same time

http://www.btinternet.com/~spooky_int13 ... 6.5.tar.gz

This is the 1.62-3 standalone package for IRIX 6.5 MIPS3. No warranty implied or supplied

Tomorrow afternoon I should have finished FreeBSD 5.X, FreeBSD 6.X and NetBSD i386 3.0 packages.

It's probably not environment - it's probably a missing (and almost certainly empty) directory All of the GNUstep files are there because if I set up the link from the oolite-deps/GNUstep to /usr/GNUstep then it works absoluetly fine even on machines that have never had GNUstep installed. I've adju...

Hmmm, this is starting to get a little frustrating. I've rebuilt my entire development kit onto another machine. Built all the libraries, built GNUstep from the startup package using default directories. I've not even attempted to slimdown the GNUstep dependancies and bugger me backwards I'm still g...

winston: Ok, I've duplicated your install script (That's a damn fine script by the way, simple and effective.) and .tar's and it installs fine. However on machines that I haven't previously installed GNUstep on I still get the errors (I also get the errors if I move my initial GNUstep folder) 2006-0...

I think the rotation is fine is as it is. The fact that it spins at all gives enough feeling of realism and solidity to the clearly game driven aspect of rotational docking. Realism isn't something I would associate with Oolite (or original elite for that matter), surely the aim of the developers is...

Ok, I'm getting a step closer to a stand alone package. I've got all the libraries sorted, I've setup a simple execution script with all necesary environment variables to point to the libraries (hacky, but it works for now) and GNUstep. However when I try to run the app I get... BlueThing 155# ./ool...

Oh dear

I switched over the timer routine in SDL_systimer to use CLOCK_SGI_FAST and the frame rate went all to hell. It bounces around between 18 and 29 and looks *REALLY* choppy. I think I might put this one into the 'to be investigated' box and go back to good old 35fps

Ahruman: I'd quite like to try and keep up to date with the releases of Oolite and I think trying to convert objc to C on an ongoing basis may be more hassle than it's worth. It's not like it's unplayable and once I sort the SDL problem I'm sure it will be positively splendid.

Once I'm done with getting a working static build I'll make the changes to SDL, they are straight forward enough. I'm not sure how much quicker I'll get though because the MGRAS card in this machine is really pretty puny. I just wish Oolite wasn't objc code because then I could use the MIPSPro compi...

Unfortunately I only get 35fps. This is due to the different hardware timer support in IRIX (one of the pitfalls of a true realtime operating system). Unless I ever get round to enabling CLOCK_SGI_FAST as the default Posix timer in SDL then it's never gonna get any quicker than that... at least it s...

That really is cool seeing Oolite on yet another platform. Well done! Thanks, I hope it inspires other users of 'exotic' machines to have a bash. The more the merrier and all that :wink: Now, if we could move AI into a separate thread… and maybe mesh loading. And then do updates + physics separatel...

Oolite isn't (particularly) multithreaded - the main game is one single thread so unfortnately, the other 15 processors will be wasted! Yeah, it barely uses one when running but I was talking more about the compiling :wink: Post a screen shot of it running in a window on your desktop, too Your wish...

You see both of those warnings on Linux, they don't seem to cause a problem That's good... at least its not just me then :wink: I'm gonna try and bang a little self contained package together which I'll hopefully have finished by tomorrow (depending on how much of bitch GNUstep is going to continue...

:twisted: SUCCESS :twisted: Managed to get a successful compile... with a little bit of tweaking. In HeadUpDisplay.m there was a conditional statement using isnan (for scanner range checks I believe). I couldn't find a library which would supply support so I fudged it a little, I'll go back and tidy...