 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
q1rad coolness again, try messing with the "-smooth x" option, its fucking lovely, x=max angle q1rad will smooth the light around, set this at around 25-30 and a 12 sided cylinder looks like a 120 sides cylinder, cool effect!
Radiosity is the sawk, I've gone back to trusty old TyrLite. That said, that 'smooth' function sounds interesting - but I can't be arsed to convert all of my coloured lights back into the stupid format that Q1rad needs, instead of the sensible format that TyrLite & co use. And anyways, I don't really like the light-saturating effect that radiosity has.
Cheers anyway! did you try -bounce 0 and what light brightness settings were you using for your surfacelights?
"radiosity" refers to bouncing light, sure, but in our line of work, it's usually paired with light emitting surfaces. So, if you want light emiting surfaces, but don't care about bouncing light, you might use bounce 0.
Yes, i'm very drunk. And i can still type better than you. glad to see you on the func_board. Does that mean you are you mapping as much as you code these days?
Thanks. I understand yaw and pitch but not 'placeholder'.
Sorry to be dense but I have never used _sunlight before: I am only trying it now after reading some comments by AguirRe in this forum. I have a rather large (high) set of mountains in FMB12 and lighting them is proving difficult. As a by the way, is 256 the largest texture size that can be used in Quake1 - I can see some pretty obvious tiling? 'Placeholder' means just put zero; i believe it's needed becuase the compiler expects a vector, but only actually has a use for two or the numbers.
Re: texture size, first, check this: http://www.celephais.net/stuff/texturefaq.htm Second, try scaling the texture up, or using more lighting variation to break up the large surfaces. (I know, "lighting variation" is contrary to the whole _sunlight aesthetic. But you could still put in some subtle point lights or antilights to create the needed variety.) placeholder is exactly that - it doesn't do anything, it's just necessary to convince the compile utils that you're using a 3-part vector.
More proof!
<goetz> http://www.celephais.net/quake/ <goetz> metlslime is that u ? <goetz> i thought u were male <metlslime> i'm a hot japanese girl <Auhsan> woa <Auhsan> I love you metlslime <metlslime> this explains why i never get laid, after all, who wants to have sex with a hot japanese girl? <metlslime> nobody. I wish i was one of those skinny white computer geeks. They get all the sex. <Auhsan> from their hands <metlslime> heh * metlslime cries I am just trying to see the difference between using _sunlight or placed light entities in a map.
For some reason, light does not seem to work on my trial, 2055 brush, map. Here is the readout: - 4361 planes 87220 4252 vertexes 51024 2387 nodes 57288 6 texinfo 240 3888 faces 77760 13244 clipnodes 105952 1202 leafs 33656 4808 marksurfaces 9616 17010 surfedges 68040 8506 edges 34024 2 textures 130652 lightdata 0 visdata 0 entdata 176 File: ter2.bsp 3 entities read, 1 are lights, 3888 faces Light: 0.0%, Elapsed: 0:00 Light: 100.0%, Elapsed: 0:01 lightdatasize: 0 0 switchable light styles Elapsed time : 0:02 BspBuild [Light complete] The numbers mean nothing to me. Can anybody spot my (probably obvious) error? like you only put on light entity:
3 entities read, 1 are lights, 3888 faces sunlight needs: _sunlight # for intensity, and _sun_mangle x x x for direction.
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2025 John Fitzgibbons. All posts are copyright their respective authors. |