Oolite Bulletins

I have strange problem here,

Sound works, Opengl works... text in menu, on planets (buy&sell dialogs), console ("Adder - help anyone here ?") works... but

when I press H nothing is shown (i remember that there should be counddown sequence) I can't see that bigger text on HUD (thought i can see vessels in square with distance shown - from targeting system)

Any hint ? (I have tried even a clean oolite from rsync)

Hmm autopackage version works ok, strange

Hi, togukawa,

it may be a stupid question (if so, then excuse me ), but: Have you chosen a destination on the planet screen first? If you don't have marked a destination for your hyperspace jump, then..ahem..there will be no hyperspace jump and of course no countdown.

Haha It only shows how imprecise my question can be.

Nope, the 'hidden text' text problem occurs when I press for example P (no pause text) - for every text in that specific place.

The jump actually happen :>

Like I have noted earlier - everything works from autopackage.

I have the same problem.

v1.69dev1 installed using the autopackage "works" but crashes frequently (ie often cannot make a single trip). I had reverted to 1.65 which is rock solid. Today I uninstalled 1.65 and reinstalled 1.69 in the hope that the problem was due to a system package which I may have updated in the past 2 weeks.

No joy, crashes saying "Erk!" and that the SDL parachute has been deployed.

I then updated to the nightly build - 1.65-703.

No relevant errors reported on the console but I cannot see on-screed messages like witch-space to .... , missile warnings etc. Essentially all the yellow messages.

I am running Debian Unstable, fully updated daily.

I can send any info you ask for.

I have found some more oddities:

Pressing Shift-6 on the Galactic map does not display routes.

The yaw keys do not work.

A treasuroid (from the Cargo Wrecks Teaser OXP) broke up into boulders instead of alloys as usual.

On the plus side:

The planet improved rendering is ON by default.

The Rock Hermit Locater OXP works (didn't with the autopackage version.

The pirates seem to be more aggressive and nimble.

The only error message generated while playing is the old favourite:

2007-08-18 19:29:06.405 oolite[4169] OPENGL_DEBUG GL_ERROR (1280) 'invalid enumerant' in: Universe before doing anything"

If you're under Debian pulling trunk and building your own debs works quite well. All you need to do is:

- check out trunk
- look in the debian/control file and install the devel packages
- listed open the GNUMakefile in a text editor, look for a line that says 'ADDITIONAL_OBJC_LIBS =' and if you see a -ljs change that to -lmozjs.

after that you just have to 'dpkg-buildpackage'. Oh, make sure you have the objective C compiler installed (gobjc I think).

You'll get a couple of pretty debs to install. (For bonus pints you can update the version file.) The reason why I bring this up, is because I've found current SVN quite a bit more solid that .69.1 on a Debian Unstable box.

Shade,

Thanks for the above but as this is a new type of activity for me I haven't a clue about what it means.

Could you possibly point me at some beginners' instructions please?

davcefai wrote:

Shade,

Thanks for the above but as this is a new type of activity for me I haven't a clue about what it means.

Could you possibly point me at some beginners' instructions please?

OK, I'll give it a whirl:

1. Install: dpkg-dev, gobjc, and svn (These are the tools to build debs, the Objective C compiler for linux, and the versioning software that will let you get the source.)

2. Go here: http://developer.berlios.de/svn/?group_id=3577 this is the instructions to checkout the source code.

In short, open a terminal, and 'svn checkout svn://svn.berlios.de/oolite-linux/trunk '

this should give you a directory called 'trunk' with the sourcecode in it. After the download is done you can rename it. In the future you ca opened a terminal and 'cd trunk' then 'svn up' to get newer code.

It's also fairly easy to check out different 'tags'. Man SVN is your friend here.

3. Open the 'trunk/debian/control' file in a text editor. At about line 6 you'll see:
Build-Depends: libsdl1.2-dev,libsdl-mixer1.2-dev,libgnustep-base-dev,gnustep-core-devel,libpng-dev,libmozjs-dev, mesa-common-dev

Install those. These are the developer packages to build OoLite.

4. Open 'trunk/GNUmakefile' in a text editor. At about line 21 you'll see: 'ADDITIONAL_OBJC_LIBS =' if that line says -ljs change that to -lmozjs to look for mozilla javascript. (Yes there is a different (or 3) javascript implementation.

5. Optional: Open the 'trunk/debian/changelog' file and add an entry. Personally I use version-svncheckout number. I find it helps if I get and unstable build, so I can install an older version. Be careful, very picky about formatting, and not strictly necessary.

6. Back in the console. Make sure you're in the 'trunk' directory. Type: dpkg-buildpackage &

Grab a coffee and pray. Stuff will flutter by. It's descriptive stuff. Good info if you hit problems. If it works you'll have two OoLite debs.

7. The debs will be built in the directory above 'trunk'. Either use your favourite package tool, or 'cd ..' then 'dpkg -i oo*.deb'.

Congratulations, you've just built and installed debs!

Commander Shade, you're a good man!

Thanks for the help. I now have a working Oolite - all but the routing diagrams (^6 on Galaxy Map)

Incidentally I may have found a part of the problem. The GNUStep dependencies in Debian Unstable are currently a mess and it took some effort to sort things out.

I had to get gnustep-back0.11_0.11.0-3_i386.deb from packages.debian.org as ...12.0-3 is currently in the repository and gnustep-common demands this file.

Anybody who may want to try this version can look for the files on ftp://cloud9.dyndns.tv/Oolite. This server is usually up between 0600 and 2300 CET (Greenwich + 1).

No prob--

Oh yeah, I should have mentioned:
-It will ask you to specify a libpng-dev version, and Debian will be transitioning for an older to newer version of the GNUStep stuff. There's a really new version in experimental, but I haven't tried to muck with the build depends to get it to build. So for now I'd suggest sticking with the version that builds. So-- if you're afraid that things will stop building, be sure to pin your gnustep versions so you don't accidentally install new ones on an update.

For those having problems with the Shift+6 key combination, could you please check by assigning a different key and see if it works for you? Do you use non-US keyboard layout configurations?

And, I know it is trivial, but sometimes trivial things slip by, you have bought the Advanced Nav Array equipment before trying to access the map routes, right?

Strange but true: Today the shift+6 key combination is working. The only reason I can think of is that I rebooted.

I did not upgrade any packages which could possibly have affected this.