What makes small file sizes?

(Emon) #21

You can do that in Jedi Academy. :smiley:

(wudan) #22

Are you sure? It seems like you could do some polygon offset autosprite dirty hackness to create something similar? It won’t be the exact effect, but it could happen, no? (well, i guess you really wouldn’t get the ‘full’ effect - ie if you block the ‘corona’ image, you’ll blot out sprites that you block, but you won’t get that ‘bleed-over’ that you get with the authentic corona-ness)

ALso, is there a way that vertex colors could get applied to brush polygons? Could this be shader supported (like a keyword to specify vertex colors)? - could be used to save texture memory, if my thinking is right - (and I’ll warrant it might not be so)…

Edit:

- i realize that the shader won’t know how many vertices a polygon has (quake3 only does triangles, though, right?), i meant vertex colors for all vertices.

(]UBC[ McNite) #23

Try Q3Map2 -info sometime on a BSP.

I m using Q3map2build by bobdev as a front end tool for all my compiles which is just perfect.
My q3map2 version is q3map_2.5.16_win32_x86 and i can’t get -info working with my front end. Can anybody plz post the code for the .bat when i want the info?

Thx a lot.

(kamikazee) #24

I use

q3map2 -game ET -info <bsp>

and it works.
If you don’t supply the -game parameter q3map complains the bsp is a wrong version.

(Detoeni) #25

hacked from my user.proj


<key name="bsp_Q3Map2: (info) BSP -info " value="! "C:\.....path_to.........\q3map_2.5.16_win32_x86\q3map2" -v # -game et -fs_basepath "C:/Program Files/Wolfenstein - Enemy Territory//" -info $"/>

edit: Blast! got betten to the submit button

(]UBC[ McNite) #26

That works… only… how can i make it log the results? The black window closes pretty fast :disgust:

And, yea, i m a noob regarding this :smiley:

(Twisted0n3) #27

q3map2toolz can monitor the compile and log the results in its own window.

(kamikazee) #28

You could start it using

q3map2 -game ET -info mylevel.bsp > levelinfo.txt

If you want to add the last run to the log, use >> instead of >