The engines list shows the admod engine, quakespasm sdl32 and Winquake. The rest I do not recognize. It does not show my QSS engine. How do I set the thing up to find more engines?

https://puu.sh/x2yTg/1dc2d3ece9.png 

quakespasm-sdl2* and I do recognize Glquake of course. 

https://www.twitch.tv/quakechampions

Get Hype! 

Is there a way, keybind/alias etc, when trying to record a demo to just have it tied to the quickload(F9) key and start recording again incrementing the demo's name?

I don't play all that great and I'd like to record some demos, like many here do, but damn man... it just breaks immersion for me when I have to quickload but drop to the console and get the recording going again making sure I don't overwrite the previous one.

Don't mean to whine but after several attempts of trying to get OTP's Jam9 map finished I m just frustrated with the process.

How is everyone else doing it? 

You could make an alias script, but the problem is you need to record to a new file everytime and I don't think that's possible to implement.

Alternatively, you could play on coop mode with only one player where you simply respawn after dying while the demo keeps recording. Not ideal, though, because you still couldn't quickload, and it might cause problems for progression if the map doesn't take coop play into account - locked doors and other showstoppers.

Optimal solution: skip OTP's map! B) 

Yeah, I just bound multiple keys(6, 7, 8, 9, 0) for recording, so it's a quick F9 and the one of those in succession. Worked well enough. 

There's been some confusion about the Quoth 2.2 release - patch vs full release, one of them possibly having (had) an old version of pak2.pak inside. On your site, the paks in both zips have different datestamps. Can you please give a definite answer what is what and how/if the corresponding zips on Quaddicted need to be replaced? 

I think SQL only looks in your Quake directory for the game engines all of mine show up - Fiztquake etc. I notice you have vQuake! That's the first HW accelerated Quake for the Verite V1000 card. 

I guess I just have whatever comes with the Steam release, plus admod and QS. I'd like to come up with another solution to the organization problem, SQLauncher just sorts through all the junk a little better. I don't want all the junk. 

I downloaded the patch and the full versions, extacted pak2.pak from each, and then the progs.dat file from each copy. After checking the both the progs files and the paks themselves with a binary comparison tool, I am happy to share that the files are byte for byte identical across the patch and the full version, and it doesn't matter which one you use. The datestamp isn't a reliable indicator, because it's generated from the zip file metadata and doesn't necessarily correspond to the creation date of the actual file. 

The SHA1 checksum for a current copy of pak2.pak is
e3 57 e0 b2 b7 87 03 e2 eb b3 2a b8 22 91 1b 77 c4 b0 a3 7a

That's the most reliable way to check the integrity. 

Overwrote my base Quake engine (the loose engine files in the Quake folder + Winquake) with QS 0.92.1. Downloaded a fresh copy of QSS and dropped the folder in root Quake. SQLauncher won't read the QSS engine, only admod. What gives? 

Primitive Discarding in Vega

On a serious note, it would be awesome to have compilers with results that are this precise. I can't speak for q1 maps, but creating optimized q3 maps (and source apparently) requires quite a bit of TLC (caulk hulls, hints, area portal, detail, etc). It seems you pretty much have to consider the vis process from the very beginning and build accordingly so that by the end you've essentially vis'd the whole thing manually. I'm still a noob so I could be making it sound more labor intensive than it needs to be. Practically speaking, you'll get very good mileage out of a few well placed hints and area portals, but for really well optimized/vis'd maps you should consider vis on a per-face basis right from the beginning. 

vis rejects things that are occluded by other geometry, the tech they are talking about in the video seems to reject things that are out of the view frustum, or backfacing, or really tiny. Quake engines already take care of frustum culling and backface culling even on unvised maps. So that's separate from what vis has to offer.

In theory, we could use hardware occlusion queries to reduce the need for vis, but i'm not sure if any quake engine uses that or if it's even practical to do it without hand-authored occlusion volumes. 

https://images.voylla.com/fb_campaign_banners/rakhi_gifts.jpg 

any news about the fully vised tronyn/ericw jam6 map? 

It's still vising 

 

Indeed. He only mentions tiny tris, backfacing and frustum culling, but it looks like they're demonstrating occluded geometry culling here? Either way, it was only a wistful joke to soothe my pain... speaking of, I should get back to trying to optimally vis my non-room-corridor-room-corridor map... 

It's still coming :) I haven't been mapping lately, but on the other hand the recent func_detail fixes I made to qbsp were probably necessary to finish this map anyway. 

I'm getting closer to starting up video tutorials for TB2. I wanted to ask some of the newer mappers who use TB2 what topics would be helpful to cover. Maybe not something that you need to know now, but something you wished would have been in a tutorial before you started mapping.

Please everyone weigh in.

For the more experienced mappers what mapping questions do you find yourself answering often? 

That's great ds to make tutorials. Your voice would be easy to listen to and understand.

I can share that when I was new to mapping I wanted to know how to make cylinders, arches, and other curve shapes.

Another simple thing was how to make pools of water and generally openings and corridors from other brushes. When you never used a map editor before, even those things seemed confusing! That was TB1 though.

I see a fair bit of compiling questions as well. 

I remember a while ago I made an image set describing how to use the different clip modes and 3-point clipping. Having something that explained the clip tool in video form seems like it would be useful.

Also can second Bloughsburgh's suggestion around curves, that'd be a good gateway into teaching how CSG works in TB2/in general.

I'd also definitely suggest covering some basic topics. Things like how to make doors move up/down, and how to use things like triggers, counters etc. Things that are relevant to any mapping tool but will probably be new to people who are using TB to try quake mapping for the first time.