2) is not a good solution, because it's a nice OXP (I'm getting used to it ),
3) would be: Install System Redux, and do the fiddling yourself. Obviously not a good solution for the general public...
CapnKev, what if you do two versions: Your own preferred one and a strict one , which only textures the main planet and does nothing else?
And I think the OXP-page has already the list you are looking for. Look at the list named Other System Objects.
This doesn`t, for example, list Assassins, and who knows what else not.
And I think the OXP-page has already the list you are looking for. Look at the list named Other System Objects.
I was hoping for something like;
mission_assassins - 13, 18, 53, 81, 82, 107, 194 and 203 in galaxy 7
another_commander wrote:
Just to give credit where credit is due: The procedural textures code is not written by me. It is either by Ahruman or Aegidian and can't be really sure about this because I entered the community after or about at the time this feature was programmed in.
I think it was Dajt.
Download Fighter HUD, Stingray and System Redux from the EliteWiki
Oops, you're right. I can't find one as well in my copy (or to be precise: my Mac's search tool can't find one). Hmmm. But then, where does "Lave Purple Moon" come from? I mean, I even know it with that name. Is it from Status Quo? Unfortunately my pdf-version refuses to be scrutinized by my Mac's search tool.
Status Quo does give Lave a moon... can't find any reference to a purple one, though!
No. Sorry for sliding off-topic again. dajt did create a version featuring textured planets, but there were only two texture types available: Earth-like and Mars-like. This version was branched off the main code tree. At the same time more or less, Giles or Ahruman had developed their own version of textured planets in the engine, which is what we have at the moment, although in a dormant state. In this implementation, each planet has its own texture, created by the engine during system generation using a certain algorithm (hence the term procedural). The same planet has always the same texture.
Hey, nothing to be sorry about It's just that there seems to be a general misunderstanding regarding the textured planets thing and I just wanted to clear it up as much as possible for all.
I was giving Lave only as an Example. And only to give it a unique texture.
That won't intefere with the Lave OXP. Or am I wrong?
@ CaptKev: BTW I find the lastest version a whole lot better so keep up the good work !
About the procedural textures. Wasn't Hoopy working on that? and I said the OXP could be a combination of ranomized planets and planets with the current texture set and randomize that too!
Just to give credit where credit is due: The procedural textures code is not written by me. It is either by Ahruman or Aegidian and can't be really sure about this because I entered the community after or about at the time this feature was programmed in.
The risks of not reading back-thread. Actually I meant Hoopy's procedural approach, not a_c's. (Mixed you two up; won't happen again. )
Anyway, having said that, I also wasn't precise, as you, a_c, kindly remind me.
So what I really wanted to say is:
I'm still waiting for Hoopy's (which probably involves other people as well) overhauling of the procedural textures.
hello. I'm aiming to get the procedural generator released as an application (with source code) where you set a few parameters, press a button and it saves out the texture.
Then we can all play with it to find some good sets of parameters and some of the objective C people can look at how it could be ported to fit into Oolite.
Real life is busy at the moment (have you notice how quiet I've been?) but I may get an evening or two at it in a couple of weeks.
What you’re seeing is ”z-fighting”. Two concentric planets (or a planet and a cloud layer) are too close together, causing their polygons to overlap imperfectly.