Page MenuHomeFeedback Tracker

Waypoints and mob initial positions are modified randomly by the game causing indeterminate behavior
Closed, ResolvedPublic


Waypoints and unit locations are altered randomly from their position set by the editor. This results in indeterminate behavior, exemplified by the two versions of a mission attached below. The elements were copied from one mission and pasted into a new mission in the editor, and positioned as a group in almost the original position. Upon loading the two missions, however, the helicopter is in dramatically different locations. Further, when the Alpha 1-1 unit travels to its first waypoint, waits for the helicopter to land, then boards the helicopter, the helicopter will immediately take off in one version, but stay put in the other version (I believe this has to do with the distance between the helipad and the helicopters next waypoint, which is increased beyond a certain threshold by the random variation.)

While having random variation in unit initial position and waypoint position can be an excellent way to spice things up and make the game less predictable, it can, as in this case, royally screw with the mission. I propose making this an optional setting for placed objects, i.e., click a check box for the unit or waypoint to be affected by randomness.


Legacy ID
AI Control / Commanding
Steps To Reproduce

Place a waypoint on an easily recognizable land mark, and position a playable unit nearby. Load the game and see where the waypoint is. Repeat several times to observe the waypoint moving about randomly.

Event Timeline

TraxusIV edited Steps To Reproduce. (Show Details)Mar 13 2013, 4:05 PM
TraxusIV edited Additional Information. (Show Details)
TraxusIV set Category to AI Control / Commanding.
TraxusIV set Reproducibility to Random.
TraxusIV set Severity to Major.
TraxusIV set Resolution to Open.
TraxusIV set Legacy ID to 208673640.May 7 2016, 12:30 PM

I would say this is unintended, as there should already be a "placement radius" option for waypoints and units. Maybe something is causing this option to act as a non-zero value even when set to zero?

That sounds pretty likely. Hadn't noticed the placement radius option, but I went back to double check it just to be sure, and all the offending waypoints are set to zero radius. I've been seeing this happen to more than just waypoints too. Seen opfor end up swimming nearly 50m offshore from time to time when placed near the waters edge.

Closing due to lack of activity for over 5 months. If this issue/request is still valid in the latest dev build, please create a new ticket or ask for this one to be re-opened.