2k DDS texture pack for newbies

[Fenerit]

Ok, Fridger. The pack 3 not the 4 haven't the directory structure, this is escaped from my operations. I've installed now Celestia 1.5.0 pre on this machine. I'm testing...

[t00fri]

Wenn you do a DXT archive, it must be tested whether the compression went without errors (corruption). That's why I always download it again, unpack it and test it with my installation before publishing it.

Bye Fridger

[Fenerit]

Wenn you do a DXT archive, it must be tested whether the compression went without errors (corruption). That's why I always download it again, unpack it and test it with my installation before publishing it.

Bye Fridger

I've repeated that operation for this machine now and I've rebuild the paths of vol 3. and for now Venus, Titan and other work fine; for Pluto I've found another problem. The file solarsys.ssc.1.5.0 when activated do miss Pluto. I've checked with the original: it's identical and not depend from textures, because it vanish from the solar system independently from the file extensions. When the original is reactivate, Pluto re-show itself: That is the Pluto code of my .SSC:

"Nereid" "Sol/Neptune"
{
Mesh "asteroid.cms"
Texture "asteroid.dds"
Radius 170

# Figure of 11.52 +/- 0.14 hours from Grav, T. et al. (2003)
# "The Short Rotation Period of Nereid", ApJ 591

RotationPeriod 11.52

EllipticalOrbit
{
Epoch 2447763.5 # 1989 Aug 25 00:00UT (Voyager encounter)
Period 360.13619 # mean
SemiMajorAxis 5513400 # mean
Eccentricity 0.7512 # mean
Inclination 28.385 # at epoch
AscendingNode 190.678 # at epoch
ArgOfPericenter 17.690 # at epoch
MeanAnomaly 36.056 # at epoch
}

Albedo 0.155
}


ReferencePoint "Pluto-Charon" "Sol"

{
CustomOrbit "pluto"
}

"Pluto" "Sol"

{
Texture "pluto-lok.dds"
SpecularTexture "pluto-lok-spec.dds"
SpecularColor [ 0.135 0.12 0.08 ]
SpecularPower 9.5

Radius 1151

OrbitFrame {
EclipticJ2000 { Center "Sol/Pluto-Charon" }
}

BodyFrame {
EclipticJ2000 { Center "Sol/Pluto-Charon" }
}

EllipticalOrbit
{
Period 6.387246
SemiMajorAxis 2411 # mass ratio of 0.123
Eccentricity 0.0002
Inclination 115.602
AscendingNode 228.328
ArgOfPericenter 47.314
MeanAnomaly 93.440
}

RotationPeriod 153.293904
Obliquity 115.60
EquatorAscendingNode 228.34
RotationOffset 320.75

Albedo 0.55
}

AltSurface "limit of knowledge" "Sol/Pluto"
{
Texture "pluto-lok.dds"
SpecularTexture "pluto-lok-spec.dds"
SpecularColor [ 0.135 0.12 0.08 ]
SpecularPower 9.5
}

"Charon" "Sol/Pluto"
{
Texture "charon-lok.dds"
SpecularTexture "charon-lok-spec.dds"
SpecularColor [ 0.135 0.12 0.08 ]
SpecularPower 9.5
Radius 593

InfoURL "http://www.nineplanets.org/pluto.html#Charon"

OrbitFrame {
EclipticJ2000 { Center "Sol/Pluto-Charon" }
}

BodyFrame {
EclipticJ2000 { Center "Sol/Pluto-Charon" }
}

EllipticalOrbit
{
Period 6.387246
SemiMajorAxis 17188 # mass ratio of 0.123
Eccentricity 0.0002
Inclination 115.602
AscendingNode 228.328
ArgOfPericenter 227.314
MeanAnomaly 93.440
}

RotationPeriod 153.293904
Obliquity 115.9
EquatorAscendingNode 227.3
RotationOffset 140.4

Albedo 0.35
}

