Q3map multiple suns

(Axedup) #1

Ok, I’ve browsed the boards to find info, but it doesnt explain enough if u know what I mean.

textures/mudriver/valley_skybox
{
qer_editorimage textures/mudriver/valley_view.tga
surfaceparm noimpact
surfaceparm nolightmap
q3map_lightsubdivide 256
q3map_surfacelight 150
q3map_globaltexture
q3map_sun 0.924 0.948 1 75 220 60
skyParms textures/env/mudriver/valley 128 -
}

As u can see, Ive got a nice sun in the sky, but I want more light, but coming from a diff direction (oppisite) so nothing is really in shadow.

So I add my light entity and give it the _sun / 1 key and value.

So I run the map and not really any difference in the light / shadow.

q3map_sun 0.924 0.948 1 75 220 60

This Line is the colour, intensity and direction etc of the sun on the skybox script.

So how do I change the properties of the light entity sun to be in a different direction?

Or is its shine direction relative to where u place it in a map?

Thx in advance

Axedup

(Valhue2) #2

Im under the impression that you set up your point based light with the _sun param just like a regular spotlight… have it target an info_null or target_position, or whatever… I may be incorrect though…

V^2

(Raven) #3

You are right Valhue2 :wink: Point your entity sun to an info. null in the direction that you want it to shine :slight_smile:

(Axedup) #4

Yeah thx lads all sorted now, but its weird what was happening…

U had to select the light and info_null in the correct order and put in the values of the light in first etc… otherwise it would just be a normal light but pointing to a info_null.

I know it sounds weird, but in GTK when u look at a selected light, it shows the ligth radius in the windows, but when a _sun entity is selected it doesent show the radius of light.

My problem was it was still showing the radius and acting like a normal light but pointing to the info_null and not being a _sun!

Any one else seen it like that?

Thx again

Axedup

(Raven) #5

Yeah. The order is very important when it comes to targeting things. You should always select the main entity first and then the info_null or notnull.