All about compiling [GoldSRC Mapping]

[@Pulkz]

I don't mod nor' play GoldSRC Games, yet I watch every single video of yours. Never stop, I love it.

[@DrClock-il8ij]

Perfect timing lol waiting for a 20 minute compile rn to find out why all my entities are invisible

[@greenth-mac2550]

I had to learn it the hard way years ago back when I tried to work with decompiled maps. At least now I find the problems easier and faster than before and attempt to fix them.

[@bosnianherba]

još jedan dobar video od admera! hvala za svu pomoć što dajes goldsrc komunitiju!

[@Admer456]

Nema na čem, hvala na lijepim riječima !!!

[@Bacontsu]

Admer here casually randomly uploading out of nowhere! P.S: Lovely work as always

[@redotix9952]

your videos (and your sona) make me so happy :)

[@SA3_Baython]

THE BROTHER REALLY MAKE LEAK FULL TUTORIAL LIKE WHAT I TOLD HIM Thank you so much ,now because of you i can fix this problem within 3 minutes

[@NotASealZebra]

Love your stuff man, your GoldSrc modding series really helped me out on getting a headstart on modding. I'm now on my 3rd mod project trying to make a Multiplayer based Halo mod for GoldSrc using custom models and anims. Would love to see a video talking about editing Multiplayer aspects such as making/implementing a CTF gamemode like HLOF, loadouts, movement speed edits, etc in the updated sourcecode.

[@saycrain]

YEEeeeessss!! A video from Admer 😄

[@UniMusuotankarep]

Pretty nice video for beginners! Also, I sure did see my post on your Discord server at 7:07.

[@trabant14]

Glad to see you back!

[@alimctavish998]

yoooo welcome back , i've been waiting for a new video :DDDDDD

[@XRAY81]

9:25 There are also microbrush entities that are in void, which happened to me often. It's rare to occur though.

[@teamlambda1337]

This is very useful, thank you so much for your videos! I want to add a trick for finding leaks in very large and complex maps, because sometimes the pointfile isn't very accurate: I basically create a huge worldbrush than encases maybe 1/3 of the map. I then try compiling the map. If the compile process gets past the world creation without any leak warnings, I stop it, knowing that the leak must be somewhere withing the boundaries of my block. I now reduce this block in half and compile again. If it still compiles, the leak is still inside the now smaller block. If the leak now appears, it has to be in the area where the other half of the block was before. With this technique I narrow the potential leak area down until a very small area is left. This usually helps me find the leak very quickly. Also creating these temporary worldbrushes forces the pointfile to change and sometimes it gets more easy to read. :)

[@mil260zs]

I may not map in goldsrc, but just source, but i still find these vids cool to watch

[@NoVIcE_Source]

aah, i really should try goldsource mapping again just for the fun of it

[@seum.]

New Admer video awsumm! :3

[@El_Shephard22]

good evening... one quick question... how do I add pain and death sounds to the player just like deathmatch classic and team fortress classic?

[@americanhuman1848]

noticed your profile says you're an immersive sim fanatic, i recommend system shock 1 (OG version, not the remake, while the remake is pretty good there are plenty of things you should experience from the original first)

[@Admer456]

Funnily enough, I beat System Shock 2 a whiiile ago and have been playing thru SS1 lately. It is a terrific game in the goodest of ways

[@CallOfCutie69]

0:40 I don’t know anything about mapping, but is this Quake-style BSP responsible for GoldSRC (and Source) having such a limited map sizes, limited interactive stuff (entities) you can put into said maps, and, consequently, frequent loadings? Because (Gold)Source loadings, and somewhat artificial, strictly square map geometry have been puzzling me since I was a kid. Or is there a different reason why GoldSRC and Source games seem so.. small scale, so to speak? I’ve always felt that games on different engines had just more.. stuff in their corresponding maps. Do I make sense?

[@Admer456]

