Oolite Bulletins

Cmdr. Maegil wrote:

Maybe marking the ones that are mutually exclusive on, for instance, [wiki]OXP List[/wiki] or [wiki]Category:Ambience OXPs[/wiki] could be a good idea?

maik wrote:

I don't have a good idea how to use the OXP List for that. I'd much rather create a wiki page for Darkspace based on the content that Gimi provided which lists the known incompatibilities.

Gimi wrote:

If you set up the framework with the text i provided, I can meddle with the page myself. (I have a logon).
I can learn some more OXPing stuff.

• Navigate to a non-existent Wiki page, e.g. http://wiki.alioth.net/index.php/Darkspace
• Say that you want to create this page.
• Copy & paste the content of your first post in this thread
• Put two equal signs left and right of the headings, e.g. ==Dependencies==
• Wikify the links. If you link to another Wiki page, use double square brackets around the name. If you link to an outside URL, use single square brackets, like so:

  Code: Select all

  [[OXP List]], [[different name for OXP List|OXP List]], [http://www.somewhere.de This gets printed and will all be one link to the URL before the first space]

Gimi wrote:

Thanks for the info Maik. I have created the page,blatantly copying templates from around the Wiki, and also added it to the OXP List. Please shoot if I have broken anything. (Pulse laser only)

Gimi wrote:

This little OXP came to be because clearskies.oxp by johnsmith is broken and lacks a license. Johnsmith is a little hard to get hold of, so I thought I would learn a little OXPing by redoing the OXP.

 Darkspace.oxp removes the nebula from the sky and limits the number of stars visible, and thus should reduce strain on slower computer systems...

Version 1.0 will come when someone tells me what I have done wrong. There is bound to be something. (Even in something as simple as this.)

Wildeblood wrote:

Okay, I reckon you've done it wrongly. I would have just set sky_n_blurs to 0, rather than setting sky_blur_alpha to 0. If the intention is to reduce the workload on slower computers, not drawing any "blurs" (nebulosity) at all has to be the better option than drawing the usual number then making them transparent. (That depends on whether or not Oolite has enough sense to "know" that there's no point in drawing fully transparent details. One of the devs will need to answer that.) To be fair to johnsmith and Clear Skies, I think sky_n_stars and sky_n_blurs are recent additions that aren't in Oolite 1.65.

Switeck wrote:

I'm having a bit of variable confusion.
The original XML defined the variables as reals.

Code: Select all

<key>ambient_level</key>
<real>2</real>

This puts quotes around the numbers as though they're strings.

Code: Select all

ambient_level = "1.75";

Are the quotes needed?

{
	"universal" = {
		"ambient_level" = 2.0;
		"sky_blur_alpha" = 0.0;
		"sky_blur_cluster_chance" = 0.0;
	};
}

Gimi wrote:

When you do a xml to openstep convert using xml2ns.py you get this:

Code: Select all

{
	"universal" = {
		"ambient_level" = 2.0;
		"sky_blur_alpha" = 0.0;
		"sky_blur_cluster_chance" = 0.0;
	};
}

Well, that diden't work, so I basically started peeking (and pokeing) around to see what other people did and followed that.