https://www.quaddicted.com/webarchive/kell.quaddicted.com/skyboxes.html 

http://www.redsorceress.com/skybox.html 

I don't make claim to the art work for these skyboxes. That credit goes to other talented people who allow you to use their wonderful skyboxes.

That's nice, but what would be even nicer is if they actually gave credit to said "talented people". I recognise at least some of sock's skyboxes on that page, but there is no mention of his name anywhere.

I had a look, and there seems to be just the same generic note included in each one:
This skybox is free for use but can't be sold for profit or altered in any way.
Those are not the terms under which sock has shared his work: http://creativecommons.org/licenses/by-nc-sa/3.0/ (and I'm willing to bet the same applies to the other skyboxes on that page).

But license or not, it just seems like common decency to at least credit people for their work. 

Sorry if I overreacted, and I didn't mean to come across as an asshole to PyroGXPilot. 

You can killtarget intermission cameras so that there is only one left in the map to force the game to use a specific one. 

is a feature in socks new mod. :) 

It was Kell's I was looking for! Thanks! 

 

Glad I was able to help someone out for a change. :) 

Something I don't know, -light (as used in worldspawn), -minlight, and -gate, numbers are talked about, but I don't remember ever seeing what the range was. For example, if -gate 5 is set, what does that mean? 5% or 5 on a scale of 0-255 or something else?

Confusing because -gate default is .001, that seems like an awfully tiny amount. I've used as high as 30 without seeing much difference. 

gate means that when light goes below the level specified, it is set to 0.

this is to stop delay 2 and 5 lights from going on forever.

make a box map with a regular light with brightnes 200 and try different gate settings to get an idea. 

I am a virtual noob when it comes to Quake map making (I made a few DM levels back in 96/97 and tinkered around a bit in 2002 or so and that's it).

So I did a little test thing where I wanted to make a rising staircase with floating platforms. I used func_door and set the lips and all is well, apart from the first platform. This one should rise up out of the floor by 16 units so that the underside of it is flush with the floor. But setting it to lip 0 does not work, instead it uses the default of 8 and thus starts already half out of it's starting hole.

I figured out that setting the lip to 0.01 works fine and looks flush as well.

I was just wondering what is going on here? Is this some kinda of bug? 

When you leave a value unset in Quake, two separate parts of the system assign it a default. First, the engine changes all blank values to zero. Then the QC script tries to detect unset values to apply a custom default, but it can't distinguish between the field being unset and it being set to 0 explicitly. So it's a big storm of unfortunate design, and your workaround is about all you can do... 

Thanks. Good to know. The 0.01 thing works pretty well. 

-0 the workaround for this? 

Wont work. 

So far, no one knows about the range(s) for the light values?

I had that problem on some steps in Wish 13, I assumed it was a bug. In my case, the player can't see the actual size of the steps, only the upper 16 units, so I just made the first one 8 units taller than it needed to be. 

I use -gate 10 on all my maps without seeing any difference other than tyrlight finishing faster, so at the very least, '10 light units' is really really dark...

I don't really know what light levels really are in a numerical sense, I just set my lights however they look nice :D 

Pretty sure it's 0-255 because that's the range of values in a Quake screenshot taken with r_lightmap 1. Although the compiler default cutoff of .001 doesn't make much sense in that context. 

So, I made a texture which has all the colours in order (apart from the fullbrights, those do not matter here)

Textured a wall with it and plopped a light in the room with delay set to local minlight.

Then I put in different light values to see when stuff changes. I took screenshots and compared it to the colormap.lmp

The colormap basically has 64 steps (63 really since the middle 2 steps are the same.)

I did this test using Winquake, because that is of course more accurate when it comes to the original colours. I did some initial tests in Quakespasm, but even in 16bit mode the colours are pretty off and not accurate to the actual palette ones.

So here are my results of the extremes.

0-5 BLACK
0-239 NORMAL COLOUR RANGE
240-255 ORIGINAL TEXTURE COLOURS (FULLBRIGHT) (technically the later range is already in the overbrights here)
256-487 OVERBRIGHTS
488 and beyond BRIGHTEST OVERBRIGHT

This is just for evenly applied lighting though and the stepping seems to be kinda wonky, must be some weird maths in there.

Once you throw actual lighting scenarios and different attenuation models into the mix things of course are a lot different. 

In the latest QuakeSpasm in a certain area of my level this "Backup Past 0" gets spammed to the console. I've never seen this before in my life and it has me puzzled :P

No errors, crashes, glitches or anything, just this message getting spammed in one area of the level. 

Post 580 on coding help. 

So quick question from the more experienced mappers:
Is there any way to have a func_train fire a trigger when it gets to a certain path corner?

Followup: can I set a trigger to fire when a monster touches it?

Thanks 

nope.

yes: http://www.celephais.net/board/view_thread.php?id=37116&start=11&end=11 

excellent.
Thank you :D