Sorry for the long post, but I got latest master to compile in VS 2005, but ran into 2 issues that I needed to fix for it to work:
In

I had to change it to a non const iterator for it to compile:
And in ./include/al/efx.h I had to change all

to



I loaded it up, and found this great new feature, dynamic sun :)
I dont mean to drop the bomb on this, but could you share how I can give parameters to this? Because most of my maps rely heavily on pre-baked lighting, and I would like to configure this to suit them more.

Also, I found numerous other rendering bugs, and would like to ask if I should share these, or are they known to you as well? Like the minimap getting corrupted, grass texture issues, and lighting level issues.

Thank you devs for your hard work on giving us great new features!

Add a fourth parameter to the "sunDir" in the map info (x,y,z,sunDist). "sunOrbitTime" (in seconds) and "sunStartAngle" (in radians) can also be set. The sun normally starts at the peak elevation point, but e.g. sunStartAngle = PI would make it start at the lowest elevation point.

x,y,z is the axis of rotation for the orbit and sunDist is the distance from the origin to the center of the orbit. So, for a sun that passes through zenith (x,0,z,0) so that x^2+z^2=1^2

For a sun at a constant elevation (0,1,0,sunDist), 0<sunDist<1. Note that a sun too near the horizon currently has zero brightness so cannot be seen.

To change settings at runtime:
Or use completely manual control:

Does it fail? Well it is all untested :)

awesome

Oh hells yes! Excellent work!

will this effect the shadows of the map (hills,...)? because i thought that they are fixed

Correct. Some maps have fixed shadows, and will not look very good if the sun direction is changed.

@manolo, for maps that have the shadows literally baked in it won't look very good (very few maps do this tho). For the ones that have baked preshading (which is most of the high quality maps), it's possible that at certain points it might look a little odd, but I doubt it will be so noticeable that it will make a difference to the player. They are all going to be shitting themselves about dynamic sunlight to notice And in the future, mapmakers will simply be not baking preshading, so while it "could" be an issue of sorts, it is one that will resolve itself.

easy enough to an ambient bake rather than a directional shadowed one; im sure combined with ssmf it will look far superior to anything that exists ATM

/shadows 2 turns off terrain shadows, guess you will still be able to do that on maps with pre baked shadows.

Oh great, then also implement a feature to let the teams swap sides.
I mean the team with the sun in their back has the advantage right?

)

And team1 cannot jeffyspam because the wind is too strong. Luckily team2 had some lightning strike their advfus to even things out a bit.

ALAPIENTRY is deprecated in OpenAL1.1, so update your OpenAL headers.

Knorke... Prebaked shadows means that the shadow is burned into the texture. As a result, using /shadows 2 would do nothing.

I think he was meaning 'turn off engine shadows if they look funky on old maps'

Wouldn't this take the place of the engine shadows?

if i understand correctly, those are the engine shadows just updated with a new feature.
yup.
So if you have some old map with shadows drawn onto the terrain, it might be better to switch engine terrain shadows off so that you do not get double shadows, possible pointing in different directions.

Ahh ok. YOur wording was a bit funky.

So how can this be turned off, for a map with shadows on the texture? SunOrbitTime=something?

I believe this post answers your question (read all the way through to the end and it'll make sense).