OK, first I want to thank all those involved with the 1.5 effort, VERY GOOD.
I have found one thing so far. I had a add-on cloud map of Mars in 1.4 and a 3D model "mars-mons-valles-131.cmod". In 1.5, Olympus Mons sticks above the clouds. It might have in 1.4 (I never noticed it). I have edited the atmosphere height to 100 with no effect. What is the correct way to get the clouds above the 3D mesh? I have a normal and bump map but those are commented out.
One other item, I have Celestia running on a Mac and Win. The Sol texture is different on the Mac. I like the Mac look better than the PC. The PC looks the same as 1.4. Is this a known issue? I cycled (Ctrl V)through the OpenGL types with no change.
Thanks
Don
PS Not sure if this should have been in a new thread or is there an existing thread were these are address?
Anomalies in Celestia 1.5.0 for Win 32
Anomalies in Celestia 1.5.0 for Win 32
Don't know anything
-
- Site Admin
- Posts: 4211
- Joined: 28.01.2002
- With us: 22 years 10 months
- Location: Seattle, Washington, USA
Re: Anomalies in Celestia 1.5.0 for Win 32
DonAVP wrote:OK, first I want to thank all those involved with the 1.5 effort, VERY GOOD.
I have found one thing so far. I had a add-on cloud map of Mars in 1.4 and a 3D model "mars-mons-valles-131.cmod". In 1.5, Olympus Mons sticks above the clouds. It might have in 1.4 (I never noticed it). I have edited the atmosphere height to 100 with no effect. What is the correct way to get the clouds above the 3D mesh? I have a normal and bump map but those are commented out.
One other item, I have Celestia running on a Mac and Win. The Sol texture is different on the Mac. I like the Mac look better than the PC. The PC looks the same as 1.4. Is this a known issue? I cycled (Ctrl V)through the OpenGL types with no change.
Thanks
Don
PS Not sure if this should have been in a new thread or is there an existing thread were these are address?
I think 1.5 is doing the right thing. Did you edit CloudHeight?
--Chris
Yes, the default value was 30. I changed it to 100 but did not see any change. So I stopped. That was the reason for the post. Is this what is changed to make the clouds cover the top of the mountain?
I guess I can keep increasing the number but it did not see to be effecting the top of the mountain. Also I started noticing on the edge of the curve the planet a separation between the model and atmosphere not sure if this is related.
Don
I guess I can keep increasing the number but it did not see to be effecting the top of the mountain. Also I started noticing on the edge of the curve the planet a separation between the model and atmosphere not sure if this is related.
Don
Don't know anything
- cartrite
- Posts: 1978
- Joined: 15.09.2005
- With us: 19 years 2 months
- Location: Pocono Mountains, Pennsylvania, USA Greate Grandfother from Irshava, Zakarpattia Oblast Ukraine
I can get the clouds above Mt. Olympus by using atmosphere height to 30 and CloudHeight to 20. The CloudHeight can be a little lower but at 10, Mt. Olympus sticks out of the clouds.DonAVP wrote:I have edited the atmosphere height to 100 with no effect.
cartrite
VivoBook_ASUSLaptop X712JA_S712JA Intel(R) UHD Graphics 8gb ram. Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz, 1190 Mhz, 4 Core(s), 8 Logical Processor(s) 8 GB ram. Running on Windows 11 and OpenSuse 15.4
This is the basic 1.5 solarsys file.
I think I figured it out. Silly me, I was editing the first record after the word Atmosphere instead of the cloudheight. I changed the value from 10 to 20 and it worked. It could be less, I have not checked. I am using another partial definition in the extras folder that came with the large Mars mesh. Below is that definition.
A question, what does the height statement control so I will know in the furture?
solarsys.ssc Def wrote:Atmosphere {
"Mars" "Sol"
{
Texture "mars.*"
Color [ 1 0.75 0.7 ]
HazeColor [ 1 1 1 ]
HazeDensity 0.45
Radius 3396 # equatorial
# Oblateness 0.0069
Atmosphere {
Height 30
Lower [ 0.8 0.6 0.6 ]
Upper [ 0.7 0.3 0.3 ]
Sky [ 0.83 0.75 0.65 ]
Sunset [ 0.7 0.7 0.8 ]
# Slightly bluish sunset, as seen in true color pictures
# from Pathfinder
CloudHeight 20
CloudSpeed 70
CloudMap "MarsClouds.png"
Mie 0.0024
MieAsymmetry -0.15
Rayleigh [ 0.0010 0.0006 0.0003 ]
Absorption [ 0 0 0 ]
MieScaleHeight 20
}
CustomOrbit "vsop87-mars"
EllipticalOrbit
{
Period 1.8809
SemiMajorAxis 1.5237
Eccentricity 0.0934
Inclination 1.8506
AscendingNode 49.479
LongOfPericenter 336.041
MeanLongitude 355.453
}
UniformRotation
{
Period 24.622962
Inclination 26.72
AscendingNode 82.91
MeridianAngle 136.005
}
Albedo 0.150
}
}
I think I figured it out. Silly me, I was editing the first record after the word Atmosphere instead of the cloudheight. I changed the value from 10 to 20 and it worked. It could be less, I have not checked. I am using another partial definition in the extras folder that came with the large Mars mesh. Below is that definition.
Mars SSC Def wrote:Modify "Mars" "Sol"
{
Mesh "mars-mons-valles-131.cmod"
Texture "mars.*"
Radius 3396 #small
Atmosphere {
Height 50
Lower [ 0.8 0.6 0.6 ]
Upper [ 0.7 0.3 0.3 ]
Sky [ 0.83 0.75 0.65 ]
Sunset [ 0.7 0.7 0.8 ]
# Slightly bluish sunset, as seen in true color pictures
# from Pathfinder
}
Albedo 0.150
}
A question, what does the height statement control so I will know in the furture?
Don't know anything