I wonder if it works properly... 

@-Tronyn: You haven't seen the dopefish yet.

@-Zwiffle: I think it is as hard as the escalator in Quake.

@-mettfuchs: gut zu wissen, dass ich ein Begleiter zusammen habe.

@-5thphant: this fucking demo took as much time as the construkting of it. What I learned is that all engines have another way of exposing.
I am still missing some frames though. 

Result of Boredom

I still would prefer Jackhammer, since Radiant seems to be more complex and challenging to master. 

it's funny you say that as, coming from a radiant background, i find hammer editors very difficult. 

https://pbs.twimg.com/media/CTRqTY4WcAABh7E.jpg:orig
https://pbs.twimg.com/media/CTVZhqjXIAAt91p.jpg:orig
https://pbs.twimg.com/media/CTZh_wcWcAUMjjf.jpg:orig 

My body is ready. 

Are those custom textures in shot #3 of red brick alpha blending into green brick? 

It's a shame he isn't around here on func_ anymore. 

The bone recess in pic 1 is awesome. I'm ashamed I didn't think of that earlier. 

is awesome indeed 

It reminded me of this infinite scroller experiment I've made over two years ago:
https://youtu.be/-qvli2BFIGk 

dat potato resolution. Do you have a higher res video? 

I don't remember. That thing is really old. 

 

I think computers were made out of vacuum tubes back then, so give him some slack. 

:D I love this place.

Anyway, the variable framerate of the Quake engine (in that case, FTEQW) made the loop get out of sync, so the floor repositioning is noticeably abrupt, and the mountains behind the trees aren't spaced correctly.

This is why one of my goals is to implement scrolling textures. It will be a much better, cleaner, easier, more flexible and more accurate approach. 

wouldn't mind scrolling textures for waterfalls, actually.

but then no one will use it until other engines have it too. :( 

as long as the texture name prefix for it isn't '(' or something dumb, you might have a chance... 

well we already have {, so using } would be a nice bookend to that atrocity! 

? 

most likely
https://twitter.com/SimsOCallaghan 

scrolls maybe? 

To use something that turns your grammar from context free to context sensitive. That would give me another chance to get told to fix my parser when I complain about it. 

? 

I *REALLY* hope editors have started properly using quotes when saving .map files by now...

it'd be really nice to NOT use yet more name prefixes as they tend to fight each other. Maybe we should start hiding our extra surface attributes inside // comments for backwards compatibility! :P