Oolite Bulletins

Frame wrote: ↑Thu Jan 12, 2017 12:16 am

and the planets/sun drawdistance be that of 1.84 instead of the currently 10 million KM.

another_commander wrote: ↑Thu Jan 12, 2017 12:23 pm

Frame wrote: ↑Thu Jan 12, 2017 12:16 am

and the planets/sun drawdistance be that of 1.84 instead of the currently 10 million KM.

Not sure what the actual problem might be here, but there is no change between 1,84 and 1,85 on how draw distances are handled. 1.84 also has a 10MKm MAX_CLEAR_DEPTH set.

another_commander wrote: ↑Fri Jan 13, 2017 1:36 pm

What is the exact version string of the nightly you use to test 1.85?

another_commander wrote: ↑Fri Jan 13, 2017 8:32 pm

Could it be the new atmosphere shader? Try this: In the 1.85 folder, go to Resources/Shaders and rename the file oolite-default-atmosphere.fragment to something else. This will force a fall-back to the previous (1.84) style of atmosphere rendering. Then repeat the test. Do planets still disappear at 4.4MKm?

Frame wrote: ↑Fri Jan 13, 2017 8:57 pm

So it is the shaders!. Does this complicate matters ?.

	}

	gl_FragColor = vec4(totalColor, newOpacity);
}

	} else {
		discard;
	}

	gl_FragColor = vec4(totalColor, newOpacity);
}

Commander_X wrote: ↑Sat Jan 14, 2017 1:34 am

Frame wrote: ↑Fri Jan 13, 2017 8:57 pm

So it is the shaders!. Does this complicate matters ?.

Although I don't understand why is it happening to you, you can try this change in the oolite-default-atmosphere.fragment file:
instead of last lines reading

Code: Select all

	}

	gl_FragColor = vec4(totalColor, newOpacity);
}

try

Code: Select all

	} else {
		discard;
	}

	gl_FragColor = vec4(totalColor, newOpacity);
}

This should cut-off the last line outside the activation distance.
My only bet is that something in this line doesn't pan out for what you're trying.

Commander_X wrote: ↑Sat Jan 14, 2017 8:08 pm

The atmosphere effect seems to be behaving correctly, i.e. becomes transparent (newOpacity=0.0) a bit before the "central lighting" appears.

If I understood correctly, you scaled the planets way more than they are in the game. The shader uses the collisionRadius uniform (which should be the atmosphere's radius, because it is a sphere) in the calculations. If you didn't apply the right scaling to this entity as well, it might happen so that at higher distances the planet and atmosphere spheres have roughly (approximated) the same radius. What I'm trying to say is that if, e.g., the atmosphere_radius=planet_radius + extra, and not planet_radius * X%, then that "extra" could be your culprit.
Also your screen has an extra overlay (the yellow E:D like reticule) - do you get the same result without it present on the screen (say, if you look aft but you have it targeting something in front)?

I cannot say I've noticed this behavior in game, i.e. the planets "melt" nicely when small enough.

discard

else
	{
		newOpacity = 0.01;
	}

Frame wrote: ↑Sat Jan 14, 2017 11:21 pm

But, wouldn't

Code: Select all

discard

Tell it to render nothing ? as in being totally transparent thus behaving like expected.

https://www.opengl.org/sdk/docs/tutoria ... iscard.php

Commander_X wrote: ↑Sun Jan 15, 2017 12:10 am

Frame wrote: ↑Sat Jan 14, 2017 11:21 pm

But, wouldn't

Code: Select all

discard

Tell it to render nothing ? as in being totally transparent thus behaving like expected.

https://www.opengl.org/sdk/docs/tutoria ... iscard.php

Yup, that was the intention.
As opposed to the git committed version of the shader, which is "rendering" totally transparent pixels once the distance to the atmosphere is greater than 12 times its radius, the "discard" change would abort processing altogether (also enhancing a bit the performance by not executing the last line _and_ presenting its output on the screen). The fact that this doesn't fix your problem but the absence of the shader does, it's the real mystery.