Lighter2 ignores <noshadows /> and <nolighting /> tags

[anonymous]

Lighter2 ignores <noshadows /> and <nolighting /> tags and generates unneeded UV-mapping and lightmaps for these objects.

[anonymous]

the unlit world file

[anonymous]

Aswell as <invisible />

[res]

The underlying problem is that lighter2 sets <nolighting /> on all objects lit by it (to avoid genmesh's software lighting to kick in). Thus from just seeing a <nolighting /> flag lighter2 can't distinguish whether it was given by the user or set by a previous lighter2 run.

[jorrit]

Well I see three possibilities:

1) the object has <nolighting/> set but no lightmap or vertex lighting information. In that case it is an option set by the user and lighter2 should consider it an ojbect it should keep unmodified.

2) the object has <nolighting/> set and it has lightmaps or vertex lighting information. In that case you can assume that the <nolighting/> was added by lighter2 because if it was added by the user you would have fallen in option 1).

3) the object has no <nolighting/> set. In this case the object doesn't have lightmap or vertex lighting information and lighter2 should add it (and the <nolighting/> flag).

So I see no problem here?

Greetings,

[jorrit]

Is this problem still present?

[res]

Replying to res:

The underlying problem is that lighter2 sets <nolighting /> on all objects lit by it

In fact, this is wrong. What lighter2 does is set <lighting>no</lighting> on genmeshes - as a mesh object specific setting.

The mesh wrapper flag <nolighting/> is actually respected (r31670 adds improvements in that area, but in principle it was supported before). Thus resolving this bug as fixed.