Oolite Bulletins

JazHaz wrote:

Svengali wrote:

The update is only scripting related and fixes missing identifiers in the lookuptable (snoopers.js) and adds a missing check for 'SHADERS_NOT_SUPPORTED'.

Does Snoopers use Shaders then? What for?

Fabulous animated backgrounds in the mission screens!

DaddyHoggy wrote:

JazHaz wrote:

Svengali wrote:

The update is only scripting related and fixes missing identifiers in the lookuptable (snoopers.js) and adds a missing check for 'SHADERS_NOT_SUPPORTED'.

Does Snoopers use Shaders then? What for?

Fabulous animated backgrounds in the mission screens!

Brightness control .-) It was added because between v1.72 and v1.73 the lightning situation changed and we needed a mechanism to set it for the logos. The mechanism is still there and someday we will polish the whole thing a bit with the new Oolite-features.

v2.0.2 and v1.0.2 are online.

Please note that 1.x versions are discontinued and it's only a fix for ATI's.

Changes (for v2.0.2):
- Fixes for ATI cards
- Decreased time between newsflashes, based on inserted news
- Overhauled CRC storage

Just passing through so to quickly answer your PM - yes I have started on G2 news, but I'd have to write an essay on how crazy RL(tm) is at the moment!

Stay tuned... (fnarr, fnarr)

Has anyone tested the 2.0.2 version with the new 1.74?

It's installed but I didn't get any newsflashes when playing last night so hard to tell if there's a problem or not

Hi, I am on 1.74 (Snoopers2.0.2) and got a newsflash. Everything looked fine, I'll see if any more appear

1.74 and Snoopers 2.0.2 (along with Bloomberg Markets 2.0) gives me this:

Muchas gracias Zieman.

Haven't checked anything after 2.0.2 release anymore (and no other oxp stuff), because my machine didn't liked trunk after r3248 and I've concentrated on tweaking my system. It's still not completely sorted and seems to be related to the FSB clock in relation to the CPU P-states (dynamic switching, no throttling), but after some more tweaking it runs again a lot better.

The prob is that .split() is working different for numeric values in mission variables. Haven't seen this error (maybe overlooked) when 2.x was released - will add a regexp to check if divider is there or not (even if it's slow). Funny. But the good thing is that the other changes will be in the next version too. If you don't want to wait until the next version, replace snoopers.js line 95 with the following code: And to make it complete.
SE-main-script.js points to a not existing key SE_market_information. Change line 100 to Edit: Will give Ramirez a pm.

Svengali wrote:

If you don't want to wait until the next version, replace snoopers.js line 95 with the following code:

Code: Select all

	if(missionVariables.snoopers_CRCNews){
		if(String(missionVariables.snoopers_CRCNews).search(/[|]/)!=-1) this.CRCNews = missionVariables.snoopers_CRCNews.split('|');
		else this.CRCNews[0] = missionVariables.snoopers_CRCNews;
	}

And to make it complete.
SE-main-script.js points to a not existing key SE_market_information. Change line 100 to

Code: Select all

mission.setInstructionsKey("SE_sp_market_information")

Edit: Will give Ramirez a pm.

I can make the first change fine, but the second seems to be an if statement and doesn't make sense?!

Svengali wrote:

The prob is that .split() is working different for numeric values in mission variables.

That’s because numerical mission variables are always returned as numbers, not strings.

For legacy-compatibility reasons, mission variables must be stored as strings internally. The options are:

1. Convert numbers to strings on assignment, but always retrieve strings.
2. Convert numbers to strings on assignment, and convert strings that are valid numbers to numbers when retrieving.
3. Require all mission variables to be converted to strings by the script.

All of these options have obnoxious effects in some cases. I believe option 2 is least bad. In any case, it is now entrenched.

To check the type of a mission variable, use: typeof missionVariables.foo === "number" (or "string" as appropriate). JavaScript technicality: in either case, the value will be a primitive, not a wrapper.

:°) Thanks Ahruman.

@JazHaz: Are you really looking at the right script?

Anyway - Snoopers 2.0.3 is online and Ramirez said BlOomberg will follow soon.

Changes:
- Changed mixture of injected and internal message to 70/30
- Fixed wrong type for positions for injected models when reloaded game has stored them.
- Fixed setUp error with stored CRC.

Wow, that was quick!

Thanks.

v2.0.4 is online.

Changes:
- Faster.