Page 6 of 6

Posted: Wed Mar 05, 2008 7:29 pm
by Leroy Boyce
Sung wrote:
I'm often rendered in C4D some Planets for other projects. I have made some planet tiles like this:

Image

after rendering it looks like this

Image

is it planned to get some detailed planets with a small texture map?
Elite 4 become true? :D
These are magnificient.

Now, if there were a gas-giant with rings, I'll think I'm in heaven...!

Posted: Wed Mar 05, 2008 10:30 pm
by CaptKev
If only we could persuade Ahruman and another_commander to enable the textured planets *sigh*

Posted: Wed Mar 05, 2008 10:39 pm
by LittleBear
Think they are comming back for 1.71, but in the meantime you can use the 1.65 alternate build by D.

I thinbk we can

Posted: Wed Mar 05, 2008 10:40 pm
by Lestradae
If only we could persuade Ahruman and another_commander to enable the textured planets
I would assume that in 1.71 the function will be possible to enable again. But perhaps we should start a planetary textures appreciation thread in the Suggestions Forum, with the petition to enable it again. I would second this ...

8)

L

P.S.: @Little Bear - we posted at the same instant, obviously :idea:

Posted: Wed Mar 05, 2008 10:46 pm
by JensAyton
Lobbying isn’t likely to have much effect, but you can always start a poll on whether people would prefer 1.71 to be delayed just to implement your pet feature. ;-)

@Ahruman

Posted: Wed Mar 05, 2008 11:13 pm
by Lestradae
Hi Ahruman,

OK, jokes aside.

I think the planetary texture feature is one many people would love to have back on.

I also think that you are doing a great job for the heck of it (can`t be mentioned enough imo) and so I would not in earnest attempt to pressure you to do this or that. Probably couldn`t if I tried, but don`t want to anyways :)

And I do understand that the textures seem to be a buggy feature and to find it`s causes is not up there on your to-do list.

But. I think nothing speaks against implementing the feature as an alternate option to switch the planetary textures back on, am I right or not?

If there´s something I don`t get here please tell me and I promise I`ll stop mentioning it. I just don`t understand why it can`t be inserted back in as OPTIONAL. :?:

All clear?

Greetings,

L

Posted: Wed Mar 05, 2008 11:24 pm
by CaptKev
How about the facility to add a planet with a particular radius?

Code: Select all

radius = system.mainPlanet.radius + 1;
system.addPlanet("my_shiny_new_planet", radius);

Posted: Wed Mar 05, 2008 11:57 pm
by JensAyton
Planet radii can be specified in planetinfo.plist. I don’t intend to add more dynamic ways before the MNSR for reasons of wanting to get a release out some time this century.

Posted: Thu Mar 20, 2008 3:41 am
by Catsy
I am wholly sympathetic to those with low-end systems, or who have decent systems but want to keep things lean and smooth, or don't have a lot of hard drive space to throw around.

By the same token, surely those with high-end systems could be allowed to make the choice of whether or not they want to take the hit in overhead? I have two terabytes of hard drive space between my computers, and I'm perfectly willing to give up a couple gigs of HD space to have Oolite dump procedurally-generated planet textures out to a file, so that they can be read with less overhead. And I've got a fast CPU and video card, and am not especially concerned about computationally expensive operations. :)

Like I said, I completely understand the need to design so that Oolite is accessible to low-end systems. But I'm all in favor of allowing folks the option to take the hit and turn on the pretty.

Posted: Thu Mar 20, 2008 5:56 am
by Wolfwood
Yup, if a poll is taken, my vote goes to textured planets! :)

Posted: Thu Mar 20, 2008 9:14 am
by TGHC
Catsy wrote:
I am wholly sympathetic to those with low-end systems, or who have decent systems but want to keep things lean and smooth, or don't have a lot of hard drive space to throw around.
It's probably a subconsience inheritance of the original restrictions, the way technology is racing ahead with speed and memory, size should not be a constraint.