Oolite Bulletins

DeathKnyte wrote:

F2 screen > Game Options... > Spoken Messages = On

DeathKnyte wrote:

I wouldn't think so, like if my car engine is making noise (or not), it should not matter which windshield I'm looking out of. But again, I don't know how computer programming works.
However, upon even further testing, I have now discovered that I don't have to change view screens. The engine sound(s) will stop, start, remain intermittent as well - even when I have them completely turned off (speed = 0). This is beginning to become a very deep mystery...

JazHaz wrote:

Can the docking sequence also be improved?

Svengali wrote:

JazHaz wrote:

Can the docking sequence also be improved?

Yes, it can be done - I only haven't got the right idea yet...

El Viejo wrote:

<puts his thinking sombrero on, and summons his awesome graphics abilities>

Svengali wrote:

El Viejo wrote:

<puts his thinking sombrero on, and summons his awesome graphics abilities>

<leans back, opens a bottle of his finest and awaits patiently results>

El Viejo wrote:

Ha... there are two 'if onlys' there: oh that I could, and oh that I could join you! Single malt, yes... Knockando?

doctorfrog wrote:

Is there a setting for idle engine or cockpit noise? I'd like to mod in a quiet background hum that is always present when in your ship, but generally noticeable when thrust is set to zero. What I have right now is a quiet, phased effect that sounds like a life support system doing its work, interspersed with very quiet scanner pings. The idea is to breathe a bit more life into those moments when your thrusters aren't on.

doctorfrog wrote:

One of my goals is to eventually create my own modification of BGS with 'harder' space sounds. I may or may not succeed in this, but at the very least, I'll be replacing quite a few of the defaults.

doctorfrog wrote:

Is there a setting for idle engine or cockpit noise? I'd like to mod in a quiet background hum that is always present when in your ship, but generally noticeable when thrust is set to zero. What I have right now is a quiet, phased effect that sounds like a life support system doing its work, interspersed with very quiet scanner pings. The idea is to breathe a bit more life into those moments when your thrusters aren't on.

while(i--){
		if(cond===b[i].start){
			if(b[i].src===1){
				b[i].init = 1;
				if(c && player.ship.scriptInfo.bgs_engine) b[i].sound = player.ship.scriptInfo.bgs_engine;
			}
			if(c && b[i].change===1 && player.ship.scriptInfo.bgs_engineUp) b[i].sound = player.ship.scriptInfo.bgs_engineUp;
			if(c && b[i].change===-1 && player.ship.scriptInfo.bgs_engineDown) b[i].sound = player.ship.scriptInfo.bgs_engineDown;
			b[i].cmp = 0;
			a.push(b[i]);
		}
	}

Diziet Sma wrote:

... but I wouldn't be surprised if it affects at least some other joystick users too.

Diziet Sma wrote:

Unfortunately, there is a certain small amount of random "jitter" present when the throttle is set to minimum or maximum. (this is also the reason "dead-zones" are needed for joysticks) Oolite itself ignores this, and the engines won't come "on" until a definite movement is applied to the throttle.

BGS, however, reacts to every tiny random jittering change in throttle value by triggering the engineUp and engineDown sounds.

Diziet Sma wrote:

Re-reading the code, I think I may have located a possible solution..

switch(this.bgsCurrentSet[i].change){
  case 1: if(cu>this.bgsCurrentSet[i].cmp) this.changePlay(this.bgsCurrentSet[i],1); break;
  case -1: if(cu<this.bgsCurrentSet[i].cmp) this.changePlay(this.bgsCurrentSet[i],1); break;
  case 0: if(cu!==this.bgsCurrentSet[i].cmp) this.changePlay(this.bgsCurrentSet[i],1); break;
  case 2: if(cu!==this.bgsCurrentSet[i].cmp) this.changePlay(this.bgsCurrentSet[i],1); break;
}