My biggest gripe right now is the inadequate "alt+rightclick" functionality.
It only works well on 90 deg angles.
PB, you're doing god's work though. I love this program
Forum posts
It's the first entity i tried.
I used them because you can have a hundred of them in a map and they don't do anything
I used them because you can have a hundred of them in a map and they don't do anything
My issues actually started with sledge - I don't think the angles work properly (probably a bug).
Ceiling and floor lights are fine, but anything with an odd angle takes less thought if it has a target.
Ceiling and floor lights are fine, but anything with an odd angle takes less thought if it has a target.
Love how we're picking games when we were told to choose a map 
Dimby, you're better than that bruh
Dimby, you're better than that bruh
Long and short of it is.. give light_spots a target and you don't need to fiddle with the angles, pitch yaw roll etc.
https://youtu.be/0UcFqgM0AfQ
https://youtu.be/0UcFqgM0AfQ
Is this: CLICKY the correct VHLT version?
Also, what compile settings will you use?
Also, what compile settings will you use?
Is that the Source Crowbar?
Maybe you're better off attaching a sprite to the model?
Can't even begin to guess how to do that, though
Can't even begin to guess how to do that, though
sounds fun!
count me in
count me in
I would think you could hide the camera pan with an env_fade
This post was made on a thread that has been deleted.
See if there's a "compile visible only" flag in your compile options.
Any giant brushes that you thought were entities but actually arent?
Make sure your visgroups are all enabled when you compile.
Have you tried doing a full compile?
Alt-P checks out ok?
There's no giant groups anywhere?
Are the cordon bounds enabled?
Have you tried doing a full compile?
Alt-P checks out ok?
There's no giant groups anywhere?
Are the cordon bounds enabled?
You did have a leak error in there.
Load up the pointfile
Load up the pointfile
That's pretty sexy instant mix!
Did you get a texture rip from Prime?
Did you get a texture rip from Prime?
Also, pretty certain that Tetsu0 used inches when making a model for goldsource and it matches perfectly with the hammer grid.I think 10 blender centimeters = 1 goldsource unit
I think you're going to have a hard time solving this one.
There's very little overlap in Spanish speakers and coders on this site.
Have you successfully compiled the code before you tried adding things?
There's very little overlap in Spanish speakers and coders on this site.
Have you successfully compiled the code before you tried adding things?
have you tried using a monster_generic? Perhaps the AI is interfering with everything.
Check your timings
Make sure you have info_nodes
Make sure the scripted_sequence has enough room around it for the monster to actually get there.
Run everything with developer 4 so you can see (top right of screen) when things trigger and if they're being blocked by something
Check your timings
Make sure you have info_nodes
Make sure the scripted_sequence has enough room around it for the monster to actually get there.
Run everything with developer 4 so you can see (top right of screen) when things trigger and if they're being blocked by something
yeah it should be but the weapon code is fucking EVERYWHERE
Not to mention you need ammo types and then the skill.cfg file
Not to mention you need ammo types and then the skill.cfg file
What weapons do you want to add?
There's a few different base types that you can expand upon.
There's projectile weapons: grenades and crossbow
There's linetrace weapons (no travel time): pistols, rifles
Multi-shot linetrace weapons: shotguns
Surely your new weapon type would use something along those lines?
There's a few different base types that you can expand upon.
There's projectile weapons: grenades and crossbow
There's linetrace weapons (no travel time): pistols, rifles
Multi-shot linetrace weapons: shotguns
Surely your new weapon type would use something along those lines?
greatest youtube video ever
Check the compile log for entity counts (%)
that's a pretty epic source, Bruce, thanks!
multisources are pretty straight forward..
the wheel's master should be the multisource. trigger the multisource to 'unlock' the wheel.
example: http://twhl.info/vault.php?map=6046
run "developer 4" in the console, and then run a test so you can see when each entity gets triggered.
if something doesn't have a "master" field, you're gonna need to find another way around the problem
the wheel's master should be the multisource. trigger the multisource to 'unlock' the wheel.
example: http://twhl.info/vault.php?map=6046
run "developer 4" in the console, and then run a test so you can see when each entity gets triggered.
if something doesn't have a "master" field, you're gonna need to find another way around the problem
It will be a true infinite horde, but if you want 50 monsters to be alive at any time, you need 50 monster makers with unique child names that can only have 1 child alive.
Off grid bothers me, but it's alright if you use HLFIX or Sledge. I'd still recommend sticking to at least 8 unit grid with world sealing brushes.
Well in that case, you want a logic_branch, but there's probably simpler ways of doing things which are definitely event specific.
Logic branch holds a 1 or 0 value; by default it's 0.
The button TESTS the logic branch which fires TRUE or FALSE outputs.
So the default action is ON FALSE.
The event will set the logic branch value to 1.
The new wanted action is ON TRUE
BUTTON OUTPUTS:
func_button:On Pressed -> logic_branch:Test
LOGIC BRANCH OUTPUTS:
logic_branch:OnFalse-> Do Default Action
logic_branch:OnTrue-> Do New Action
OTHER EVENT OUTPUTS:
Misc_Event:OnTrigger-> logic_branch:SetValue:0
Logic branch holds a 1 or 0 value; by default it's 0.
The button TESTS the logic branch which fires TRUE or FALSE outputs.
So the default action is ON FALSE.
The event will set the logic branch value to 1.
The new wanted action is ON TRUE
BUTTON OUTPUTS:
func_button:On Pressed -> logic_branch:Test
LOGIC BRANCH OUTPUTS:
logic_branch:OnFalse-> Do Default Action
logic_branch:OnTrue-> Do New Action
OTHER EVENT OUTPUTS:
Misc_Event:OnTrigger-> logic_branch:SetValue:0
Yeah there's no real way to give you a solid answer.
Present us with a situation and we can definitely help out.
If you figured it out for yourself, let us know!
Present us with a situation and we can definitely help out.
If you figured it out for yourself, let us know!
You could also just make the floor open up and then the player falls 50 feet into a nasty pit of sewer water infested with leeches.
place a single spotlight over the only ladder in view.
When the player is 15 feet from the ladder, shut off the light and play super loud metal groaning sounds.
Then instantly teleport the player into a re-creation of the teletubbies playhouse.
place a single spotlight over the only ladder in view.
When the player is 15 feet from the ladder, shut off the light and play super loud metal groaning sounds.
Then instantly teleport the player into a re-creation of the teletubbies playhouse.
To be fair, i just saw the floating cyclers and immediately saw that as the issue - I didn't even try to compile.
That being said, your map should still generate a pointfile if the compile tools detect a leak. After compiling, in Hammer, Go to MAP > Load Pointfile. The .pts file should be located wherever your .rmf or .map is located.
You'll see a funky colored line bouncing all over the place. Follow that in the 3D view starting from the leaked entity (noted in the compile log).
That being said, your map should still generate a pointfile if the compile tools detect a leak. After compiling, in Hammer, Go to MAP > Load Pointfile. The .pts file should be located wherever your .rmf or .map is located.
You'll see a funky colored line bouncing all over the place. Follow that in the 3D view starting from the leaked entity (noted in the compile log).
You have cycler sprites in the void.
That'll do it everytime.
That'll do it everytime.
^^^^^^^^^
Go into edit mode and Edge select mode
Select a bunch of edges where you want to create seams (hard corners etc)
Once that's done, select all, and find the UV unrwap option.
Then you can pull open a new window, set it to UV view.
Select a bunch of edges where you want to create seams (hard corners etc)
Once that's done, select all, and find the UV unrwap option.
Then you can pull open a new window, set it to UV view.
Have you tried different compile tools?
Is that grate it's own entity - aka it's not a group?
Try replacing the func_walls with func_illusionary and placing a clip brush over them.
I know it's a pain, but there are so many other things to try.
Is that grate it's own entity - aka it's not a group?
Try replacing the func_walls with func_illusionary and placing a clip brush over them.
I know it's a pain, but there are so many other things to try.
He even goes through when the wall isn't bustedHACKER!
Yeah like everyone else said, they need to be textures within a WAD.
Use a trigger_camera to quickly take over the player's view and point at a textured wall. If the resolution is too low, split the image into multiple textures, and use 4 textures instead of 1.
Other than that, you'll need to make a custom overlay and code it into the gameplay - which is far more time consuming and then you'll need to distribute the custom binaries.
Use a trigger_camera to quickly take over the player's view and point at a textured wall. If the resolution is too low, split the image into multiple textures, and use 4 textures instead of 1.
Other than that, you'll need to make a custom overlay and code it into the gameplay - which is far more time consuming and then you'll need to distribute the custom binaries.
The issue you're having there is (in my opinion) leaf node related.
When you're halfway up the ramp, you're occupying a leaf node that the engine doesn't think can see the fire.
A hint brush could help with that.
I would first try to create a hint brush that faces the floor and is on the same plane as your wall trim.
That will force the room to be divided half-way up the ramp and then the engine will calculate all other leaf nodes. You should be able to see the fire after that.
Also, use the latest VHLT
To answer your question abaddon, HINT brushes only define edges of vis leaves. You can have 100 vis leafs in a row, and so long as the first can see the last (essentially a ray-trace), you'll be able to see everything within those.
This is why VIS takes so freakin long - it almost has to check if every single vis leaf can see every other one.
When you're halfway up the ramp, you're occupying a leaf node that the engine doesn't think can see the fire.
A hint brush could help with that.
I would first try to create a hint brush that faces the floor and is on the same plane as your wall trim.
Also, use the latest VHLT
To answer your question abaddon, HINT brushes only define edges of vis leaves. You can have 100 vis leafs in a row, and so long as the first can see the last (essentially a ray-trace), you'll be able to see everything within those.
This is why VIS takes so freakin long - it almost has to check if every single vis leaf can see every other one.
Thanks for the Shout, Captain 
I could write another book just on Goldsource Optimization.
The clip brush limit is evil
Also, don't clip anything but 90 degree surfaces. (cubes, rectangular prisms, etc)
You might be better off making it one huge model and surrounding it with Null brushes.
I could write another book just on Goldsource Optimization.The clip brush limit is evil
Also, don't clip anything but 90 degree surfaces. (cubes, rectangular prisms, etc)
You might be better off making it one huge model and surrounding it with Null brushes.
What if you make the wall a func_illusionary and use clip brushes to block the player only?
That or place a smaller func_wall_toggle inside the func_illusionary that will block anything until the hole gets created.
Then you can switch off the func_wall_toggle and create essentially a passable wall.
Smoke and mirrors, my friend.
That or place a smaller func_wall_toggle inside the func_illusionary that will block anything until the hole gets created.
Then you can switch off the func_wall_toggle and create essentially a passable wall.
Smoke and mirrors, my friend.
YES! ANOTHER SOURCE MAPPER
Welcome to TWHL!
To get a good sense of scale, try this:
Create a floor brush 512u wide x 512u long x 16u tall.
Make 4 walls that are 120u high x 16u deep.
Clone the floor to the ceiling (shift+drag) and then texture everything as you see fit.
Place 3 prop_physics entities on the floor and set one as a chair, one as a table, one as a floor lamp.
As far as doors go, place a prop_door_rotating somewhere in the level - then you can build a frame around the door (you'll need to drop your grid setting down to 1)
Welcome to TWHL!
To get a good sense of scale, try this:
Create a floor brush 512u wide x 512u long x 16u tall. Make 4 walls that are 120u high x 16u deep. Clone the floor to the ceiling (shift+drag) and then texture everything as you see fit. Place 3 prop_physics entities on the floor and set one as a chair, one as a table, one as a floor lamp. As far as doors go, place a prop_door_rotating somewhere in the level - then you can build a frame around the door (you'll need to drop your grid setting down to 1)
This post was made on a thread that has been deleted.
YEAH!
Nice work
Nice work
is the direction facing east in hammer?
All trains need to start facing left->right (east)
All trains need to start facing left->right (east)
No changes, just clean it up. No double walls etc..
Relax guys. Lets whip up a new basemap and settle on EP2. Do we really need chapters? My thoughts say no...
I think Unq has the answer here. Ensure the names are exact. Ensure the level transitions are referencing the same thing. Also check to see you don't have a hidden duplicate landmark somewhere
Just slap an autosave before each level. Only the VERY first autosave should be a new chapter.
Pros and cons to this being a mod:
PROS
Ease of download and launching maps
We could add custom code
Splash Screens
CONS
More Work
Kinda overkill since this is a glorified map pack
We lose some EP1 & EP2 content
Pros and cons to this being a mod:
PROS
Ease of download and launching maps We could add custom code Splash ScreensCONS
More Work Kinda overkill since this is a glorified map pack We lose some EP1 & EP2 contentEach level still has to have a player start.
And just make sure your landmark is in the right place.
And just make sure your landmark is in the right place.
Two Things Ghost:
1) You're probably right about the folder location, there's been a "HL2 BIN" shortcut on my desktop since... a long time ago... and I'm at work and can't check
2) Your message signature is unnecessary.
1) You're probably right about the folder location, there's been a "HL2 BIN" shortcut on my desktop since... a long time ago... and I'm at work and can't check
2) Your message signature is unnecessary.