Not sure what you mean by "strictly square", there's plenty of examples where it's more organic, e.g. Xen. This question has a super complex answer, it can be both yes and no, depending on your perspective. You can skip to the TL;DR on the bottom of my reply if you don't wanna read all of this. Limited map sizes are partly due to netcode: player coordinates use 17 bits each, of which 12 are for the whole part (going up to 4096), 1 is for the sign, and 4 are for subdecimal precision (i.e. accurate down to 1/(2^4) of a unit). Ultimately, this gives you up to 8192^3 units of playable map space - you can still make stuff outside of it, but you won't be able to go there. This can be overridden in today's mods, but shh. GoldSRC itself can handle about 2048 entities total within a map, which should be pretty reasonable. A hundred NPCs, a few dozen triggers and other logical entities, leaves you with a lot of space for other things. So that is definitely not a reason for small maps. The only problem is that, again, due to netcode, you can only see up to 256 entities simultaneously. This doesn't let you have many entities within close proximity. Since the 25th anniversary, that is now upped to 512 entities, but still. I think the more "frequent loadings" happen simply because they didn't want to waste too much RAM and processing power back then. The original HL maps never really got close to any of the GoldSRC BSP format limitations. Some limitations also stem from the software renderer: it can only render up to 800 map polygons, no more than that. If you go above that, any polygon above the 800th one is simply not gonna get rendered and you'll have missing surfaces. As such, you couldn't have very detailed rooms or outdoor areas. HL1 maps are relatively simple, they are not technologically demanding. I think this is partly because Valve was in a rush to make them all, so there was no time for super duper detailed brushwork, or fitting them with all kinds of props and interactive items. The game itself provides basic tools for us mappers to do interactive things: buttons, doors, trains, levers etc., and you can already do a lot with those. You don't need to specifically make buttons out of buttons, you can use a sliding door entity with the visuals of a button, and the player won't really notice a difference if you do it well enough and consistently. As for Source, I dunno, it's got its own thing. In either case, the engines are pretty capable of non-square geometry, and lots of interaction. It's just that Valve either didn't have the time for it, or they felt like it'd be too much. I can't put the blame on the level editor (Hammer), because games like Unreal, System Shock 2 and Thief weren't made with more advanced tools than that. UnrealEd has some tricks up its sleeve, but fundamentally it's just as "bad" as Hammer, and it has its own quirks. And don't get me started on DromED. But yeah, TL;DR: A combination of networking code in small part (so, Quake-style client-server architecture), lack of time to do lots of polishing and detailing, not wanting to waste a lot of resources (it's easier to digest a dozen small bites than one huge bite), and generally just playing it safe, so that the engine doesn't bite them in the butt. if you had access to GoldSRC, it would absolutely be possible to just raise some of these limitations and make really huge maps, on the scale of Unreal, Gloomwood etc., with lots of interactivity. Sven Co-op has some of these limits raised, as well as Xash3D, and I mean heck, a lot of Quake forks nowadays have it even better. I think it really boils down to how much time you can spend on making one level.

[@CallOfCutie69]

@@Admer456 Thank you for the detailed reply. The loading frequency and map sizes were especially jarring in Portal 2 and Episodes, as “newer” Valve games. It seemed like they retained entire set of limitations of GoldSRC. I think by that time we had dynamic loading and much larger maps as industry standard. Don’t know how are things in Alyx. But it seemed like frequent loadings were some fundamental limitation of Valve’s technology. Square geometry.. Well, it’s like the levels are extremely flat and geometric, like in brutalist architecture, no detail, and there’s stuff just put on top of it. Like props, etc. Gives very artificial feeling, like, I can feel and see geometry, map limitations, particle sources, interactable entities, all the inner works and artificiality of the world, while with time in other games it was hidden better and better. And HL2 and Episodes seemed like they were stuck in the 90s. Compare even CoD4 and Episodes 2, even though CoD wasn’t technologically impressive. The only thing they did to alleviate that feeling was pre-baked destructible environments that saw heavy use in Portal 2, arguably more than in EP2. Or maybe I spent too much time in these Valve games and started to see inner workings clearly.

