@Guitar: nice contribution, i'll look at it later

@lostclimate: if you guys ever do get that working, it'd be a sweet contribution

It would be a nice project. If you read the positions from thye WMP and saved them to a text file. Then loaded the positions from the text file into an array. Then create a light management system to tell which lights need to be passed to the shader.

The only problem I see is when passing to the shader. For each light, you have to pass 7 variables (x, y, z, red, green, blue, range). I'm not sure what would be the best way to pass these to the shader though.

Woulden't that work with a vecSkill41 (for the position) and a mtlSkill1 via pixel_for_vec (for the colors)?

...and thanks for this great contribution!

i could, but then I'd have to use both (for light position and color), limiting me to one light passed to the shader...

well i can read the colors directly from the file, so pixel for vec isnt really needed

edit: I also wanted to add that its real easy to get info and write info to wmps, i made landscape block editor the first month i started using 3dgs seriously, but it didnt work out because it was to many wierd angles for the engine, and the lighting got all screwed up.

pixel_for_vec() would still be needed to convert the c-script values to float() vectors...

For the normal mapping on terrains, should the NM's be for each texture (tiled), or one NM for the whole terrain?

If you want to create big terrains then you must tile them for sure.