I was thinking east coast and not Tampa. St. Augistine is the oldest fort in Florida so that's what I thought you were talking about. Fort Myers was going to be my second guess. Desoto was my third.

I'm not a big fan of the Gulf. It's too shallow. Deeper is better when you happen to be inside a submarine. The North Sea and Irish Sea was also a problem in that regard (600 feet isn't the best depth band). The White Sea and the Barents were all good though. Deep water is better, less chances of hitting the dirt that way. 

I think this mapping scene is only getting better with age!
I need to get my pc sorted out so I can join in again 

http://i.imgur.com/Fl5rzED.png 

 

Thank you! 

your
prefab
sprout 

 

... it needs to be released now ! 

So in the latest Nvidia driver they have included something called "DSR" or "Down Sample Resolution" that lets you boost the native rendering resolution of any game by up to 4X and then resize the image to your monitor (basically giving you controllable super sampling in any game you like).

So here is The Marcher Fortress in 4K resolution http://www.quaketastic.com/files/screen_shots/marcher4k.jpg

Great for screenshots! :D 

nice screen. does nvidia dsr work with any dx version and opengl? i use gedosato sometimes - borderlands 2 in 4k downsampled to 1920*1200 looks amazing - but it works only with dx9. 

What's the benefit to the gazillions of anti-aliasing options? Super sampling is from the 90s, right? 

supersampling is extremely resource demanding and incompatible with some modern engines. post-procesing fake aa works always but the result is questionable at best. instead of sharpening the image it just blurs everything. the idea behind dsr is interesting. would be nice to have one standart for both amd and nvidia cards. i tested stalker: shadow of chernobyl in 4k donwsized to 1920*1200 and it it incomparable with those crappy fxaa or mlaa fake anitaliasing modes. proper supersampling doesnt work in stalker so downsampling is the only option. of course you need super fast gpu.. 

The driver release notes state that is should work with any game, opengl/dx. I believe you do need a (somewhat) recent nvidia gpu for it to actually work however, I have a 660 and it works for me.

As for performance, yes it is super resource demanding. Quake was just about holding 35-40fps @ 4K resolution but I also had 8X msaa anti aliasing enabled as well which much be a huge resource hog with so many pixels on the screen.

Definitely recommending for screenshots only! 

i think it's a good way how to play older games that are not so hardware demanding. in many older games we can set 4k resolution and even standard gpu can handle it at playable fps. 

Not sure where to put this so I'll post here.
Seeing the trend towards large BSP2 maps. I wanted to see how far I could go before something broke. I used Hammer 3.5 and the ID map source. I was able to add the first 14 Quake 1 maps to a single BSP2 file.

I strung the maps together so you can play it. Somethings are broken due to redundant targetnames.

http://www.mediafire.com/download/ipdets9uiogdq3y/stress.zip 

cool! i had tried to glue the other episodes into a single map and couldn't do it in bsp... maybe now that bsp2 is more widely supported, it might be time to revisit that project... 

Run through quake in a single go. I like. 

How easy would it be to convert the q2 maps to q1, maybe string several together using bsp2? replace the baddies with their q1 equivalent, maybe rework some of the textures. could be a cool remix project. 

Give me the sources of your Q2 maps and I'll tell you. 

A glimpse at the original Id map sources shows they have targets and targetnames like this:

"targetname" "t143"
"targetname" "t143"
"targetname" "t141"
"targetname" "t142"
"target" "t53"
"target" "t144"
"targetname" "t144"

It's no wonder they clash if you try to join the maps together. However, I think it would be easy to transform them by adding the map name as a prefix, so you'd end up with names like
"e1m2t142" and e1m2t144" in map E1M2, which is where I got the above lines from. These names couldn't clash with those from any other map, because the other names would have different prefixes.

This a simple text-processing task that any programmer can quickly script together. If there aren't any serious problems with the simple solution that I am missing (not knowing the map format inside and out), it looks it could make joining multiple maps together much easier.

So, I guess I almost volunteered to write such a program with this post. Heh. Does anyone think a little helper program like this would be super useful to have? 

sed -i 's#"targetname" "t#"targetname" "e1m2t#g' 

 

find ^(s+)?"(kill)?target(name)?"s+"(.+)"(s+)?$
replace \\1"\\2target\\3" "whatever_\\4"

That covers targetname/target/killtarget, are there other places targetnames are referenced in the standard id progs? 

\1"\2target\3" "whatever_\4" 

Your proposed solutions are not very practical for people who only use Windows without Unix-like extra packages like Cygwin. (Which is not what I do.)

I found only the three keys, killtarget, target and targetname with this:

grep (BACKSLASH)"t[[:digit:]] *.MAP -h | awk '{print $1}' | sort | uniq

Replace (BACKSLASH) with the actual backslash character, because the preview is apparently eating it.

It printed this when run on the Id map sources:

"killtarget"
"target"
"targetname"

I think that a simple Python script would be more practical for Windows users. They'd only have to one fairly basic install to run the program, if they don't have Python already.

People who want to do this, but don't have the programming experience, just ask someone. It really is as easy as czg made it look. Just, you know, better not ask Spirit, because he will judge you for not having sed on your computer :)

(Actually, I will too.)