Bug #12378

orderGetIn overrides speedMode

Added by shuko almost 5 years ago. Updated over 3 years ago.

Status:Closed Start date:07/27/2010
Priority:Normal Due date:08/31/2011
Assignee:shuko % Done:

0%

Category:Scripting: Problem
Target version:-
Affected ArmA II version:1.60 BETA First affected build:
Reproduced by another DH user:No First affected ArmA II version:
I am using some Mods:No Single / Multi Player?:
I am using: BIForumURL:
Reproducible for you:Yes NGUrl:
Related to content of DLC: WIKIurl:

Description

This is a minor issue, but would still be an improvement.

1. Set unit's speedmode to limited with waypoint setting or setSpeedMode command.
2. Unit walks nice and slow.
3. Assign him to a vehicle and issue orderGetin true to him.
4. He will change to full speed mode and run to the vehicle.

The assigned speedmode is being overridden by the orderGetin.
It would look better and be more logical to keep the current mode. If you need to have them run, then call setSpeedMode "full".

_ordergetinBehaviour.Desert_E.rar - Radio Alpha and Bravo (1.1 kB) shuko, 07/27/2010 12:15

12378.zip - same using forceSpeed. (1.1 kB) alef, 08/17/2011 19:00

History

Updated by kju almost 5 years ago

  • Due date set to 08/14/2010
  • Status changed from New to Feedback

Did you try limitSpeed?
http://community.bistudio.com/wiki/limitSpeed

From what I recall BI uses it in the campaign for the very same reason.

Updated by shuko almost 5 years ago

Just tried it. It works, but I don't think it's a very feasible method to run sleep 0.1 (they still manage to start the running animation now and then) loop to force it. Especially when you have more than 1 or 2 units (in my case there can be ten times that) and they are dynamically created and deleted.

I'll just use move + distance + moveindriver for now.

Updated by kju almost 5 years ago

  • Due date changed from 08/14/2010 to 10/23/2010
  • Status changed from Feedback to Assigned

tx

Updated by CarlGustaffa almost 5 years ago

Try forceSpeed instead of limitSpeed.

Updated by alef almost 4 years ago

  • File 12378.zip added
  • Due date changed from 10/23/2010 to 08/31/2011
  • Status changed from Assigned to Feedback
  • Assignee set to shuko
  • Affected ArmA II version changed from 1.53 BETA to 1.60 BETA

The workaround from Carl works. Please test with this mission and let us know if it's OK for you to close the ticket, Thanks.

Updated by zGuba over 3 years ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF