Oolite Bulletins

Yay Oolite BB !

Hehe I've just read some topics on the ED forums. Some heated discussions there. Yeah... it becomes tiresome reading some of it. I've had to add a couple of people to my ignore list. I haven't put anyone on my ignore list yet, I usually just cursorily skim through some poeple's posts, or skip them....

another_commander wrote:

Is it just me or is there influence from Griff's Coriolis in the Frontier's station exterior design?

Hehe, my first impression when I saw the pic was: "Hey! That's Griff Coriolis!"

Here's a big list of streamers & other videos (including my humble YouTube channel):

http://forums.frontier.co.uk/showthread.php?t=9172

Entertaining tale, as always.

There must be something wrong with my new PC: nothing I set in Nvidia Control Panel seems to have any effect on Oolite. Vsync on or off - nothing changes. Various AA settings - no discernible difference. With Oolite's own Vsync on, the graphics are twitchy, Vsync off everything is fine. So far I'm h...

Yes, or basically just type the line above. Another segment I use (if you have a multi-core CPU) is -j4, where that tells the compile to use that number of cores (4 in the -j4 case) to speed things up a bit. Before you do it though, you probably should "make clean" which will remove the p...

Edit 2: MYSTERY SOLVED. You are not gonna believe this.. it's the Griff_Shipset_[color=#FF0000]Replace[/color]_v1.34.oxp . :shock: When I remove the OXP, the ring looks identical to when it's under 1.79. The Griff_Shipset_[color=#FF0000]Addition[/color]_v1.22.oxp , on the other hand, is not a probl...

When you do the final build, you need something like "make -fMakefile release-snapshot" (without the quotes) in the root of your trunk code set-up after you do the git download or update. So I just ditch the "debug=no" -part and insert "-fMakefile release-snapshot" ins...

cim wrote:

Make the target "release-snapshot" (which defines compile-time constants which enable the watermark)

Sorry, but that's Hebrew to me.
What should I type, and where, and when?

I'm now downlaoading stuff to test the self-build version on my work laptop, to see if that makes any difference. If not, then I''l test with my home desktop, and make sure no other Oolite version is installed when I test a particular version.

how do I get the version number/code to show on screen with this method?

Thanks - is the 1.79 the same set up you had the probs on before? Also did you use the OXP as dewnloaded, or with the modified shipdata code I posted the other day? (for the station transparency issue). But I have no idea where Dizzy's odd results are from? A question for the dev's - could there be...

Did some testing with this OXP on my work laptop.

Win 7 Pro 64-bit & NVIDIA Quadro 1000M &

- Oolite 1.77.1 32-bit : ok
- Oolite 1.77.1 64-bit deployment : ok
- Oolite 1.77.1 64-bit test : ok
- Oolite trunk-1.79.0.c272d89-dev.x64 : ok, except transparent waystations

Something goes wrong here (1.79 trunk from Friday):
http://www.youtube.com/watch?v=k2g_8dsuG9A
http://www.youtube.com/watch?v=gdb2SP2Y1X4
Ring length / amount of segments vs planet radius? Or what?