Payload cart stops at second point

I'm working on a payload map (as you may have already gathered), and for reasons I can't really figure out, the cart just ends after capping the second point.

It's not stuck on geometry, if it was stuck, you'd still be able to "cap it", but here it just turns off, like the round ended.

After a few seconds, the cart starts rolling backwards, and even triggering the push area won't affect it.

Is this a common problem, or should I upload a .vmf?

 

Just use this: ABS Ultimate Resource Pack
When you download it and install it, you can open use an already created payload prefab.

 

I'm already using that, but I didn't copy the caps straight from the example map.

I've checked the two, doesn't seem like mine are any different.

 

Hmm... If it's not something with geometry, i don't know what it is.
Maybe upload your vmf.

 

Sounds like you aren't advancing the targeted CP, therefore the cap area goes inactive.

 

http://filesmelt.com/dl/payload_bug.zip

Please take a look at it, I've been wracking my brain to figure it out.

 

...that's not exactly all the entities. How is anyone supposed to figure anything out.

 

Alright, but I don't see the reasoning, I was trying to narrow it down to the problem areas.

What would you prefer I upload?

The whole track or the whole map?

 

At the very least I'd need the cart entities, the track, and the core entities (watcher, rounds, etc).
As it is, you are here because you don't know what the problem is, so trying to narrow it down according to your knowledge is somewhat silly logic to follow

 

http://filesmelt.com/dl/payload_bug1.zip

That's the cart, game entities, path_tracks, and capture points.

It's not getting stuck on geometry, I've confirmed this by using ingame console commands to get the train to keep advancing.

 

Your final point is still set to require ownership the third CP (which you don't have). This might have been noticeable in the first thing you uploaded, but I just didn't even want to spend time looking at such a small piece of the puzzle.

Also, when the second point is captured it disabled the wrong path (cart will roll back further than the point).
Lastly, you should always use the CaptureCurrentCP input to perform the captures, because that will cause the capture to show in the death notification area and recognize the people who did it. Sending SetOwner directly to the TCP bypasses the TCA and prevents that, however the SetOwner still needs to be there as a fail-safe because it's possible for CaptureCurrentCP to fail under rare conditions.

 

Thanks, buds.

Keep up the good work.