Quote from Skotty on June 30, 2012, 7:43 am

BlackBird Studios wrote:

ONMAPSPAWN: Crusher: SetPlayBackRate: Parameter 1

To make them slower, you need to use smaller values than 1, for example 0.6.

Quote from MasterLagger on June 30, 2012, 10:54 am

Skotty wrote:

BlackBird Studios wrote:

ONMAPSPAWN: Crusher: SetPlayBackRate: Parameter 1

To make them slower, you need to use smaller values than 1, for example 0.6.

To make things more specific, like Brainstone said, setting the "SetPlayBackRate" to 0 puts the animation speed at 0%, while setting the "SetPlayBackRate" to 1 puts the animation speed at 100% (the original animation speed). So putting the "SetPlayBackRate" to 0.5, for example, would reduce the animation speed by half (50%).

Quote from BlackBird Studios on July 1, 2012, 1:52 pm

Thanks very much Brainstorm, Skotty, and MasterLagger. This should hopefully indeed help the crushers. Now I just gotta wait 1 hour and 19 minutes just for the compiling alone for one portion of the map to see the result of this change lol

(A little help if anyone wouldn't mind, is there a way to find the spot in your map in which it is leaking, it is causing my map to not load in Chapter 2. Idk why, but it has to be just the smallest crack imaginable... Nothing to obvious. If not, I guess I will just have to fly around until I literally find it... (and now I am getting an error message from something else now... which closes portal down before I can even start it up) I am getting confused by the second, if a trigger leaks does that cause an error at all? Even if it is from the smallest smallest crack?

EDIT: Alright so I found what is wrong with my map and why it wont compile, I deleted the last edit so it didn't look so big here on the forums, but it is my arm panels. When I deleted them the map spawned fine, put them back up, Portal 2 would get to 2 blue circles on the loading screen and then it would crash. I can't find the problem with these arms though. I've used the before perfeclty fine but now idk. If anybody can help me with this second problem also that would be great.

Quote from FelixGriffin on July 1, 2012, 2:42 pm

Map > Load Pointfile, then look for a red line escaping your map.

Quote from MasterLagger on July 1, 2012, 4:18 pm

Yeah, but the problem isn't a leak (but still nice to know anyway), it's the arm panels. Is the arm panel the one that rotate to open walls, floors, etc and has the blue glass on it?

Quote from BlackBird Studios on July 2, 2012, 7:25 pm

Ok I did what you said Griffen, but the red line is the weirdest line I've ever seen. It comes out of a wall that (I know definitly has no holes in it and the line extends outwards from the box and then shoots up at an angle and comes back down...

And to answer your question MasterLagger, no they are the arm54x64_interior.mdl, the ones that look black and have 2 verticle lines coming down in the middle and the whole thing is connected to an arm.

In response to you BEARD!, I did what you said, but still no dice. I checked the map and there are no fun_detail that are left open. Anything that I thought would cause a problem like that, I just covered it ontop with a wall. I really can't find out what's going on. It has to be somthing in the map because I created a bigger box around my map to see if that would get rid of the problem, but soon when I expand the map, I don't want that box there so I would like to try to find the problem.

If anybody has anymore ideas on what to do that would be greatly appreciated.

Quote from BEARD! on July 2, 2012, 7:27 pm

Brushes that are func_detail won't seal the map against leaks; perhaps this is (part of) your problem. A good way to check would be to use visgroups. In the Auto Visgroups section to the right-hand-side of hammer, try turning off everything except for "World Geometry". This should help clarify where the leak is occuring.

Quote from HMW on July 3, 2012, 2:43 pm

BlackBird Studios wrote:

[...] the red line is the weirdest line I've ever seen. It comes out of a wall that (I know definitly has no holes in it and the line extends outwards from the box and then shoots up at an angle and comes back down...

If you are sure that this wall is not a func_detail or something like that, then it could be that the brush is just invalid. This has happened to me a few times as well. Just delete and recreate the wall and try again.