⭐ Check out Mannco using this link: mannco.store/?ref=mwu2zdc ⭐ Again, they're actually a great marketplace site, and using my link really helps. Cheers! 🫡
A few tips from my limited experience in dealing with Hammer: You can try making a grouped "hallway segment" for your map out of four brushes ( Walls, floor, ceiling. ) and shaping it with the Vertex Tool, duplicating that segment when required and repeating the process from there. Once you're happy with the rough shape of the whole passage or network of brushes, convert them to displacements and see how it feels to sculpt from there. Applying noise to surfaces makes them instantly feel more "believable", too. I like to use a range of -4 to +4 units on floors and ceilings, and a range of -8 to +8 for things like rocky walls ( Your mileage may vary here depending on what kind of surfaces you're making, of course. Not everything has to be bumpy, and some surfaces may need to be even messier ) Once that's done, smoothing floors a little bit ( Especially in places you expect players to navigate! ) to make inclines easier to traverse, and softening the transition between floors to walls and walls to ceilings can tie the whole thing together. Also the most important tip I think I could bestow upon you is to look at any relevant tutorials from TopHATTWaffle's channel if you haven't already. Even after an entire DECADE, they are still unbelievably useful. Happy mapping!
@@mil260zs it's just practice. one tip that makes it a lot easier is working with cubes as starting brushes so it's easy to align all the vertices, making sewing and stuff like subdivision way easier. also, group your displacements so whenever you go back to sculpting etc., you don't have to select each face again and again (and forget one)
I joined a dust bowl server recently where a guy called “heavy in wall” displacement clipped in the wall outside blue spawn and kept shooting us through it lol
I'm assuming it's because you can't actually make that jump too the roof from there but could be a rare occurrence of LED sarcasm. Getting up there would be huge - I love Hoodoo stage 2 because its fun sneaking teleporters on that roof and I wouldn't need a sentry jump to do it.
Anyone that has worked with displacements in hammer knows about the pain of saving, closing the program only to have to fix all of your displacement seams afterwords because of floating point errors
3:24 collision data takes disk space, memory and CPU time. By disabling collisions on displacements that nothing is ever going to hit (mostly in the 3d skybox), you save up on that data.
I will disclose this secret since NO ONE who talks about OOB explains how to find these exploits, even though it's well known between exploiters: Out of bounds displacement glitches ALWAYS happen in/near coordinates that are powers of 2. Don't believe me? Go to any map that has these glitches, type cl_showpos 1 in console and see for yourself. That's how exploiters find these glitches to begin with. If you find a displacement that sits in a coordinate that's a power of 2, you will most likely be able to get stuck in it, and maybe phase through the displacement if you're lucky. There are still a HANDFUL of OOB glitches that haven't been disclosed by the exploiters. Including an extremely game breaking (but equally hard to pull off) one in Goldrush, by the first stage tunnel.
A good practice to avoid clipping through it's to put nodraw brushes near to displacement surfaces. Not only in seals the map properly, it also helps with visibility culling.
@LEDs I think @RustysRevenge is suggesting that teleporters ctap for you so that you'll essentially be standing up out of the teleporter if there's room, but crouching if there isn't. A good idea, I say!
8:39 This sounds like another case of compiler-specific rounding issues. Presumably, the Windows code is the intended behavior, as the player is stopped from uncrouching due to the solid surface above them, yet the Linux version probably uses a different set of instructions to accomplish this that doesn't work for those edge cases due to imprecision. Sort of like how on Windows servers, small ammo packs give 41 metal instead of 40 due to a less-precise floating-point multiply instruction being used on the former, and since the number's rounded upward to remove decimals, the lower precision gets caught while the high-precision instruction on Linux doesn't.
In the video it is implied it's done with already compiled maps, and the only thing that changes is the operative system running the already compiled map. It is likely like you mentioned some platform-specific rounding for the height check of the bounding box that on Windows correctly causes collision and prevents standing up but on Linux it outputs a different number/result allowing the player to stand up and "skip" that height check, clipping through the displacement.
@@KidaJiwo By 'compiler', I was referring to the tool that compiled the executables/libraries for the server software from the original code. Since Linux and Windows have drastically different architectures, the compiler would need to create two different sets of those files in order for them to work for each platform, leading to the possible mismatch in the CPU instructions that were generated from the interpretation of the source code.
As someone who dabbled very lightly into Hammer mapping back in za day, I wish I could trust anyone as much as these mappers trust displacements without a foundation clip brush behind them. The way I see displacements vs proper brushes is that displacements are comparable to wallpaper, which does its job stopping the elements from passing through but not much more, and brushes are comparable to brick, being very solid and much more reliable against roudy players - just be sure to line them up properly and don't make them _too_ thin or problems start to occur.
no hull collision on displacements does have a usecase! in jump maps specifically it is the main component of something we call "phase", where your rockets will detonate and your stickies will explode, but you yourself can go through. if you're interested in how this gameplay looks i'd recommend looking at the maps jump_phase_b4 and jump_detached_rcx for soldier, and jump_estrogen and jump_the_b7 course 5 for demoman.
So glad to see someone finally talk about displacement clipping! Something of note is that it only occurs near X/Y coordinates that are powers of 2. Here's a list of non-halloween maps you can go completely through a displacement & behind it: Frontier (Fully out of bounds) Borneo (Fully out of bounds) Gravelpit Hydro (Fully out of bounds but limited effectiveness) Yukon Nucleus (Fully out of bounds) Enclosure Upward (Fully out of bounds, somewhat limited effectiveness)
As someone who knows what they do in hammer I can say There was an ancient technique of make brush displacements It's like a simple form of displacements, vertex manipulation of triangular brushes. It's like Alot of triangular brushes, changing their edges positions to make terrain. It was used in the beginning of hl2 development and in hl1 I think
3:08 hi mapper here. The reason these exist is to make different types of clipping in games where the displacement clip doesnt exist and also to make decorative displacements whose collisions should be disabled in different ways. Disabling all 3 is super useful for making a shoreline wave, or a small trash pile, etc
0:16 I looked away to get a drink the split second this red thing on the blue background showed up on-screen, and I shit you not, I for some reason was convinced there was a giant Barney Calhoun behind Demo, filling up the screen, until I looked back to the screen and had to rewind. The human mind.
the power level doesn't increase vertex count, it increases the division. the "weird parameters" are there for optimization. if the displacement is out of bounds (so no player interacts with it), you can disable collision which then doesn't have to be compiled, resulting in faster compilation times and smaller map file size.
8:40 a possible reason why you can displacement clip on linux servers and not windows is the precision difference: linux has ms accuracy for timers and windows has ~15ms accuracy with significant jitter. depending on how source makes a tick or does physics it could mean that the threshold for floating point comparison is wrong, or the linux server has dt values that are too small or prevent colision entirely.
hey, just wanted to say i REALLY like your videos a lot, i love watching everything related to hammer and or source games, keep up the good work! btw, you deserve much more views and subscribers
not a legitimate explanation because I don’t use hammer but it’s good to note that 2^n could be the barriers for certain types of number. In binary, the amount of digits always corresponds to 2^n-1, I.e 000 = 0 and 111 = 7 (or 2^3-1) or 00000000 = 0 and 11111111 = 255 (2^8-1). When you have a negative number, it’s a little more complex but basically it has a leading bit (an extra 1 to display its negative at the very start) and the original number is affected by Twos Complement, where you invert the whole number then add one. Makes it easier to work with. Look up a calculator for it - it’s kind of hard to explain in text. Essentially what could be happening is that it’s reading your collision position wrong by - perhaps - using the negative as a part of the number - making 1 1000 0001 calculate as 193 instead of -127. No collision detected at position 193? go ahead! My guess is that the compilers are slightly different in Win vs Linux causing this mismatch to occur - perhaps a developer tested collision code on windows instead of Linux and missed an edge case. It’s likely not exactly that but the likelihood it’s to do with binary numbers - and how negatives are handled in the engine - is *incredibly* high. I just wanted an excuse to talk a little about binary math and how overflow can be handled (and has been handled in one or two of my own mistakes).
Great video... I still don't understand Source/Hammer but this was fascinating anyways. Also I didn't expect this video to be in HDR so I was surprised how the text overlays were startlingly bright compared to the screen recordings like at 1:00... might need to check that lol, HDR is tricky especially on RUclips and some software does silly stuff with multiple "white" colors.
I could try to add hurt triggers to prevent any exploit, if even found, it will be useless to use. On second though, making a check where no bullets would pass trought
Honestly thought this was going to be about how huge of an issue TF2's hit registration is especially with the whole sniper headshotting you around the corner and spy backstabbing you from 3 feet away and facing your front.
Because the maps' entire optimization process is based around "binary space partitioning", which comes all the way from the development of Doom, and the way it works is that every difference in map geometry cuts the map into segments that it can turn off and on, as well as quickly figure out what can be seen or not seen by the player. Complex geometry is confusing for the program and concave geometry is due to some shenanigans impossible.
Over simplified collision detection that mostly just works. In short, it comes from way long from Quake with it's cheap implementation. These boxes collisions, yes.
valve didnt "create" the displacement thing, but rather a feature from the quake engine afaik. Hammer editor seems to have reworked the interface for useability much more than radiant ever did though. Seems like they half-baked the considerations regards to the physics and boundry checks when it came to some of source engine's improvements however, since it more or less worked fine in quake engine
Stupid Question: why even use displacements if you can (automatically) create similar surfaces out of tiny brushes? Are displacements brushes under the hood?
Displacements are "cheaper" to render, allow blending textures, have better lightning smoothing. The brushes suck to sculpt, "unreliable", and don't resolve collision bugs (referring to pixel walking) To see the maximum you can get from brushes, see counter-strike de_dust2 cliffs near CT spawn.
exactly what xDshot said, a map that is just made out of brushes takes forever to compile and will likely cause gamers with lower end PCs to have really bad fps. sometimes it's better to make something a displacement even if you don't intend to sculpt it, just because it's so cheap and makes next to no difference to how it looks.
I had no idea Source had problem with concaves, damn! That really intrigued me. Seems like such a specific thing but there's probably a good reason for it right? ...Why can displacements have it and not other things though??? Why??
I guess it just has to do with how the engine reads blocks vs displacements? Like displacements don't go through the same checks and calculations as world geometry. This is completely different in Source 2, though.
can shrinking your "player box" be used to escape stuck teleportation spots? if so i wonder if theres a link there for why certain things are how they are and let be...
8:40 this problem most likely occurs because of number rounding problem. on windows it doesn't work because windows rounds higher. meanwhile linux rounds lower and leaves a small gab that allows for such weird stuff. small math errors and problems. that's a speculation tho But rounding thing is real, small medkits gives 41 hp on Win and 40 on linux (soldier's health)
I've been learning Hammer and making a TF2 map for me and my friends to play on, does anyone know if there is a way to cut a hole in a displacement? I made the mistake of making the entire map out of one large displacement and I want to make a tunnel that goes through a hill. Can I delete specific triangles from it or somehow move them around to create a hole in it that I can then fill in with a tunnel? I tried googling this and didn't really find any straight answers on it.
![Noob To Max With DRAGON REWORK In Blox Fruits [FULL MOVIE]](http://i.ytimg.com/vi/LnBMOinoOvA/mqdefault.jpg)
⭐ Check out Mannco using this link: mannco.store/?ref=mwu2zdc ⭐
Again, they're actually a great marketplace site, and using my link really helps. Cheers! 🫡
is this you saying it or them?
displacements are such a pain to work with in hammer, i can barely make a cave without going insane or just not being able to.
i have lots of respect to mappers who can make caves look actually good with displacements
A few tips from my limited experience in dealing with Hammer:
You can try making a grouped "hallway segment" for your map out of four brushes ( Walls, floor, ceiling. ) and shaping it with the Vertex Tool, duplicating that segment when required and repeating the process from there. Once you're happy with the rough shape of the whole passage or network of brushes, convert them to displacements and see how it feels to sculpt from there.
Applying noise to surfaces makes them instantly feel more "believable", too. I like to use a range of -4 to +4 units on floors and ceilings, and a range of -8 to +8 for things like rocky walls ( Your mileage may vary here depending on what kind of surfaces you're making, of course. Not everything has to be bumpy, and some surfaces may need to be even messier )
Once that's done, smoothing floors a little bit ( Especially in places you expect players to navigate! ) to make inclines easier to traverse, and softening the transition between floors to walls and walls to ceilings can tie the whole thing together.
Also the most important tip I think I could bestow upon you is to look at any relevant tutorials from TopHATTWaffle's channel if you haven't already. Even after an entire DECADE, they are still unbelievably useful.
Happy mapping!
Skill issue
Do in Blender 💪
@@mil260zs it's just practice. one tip that makes it a lot easier is working with cubes as starting brushes so it's easy to align all the vertices, making sewing and stuff like subdivision way easier. also, group your displacements so whenever you go back to sculpting etc., you don't have to select each face again and again (and forget one)
I joined a dust bowl server recently where a guy called “heavy in wall” displacement clipped in the wall outside blue spawn and kept shooting us through it lol
Funny spot
How? I though it was fixed.
HES IN THE GODDAMN WALLS
That wall's a bloody Heavy!
“Random spots that serve no purpose”
-shows first step of getting to the best sniper spot on the entire map.
Best Engineer Sentry teleporter and dispenser spot on the roof too.
I'm assuming it's because you can't actually make that jump too the roof from there but could be a rare occurrence of LED sarcasm.
Getting up there would be huge - I love Hoodoo stage 2 because its fun sneaking teleporters on that roof and I wouldn't need a sentry jump to do it.
Only thing I can think of for No Hull Collision setting is being used as snow on top of a floor collision.
fake wall secret waterfall gamer moment backrooms clipping secret spooky secret
Very smart!
@@MadContendery i had a stroke reading this
You right!
@@LEDsOr you could say: "You LIGHT"! Ahahahahahahaha
Help me
The running gag of the player getting sniped got a chuckle out of me everytime it happened.
Anyone that has worked with displacements in hammer knows about the pain of saving, closing the program only to have to fix all of your displacement seams afterwords because of floating point errors
hammer++ in the modern age is a godsend
1:33 spheres are a massive pain too, they always end up getting corrupted
@@alexkoehn5036this is the way
tf2 mappers be like: I have this giant walkable space above the map. This shouldn't be a problem.
Wut the ville?
laggy map
3:24 collision data takes disk space, memory and CPU time. By disabling collisions on displacements that nothing is ever going to hit (mostly in the 3d skybox), you save up on that data.
I didn't know that
I will disclose this secret since NO ONE who talks about OOB explains how to find these exploits, even though it's well known between exploiters:
Out of bounds displacement glitches ALWAYS happen in/near coordinates that are powers of 2. Don't believe me? Go to any map that has these glitches, type cl_showpos 1 in console and see for yourself. That's how exploiters find these glitches to begin with. If you find a displacement that sits in a coordinate that's a power of 2, you will most likely be able to get stuck in it, and maybe phase through the displacement if you're lucky.
There are still a HANDFUL of OOB glitches that haven't been disclosed by the exploiters. Including an extremely game breaking (but equally hard to pull off) one in Goldrush, by the first stage tunnel.
How the fuck?
0:16 free pootis button
Nice
A good practice to avoid clipping through it's to put nodraw brushes near to displacement surfaces. Not only in seals the map properly, it also helps with visibility culling.
This too
5:22 wouldnt it be cool if teletraps just teleported you crouched down
If you hold crouch then you don’t get trapped
@LEDs I think @RustysRevenge is suggesting that teleporters ctap for you so that you'll essentially be standing up out of the teleporter if there's room, but crouching if there isn't. A good idea, I say!
3:00 the LED man doesn't get tired of the barrels in Dustbowl I guess
Aaa~😩
8:39
This sounds like another case of compiler-specific rounding issues. Presumably, the Windows code is the intended behavior, as the player is stopped from uncrouching due to the solid surface above them, yet the Linux version probably uses a different set of instructions to accomplish this that doesn't work for those edge cases due to imprecision.
Sort of like how on Windows servers, small ammo packs give 41 metal instead of 40 due to a less-precise floating-point multiply instruction being used on the former, and since the number's rounded upward to remove decimals, the lower precision gets caught while the high-precision instruction on Linux doesn't.
In the video it is implied it's done with already compiled maps, and the only thing that changes is the operative system running the already compiled map. It is likely like you mentioned some platform-specific rounding for the height check of the bounding box that on Windows correctly causes collision and prevents standing up but on Linux it outputs a different number/result allowing the player to stand up and "skip" that height check, clipping through the displacement.
@@KidaJiwo By 'compiler', I was referring to the tool that compiled the executables/libraries for the server software from the original code. Since Linux and Windows have drastically different architectures, the compiler would need to create two different sets of those files in order for them to work for each platform, leading to the possible mismatch in the CPU instructions that were generated from the interpretation of the source code.
Weird how it was never fixed, seems like an easy tweak
Idk if this was intentional, but the sentry shooting the subsrice pop-up at the end was amazing lol,
Displacement? Just place it correctly
As someone who dabbled very lightly into Hammer mapping back in za day, I wish I could trust anyone as much as these mappers trust displacements without a foundation clip brush behind them.
The way I see displacements vs proper brushes is that displacements are comparable to wallpaper, which does its job stopping the elements from passing through but not much more, and brushes are comparable to brick, being very solid and much more reliable against roudy players - just be sure to line them up properly and don't make them _too_ thin or problems start to occur.
4:10 the soldier waiting was way too funny
Remember csgo dust 2 weapons falling through geometry? That's why.
no hull collision on displacements does have a usecase! in jump maps specifically it is the main component of something we call "phase", where your rockets will detonate and your stickies will explode, but you yourself can go through. if you're interested in how this gameplay looks i'd recommend looking at the maps jump_phase_b4 and jump_detached_rcx for soldier, and jump_estrogen and jump_the_b7 course 5 for demoman.
Oh no he showed the nucleus displacement clip, now that's going to be 500 times more common than it was before 😵💫
So glad to see someone finally talk about displacement clipping! Something of note is that it only occurs near X/Y coordinates that are powers of 2. Here's a list of non-halloween maps you can go completely through a displacement & behind it:
Frontier (Fully out of bounds)
Borneo (Fully out of bounds)
Gravelpit
Hydro (Fully out of bounds but limited effectiveness)
Yukon
Nucleus (Fully out of bounds)
Enclosure
Upward (Fully out of bounds, somewhat limited effectiveness)
5:20 I'm gonna hazard a guess that the map is Frontier.
🏆 WINNER! 🏆
Lowkey pixel jumps sound like a cool thing to use as long it is applied correctly if making a map.
Literally never once in my life seen, heard of or encountered a Sniro, and I've got 10,000 hours in this game. You learn something every day.
MY BRAIN HAS A DISPLACEMENT PROBLEM!!!!! LET SGOO /s
Goo'd my pants /srs
3:00 😭😭😭😭
Womp womp
🤷♂️
As someone who knows what they do in hammer I can say
There was an ancient technique of make brush displacements
It's like a simple form of displacements, vertex manipulation of triangular brushes.
It's like Alot of triangular brushes, changing their edges positions to make terrain.
It was used in the beginning of hl2 development and in hl1 I think
Yup, and also in the original Dustbowl from Team Fortress Classic
8:33 This map still has purple spells that drop from the skeleton king after he’s killed, and you can still get the minify spell from them.
2:55 RINGINGRINGINGRINGING
3:08 hi mapper here. The reason these exist is to make different types of clipping in games where the displacement clip doesnt exist and also to make decorative displacements whose collisions should be disabled in different ways.
Disabling all 3 is super useful for making a shoreline wave, or a small trash pile, etc
0:16 I looked away to get a drink the split second this red thing on the blue background showed up on-screen, and I shit you not, I for some reason was convinced there was a giant Barney Calhoun behind Demo, filling up the screen, until I looked back to the screen and had to rewind. The human mind.
0:28 soldier have becomed miner?
rock and stone
ROCK AND STONE MAGGOT.
An absolutely beautiful video! Fun and informative. Made me want to make TF2 maps myself!
Nice! 😃
the power level doesn't increase vertex count, it increases the division. the "weird parameters" are there for optimization. if the displacement is out of bounds (so no player interacts with it), you can disable collision which then doesn't have to be compiled, resulting in faster compilation times and smaller map file size.
I said it increases the number of vertices you can work with.
@@LEDs yea but a rectangle only ever has 8 vertices in hammer :D
Ive never seen a video in HDR
3:00 Incoming!
Lmao
6:26 at this point cashworks will probably go in history as an example of how to not make a map
I was so focussed on the random perfectly cut deaths
7:24 🤓 Actually that pyro can use that pixel walk to get onto the roof and destroy the sentry nest that's always there. You need to play Hoodoo more.
🤔
Displacements and the clipping tool are the reason why i stop mapping anytime i try to learn
This takes "He's in the walls" to a whole new level
8:40 a possible reason why you can displacement clip on linux servers and not windows is the precision difference: linux has ms accuracy for timers and windows has ~15ms accuracy with significant jitter. depending on how source makes a tick or does physics it could mean that the threshold for floating point comparison is wrong, or the linux server has dt values that are too small or prevent colision entirely.
hey, just wanted to say i REALLY like your videos a lot, i love watching everything related to hammer and or source games, keep up the good work!
btw, you deserve much more views and subscribers
8:40 I'm more interested in why this only works in places where your position is either x or y = -(2^n) which is not explained in the video
not a legitimate explanation because I don’t use hammer but it’s good to note that 2^n could be the barriers for certain types of number. In binary, the amount of digits always corresponds to 2^n-1, I.e 000 = 0 and 111 = 7 (or 2^3-1) or 00000000 = 0 and 11111111 = 255 (2^8-1). When you have a negative number, it’s a little more complex but basically it has a leading bit (an extra 1 to display its negative at the very start) and the original number is affected by Twos Complement, where you invert the whole number then add one. Makes it easier to work with. Look up a calculator for it - it’s kind of hard to explain in text.
Essentially what could be happening is that it’s reading your collision position wrong by - perhaps - using the negative as a part of the number - making 1 1000 0001 calculate as 193 instead of -127. No collision detected at position 193? go ahead! My guess is that the compilers are slightly different in Win vs Linux causing this mismatch to occur - perhaps a developer tested collision code on windows instead of Linux and missed an edge case. It’s likely not exactly that but the likelihood it’s to do with binary numbers - and how negatives are handled in the engine - is *incredibly* high.
I just wanted an excuse to talk a little about binary math and how overflow can be handled (and has been handled in one or two of my own mistakes).
I really like your videos. You speak in a technical and serious way, but the scenes you use to represent what you are saying are so funny!
❤️
I am gaining some forbidden knowledge
And i dont know how scared i should be
I haven't seen any of your videos before but in just the first 4 seconds i knew you're awesome, rock 005 front and center
Thanks bro
5:20 My guess is Yukon
Nope
doomsday :D
1:19 The block tuah 🤪
💀💀
6:06
So THAT is how you are supposed to reach that outcrop?
6:29
It sure came in handy.
It’s one of the hardest jumps in the game. I don’t recommend trying it, this was just for demonstration purposes.
@@LEDs
It does give me ideas for a C&D spy. I mean, people don't tend to check up cliff walls.
I want to see versions of these classic maps that replace all of displacements with flat surfaces
the HDR white text caught me off guard lol
You uploaded in HDR? I dont think ive seen someone do that in a long time. (I shall watch it on my non HDR phone screen lol)
Yeah man, not much TF2 HDR content out there
@@LEDs It actually started to lag the heck out of my app, so I had to swap to non HDR :,(
But I appriciate your commitment for visual clarity
Great video... I still don't understand Source/Hammer but this was fascinating anyways.
Also I didn't expect this video to be in HDR so I was surprised how the text overlays were startlingly bright compared to the screen recordings like at 1:00... might need to check that lol, HDR is tricky especially on RUclips and some software does silly stuff with multiple "white" colors.
You’re absolutely right, it is tricky to nail down. I’m still trying to figure it out.
Love your informative videos about these niche (and sometimes global) TF2 things I've never dug deep into. Keep it up, sir! 🎩🎩🎩
🎩
displacements are just quake 3 patches but upgraded a bit
I could try to add hurt triggers to prevent any exploit, if even found, it will be useless to use. On second though, making a check where no bullets would pass trought
You could use the displacement with no hull collision to do something like waist high snow or something
Honestly thought this was going to be about how huge of an issue TF2's hit registration is especially with the whole sniper headshotting you around the corner and spy backstabbing you from 3 feet away and facing your front.
5:20 Blu's 3rd Spawn on Frontier?
Yes
Displacements are so difficult to work with. Zbrush it is not. I hate the archaic tool so much.
That sponsor transition was smooth as hell
Thanks!
i never understood why source handles displacement likes this, doesnt help that what source calls displacement is like, completely antiquated lmao.
Because the maps' entire optimization process is based around "binary space partitioning", which comes all the way from the development of Doom, and the way it works is that every difference in map geometry cuts the map into segments that it can turn off and on, as well as quickly figure out what can be seen or not seen by the player. Complex geometry is confusing for the program and concave geometry is due to some shenanigans impossible.
You didnt actually explain why displacement clipping occurs... if you do know i would be interested in hearing
Over simplified collision detection that mostly just works.
In short, it comes from way long from Quake with it's cheap implementation. These boxes collisions, yes.
I wouldn’t know, it has something to do with the game’s code and Linux
valve didnt "create" the displacement thing, but rather a feature from the quake engine afaik. Hammer editor seems to have reworked the interface for useability much more than radiant ever did though. Seems like they half-baked the considerations regards to the physics and boundry checks when it came to some of source engine's improvements however, since it more or less worked fine in quake engine
do displacements have better performance than static props?
Wouldn't be also a collision fix to check to binary code to compare the collision check between Windows and Linux to fix it that way?
Funny thing is, vbsp used to compile separate collision info for linux, later it removed, probably shouldn't
i skipped five seconds at the perfect time to make him say "this video is sponsered by- *money"*
Heya LED--my room's been pretty dark for five days now,, and I was wondering when you would switch on again?
Stupid Question: why even use displacements if you can (automatically) create similar surfaces out of tiny brushes? Are displacements brushes under the hood?
Displacements are "cheaper" to render, allow blending textures, have better lightning smoothing. The brushes suck to sculpt, "unreliable", and don't resolve collision bugs (referring to pixel walking)
To see the maximum you can get from brushes, see counter-strike de_dust2 cliffs near CT spawn.
Tiny brushes are always bad. Displacements are not brushes under the hood.
exactly what xDshot said, a map that is just made out of brushes takes forever to compile and will likely cause gamers with lower end PCs to have really bad fps. sometimes it's better to make something a displacement even if you don't intend to sculpt it, just because it's so cheap and makes next to no difference to how it looks.
Adding on to this, some mappers use displacements for blending textures on man-made stuff, like the walls on Embargo and Sandcastle, for example.
5:20 is the tunnels between A and B in Gravel Pit
No
My Favorite Tf2 topic discussion
WALLS and/or FLOOR
I had no idea Source had problem with concaves, damn! That really intrigued me. Seems like such a specific thing but there's probably a good reason for it right? ...Why can displacements have it and not other things though??? Why??
I guess it just has to do with how the engine reads blocks vs displacements? Like displacements don't go through the same checks and calculations as world geometry. This is completely different in Source 2, though.
@@LEDs hey thanks for replying :]
8:39
LINUX STRIKES AGAIN
What does the source engine have againse concave things?
valve shall switch to windows servers now
they should really be fixing linux tf2 so it rounds correctly, linux uses much less cpu than windows (thats why valve uses it)
linux uses less cpu/ram than windows + valve should fix linux tf2
I feel like the mystery map could be either Vanguard or Foundry leaning on both but I'm likely wrong
Neither
Could anyone tell me what song is used at 6:20 ?
I miss old cashworks :(
everytime i watch one of these videos, i bust everwhere
Amazing quality video ❤
can shrinking your "player box" be used to escape stuck teleportation spots?
if so i wonder if theres a link there for why certain things are how they are and let be...
Awesome sauce video, lighting!
3:36 why not just cut a normal brush here?
i have watched this 3 times i love this
8:40 this problem most likely occurs because of number rounding problem.
on windows it doesn't work because windows rounds higher. meanwhile linux rounds lower and leaves a small gab that allows for such weird stuff.
small math errors and problems.
that's a speculation tho
But rounding thing is real, small medkits gives 41 hp on Win and 40 on linux (soldier's health)
Hey led, I might want to work on sfm, can you tell me what are you using?
probably sfm
He uses blender and sfm for his thumbnails
Blender. I don’t use SFM anymore.
particularly based video, thank you LED
Thanks for the based comment
There are definitely maps that have those stair that fuck up explosives
I've been learning Hammer and making a TF2 map for me and my friends to play on, does anyone know if there is a way to cut a hole in a displacement? I made the mistake of making the entire map out of one large displacement and I want to make a tunnel that goes through a hill. Can I delete specific triangles from it or somehow move them around to create a hole in it that I can then fill in with a tunnel? I tried googling this and didn't really find any straight answers on it.
Nope
@@LEDs I have since come to that conclusion and reworked the map, ty for responding though
TF2 without modelling problems isn't TF2
Or hats, characters, visual style, color, gameplay balancing, and community, and more.
(Team Fortress Classic too)
great video my brother
1:23 oh god please have mercy for they do not know their sins.
5:21 was it gravel pit?
No
@@LEDs NOOOOOOOOOOOOOOOO!!!!!!!!!!!!!!!!!!!!!!!!!!!!1
Displacement? Like physics?
I thought I was watching solarlight so when I saw the green beard and hat I was scared then realised it wasn’t solarlight
bullets but no fire seems like glass
5.20 breadspace? Not sure
Nope