 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
So I guess now, whoever has the most cores/processors on their machine needs to become a VIS mule for the group. :P
Yes, there's definitely some improvement (with 2 threads) - I'd say it's at least 40% faster. I was so dumb as to accidentally close the window just now, so I can't tell the exact difference, unfortunately. But still, your version is useful for running at night when there're no other programs running beside vis. Thanks for offerning your lunch break.
well, i've been using it all day with fast vising. it is faster, but it's hard to tell just how much without doing a proper full vis.
i have a second map that's in the final stage so i'll do a couple of test runs of full -level 4 vising on it, one with and one without multithreading for a proper comparison, but assuming there isn't a fundamental difference in what vis is doing in -fast vs without -fast, i'd say it's creating how you managed to improve this blocking up tool, Willem!
If I count all vis time I made since I started mapping in '97 I could have learned C+ and have dived into it... too late I guess. Sorry, the file moved. I've made it permanent here:
http://www.quaketastic.com/upload/files/tools/windows/misc/WVis.zip It looks like the WVis times are rounded to the nearest minute?
This was on a Core2Duo E6850 (3 GHz). Original VIS run: ---- Vis 2.31 ---- Modified by Bengt Jardrup File: c:\quake\id1\maps\wish16.bsp 2929 portalleafs 8356 numportals State file out of date, will be overwritten testlevel = 4 ambient sky disabled average leafs visible: 192 max leafs visible: 646 near (-608 352 592) c_chains: 39836161 visdatasize: 219 kb compressed from 1049 kb Elapsed time : 6:52 WVis run: ---- WVis 2.31 ---- Modified by Bengt Jardrup Multithreading enabled by Willem File: c:\quake\id1\maps\wish16.bsp 2929 portalleafs 8356 numportals State file out of date, will be overwritten testlevel = 4 ambient sky disabled Using 2 threads. average leafs visible: 192 max leafs visible: 646 near (-608 352 592) c_chains: 39880904 visdatasize: 219 kb compressed from 1049 kb Elapsed time : 3:00 I just did this, so I haven't actually looked at the map in the game. If I see any problems I'll post them. The only difference in the log is the c_chains (no idea if that's important). I ran the full BSP, Light, Vis each time with no change to the actual I guess this is the recursive linkage made in between volumes. As in bsp process there's a volume expansion process that defines where are each faces / leafs, I think it is almost the same for vis process except the tools creates a chained list of volume in order to process them recursively (i.e from this volume, process the faces, and check what are the others visible volume not in the list, etc...) and determine which volumes (and then number of faces to render per volume) are visible from a given position.
This is how I understood the system in very "rough" way.. and maybe I'm wrong :P Progress in Quake map building, after all these years ! Nice work !
Quick question about something else: Does it really make a lot of difference if you make your curves just by cutting them with a circle, or if you use the vector manipulation to make them more or less the same size and triangles ? If anyone has some more info (on the web, maybe ?) about vector manipulation, please let me know. http://www.quaketerminus.com/hosted/happymaps/curv_tut.htm
Learn those ratios by heart, use them. The ratio used in the above tut is 0:2 2:4 4:2 2:0 if that makes any sense. There are other possible workable ratios but that one's always worked for me. As far as constructing said curves, the 2-point clipper will probably give you less headache (and fewer invalid brushes) than trying to vertex manip everything into place. I remember someone else having a problem awhile back with this
If they're passing over a sky brush then they'll always appear black unless the sky brush has a normal, solid brush inside it.
If they're appearing black when passing over normal lit floor then there's an issue with the origin of the monster. They take no reference from the walls. But what can I do as a mapper? Just rework the brushes in the area until the engine stops having an issue?
The screenshot would just be an enforcer standing a well lit ledge but he's black. If he moves to either side a little bit, he lights up. I guess I'll just play with it. :)
the problem i believe you're remembering was mine where i had torches and stuff fulldark even though the ground under them was nearly fullbright (or overbright even).
i think i understand what causes it. i suspect it has to do with FQ's lighting interpolation, but only on maps that are unsealed. the problem usually happens in corners or along walls, never in the middle of a room. i believe this was because the sides that made up the bottom of the wall brush and the side of the floor brush were fulldark and the interpolation was getting messed up. i've found that sealing maps so that those faces are removed tends to fix it. if you have an enforcer on a ledge, is it possible there are faces in the area that are messing up the interpolation? from what i recall of how metl explained it to me, FQ doesn't just look at the floor directly beneath the model to light it. The map is definitely sealed but there might be some dark polygons in the area. I'll take a closer look...
from what i recall of how metl explained it to me, FQ doesn't just look at the floor directly beneath the model to light it.
I haven't actually figured out this bug yet, but the fitzquake interpolation should still be looking just at the same floor polygon as glquake. The difference is that when you trace a line down and it hits between lightmap samples, glquake picks the nearest one and fitzquake blends between all four. Again, since i haven't figured out this bug, i can't say in what way fitzquake is doing it wrong.
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |