[BUG]spot&directionnal lights

Crashy

06-10-2005 18:13:39

hello. I've a quite old version of the plugin, and cannot update atm for many reasons :roll:

I've a strange bug here, maybe he's still here because it has'nt been highlighted.

When I set a light to LT_SPOTLIGHT or LT_DIRECTIONAL, the terrain is not loading correctly: some pages aren't loaded, but pages behind them are correctly loaded.

Someone has the same result?

With LT_POINT it works fine, but I need directional lights for texture shadows

tuan kuranes

07-10-2005 10:39:14

cannot reproduce that here ...
Demo uses LT_DIRECTIONAL since the beginning...

did you check ogre.log for data acess problem ?

Crashy

07-10-2005 11:05:47

Erf, yes you're right, this is a directionnal light in the demo.. and the demo works fine
I've no error in the log, let see what are the difference in the light creation..

Crashy

07-10-2005 11:46:11

Ok, works with LT_DIRECTIONAL, but only with
SHADOWTYPE_STENCIL_MODULATIVE
or SHADOWTYPE_STENCIL_ADDITIVE,
not SHADOWTYPE_TEXTURE_MODULATIVE


Maybe a conflict with the shadow_receiver_vertex program? i'll test without asap.
EDIT: no, that's not the shadow_receiver_vertex_program. :s
By the way, here is a screen of the result :

Crashy

08-10-2005 12:17:17

Ok I just reprouduced it with the demo on your website
With my own map:
stencil shadows:
http://crashy.cartman.free.fr/wip/Demo_ ... -10-12.JPG
texture shadows:
http://crashy.cartman.free.fr/wip/Demo_ ... -11-82.JPG

Same thing with you puget sound:

Stencil:
http://crashy.cartman.free.fr/wip/Demo_ ... -06-81.JPG
texture:
http://crashy.cartman.free.fr/wip/Demo_ ... -08-09.JPG


Same settings for all screenshots .

tuan kuranes

13-10-2005 17:48:02

Cannot reproduce bug on CVS version.
Did you check with new ogre SDK compatible source
Tell me how you exactly you set up shadows in order to reproduce bug (code)

Crashy

15-10-2005 19:46:30

As I said, I've the same bug with the 1.0.3 binary demo on your website.
I 've not tried with your new binary demo at the moment. But if I juge from the result I get with catalyst 5.1, it is a driver-linked issue. :x

Let's wait for the 5.11.