brokfn wrote:It would be finer yet if the focus anomaly with the set time box could be fixed, but even then, this will be the most fascinating Celestia release ever!
brokfn wrote:Sure...
Try this: open set time box (focus is on the year). Click on the minutes. The focus comes to the minutes. Then click on the month: the focus comes to the month. Click on the year: the focus doesn't come to the year.
Bye,
Brokfn
PlutonianEmpire wrote:I was looking down on Earth from space at Minneapolis, and saw that according to the ring's shadow on the planet indicated that the sun now shines between the horizon and the innermost ring:
But when I went down to the surface, I found out that the sun really did NOT appear between the horizon and innermost ring as the shadow implies--it is still hidden behind the rings instead:
Is there gonna be a fix to this at all?
fsgregs wrote:cHRIS:
Just a quick reminder to add a toggle for nebula labeling to 1.4.0 final. It is not yet functional in pre10, either as part of galaxy labeling or as a separate keymap.
Thanks
Frank
Precisely.chris wrote:So the ring shadows aren't exactly where they should be?
Have you tried using the OpenGL 2.0 render path (use Ctrl+V to cycle among render paths.)
--Chris
Kolano wrote:P.S.-I got Nvidia cards with my new PC specifically because I believed they would work better with Celestia. Of course now it's ATI cards that render all the eye-candy appropriately.
Cham wrote:Kolano wrote:P.S.-I got Nvidia cards with my new PC specifically because I believed they would work better with Celestia. Of course now it's ATI cards that render all the eye-candy appropriately.
Not at all. I have an ATI card, and the OpenGL 2.0 doesn't work properly, like you. I believe the bugs are in the drivers and possibly in the OGL 2 library also (it's pretty recent, and it is version 2.0 ... so...).
Kolano wrote:An other major bug remaining in 1.4.0pre10 would be issues on NVidia with the OpenGL 2.0 shader path. I still see planets as bright red, and etc.
Are these all NVidia driver bugs that won't be directly resolved?
P.S.-I got Nvidia cards with my new PC specifically because I believed they would work better with Celestia. Of course now it's ATI cards that render all the eye-candy appropriately.
ANDREA wrote:I have found another strange situation in 1.4.0pre10 release: looking at the classic three satellites shadows on Jupiter (Io, Ganinede and Callisto), everything goes OK if I use the normal graphic settings, but with "FX" Callisto shadow disappear, and if I choose OpenGL 2.0 Io and Ganimede's shadows disappear the same way (but the shadow of Ganimede over Io surface remains there!).
A selective bug?
Anyone with the same problem?
Here is the cel to be used to check it:
cel://SyncOrbit/Jupiter/1997-11-11T03:5 ... 68179&lm=0
Press Ctrl+v and check if you have same results.
Thank you
Bye
Andrea
Code: Select all
Vertex shader source:
1: uniform struct {
2: vec3 direction;
3: vec3 diffuse;
4: vec3 specular;
5: vec3 halfVector;
6: } lights[1];
7: uniform vec3 ambientColor;
8: varying vec4 diff;
9: varying vec2 diffTexCoord;
10: uniform float textureOffset;
11:
12: void main(void)
13: {
14: float nDotVP;
15: diff = vec4(ambientColor, 1.0);
16: nDotVP = max(0.0, dot(gl_Normal, lights[0].direction));
17: diff.rgb += lights[0].diffuse * nDotVP;
18: diffTexCoord = gl_MultiTexCoord0.st;
19: diffTexCoord.x += textureOffset;
20: gl_Position = ftransform();
21: }
Fragment shader source:
1: varying vec4 diff;
2: varying vec2 diffTexCoord;
3: uniform sampler2D diffTex;
4:
5: void main(void)
6: {
7: vec4 color;
8: color = texture2D(diffTex, diffTexCoord.st);
9: gl_FragColor = color * diff;
10: }
Vertex shader source:
1: uniform struct {
2: vec3 direction;
3: vec3 diffuse;
4: vec3 specular;
5: vec3 halfVector;
6: } lights[1];
7: varying vec4 diffFactors;
8: varying vec2 diffTexCoord;
9: uniform float textureOffset;
10: varying vec2 shadowTexCoord0_0;
11: uniform vec4 shadowTexGenS0_0;
12: uniform vec4 shadowTexGenT0_0;
13:
14: void main(void)
15: {
16: float nDotVP;
17: nDotVP = max(0.0, dot(gl_Normal, lights[0].direction));
18: diffFactors.x = nDotVP;
19: diffTexCoord = gl_MultiTexCoord0.st;
20: diffTexCoord.x += textureOffset;
21: shadowTexCoord0_0.s = dot(gl_Vertex, shadowTexGenS0_0);
22: shadowTexCoord0_0.t = dot(gl_Vertex, shadowTexGenT0_0);
23: gl_Position = ftransform();
24: }
Fragment shader source:
1: uniform vec3 ambientColor;
2: vec4 diff = vec4(ambientColor, 1.0);
3: uniform vec3 lightcolor0;
4: varying vec4 diffFactors;
5: varying vec2 diffTexCoord;
6: uniform sampler2D diffTex;
7: varying vec2 shadowTexCoord0_0;
8: uniform float shadowScale0_0;
9: uniform float shadowBias0_0;
10:
11: void main(void)
12: {
13: vec4 color;
14: float shadow;
15: vec2 shadowCenter;
16: float shadowR;
17: shadow = diffFactors.x;
18: shadowCenter = shadowTexCoord0_0.st - vec2(0.5, 0.5);
19: shadowR = clamp(dot(shadowCenter, shadowCenter) * shadowScale0_0 + shadowBias0_0, 0.0, 1.0);
20: shadow *= sqrt(shadowR);
21: diff.rgb += shadow * lightcolor0;
22: color = texture2D(diffTex, diffTexCoord.st);
23: gl_FragColor = color * diff;
24: }chris wrote:Kolano wrote:An other major bug remaining in 1.4.0pre10 would be issues on NVidia with the OpenGL 2.0 shader path. I still see planets as bright red, and etc.
Are these all NVidia driver bugs that won't be directly resolved?
P.S.-I got Nvidia cards with my new PC specifically because I believed they would work better with Celestia. Of course now it's ATI cards that render all the eye-candy appropriately.
What driver version do you have installed? I've got a 7800GTX in my development system too, so you can be sure I've verified that the OpenGL 2.0 shader path works just fine with that card.
--Chris
selden wrote:Andrea, I just did some tests: The problem of only two shadows on Jupiter in the FX render path is present in Celestia v1.3.2 final.
The problem of no shadows on Jupiter in the OpenGL 2.0 render path has always been with us. It first happened in Celestia 1.4.0pre1 when that render path was first implemented. *sigh*
