Oolite Bulletins

cim wrote:

(Mission offer on dock should probably move to an interface screen anyway, of course)

this.showScreen = "firstPage"; // default page (used, unless there were pending messages).

Eric Walch wrote:

But I noticed that during the "this.startUp" handler, the station is the main station, even when loading a game saved at a seedy bar. This should be the place for a script to check were he is at the start in my opinion.

cim wrote:

There is, however, a new startUpComplete handler which runs after the populator and after the player has been placed in the correct station.

Eric Walch wrote:

@Thargoid: Yes it is big now. Was big already though. I downloaded it from the new http://addons.oolite.org/ pages so no hickups in Oolite itself. But I have a connection of 11 MByte/sec, so 108 MB takes here about 10 seconds downloadtime.

I think it's my machine (which is low spec) rather than the download speed itself. I can manually download the file in about 30-40s (not quite as quick as you ), but if I try to do it in-game then things become non-responsive. But it takes a couple of minutes for the game to start-up (after a trunk build), hence the thought about it being the machine.

As I said I'm just concerned that such delays may put newer players with similar low-spec machines off either the OXZ or the whole game.

Eric Walch wrote:

But it still doesn't do nothing, so the script probably needs more things to set instead of just calling the ShipDockedWithStation handler to make it work correctly without launching first. So I have some work to do.

spara wrote:

About the size. Maybe the extension manager could show some warning when the size is over some limit? With 1.79 it's also possible to chop the oxp into core + additional ship sets. That would naturally require some rewriting of the code.

Thargoid wrote:

You can do it without re-writing anything, just packaging things up differently. Just split it into multiple OXZs (say a core one plus one or more shipset ones) and make each OXZ require all of the others. Then once loaded nothing has changed, but you can download them in smaller chunks rather than all at once.

spara wrote:

If I'm not totally mistaken, you'll need to set this.random_hits_docked = true after calling this.shipDockedWithStation(). That's how I got it to work.

this.startUpComplete = function (){
    if (player.ship.docked && player.ship.dockedStation.name === "A Seedy Space Bar"){
        this.shipDockedWithStation();
        this.random_hits_docked = true;
    }
};

Thargoid wrote:

Just make the large one conflict with each of the group ones, and the group ones individually conflict with the large one.

• You have a clear separation of functionality between components so you can usefully install only some (e.g. "Povray Planets" or "Your Ad Here!")
• You want to separate assets and config (e.g. "Griff's Shipset"), because you expect the config to change more frequently than the assets and don't want to force a redownload of the assets every time, or because you want to have multiple configs for the same assets - in that case, the config should depend on the assets, and the assets could add the config(s) to their optional list

Diziet Sma wrote:

I'm wondering how much of this download difficulty is due to the download method Oolite uses, and also perhaps the Wiki software involved.

I can manually download the file in about 30-40s (not quite as quick as you ), but if I try to do it in-game then things become non-responsive.

Diziet Sma wrote:

On the other hand, how well does the Wiki software and server cope with multiple simultaneous large downloads going on? If a number of large downloads are going on at once, as may well happen after a new release of a popular OXZ, are some connections timing out, perhaps, as the server struggles to serve all requests in a timely fashion?

Diziet Sma wrote:

Server load could have dropped considerably in the time between Thargoid trying to download via the OXZ Manager, and downloading via his browser.

maik wrote:

Good question. I don't know the server's specs off the top of my head but I recall they were mentioned on the BB after a server switch took place. It wasn't too shabby though. I'd be surprised if it wouldn't be able to answer hundreds of parallel download requests, which seems absurdly high.