Easily install and launch Quake maps with the cross-platform Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
tools:vis_benchmark [2013/03/05 17:25] Spirit forgot the time column header |
tools:vis_benchmark [2013/03/29 13:25] Spirit corrected qfvis timing |
||
|---|---|---|---|
| Line 18: | Line 18: | ||
| Download [[/files/tools/tyrutils-0.5-win32.zip|tyrutils-0.5-win32.zip]] and extract it. Here you find vis.exe in the bin/ directory. Run | Download [[/files/tools/tyrutils-0.5-win32.zip|tyrutils-0.5-win32.zip]] and extract it. Here you find vis.exe in the bin/ directory. Run | ||
| - | * ''vis.exe gmsp3v2.bsp'' | + | * ''vis.exe -level 4 gmsp3v2.bsp'' |
| If you are on Linux, use [[/files/tools/tyrutils-0.5.tar.gz|tyrutils-0.5.tar.gz]] . Just ''make'', it will build a binary named vis in the bin/ directory. | If you are on Linux, use [[/files/tools/tyrutils-0.5.tar.gz|tyrutils-0.5.tar.gz]] . Just ''make'', it will build a binary named vis in the bin/ directory. | ||
| - | |||
| - | Download [[/files/tools/quakeforge-tools-0.7.2-win32.zip|quakeforge-tools-0.7.2-win32.zip]] and extract it. Here you find qfvis.exe in the quakeforge-0.7.2-win32/bin/ directory. Run | ||
| - | * ''qfvis.exe -t 4 gmsp3v2.bsp'' | ||
| - | |||
| - | **Adjust the number after the -t according the number of threads your machine can run in parallel.** | ||
| And for laughs and nostalgia also run a full-vis with the one single-threaded Vis.exe from the bjp tools. | And for laughs and nostalgia also run a full-vis with the one single-threaded Vis.exe from the bjp tools. | ||
| * ''Vis.exe gmsp3v2.bsp'' | * ''Vis.exe gmsp3v2.bsp'' | ||
| - | Then add your times and information about your processor to the table below. If you are running with a non-standard frequency, please add that. Please add entries ordered by time, if in doubt by the time of the tyrutils. The top entry should be the fastest. | + | Then add your times and information about your processor to the table below. If you are running with a non-standard frequency, please make that bold. Please add entries ordered by time. The top entry should be the fastest. |
| ==== Results ==== | ==== Results ==== | ||
| ^ Processor ^ Platform ^ Compiler ^ Time ^ Name ^ | ^ Processor ^ Platform ^ Compiler ^ Time ^ Name ^ | ||
| - | | i5-3470 | Linux | tyrutils v0.5 | 67s | Spirit | | + | | Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz | Linux | tyrutils v0.5 | 76s | DrLabman | |
| - | | i5-3470 | Linux/Wine | WVis 20100119 | 780s | Spirit | | + | | Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz | Linux | qfvis 0.7.2.64-59508 | 91s | Spirit | |
| - | | Intel(R) Atom(TM) CPU N570 @ 1.66GHz | Linux | tyrutils v0.5 | 1182s | Spirit | | + | | Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz | Linux | tyrutils v0.5 | 91s | Spirit | |
| + | | Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz | Windows | tyrutils v0.5 | 93s* | necros| | ||
| + | | Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz | Windows| tyrutils v0.5 | 144s* | Spy | | ||
| + | | Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz | Windows | WVis 20100119 | 180s | necros| | ||
| + | | Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz | Windows| WVis 20100119 | 240s | Spy | | ||
| + | | Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz | Linux | tyrutils v0.5 single-thread | 343s | Spirit | | ||
| + | | Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz | Linux/Wine | bjp May 2006 | 634s | Spirit | | ||
| + | | Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz | Linux/Wine | WVis 20100119 | 780s | Spirit | | ||
| + | | Intel(R) Atom(TM) CPU N570 @ 1.66GHz | Linux | tyrutils v0.5 | 1182s* | Spirit | | ||
| + | | Intel(R) Pentium(R) III Mobile CPU 1000MHz | Windows | bjp May 2006 | 3840s | Spirit | | ||
| + | * denotes entries where we ran tyrann's vis without specifying "-level 4". It did not use that by default. | ||
| - | WVis already rounds to full minutes. | + | WVis always rounds to full minutes. |