PChase doesn't seem quite right

[Cloudee1]

When using PChase to have an actor chase after ego, and ego is on the move, then the other actor seems to stutter. When ego stands still, the other actor moves fluidly. It seems that when the ego is moving then the other actor is to busy trying to figure out where to go than actually go somewhere.

Code: [Select]

(offerGuy:setCycle(Walk)setMotion(PChase gEgo 20 offerScript))

As a side note, PFollow seems to suffer from the same stuttering issue while ego is on the move. Something I didn't realize before now, PFollow does not take the cue at the end.

Code: [Select]

(offerGuy:setCycle(Walk)setMotion(PFollow gEgo 10)) // correct
(offerGuy:setCycle(Walk)setMotion(PFollow gEgo 10 offerScript)) // oops error

Not that there is anything wrong with that, just didn't know.

[troflip]

With PFollow, the client is constantly following the target, so it never reaches the destination. Hence no cuee. The docs are live ;-) : http://scicompanion.com/Documentation/Classes/PFollow.html?highlight=pfollow

Although I guess they don't spell it out explicitly.

It's possible there's been a decompilation bug with PFollow/PChase, I'll have to take a look and see if I can repro this. Thanks for bringing it to our attention!

[edit:] Hmm, I'm not seeing any stuttering... I actually used this as I was writing a tutorial for Motion classes. It doesn't seem to be any different when the ego is moving or not. What does the stutter look like?

[Cloudee1]

Here you go. You will want to open script 35 and start from there.

After pulling into the screen, ego will hop off the skimmer and a guy will appear from the north. That's the guy.

Simply walk around and you should see the issue that I am referring to.

[Cloudee1]

Those are some pretty nice docs you've got going there Phil. I am assuming that you have a template game that you have been working on as well. The reason I say that, I noticed this description of aimtoward that claims to be a public procedure in main but I sure can't seem to find it in there.

http://scicompanion.com/Documentation/Procedures/AimToward.html

[troflip]

Ugh, yeah, that stuttering is awful. I can't immediately see why it's happening.

If you just create a basic new room and make an actor follow the ego, I suspect it won't happen. So something in that room is causing it, presumably.

Those are some pretty nice docs you've got going there Phil. I am assuming that you have a template game that you have been working on as well. The reason I say that, I noticed this description of aimtoward that claims to be a public procedure in main but I sure can't seem to find it in there.

http://scicompanion.com/Documentation/Procedures/AimToward.html

It's proc0_8 in your Main.sc. It has a name now :-)

[Cloudee1]

So it was apparently the large views. Ship1, Ship2, and the doorway. I used them because it turns out I was to lazy to fight with the priority and the polygon combinations to get it right. I hate it when things don't line up with the priority bands lol. Anyway, with a small tweak I got the stutter to go away.

I changed them from Prop's that were init'ed to use addToPic instead and the stutter has gone away.

However if I remember correctly, I can now no longer use a noun property on them, only when they are init's. So I will have to go in and add a couple of features so that I can register clicks on them now.

[Cloudee1]

By the way,  that AimToward... that kicks ass. I went ahead and changed the procedure name in my main script to match. Then I made use of it in the very script and scenario that we were looking at.

Code: [Select]

(case 0 (offerGuy:setCycle(Walk)setMotion(PChase gEgo 20 offerScript)))
(case 1 (send gGame:handsOff())
        (send gEgo:setMotion(NULL))
        AimToward(gEgo offerGuy offerScript)
)


[lskovlun]

I changed them from Prop's that were init'ed to use addToPic instead and the stutter has gone away.

You could also have called stopUpd on them.

[Cloudee1]

Thanks for that Lars, that does indeed work as well. This is the approach that I am going to use as it restores the ability to set the noun property of the instances rather than going through and creating features taking up the same space.

Code: [Select]

(ship1:init()ignoreActors()stopUpd())