This issue should not have to do with airmass or extinction. The projection geometry has changed due to bugfixing refraction, and now we likely see numerical effects in some vector computations.
I am just downloading Qt5.3.2/64 for MSVC2013...
My best bet would be at changing one or two significant mediump to highp (but which ones? Maybe all down to gamma?), and not destroy the Oren-Najar reflection model for lunar surface roughness! Turning down roughness likely removes the brightness peak at full moon.
From what I have read, however, highp may not be available (or defined away to be equal to mediump) on OpenGL ES2, depending on implementation. If the solution depends on highp, this would again be quite stupid. (like #define double float)
This issue should not have to do with airmass or extinction. The projection geometry has changed due to bugfixing refraction, and now we likely see numerical effects in some vector computations.
I am just downloading Qt5.3.2/64 for MSVC2013...
My best bet would be at changing one or two significant mediump to highp (but which ones? Maybe all down to gamma?), and not destroy the Oren-Najar reflection model for lunar surface roughness! Turning down roughness likely removes the brightness peak at full moon.
From what I have read, however, highp may not be available (or defined away to be equal to mediump) on OpenGL ES2, depending on implementation. If the solution depends on highp, this would again be quite stupid. (like #define double float)