[@gibsson]

@@Admer456 does source 2 have this kind limitations too? i mean they ditched the bsp altogether in favour of octree

[@Admer456]

@@gibsson Nah, Source 2 maps are basically meshes and Source 2's Hammer is basically a model editor with some game-specific functionality. No longer do you need to worry about the exact shape of your map geometry and how well it can "cut". I don't have a lot of experience with Source 2 though, other than a couple months tinkering with s&box a little bit, so I'm not sure what exact limitations it has of its own.

[@NotGavinV]

are you eventually going to make a video where you combine a series of maps and make it into a single player mod like afraid of monsters but without the custom textures and models?

[@Admer456]

@@NotGavinV That sounds like a custom campaign/map pack, but we'll see. I'll def. have a video on level transitions, cuz' those are a bit tricky

[@NotGavinV]

@@Admer456 do you recommend someone who has the knowledge in this?

[@Admer456]

@@NotGavinV I dunno if there's any videos about it, but here's a written guide: twhl.info/wiki/page/Tutorial%3A_Changing_Levels

[@reiisenmachinima]

When it comes to mapping for Half-Life, would you recommend going with trenchbroom or jack?

[@Admer456]

I make a lot of terrain, so TrenchBroom is the logical choice. I'm also a bit biased towards it because it's open-source and I can extend it with my own features - something I can't do with J.A.C.K. but it's also something most people don't care about. It really depends on you though. If you're a beginner, it's best to mess around and find out which one suits you.

[@Kayosh_]

chad

[@itryen7632]

flob♥️♥️♥️♥️

[@GraVVicE]

can you make a video for half life sdk how ro create a new monster?????

[@Admer456]

Yes, when I finish the weapons programming chapter. The monster/NPC programming chapter will have around 3 videos, focusing on the Half-Life AI system, creating simple NPCs and then ideas by viewers.

[@kez963]

Can't find the leak? Quick fix - Just but a box around your map xP

[@Admer456]

No

[@DeanAmx]

Admer exposed daily acitivity in twhl discord channel

[@polyrobo]

The world if quake tools v2 was open sourced: [utopia] I think I could technically port qrad3 to quake 1 spec but it would be a hassle. Unless I'm an idiot and it is backwards compatable? IDK i'm not clever enough for this

[@Admer456]

They are open-sors though. Quake compilers, Quake 2 compilers, Quake 3 compilers... there's also ericw-tools which supports Q1, Q2 and GoldSRC. Porting qrad3 to Q1 spec is possible, you'd just need to make it monochrome instead of RGB, but t.b.h. modern Quake forks support RGB as a standard thing, with .lit files and all.

[@polyrobo]

​@@Admer456 I was referring to the unreleased version of the quake tools suite that wasn't released publicly but WAS licensed to valve, which you can see mentioned in the publicly released quake tools readme: ""qrad : a radiosity replacement for light.exe. Instead of placing light entities, certain textures automatically become light emiters. The light bounces off of surfaces, so a single light panel can light all sides of a room. qcsg / qbsp / qwrite : qbsp.exe is being broken up into multiple programs to reduce memory usage and provide a better means for experimentation. It should get faster, as well."" - I say quake tools v2 because half life's repo contains qbsp2, and the quake 2 tools were all versioned 3. Quake tools.. It could be a misnomer and i'm just stupid tho

[@Admer456]

@@polyrobo Oh. I've never heard of those oof Besides I don't think it's worth it really, we have VHLT nowadays

[@Fastmancz_]

Thank you for another video.

[@Tr0tim]

nooo flob is toxic

[@Admer456]

Flob is an evil little menace

[@Mittzys]

the focs

[@diegosandoval6316]

FopSRC