Trunk nightly

[Rorschachhamster]

Huh, I had installed a newer trunk just over the installation... Trying to deinstall first, now.

[Diziet Sma]

Huh, I had installed a newer trunk just over the installation... Trying to deinstall first, now.

Heh.. there is an easier (and far less bandwidth intensive) way to update trunk in Windows, if you're willing to put in a little one-time-only effort.. after which, to update trunk you simply have to double-click a shortcut, which will then execute a script that will automatically download and install only the files that have actually changed, instead of having to download, uninstall, and reinstall the entire 100MB installer every single time. Then you can be just like us penguins, who only have to run 'oolite-trunk update' in a terminal window to update to the latest version!

Quoting the relevant parts from the Windows Nightly Builds thread:

Do you have a low-bandwidth high-latency internet connection
and it will take a life-time to download the latest nightly?
Are you away from home and your low download quota
keeps you away from that last fix that will let you get even with the six-limb race?
Do you envy the Linux commanders, as they don't have to download the full setup with every nightly release?

If you answered positively to at least one of these questions... keep reading.

Responding to the public's need, the Windows nightly service has been extended
to deliver "upgrade" functionality through rsync network protocol.

In that way, you can update your Oolite-Trunk installation to the latest nightly release,
getting the differences only.

Since rsync is not delivered with Windows, you can try cwRsync client.
(To be honest with the community, I have only tested the service with cwRsync.)

Having installed cwRsync, you can execute the following in a command prompt:

For 64bit Oolite-Trunk Windows installations:

Code: Select all

C:\>"c:\Program Files (x86)\cwRsync\bin\rsync.exe" -rlvz --progress rsync://terrastorage.no-ip.info/oolite-trunk-windows_x64/* /cygdrive/c/Oolite-Trunk/.

For 32bit Oolite-Trunk Windows installations:

Code: Select all

C:\>"c:\Program Files (x86)\cwRsync\bin\rsync.exe" -rlvz --progress rsync://terrastorage.no-ip.info/oolite-trunk-windows/* /cygdrive/c/Oolite-Trunk/.

Some hints:
The c:\Program Files (x86)\cwRsync\bin\rsync.exe and /cygdrive/c/Oolite-Trunk/. should be changed according
to your installation paths. For example D:\MyPath\Oolite-Trunk becomes /cygdrive/d/MyPath/Oolite-Trunk/.
If your Oolite-Trunk path contains spaces, do not use quotes.

EDIT: Note, that any missing file or any changed file that is part of the Oolite-Trunk original installation,
will be re-downloaded and overwritten!

...I had to tinker with the command line a little...

Hint: There is a cwrsync.cmd in the root installation folder of cwrsync.
Edit this and add the following line at the end of the file:

Oolite nightly 64bit

Code: Select all

"C:\Program Files (x86)\cwRsync\bin\rsync" -rlvz --progress rsync://terrastorage.no-ip.info/oolite-trunk-windows_x64/* /cygdrive/c/Oolite-Trunk/.

Oolite nightly 32bit

Code: Select all

"C:\Program Files (x86)\cwRsync\bin\rsync" -rlvz --progress rsync://terrastorage.no-ip.info/oolite-trunk-windows/* /cygdrive/c/Oolite-Trunk/.

If Windows is 32bit (and you have kept the original cwrsync installation) then you need to change the rsync path removing
the " (x86)" form the path. There is a space before the left parenthesis that needs to be removed too.
This line of code also assumes default installation path for Oolite nightly too... change it as per your needs... keeping the /cygdrive/ of course.

Create a shortcut of cwrsync.cmd wherever is handy for you and you are now one double-click away from rsync-ing getting the latest nightly!
(Cudos to AC for pointing this out!)

Showing my ignorance here perhaps, but if I add:

Code: Select all

"C:\Program Files (x86)\cwRsync\bin\rsync" -rlvz --progress rsync://terrastorage.no-ip.info/oolite-trunk-windows_x64/* /cygdrive/c/Oolite-Trunk/.

to cwrsync.cmd, it won't let me save it (using Notepad++). Instead, it asks me to check if this file is open in another program.
I'm obviously doing something wrong - so I'll use the manual method again.

@Cody
Execute notepad++ as administrator by right-clicking on notepad++ executable/icon.

Then open cwrsync.cmd.

