YOUR AD HERE!!! 300 ads (sets A, B, C, D, E, F & G)

[Smivs]

This is one of the best ones I've come across

[ADCK]

We've got one at the local train station in between the railway tracks, it says:

WARNING!
No Safe Place

With nothing else written on it, like no specifics where safety is, the sign leads me to believe no where in the universe is safe
I wanna steal 'Borrow' that sign and put it in silly places, like out the front of a candy store, a church, a pre-school, a police station, etc.

[Staer9]

what about this ad?

[Smivs]

Speaks volumes

[Dragonfire]

Mm, remind me to submit something for this for Dark Sky Industries when I release the OXP...

[DaddyHoggy]

Back to an Oolite related ad!

[Disembodied]

[Switeck]

I seem to be having problems sometimes when I jump to a new system that has a Constore in it. Memory usage by Oolite alone shoots up as high as 500 MB, typically reaching 300 MB...and jumps are going far slower than normal. And I spotted this in Latest.log:

05:03:04.796 [script.javaScript.exception.notFunction]: ***** JavaScript exception (ahruman-billboard-setup): TypeError: this.ship.setOrientation is not a function
05:03:04.796 [script.javaScript.exception.notFunction]: ../AddOns/YOUR_AD_HERE v4.1.7 MOD.oxp/Scripts/yah_asteroid-billboard-setup.js, line 6.
05:03:04.796 [script.javaScript.load.failed]: ***** Error loading JavaScript script ../AddOns/YOUR_AD_HERE v4.1.7 MOD.oxp/Scripts/yah_asteroid-billboard-setup.js -- could not run script
05:03:11.156 [shader.link.failure]: ***** ERROR: GLSL shader program linking failed for ahruman-generic.vertex/yah_griff_station_bottom_section.fragment:
>>>>> GLSL log:
Fragment shader uses varying vTexCoord but vertex shader does not write to it.

05:03:11.156 [shader.load.fullModeFailed]: ----- WARNING: Could not build shader ahruman-generic.vertex/yah_griff_station_bottom_section.fragment in full complexity mode, trying simple mode.
05:03:11.156 [shader.link.failure]: ***** ERROR: GLSL shader program linking failed for ahruman-generic.vertex/yah_griff_station_bottom_section.fragment:
>>>>> GLSL log:
Fragment shader uses varying vTexCoord but vertex shader does not write to it.

05:03:11.156 [shader.load.failed]: ***** ERROR: Could not build shader ahruman-generic.vertex/yah_griff_station_bottom_section.fragment.
05:03:11.281 [script.javaScript.load.failed]: ***** Error loading JavaScript script ../AddOns/YOUR_AD_HERE v4.1.7 MOD.oxp/Scripts/yah_asteroid-billboard-setup.js -- could not run script
05:03:11.281 [script.javaScript.exception.notFunction]: ***** JavaScript exception (Pi-Forty-Two Con stores 4.1.7): TypeError: this.ship.setOrientation is not a function
05:03:11.281 [script.javaScript.exception.notFunction]: ../AddOns/YOUR_AD_HERE v4.1.7 MOD.oxp/Scripts/yah_asteroid-billboard-setup.js, line 6.

[DaddyHoggy]

Eek! Shaders! Hopefully Eric W or Griff will be along shortly!

[Eric Walch]

Eek! Shaders! Hopefully Eric W or Griff will be along shortly!

I think this problem is caused by mixing old and new code when reading the logged error:

Code: Select all

05:03:04.796 [script.javaScript.exception.notFunction]: ***** JavaScript exception (ahruman-billboard-setup): TypeError: this.ship.setOrientation is not a function
05:03:04.796 [script.javaScript.exception.notFunction]: ../AddOns/YOUR_AD_HERE v4.1.7 MOD.oxp/Scripts/yah_asteroid-billboard-setup.js, line 6.
05:03:04.796 [script.javaScript.load.failed]: ***** Error loading JavaScript script ../AddOns/YOUR_AD_HERE v4.1.7 MOD.oxp/Scripts/yah_asteroid-billboard-setup.js -- could not run script

The file 'yah_asteroid-billboard-setup.js' should not be used at all in the current version. So one of the modules is still using the not-updated code. i assume the same is valid for the shaders.

I admit that it is a mess and I said it often before. All those updaters should be incorporated in the original. But I have no bandwith to store all those originals. I only have the very small updaters in my download area. For mac and windows that should be no problem because the load order makes that the updaters do overwrite the old code. Linux users however, must replace the individual files inside the oxp.
But, the only decent solution is to get rid of the updaters and upload fixed originals.

[Cmd. Cheyd]

As I am the unofficial clearing house of OXP's, would you like some space on Deep Horizon?

[DaddyHoggy]

As I am the unofficial clearing house of OXP's, would you like some space on Deep Horizon?

Hooray!

<virtual hug>

<cough>

<Manly slap on the back>

[DaddyHoggy]

Another potential rag - for those Snoopers roving reports (and they said it wouldn't be back!)

[JensAyton]

I thought they were calling it the Soon on Soonday now. Or at least soon…

[DaddyHoggy]

I thought they were calling it the Soon on Soonday now. Or at least soon…

In RL(tm) indeed they are - apparently that web domain was set up the same day the closure of the NotW was announced, but that could just be me being cynical...