Page 1 of 1
Mercury-MESSENGER
Posted: 20.08.2008, 07:13
by John Van Vliet
--- edit ---
Re: Mercury-MESSENGER
Posted: 20.08.2008, 19:42
by danielj
Unfourtanetelly it didn?t work.In Celestia 1.5.1,See below:
I think Celestia don?t support PNG files anymore.
Re: Mercury-MESSENGER
Posted: 20.08.2008, 20:00
by John Van Vliet
--- edit ---
Re: Mercury-MESSENGER
Posted: 20.08.2008, 21:53
by John Van Vliet
--- edit ---
Re: Mercury-MESSENGER
Posted: 20.08.2008, 23:24
by danielj
.JPG is the termination of the picture I take of Celestia.
I changed the solarsys.ssc like this:
"Mercury" "Sol"
{
Texture "16k_map3.*"
Radius 2440
And the result is what you see in the pics I take from Celestia.Although it has 32.2 MB,the texture is ONLY 1k!
Re: Mercury-MESSENGER
Posted: 20.08.2008, 23:28
by danielj
One picture near:
It appears some compatibility problem.This is Limit of Knowledge.When I put Normal,Mercury seem all black and featurless.
Re: Mercury-MESSENGER
Posted: 20.08.2008, 23:39
by cartrite
Hey John,
Nice job. Did you use qnet to help assemble these?
cartrite
Re: Mercury-MESSENGER
Posted: 20.08.2008, 23:48
by symaski62
SPICE NAIF
Code: Select all
"Mercury" "Sol"
{
Texture "mercury.*"
Radius 2440
SpiceOrbit
{
Kernel "de406.bsp" # 300Mo -3000 & 3000 yaers
Target "199"
Origin "10"
BoundingRadius 1
Period 0.2408467
}
SpiceRotation
{
Kernel "pck00008.TPC"
Frame "IAU_MERCURY"
BaseFrame "eclipj2000"
Period 1407.5088
}
Albedo 0.06
}
AltSurface "limit of knowledge" "Sol/Mercury"
{
Texture "mercury.*"
OverlayTexture "mercury-lok-mask.png"
}
Re: Mercury-MESSENGER
Posted: 21.08.2008, 00:17
by bdm
john Van Vliet wrote:edit solarsys.ssc and change the name for the Mercury map to "1k_map3.png"
Editing the core files isn't recommended.
We can also change the Mercury texture with a Modify directive in a small SSC file in the
Extras directory with something like this:
Code: Select all
Modify "Sol/Mercury"
{
Texture "16k_map3.*"
}
(I haven't done a "Modify" file before so I don't know if it will work. The intent is just to modify what we want to change and leave the rest as is.)
Re: Mercury-MESSENGER
Posted: 21.08.2008, 00:26
by danielj
I think one of the problems is that it ISN?T A PERFECT FLAT PROJECTION CARTOGRAPHIC MAP!It is more or less irregular at the edges and I don?t know if it will work...
Re: Mercury-MESSENGER
Posted: 21.08.2008, 01:15
by John Van Vliet
--- edit ---
Re: Mercury-MESSENGER
Posted: 21.08.2008, 01:32
by cartrite
I see you were able to use mdis2isis. I was only taking a quick look and I didn't try because it looked like it wanted an IMA or LBL file. So I used pds2isis instead.
I see that you didn't use mdiscal? I'll have to take a closer look at these images.
QNET is part of ISIS3. I just started to use it to see if I can correct seams in CTX images. It's a pretty cool program. It allows you to create tie points to mend a lot of images together before cam2map is run. One of the features of this is a blinking tool. It allows you to shift one image a pixel at a time relative to the other while the two images "blink" back and forth to help with the alignment. It's still in development so the documentation is lacking and it's a little buggy. I was just wondering if you had used this before.
cartrite
Re: Mercury-MESSENGER
Posted: 21.08.2008, 02:55
by John Van Vliet
--- edit ---
Re: Mercury-MESSENGER
Posted: 21.08.2008, 15:22
by danielj
No,there is NO OTHER Mercury.ssc.
I give up,sorry...
Re: Mercury-MESSENGER
Posted: 23.08.2008, 23:02
by John Van Vliet
--- edit ---