Stellarium 0.12.0dev5 (beta) doesn't show the real lunar phase

[Phongsathon Kitchawet]

In Stellarium 0.12.0dev5 (beta version),
the lunar phase is fixed.
When you change the date, the lunar phase doesn't change.

For example:
30 October 2012, 02:50 am Chiang Mai, Thailand local time;
it should be the full moon.
Stellarium 0.12.0dev5 shows the lunar phase is 1.00 (100%).
But the Moon image is not.

See the screenshot here:
http://image.free.in.th/z/ix/0120dev5_moon.jpg

Please fix it.
Thanks.

[Alexander Wolf (alexwolf)]

I can't reproduce this issue on Linux and Windows systems. Please give more info.

[Phongsathon Kitchawet (lovethisman123)]

My specifications:
Windows 7 Ultimate 32-bit
Processor: Intel Pentium Dual T2390
RAM: 3 GB
Graphic: Mobile Intel 965 Express Chipset

[Alexander Wolf (alexwolf)]

Thanks! I can reproduce this bug only on Intel GPU.

Hint: OpenGL error detected at "drawWindow() start" : "GL_INVALID_VALUE"

[Keatah (keatah)]

I have old intel graphics, and have this incorrect phase problem.

[Ferdinand Majerech (kiithsacmp)]

On Intel, I can reproduce this in GL1 mode, not GL2.
I can also reproduce it in GL1 mode on my Radeon PC.
(open source drivers, both Intel and Radeon)

I don't get any GL_INVALID_VALUE on either. I think that's specific
to the pre-SandyBridge Intel GPUs.

I think the CPU lighting probably has a bug, but don't know where yet.

[Keatah (keatah)]

Could it be that pre-sandy bridge graphics are reporting 0 lights, when there are actually 8 points?

[Ferdinand Majerech (kiithsacmp)]

Stellarium never uses the old fixed-function lights
(lighting is done on the CPU for GL1, shaders for GL2)
so I don't think that is the cause.

[Ferdinand Majerech (kiithsacmp)]

I've determined that this bug was introduced in 5273.1.126 (part of my GL refactor work):

http://bazaar.launchpad.net/~stellarium/stellarium/trunk/revision/5273.1.126

Not yet sure what the cause is.

[Alexander Wolf (alexwolf)]

Diff: http://bazaar.launchpad.net/~stellarium/stellarium/trunk/revision/5728

[Phongsathon Kitchawet (lovethisman123)]

Now the latest version 0.12.0 solved this bug. Thank you very much. :)