AltSurface "limit of knowledge" "Sol/Pluto/Charon"

{
Texture "charon-lok.dds"
SpecularTexture "charon-lok-spec.dds"
SpecularColor [ 0.135 0.12 0.08 ]
SpecularPower 9.5

}



Note: Pluto is vanish even with .*

[Fenerit]

I've updated the 1 - 2- 3- 4- packs as until now found bugs.

Below there are the files .ssc rispectively: the main solarsys.ssc.bak; solarsys.ssc.1.4.1 and solarsys.ssc.1.5.0.

http://fenerit.webng.com/files/solarsys.ssc.bak.txt
http://fenerit.webng.com/files/solarsys.ssc.1.4.1.txt
http://fenerit.webng.com/files/solarsys.ssc.1.5.0.txt

I've found an "official" versions of Celestia 1.4.1 where Pluto doesn't show itself in solarsys.ssc whereas being in 1.5.0; centered with an ensemble of directives quitted for 1.4.1. When I'd attempted to estract from the relevant asteroid.ssc the Pluto's strings to the main solarsystem.ssc, they does weren't work.

So, I don't know where Pluto is in other installations. The strings early installed by me were updated from the relevant tour's script (add-on?). I know now that the solarsys.ssc for the 1.5.0 has the same problem.

Time to change machine and I'll show what i've said for Uranus and the Pluto strings away from the 1.4.1. solarsys.ssc.

[Fenerit]

Just for the "paranoid checking" I've check now the Pluto's tours and there isn't track of .ssc. Surely it's my memory to lack in where I've found Pluto. So, if I should be crazy, or Celestia is under a reverse engineering attack, please Selden: do erasing completely this thread and myself will erase the web page about 2k the texture pack.

[selden]

Fenerit,

I'm not at all sure what you mean, but

v1.4.1 solarsys.ssc does not work with v1.5.0
v1.5.0 solarsys.ssc does not work with v1.4.1

also
v1.4.1 cel:/urls do not work with v1.5.0
v1.5.0 cel:/urls do not work with v1.4.1

They all give the wrong results when used with the other version of Celestia.

v1.5.0 has many incompatible changes.

[Fenerit]

Fenerit,

I'm not at all sure what you mean, but

v1.4.1 solarsys.ssc does not work with v1.5.0
v1.5.0 solarsys.ssc does not work with v1.4.1

also
v1.4.1 cel:/urls do not work with v1.5.0
v1.5.0 cel:/urls do not work with v1.4.1

Ok, these are the Pluto strings which are in asteroids.ssc of Celestia version 1.4.1:

http://fenerit.webng.com/files/pluto_strings.txt

When I've tried to paste it in the solarsys.ssc of 1.4.1, Pluto disappear from solar system database. It reappear only with these strings in asteroid.ssc; which seem straight inexistent for DanielJ. For what concern the 1.5.0, Pluto IS in solarsys.ssc but when I've made the 1.5.0 .ssc for the 2k texture pack, pratically identics with the exception of having DDS textures, this file doesn't show Pluto in the database, nor as blank spheroid or the label "Pluto" high on left of the screen; and yet the strings they are.

[selden]

Fenerit,

Please do not edit solarsys.ssc
It is too easy to make mistakes and damage it in ways that cannot be seen.

When providing new textures, you do not need to touch solarsys.ssc at all.

Here are three different ways to add new textures:

1. The easiest way to provide just one set of textures is to give them the same names as the existing textures and put them in Celestia's folder \textures\hires\
Then the user can select between the old textures and the new textures by typing "R" and "r"
No new ssc is required. No changes to solarsys.ssc are required.

2. If you want to allow people to select different textures, but want to provide them as a separate Addon with its own directories in \extras\, create a .ssc which contains AltSurface statements:

mytextures.ssc could contain

Code: Select all

