 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
And some of the background designs look a bit bland in that E4 corridor sort of way. But it still looks well built and some of the ideas look very cool and promising - the floating rune things especially. Keep it going dude.
It's too early to give you an estimation since because it really depends on how much free time I have and right now it's not all that much :)
I'd say the map is about 30% completed. Two info_player_starts?
BTW, you know you can make albums in imgur, right? You don't have to post one link per screenshot. If you're using tyrutils-ericw compilers, you should check Surface lights. Might be useful in this case.
Surface lights.
Does this mean what I think it means? What I think is: compiler deciding light value (and color) automatically from the light textures without the need to add light entities. Surface lights are just a "Hack" (not to put a dampner on the awesome stuff ericw achieves) as far as I understand it. What happens is that you set up a light entity with a key that has the name of a texture in it, and at compile time that entity is duplicated repeatedly over all surfaces with that texture. It's the sort of thing you could do yourself, if you had the patience of a robot. It's pretty effective though with the caveat that if you wanted some of those textures to be lit and others not to be you'd have to have two of the same texture with different names in your map.
Feel free to correct me if I'm wrong about how it works, it's been a while. In case I didn't make it clear, the light that's emitted depends on the values given to that original entity, so there's nothing picked out from a texture or anything like that. (For picking colours from a texture, I like to use shareX's screen colour picker, it can give you the numbers in a format that you can just paste into an entity.)
Yes, it just duplicates one light entity over faces with specified texture name. Saves time when you have to edit lots of duplicated lights.
you set up a light entity with a key that has the name of a texture in it, and at compile time that entity is duplicated repeatedly over all surfaces with that texture.
Wow, good to know, this is gonna save me heaps of time! One thing though: would it still allow lightstyles on specific lights, like a neon blinking while others don't? I tried surface lighting on lava but found it to be very erratic, I think because of how the surfaces are chopped up. Some lava looked fine, while in other places didn't seem to emit any light at all.
What it's really best at is light emitting textures that have an obvious source in the center. You save having to place many lights, and they are all consistent throughout the map for color, brightness, etc. I'm pretty sure light styles work, switching the light on and off definitely does. Targetnames are retained by every duplicated light.
If you want some of them to do one thing and others to do another, then you'll either have to do ugly things with your brushes/textures or handle the lights manually. As far as I know there's no way to edit the individual lights that get created, they're only added when you compile. (Maybe if you decompile your own map... but seriously?) "−surflight_dump" command line option for light.exe saves all of the generated lights to a file "mapname-surflights.map", so you can then paste the copies into your map and edit them individually.
http://imgur.com/a/p6jZt
From this screenshot you can see how i light my maps, hundreds or thousands of low emission lights that i tweek after i have vised my map, i move them change the values, and its difficult. How do the Pro's create lighting in maps?
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2025 John Fitzgibbons. All posts are copyright their respective authors. |