yeah, i try to get all my games from there when I can. sadly not all stuff on steam is available there. 

Yes, I am awaiting Galaxy! 

Demos not existing anymore is not Steam's fault in the slightest. 

This Duke couldn't get in Steam
because it refuzes my earlier 3DNukum
CD identity! Thanks CD owner! 

There is already a participant that's has played this game.
Of course, meself that remembers his log file.
Make another username and log in again.
Windows Life welcoms you.
madfox, get off steam. 

Starts in a few minutes http://www.dota2.com/international/live/ 

http://www.dedoimedo.com/computers/windows-7-to-10-gwx-how-to-remove.html
But win10 sounds like the general GUI is ok. 

http://www.big-game-theory.com/2015/08/these-halls-i-walked-homage-to-doom-and.html?m=1 

^written by peekaboom 

Great read. Thanks for the link! 

i hate func_trains and
think that they really suck;
why are they so bad?


seriously, why do they teleport to the first path_corner you target them at? that means if you want to do several spaced out trains, you need that many path nodes, which introduces slight noticable stops into the path. Why not just let them start where I built them in the level and just float toward their first path_corner? 

It's sp you can light them in separate areas... 

oh crap, you're right, that actually is super useful for what I am doing... I was positioning things really carefully and trying to light them each reasonably the same way... but fuck that, I'll just stack them and they'll all light exactly the same.

Also... I am dumb, I can just make path_corners that are only start positions, they don't have to be part of the chain. 

Good idea, I made them part of the chain for a stupidly over complex map I abandoned ages ago.

Quake is great for these types of proto hacks. 

I looked at engines that allow different screenshot formats. I looked at 6 of them and I found 5 different ways.

scr_screenshot_jpeg/scr_screenshot_png
scr_screenshotformat
scr_sshot_format
scr_sshot_type
sshot_format 

http://cache.desktopnexus.com/thumbseg/1213/1213217-bigthumbnail.jpg 

I'd be more amazed if they were consistent tbh. I think the days of there being some sort of committee-agreed "standards" for quakery is kinda over. 

you don't need a committee to check if any other engines have implemented a feature before you, and if they have, conform to their implementation (as long as it's not really dumb.) 

If i was doing my own engine, I wouldn't give a crap what others were doing and make everything the way I want.


The fact there is _anything_ in common between engines is a damn miracle. 

it seems that most other engine creators follow the same philosophy. 

yeah... I guess I'm just saying to look at the other side of the picture.

I think we'd all balk if someone told us all end level triggers had to look like the big gates in id maps or something.

Engine coders are in a funny position in that they are doing something creative yet are heavily constrained unlike mappers who have the freedom to do whatever they want.

I don't know what point I was trying to make now. 

spirit, if it helps, fte's cvar was named to match fuhquake.
except that fuhquake renamed its cvar with 0.31. randomly renaming cvars will always result in issues like this.

personally I'd say to go with screenshot_format, that way people stand a reasonable chance of finding it with tab (in engines that provide alternatives anyway).
sure, its not on your list, but hey...

the problem with committees is that you need someone to take charge and harass people until they get their act together.
my own attempts at getting other people to stick to the standards that they claim to support didn't really go too well. frankly, its kinda impossible to disagree with Kinn - people just don't give a damn about compatibility until they're humiliated by it. On some level its actually beneficial when other engines can't run the mods targetted at your engine because you implemented the standard wrong (embrace, extend, extinguish).

the stupid thing is that there's no reason that a cvar can't have multiple names. sure, each engine will still have a preferred name that is used for saving configs, but they should still accept other names for the cvar.

metlslime, not a committee, no, but you do need teeth to ensure that people actually put in that extra effort.
it doesn't help that there are so many different engines that would need to be checked, and half the time engine devs don't bother looking further than their favourite competitor (if that).

the other problem is that most engines are dead now, even if they're still used (who'd want to upgrade to a third-party fork that claims only to break their configs?).

</rant>