Kismet behaviour change since patch

[LordGleedo]

Just tried running my map since the patch in PIE and my objectives which are cap only and lock are not getting locked. Once capped, they are then in 'defend' mode

Anyone else seeing this? I have tried outside of PIE yet....

[Drecks]

I have noticed this one time during the free weekend on the TWB server on
my own map.As Allies we where defending an objective while the game told me
to capture it. I quickly made a screenshot.

You see a Russian which have to cap the objective while the overhead shows the objective B
is already red...





Weird thing was this happend only 1 time. I decided to commit suicide and
spawn as Axis. Their end worked normal they also had to attack the objective. Which was normal. When I spawned back as Allies all worked well. My guess is that is was some sort of hick up.....

[LordGleedo]

Well I do not know what the heck is going on. All my cap 'n lock objectives are now not locking and can be recaptured (since the patch).

I'll be buggered if I'm gonna redo all my figgin kismet again.

This coupled with the fact that it now seems impossible to get a new game type running online on a server without getting all stock maps recompiled/cooked with the new gametype as a supported game type means I am wasting my time...

Its all gone Snafu!

[LordGleedo]

It seems as though the 'Lock Objectives' node no longer work which was causing my issue.

If you remove the lock objective node, captured and disabled objectives lock ok.

[Catalavos]

Originally Posted by LordGleedo

It seems as though the 'Lock Objectives' node no longer work which was causing my issue.

If you remove the lock objective node, captured and disabled objectives lock ok.

Wish I would have re-checked this thread before I nuked all of my Kismet this morning. Oh, well.

[LordGleedo]

Originally Posted by Catalavos

Wish I would have re-checked this thread before I nuked all of my Kismet this morning. Oh, well.

DOh!

[Catalavos]

Originally Posted by LordGleedo

DOh!

I'll just consider it practice. Kudo's for figuring it out, by the way!

[[TW]Swag]

In my quick testing the Lock Objective Kismet node does in fact work. There is a method to working with the Lock/Unlock when it's a situation where an objective can be unlocked for whatever reason.

Disable Objective -> Lock Objective

Unlock Objective -> Enable Objective

Make sure your Kismet is handling it that way. Also, make sure your problematic objective(s) isn't being lock/unlocked somewhere else in the Kismet logic.

[LordGleedo]

Originally Posted by [TW]Swag

In my quick testing the Lock Objective Kismet node does in fact work. There is a method to working with the Lock/Unlock when it's a situation where an objective can be unlocked for whatever reason.

Disable Objective -> Lock Objective

Unlock Objective -> Enable Objective

Make sure your Kismet is handling it that way. Also, make sure your problematic objective(s) isn't being lock/unlocked somewhere else in the Kismet logic.

Well it was working perfectly before the patch and is now again working since completely removing the locks. Go figure.

[[TW]Swag]

Originally Posted by LordGleedo

Well it was working perfectly before the patch and is now again working since completely removing the locks. Go figure.

Negative. I just made a simple test map in the public SDK to see if the locking kismet node is malfunctioning. It is not in my test map.

Could you please copy your Kismet with the Lock Objective Kismet node into a text document and email it to me? I suspect that Kismet may be whipping your map around.