Oolite Bulletins

Hi all. This is my first post on this side of Riedquat. Playing Elite since the 80s, mainly on Archimedes. I've been reading this forum and playing Oolite for a couple of years.

I voted against: all HUDs are software lincenced by CC-BY-NC, so why pay for them?

I like the idea of separating the HUD from the cockpit: a ship comes with a cockpit, the pilot choses his or her most effective HUD. I'd be prepared to pay for a new cockpit. In cockpit view, the HUD elements could be mapped onto several screens of the cockpit. In the front window view, I'd like to see my favourite HUD pretty much as it works now. I guess this would be a change to the core game, because I think an OXP cannot add a new view.

Would it be possible for a "cockpits OXP" to display a different cockpit depending on ship type? I guess such an OXP would define cockpits for standard ships (also perhaps for very popular OXP ships) and would provide for a mechanism for ship designers to integrate the cockpits of their ships with the "cockpits OXP". Such an OXP could use the Oolite HUD system as it currently is.

Hi Gimbal Locke, welcome to the friendliest board this side of Riedquat (tm).

You've made a small error in your post - "buy" in this sense means that a player must hand over Credits in the game to acquire their shiny new HUD (just like other equipment - lasers, Nav aids, etc...)

Oh, and the CC-BY-NC license does not necessarily forbid (re)sale of anything: http://wiki.creativecommons.org/Frequen ... icenses.3F

Gimbal Locke wrote:

I voted against: all HUDs are software lincenced by CC-BY-NC, so why pay for them?

Hi, Gimbal Locke, welcome to the friendliest one this side of Riedquat...

I think you got it wrong, we're discussing about selling them in-game in the shipyard, and not on RL e-bay or something...

As it stands now, the players have to be careful to remove an old HUD OXP from the Addons folder before adding a new one or they'll conflict, but if they were to be bought and sold as other normal equipment, the player could safely have as many as desired in the folder without problems.

EDIT: ninja'd!

Thanks Daddyhoggy & Cmdr. Maegil for the warm welcome.

I'm well aware we're discussing in-game credits here, I was absurdly extending the CC-BY-NC license into the ooniverse itself - perhaps my sense of humour is too weird. But Daddyhoggy's link is interesting nevertheless, thanks for pointing out that there are subtilities to the NC clause.

I see how Maegil's reasons for having sellable HUDs make sense. I've always been using HUDs which I combined from HUDs I downloaded, I like very much how easy this is with Oolite - my current HUD is based on Smiv's Combat HUD and Deepspace's HUD. I tune my HUD to be exactly as I want it (well... trying to get as close as possible to that), therefor I was never really interested in having more than one HUD in my AddOn folder.

Cheers,
Gimbal.

Cmdr. Maegil wrote:

As it stands now, the players have to be careful to remove an old HUD OXP from the Addons folder before adding a new one or they'll conflict, but if they were to be bought and sold as other normal equipment, the player could safely have as many as desired in the folder without problems.

Let's knock that misconception on the head before it gains currency. No, they couldn't. They could have several, not an unlimited number, provided all of them were correctly scripted. That will never happen, not because it couldn't happen, but because of "human factors".

Gimbal Locke wrote:

I'm well aware we're discussing in-game credits here, I was absurdly extending the CC-BY-NC license into the ooniverse itself - perhaps my sense of humour is too weird.

I understood your remark as you intended it, but you'll find a lot of the posters here tend toward "over-literal" interpretation.

There is some appeal for me ,in starting out with a bare bones functional HUD and having then ( as ones balance increases) the option to add one's preferred bells and whistles. After all the Game is ostensibly already as individual as the player playing it viz a viz Expansion Pack preferences