buggy?
works fine for me.
With the wireframe checkbox checked, orbiting the model makes the wireframe all garbled, unless you are currently orbiting. Resizing the window makes the green/yellow ring around the model disappear unless you’re orbiting. Certain menu items crash it. Etc.
My Faceposer gesture timing tags are missing, the gestures don’t blend together either, and on top of that, the buttons for previewing the scene are missing and all I have are white squares. Help?
Example: 
lern2ramp
[COLOR=‘Red’]If you don’t have anything helpful to say, don’t post here.
It was less apparent when Half-Life 2 was first out, because there was no game of it’s graphical abilities, but today, Source shadows really suck. It really sucks when you have long shadows in a small room when a chair directly under the light. In my opinion, making shadows better should be the next thing Valve adds to the Source Engine.
I think they’ll use an improved version of the flashlight shadows
What I said was very helpful.
If he learns to use the Ramp tool, gestures and animations will flow seamlessly.
It worked fine without using ramp before. Then one day, Hammer wouldn’t let me used my tools, so I did a quick re-install. Then, Hammer worked, but Faceposer didn’t.
EDIT:
I checked the Ramp tool. I think Source forgot it’s animations:
Why is it that when I try to map for HL2 : DM, weapons respawn in the air above the middle of my map, instead of where I left them? This also happened when I playtested one of garthbartin’s maps, and I tried looking it up in properties, but found nothing 
Make sure your items are positioned correctly (slightly above the ground; not clipping through it) - I am not familiar with this issue or HL2DM but I can only guess that they would have issues respawning if they are clipping through a solid surface somewhat.
Why would source be unable to render an invalid solid structure? I know what makes them invalid, but why does that prevent them from working? Also, look at L4D for the new lighting in the source engine.
It probably has to do with necessary optiomisations that only work on “valid” stuff - if they weren’t optomised the framerate would suffer, but the tricks need valid input or stuff breaks.
I believe it is because the concave structure would fuck up the visleaves and the BSP tree would end up making no sense.
Summary, explanation or reference; take your pick (c:
Hi there, just bumping a thread by 6 months. Nothing major.
Figured better to use an old thread than make a new one.
Any way, the issue:
I have created a moving platform that lowers upon the push of a button, but will retract when shot at by the hunters nearby, necessitating their removal. This is achieved by having them shoot at a NPC-bullseye in front of a brush that on taking damage retracts the bridge (which is parented to a door). The hunter’s AI relationship is changed when the bridge starts to lowered and then reset when the brush is shot. The problem is simple. Upon the brush taking damage, HL2 crashes. Any ideas what is going on?
Does it crash whenever it takes damage, or only when the hunters fire at it? If it always crashes, then you should check all the settings.