Using different version of q3map2 per phase

(Q.) #1

How do you do?
As the title says, is there anyone who is doing so?
I’m wondering it’s possible or not to use q3rmap.exe(q3map for q3rally mod) for bsp phase, then latest q3map2 for later phases to get the advantage of q3map2.
I tried only to fail. :-
I tried again with additional bsp phase using q3map2 to generate .srf file to be used at light phase.
Just no luck. :-
Help please.

(phobos) #2

Why would you need to do that anyway? I can’t think of anything that’s changed more than lighting (and the old vertex stuff has been added in 2.5.13 http://shaderlab.com/q3map2/2.5/readme.txt). You can turn off BSP optimizations with -notjunc and that should look very similar to the original q3map.

Otherwise just traverse directories in your batch file like thus:

..\..\q3tools\q3map.exe mapname
..\..\q3map2\q3map2.exe -vis mapname
..\..\q3map2\q3map2.exe -light -fast -samples 2 -shadeangle 60 mapname

Does it fail at VIS?

(Q.) #3

Oh, really?
I’ll try -notjunc @ bsp phase.
Thank you very much. :slight_smile:

Does it fail at VIS?

No, @ light phase with thousands lines of same warning messages which I don’t remember and erased to secure disk space.
Light phase seemed to stop at …7…8…9.(while illuminate lightmap), consumed incredibly long time.
I’ll paste them once reget. :slight_smile:

(Q.) #4

@phobos
Everything worked fine soley with q3map2. :clap:
The thing doing harmful things was my messed up batch file. :bump:
Please forget about the problem.
Thank you.

(ydnar) #5

Uh, T-junction fixing is in the original Q3Map.

Why would you need to use Q3Rally’s compiler instead of Q3Map2?

y

(Q.) #6

Now I see q3rmap does just surfaceparm related things and it’s unnecessary. :cool: