Oolite Windows - Trunk nightly builds

[Switeck]

I mostly just seek the nightly builds.

I've tried to build from source a couple of times to delve deeper into what's triggering a bug, but the cryptic results I got were beyond me...so I prefer to leave that in the hands of the experts.
It's usually hard enough for me to come up with conditions to consistently trigger bugs I've seen.

[Diziet Sma]

Well, okay, bar one change which I've not got around to making in SVN as well...

Which I see you've now done.. woohoo! an update! It's been so long since we've had one, I had to toggle waaaay back in my bash history to find the update command..

[Cody]

... woohoo! an update! It's been so long since we've had one...

See... you wait ages for an update, then three come along at once!

[imipak]

I'm just getting a lot of page unavailable errors, have been for many days now. The Galactic Navy has been informed, but they said it might have something to do with a bunch of Gits. They've sent a Krait to take a look.

[Getafix]

Nightly trunk binaries for the Windows port of Oolite are now available from the page below:

http://terrastorage.dyndns.info/oolite/ ... win32.html

First post needs to be updated.


EDIT 2014/05/01: http://terrastorage.no-ip.info/oolite/status_win32.html

[Svengali]

Muchas gracias, Getafix!

[JazHaz]

Nightly trunk binaries for the Windows port of Oolite are now available from the page below:

http://terrastorage.dyndns.info/oolite/ ... win32.html

Is this building SVNs from Berlios or the new place (github?)?

[Getafix]

SVNs... no github yet...

[another_commander]

The nightly builds of the Windows port of Oolite are up and running again on terrastorage and are available for download from http://terrastorage.no-ip.info/oolite/status_win64.html.

Note that the nightlies are now built as Win x64 binaries. This is because we want to give as much testing as possible to the newly introduced x64 versions. 32-bit nightly binaries might become available at a later time, but not at this moment.

Also, the version scheme shown on the watermark has been changed slightly. It is now 1.79.0.xxxx-YYMMDD, where xxxx is the incremental build number on github (not to be confused with SVN revisions, which have nothing to do with anything at this point) and YYMMDD the format referring to the date the build was created. On top of that, the installer filename will contain the seven first digits of the actual hash used by github for tagging the commit the build refers to. This should allow for precise identification of builds for bug reports, testing etc.

[JazHaz]

Couple of questions.

1) Why aren't the nightlies for 1.78 instead of 1.79?

2) Is the oolite_x64.app directory reverting back to the oolite.app directory?

[Gimi]

Couple of questions.

1) Why aren't the nightlies for 1.78 instead of 1.79?

2) Is the oolite_x64.app directory reverting back to the oolite.app directory?

If I have understood this correctly 1.78 will be the next stable release based upon 1.77 and replacing 1.76 stable.
1.79 (under development) will eventually become 1.80 stable at some point in the future.

Edit: This didn't really answer your question, did it....

[another_commander]

Couple of questions.

1) Why aren't the nightlies for 1.78 instead of 1.79?

Because 1.78 is not a development version, it is essentially 1.77.1 plus whatever fixes might go in until it is decided that it gets released, which is pretty much next to none for the moment. Not very interesting, really. 1.79 is where all the new development happens and what we want to have tested.

2) Is the oolite_x64.app directory reverting back to the oolite.app directory?

The oolite_x64.app folder was named like this in order to be able to be copied directly inside an existing Oolite installation and run side by side with the 32-bit version residing in oolite.app. With the nightlies coming back in, this is no more relevant. The nightlies get installed separately from the standard game as it's always been the case and there is no need to name the app folder differently. In short, the answer is yes.

[Duggan]

Thank you for the new trunk game, I am very much enamoured with the new features and effects (no spoiler's here).

I would like to ask if there is anything I can do viz a viz key config to get my steering back in the 2 (down), 8 (up) 4 (left) 6(right) key grid to the right of the Enter/Return key please.

Though I do not doubt , given patience and practice, I could get used to the < > keys.

Wonderful work guy's thank you for all your effort and hard work .

[cim]

Number pad and arrow keys are separated out now, so you should be able to go back to the numpad for flight by editing your keyconfig.plist. The numbers are 310=numpad0 .. 319=numpad9 so

Code: Select all

   key_roll_left            = 314;      // Numpad 4
   key_roll_right            = 316;      // Numpad 6
   key_pitch_forward         = 318;      // Numpad 8
   key_pitch_back            = 312;      // Numpad 2

You may or may not want to also change the key_gui_arrow_... settings similarly - if you don't, it'll be numpad for flight, and arrow keys for GUI screens (e.g. market)

[Duggan]

Thank you cim,

In my attempt to replicate the keyconfig plist of 177.1 I now have the following;

{
key_roll_left = 253; // left arrow
key_roll_right = 252; // right arrow
key_pitch_forward = 318; // up arrow
key_pitch_back = 312; // down arrow
key_yaw_left = "314";
key_yaw_right = "316";

I note however that in 177.1 and previous versions I could also use the up and down below the shift key in addition to 8 and 2 key to perform the same functions and now my up and down keys are exclusively the 8 and 2 keys respectively. This is not a complaint though, rather an observation. I was obviously spoiled in previous versions .