AltSurface "2K_Textures" "Sol/Pluto" { Texture "pluto_2k.*" }
AltSurface "2K_Textures" "Sol/Pluto/Charon" { Texture "charon_2k.*" }
AltSurface "2K_Textures" "Sol/Mars" { Texture "mars_2k.*" }

...etc...


Then the user can select "2K_Textures" and see the new 2K textures on all of the planets.

3. If you want to make a "permanent" change to solarsys.ssc, so a different texture name is used, create a .ssc which contains the Modify directive:

mypluto.ssc could contain

Code: Select all

Modify "Pluto" "Sol" { Texture "mypluto_hires.*"}

Then you could provide
a 2K mypluto_hires.dds in \textures\lores\
a 4K mypluto_hires.dds in \textures\medres\ and
an 8K mypluto_hires.dds in \textures\hires\
and use r and R to select among them.

[Fenerit]

Ok. I know this alternative methods. Less that the solarssys.ssc was soooooooo critical, expecially at EOF.

[Fenerit]

Ok. I've updated the packs, tested again the textures with another computer and changed the guide how to install it. Moreover, I've linked the bugs report to here and specifying that the textures are for Celestia 1.4.1 only.

[Fenerit]

Below there is a screendump of the gradius_fanatic 2k Uranus (above) and (below) the same texture as procedural 2k saved ad .PNG.
The artefacts has been removed by the procediment.

[danielj]

Ok,great,but is this texture partially fictious?

Below there is a screendump of the gradius_fanatic 2k Uranus (above) and (below) the same texture as procedural 2k saved ad .PNG.
The artefacts has been removed by the procediment.

[Fenerit]

Yes; it's fictious, as gradius_fanatic explain, but there isn't other which I know. Pratically seem that all planet's textures are fictitius, whether for the unmapping yet or for the planetary dynamics in certain cases (great spot on Neptune, for example). Also the Earth; look here about what happen to the Lake Meade:

http://www.forum.celestialmatters.org/v ... c&start=45

Note that in the previous shot I've made nothing else that wasn't to take the texture and tell to the texture tool of the 3d modeller of dealing as procedural, no retouch.

[t00fri]

Yes; it's fictious, as gradius_fanatic explain, but there isn't other which I know. Pratically seem that all planet's textures are fictitius, whether for the unmapping yet or for the planetary dynamics in certain cases (great spot on Neptune, for example). Also the Earth; look here about what happen to the Lake Meade:

http://www.forum.celestialmatters.org/v ... c&start=45

Note that in the previous shot I've made nothing else that wasn't to take the texture and tell to the texture tool of the 3d modeller of dealing as procedural, no retouch.

Fenerit,

the main point in Celestia's official visualization strategy is the consequent and strict reference to published scientific data, irrespective of their possible deficiencies! If we make additions/improvements to those data,. the changes MUST be clearly documented! If e.g. we add a layer of polar ice to the BMNG images, it's sources MUST be documented, etc.

Your Uranus texture above is just phantasy. A big difference in basic strategy.

In order to investigate the issue with the extent of that water arm of lake Meade, one should look into other base textures throughout the year 2004. The water in that arm may be generally shallow and the level of water different one year later.

-----------------------------------------------
With my F-TexTools it is less than 30 minutes of CPU time to just examine level 5 of another month of BMNG imaging data wrto lake Meade in 2004. All it takes in the respective command line, is the change in ONE number 200406 -> 200412, for example.
-----------------------------------------------

Bye Fridger

[Fenerit]

I've searched here and there on the web to find a good texture of Uranus, but I've fail. Take note that I myself want scientific textures, but seem that in case of this gas giant the only thing one can do is to map a slighty cyan monocolor; although here is seen storms in false colors (last image):

http://www.daviddarling.info/encyclopedia/U/Uranus.html

Fictional storms as in the texture above served to me as points in which to show the behavior of the procedural treatment, otherwise uncleared in monocromatic-like texture.

P.S.
I know you skepticism about fictional...