Page MenuHomeFeedback Tracker

Ambient animals behaviour broken with recent dev builds eg 1.41.129406
Closed, ResolvedPublic


There seems to be something awry with the behaviour/FSM of the various ambient animals with recent dev builds.

createAgent ["Goat_random_F",position player, [], 0, "NONE"];
This code spawns a goat near the player. Previously, this goat would then wander around grazing and doing goatlike things. With the latest dev builds the goat behaves normally for a few seconds and then freezes.

createAgent ["Hen_random_F",position player, [], 0, "NONE"];
Chicken freezes after a few seconds same as the goat.

createAgent ["Sheep_random_F",position player, [], 0, "NONE"];
The spawned sheep now runs around endlessly, never stopping.

createAgent ["Fin_random_F",position player, [], 0, "NONE"];
Dog never actually moves anywhere, but is not frozen.


Legacy ID
Steps To Reproduce

Enter the following into the debug shell:

createAgent ["Goat_random_F",position player, [], 0, "NONE"];createAgent ["Hen_random_F",position player, [], 0, "NONE"];createAgent ["Sheep_random_F",position player, [], 0, "NONE"];createAgent ["Fin_random_F",position player, [], 0, "NONE"];

Observe the strange behaviour of the animals that spawn near the player

Additional Information

I know this seems like a trivial observation but for those of us trying to run ambient animal scripts to liven the place up, these latest changes are reducing functionality quite a bit.

Event Timeline

tpw edited Steps To Reproduce. (Show Details)Feb 22 2015, 11:09 AM
tpw edited Additional Information. (Show Details)
tpw set Category to Other.
tpw set Reproducibility to Always.
tpw set Severity to None.
tpw set Resolution to Duplicate.
tpw set Legacy ID to 431701043.May 7 2016, 8:18 PM
R3vo added a subscriber: R3vo.May 7 2016, 8:18 PM
tpw added a subscriber: tpw.May 7 2016, 8:18 PM
tpw added a comment.Apr 7 2015, 5:38 AM

As of build 130139 the goat and sheep are invisible.

Thank you for the report! I've marked this ticket as a duplicate, we will solve the issue in the following ticket which is already assigned: