AirSpeed upper-limit possible bug? Or MoveTo()?

[ExpEM]

Working on a new pawn, noticed that MoveTo(Destination,AirSpeed) seems to have an upper limit. AirSpeed 400, AirSpeed 2000 and Airspeed 10000 make no difference. I have not tested extensively if other people want to look into it, otherwise I'll get back to this after I finish this current project.

[[]KAOS[]Casey]

what PHYS mode is this pawn in under Physics? I do know theres a lot of native fuckery with physics modes behind the scenes.

[ExpEM]

what PHYS mode is this pawn in under Physics? I do know theres a lot of native crappity smackery with physics modes behind the scenes.

PHYS_Flying.

You can replicate what I'm talking about by messing around with the AirSpeed of a Bird FlockPawn with bCircle = True. And timing how long it takes to complete a full circle, no observable difference at any speed over 1000.

[Smirftsch]

MoveTo also depends on MaxDesiredSpeed, maybe it's that?

[code]
Max(0.f, Min(MaxDesiredSpeed, speed));
[/code]
while speed would be AirSpeed in this case.

[ExpEM]

MoveTo also depends on MaxDesiredSpeed, maybe it's that?

[code]
Max(0.f, Min(MaxDesiredSpeed, speed));
[/code]
while speed would be AirSpeed in this case.

I had a tinker but no dice. That did however get me thinking about AccelRate which was the cuprite. It appears that Default.AccelRate prevents reaching AirSpeed when MoveTo is across small distances. Even when running through a constant chain of MoveTo. I really should have thought of this sooner.

Thank you!