Bug in q3map2?? it´s not in original q3map...

[Tweety]

Hi...

got an error in rtcw. It only appears using q3map2 for the lighting.
Max_Shaders hit.
I have seen this in earlier discussions, but no one really seems to have a solution for it.
If this is a known bug: can it be fixed?
I also read that 1.4.1 supports more shaders (8192). I´m currently using 1.31 but I do not think it will solve the problem because the original tool does not produce this problem in rtcw version 1.31.

Any ideas???
greetings
TweetyTheBird

[pazur]

i had the same error before the wolf 1.4 patch. i found out that placing a lot of hints and going up with lightmap size helps(_lightmapscale <value> of func_groups)

[ydnar]

Upgrade to 1.4+. It's a bug/limitation that has been addressed. For a detailed explanation of why this happens, see the SOF2 lightmap thread in this forum.

y

[Tweety]

Hey...

found the problem...pazur mentioned func_groups... that´s it.
I was testing some new trees (no md3 models). I grouped them in the editor and pasted them several times in the map.
The original tool works fine with it, but for q3map2 I have to ungroup the entities then the problem does not appear.
I´m not sure why this happens but I think it has nothing to do with rtcw and the limitation ydnar mentioned (I´m still using 1.31).
Another interesting aspect. Using q3map2 for this map with the func_grouped trees will result in about 12 min for lighting. With the ungrouped entities it´s about 3 minutes.

greetings
TweetyThe Bird

[wudan]

Wouldn't it be cool then, if Q3Map2 automatically treated func_groups without any keys/values as though they were ungrouped, at time of compile. I don't know how hard this would be to implement in Q3map2, but ydnar's already pushed it farther than anyone thought it could go.

[Emon]

Wouldn't it be cool then, if Q3Map2 automatically treated func_groups without any keys/values as though they were ungrouped, at time of compile.

It does.