Note that the path to the rsync file itself is a little different in the free version of cwRsync I downloaded from the above source, (there's no 'bin' folder, basically) so you may need to edit things a little..

Instead of cwRsync\bin\rsync, if you simply unzip the file it will be: cwRsync_5.4.1_x86_Free\rsync
Initially, I renamed the cwRsync_5.4.1_x86_Free folder to just cwRsync, and put it in the root of my C:\ drive, but for some stupid reason didn't realise there was no bin folder, and then wondered why things weren't working.

I'm guessing that perhaps Getafix and a_c purchased the commercial installer version, instead of the free zip file version.

Note also that you will most likely have to edit line 13 of cwrsync.cmd to point to the location where you placed the cwRsync folder.. in my case:

Code: Select all

SET CWRSYNCHOME=C:\CWRSYNC

For the record, I dragged the shortcut mentioned above to my start menu, which then offered to pin it to the menu.. so now it's super-easy to launch whenever I want.

[Cody]

<hugs updater>

[Rorschachhamster]

Me too.
Even if I haven't built my batch yet...

EDIT: Done and runs! Thank you even more much...

[Cody]

I've been grounded for a while, but I got out there tonight - and immediately got roughed-up by three ships. Two I splashed without too much trouble, but the third proved tricky and damaged some kit, including the TSME. This left me with one already locked-on hardhead - which I could not fire. Even after re-targeting, it refused to fire! Not seen that before - is that normal? There then followed a nice dogfight with the third ship - an Adder, of all things! Tough little blighter!

As regards the cloak: I'll have to test it some more, but it seems almost completely ineffective against wings of assassins and/or bandits now.

[cim]

I've been grounded for a while, but I got out there tonight - and immediately got roughed-up by three ships. Two I splashed without too much trouble, but the third proved tricky and damaged some kit, including the TSME. This left me with one already locked-on hardhead - which I could not fire. Even after re-targeting, it refused to fire!

Interesting. Not a case that's had much testing, I expect - I'll look into that more closely.

As regards the cloak: I'll have to test it some more, but it seems almost completely ineffective against wings of assassins and/or bandits now.

If you're the only hostile around, it's unlikely to get them to break target lock - but even token attempts at dodging should make you almost impossible for them to hit, and it should still stop them firing missiles.

Possibly that's slightly too ineffective ... on the other hand, NPCs cloaking against the player tend to just drain their energy to 50% without really helping their defence at all. It should still be good for sneaking up on / past wings.

[Cody]

... but even token attempts at dodging should make you almost impossible for them to hit...

Oh they were still hitting me whilst I was cloaked and dodging - heavy hits too!

[cim]

Oh they were still hitting me whilst I was cloaked and dodging - heavy hits too!

Skilled NPCs OXP, I would guess. I haven't tested the cloak behaviour with high accuracy opponents yet - I'll try to get that done soon.

[Cody]

Skilled NPCs OXP, I would guess.

<nods> Yeah, I should've removed that one - done!

On reloading last night's save (TSME still damaged), I can fire three missiles okay, but not the fourth!

[cim]

On reloading last night's save (TSME still damaged), I can fire three missiles okay, but not the fourth!

That's strange... Could you send me the savefile, please, if it's still broken on reloading!

I've managed to get this to happen briefly, so I should be able to track it down soon.

[Cody]

PM incoming!

[cim]

Hmm... hold on, the TSME appears to be a red herring. Loading a savegame with four missiles and intact TSME, launch, fire three at the nav buoy, the fourth won't fire. I'll keep looking.

EDIT: And should be fixed in tonight's build. Thanks.

[Cody]

... should be fixed in tonight's build.

Right on... and I'll go hunting red herrings tonight!

[Cody]

<chortles>

Code: Select all

18:47:49.952 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (Oolite Bounty Hunter AI 1.81): Unknown expansion key [oolite_entityClass] in string.
18:47:49.952 [script.javaScript.warning.ooliteDefined]:       Resources/Scripts/oolite-priorityai.js, line 388.
18:47:49.952 [script.javaScript.stackTrace]:  0 (oolite-priorityai.js:388) <anonymous function>
18:47:49.952 [script.javaScript.stackTrace]:     this: {...}
18:47:49.952 [script.javaScript.stackTrace]:     priority: 3
18:47:49.952 [script.javaScript.stackTrace]:     params: [Wormhole destination: Xegearer ttl: 43199.66s arrival: 2089571:21:44:53]
18:47:49.952 [script.javaScript.stackTrace]:     key: "oolite_beginningAttack"
18:47:49.952 [script.javaScript.stackTrace]:     message: undefined
18:47:49.952 [script.javaScript.stackTrace]:     template: "[commsPackA_mercenary_beginningAttack]"
18:47:49.952 [script.javaScript.stackTrace]:     recv: 180538975829.8927
18:47:49.953 [script.javaScript.stackTrace]:     send: 180538975829.8927
18:47:49.953 [script.javaScript.stackTrace]:  1 (oolite-priorityai.js:670) <anonymous function>
18:47:49.953 [script.javaScript.stackTrace]:     this: {...}
18:47:49.953 [script.javaScript.stackTrace]:     priority: 3
18:47:49.953 [script.javaScript.stackTrace]:     code: "beginning"
18:47:49.953 [script.javaScript.stackTrace]:     target: [Wormhole destination: Xegearer ttl: 43199.66s arrival: 2089571:21:44:53]
18:47:49.953 [script.javaScript.stackTrace]:     scan: "CLASS_WORMHOLE"
18:47:49.953 [script.javaScript.stackTrace]:     msgcode: "oolite_beginningAttack"
18:47:49.953 [script.javaScript.stackTrace]:  2 (oolite-priorityai.js:2913) <anonymous function>
18:47:49.953 [script.javaScript.stackTrace]:     this: {...}
18:47:49.953 [script.javaScript.stackTrace]:     handlers: {...}
18:47:49.953 [script.javaScript.stackTrace]:  3 (oolite-priorityai.js:224) _reconsider()
18:47:49.953 [script.javaScript.stackTrace]:     this: {...}
18:47:49.953 [script.javaScript.stackTrace]:     newBehaviour: function
18:47:49.953 [script.javaScript.stackTrace]:  4 (oolite-priorityai.js:75) _handlerAIAwoken()
18:47:49.953 [script.javaScript.stackTrace]:     this: {...}
18:47:49.953 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (Oolite Bounty Hunter AI 1.81): Unbalanced ] in string.
18:47:49.953 [script.javaScript.warning.ooliteDefined]:       Resources/Scripts/oolite-priorityai.js, line 388.
18:47:49.953 [script.javaScript.stackTrace]:  0 (oolite-priorityai.js:388) <anonymous function>
18:47:49.953 [script.javaScript.stackTrace]:     this: {...}
18:47:49.953 [script.javaScript.stackTrace]:     priority: 3
18:47:49.953 [script.javaScript.stackTrace]:     params: [Wormhole destination: Xegearer ttl: 43199.66s arrival: 2089571:21:44:53]
18:47:49.953 [script.javaScript.stackTrace]:     key: "oolite_beginningAttack"
18:47:49.953 [script.javaScript.stackTrace]:     message: undefined
18:47:49.953 [script.javaScript.stackTrace]:     template: "[commsPackA_mercenary_beginningAttack]"
18:47:49.953 [script.javaScript.stackTrace]:     recv: 180538975829.8927
18:47:49.953 [script.javaScript.stackTrace]:     send: 180538975829.8927
18:47:49.953 [script.javaScript.stackTrace]:  1 (oolite-priorityai.js:670) <anonymous function>
18:47:49.953 [script.javaScript.stackTrace]:     this: {...}
18:47:49.953 [script.javaScript.stackTrace]:     priority: 3
18:47:49.953 [script.javaScript.stackTrace]:     code: "beginning"
18:47:49.953 [script.javaScript.stackTrace]:     target: [Wormhole destination: Xegearer ttl: 43199.66s arrival: 2089571:21:44:53]
18:47:49.953 [script.javaScript.stackTrace]:     scan: "CLASS_WORMHOLE"
18:47:49.953 [script.javaScript.stackTrace]:     msgcode: "oolite_beginningAttack"
18:47:49.953 [script.javaScript.stackTrace]:  2 (oolite-priorityai.js:2913) <anonymous function>
18:47:49.953 [script.javaScript.stackTrace]:     this: {...}
18:47:49.953 [script.javaScript.stackTrace]:     handlers: {...}
18:47:49.953 [script.javaScript.stackTrace]:  3 (oolite-priorityai.js:224) _reconsider()
18:47:49.953 [script.javaScript.stackTrace]:     this: {...}
18:47:49.953 [script.javaScript.stackTrace]:     newBehaviour: function
18:47:49.953 [script.javaScript.stackTrace]:  4 (oolite-priorityai.js:75) _handlerAIAwoken()
18:47:49.953 [script.javaScript.stackTrace]:     this: {...}
18:47:49.953 [strings.expand.warning.unknownExpansion]: ----- WARNING: Unknown expansion key [oolite_entityClass] in string.
18:47:49.953 [strings.expand.warning.unbalancedClosingBracket]: ----- WARNING: Unbalanced ] in string.

[Cody]

Another planet-diver (after launching from a Torus station) to report - a lone Python.

Even with Skilled NPCs removed, those heavy assassins are hitting through my cloak with alarming regularity - and there seems to be more of them using injectors too. I run with a 0.5ly reserve tank as standard, and I've had to make use of it tonight. It's finely balanced - but life as an ace courier is definitely harder now.

Oh yeah - I've lost/forgotten the whereabouts/method of that order-of-kit thingy - help!