How the "dist" works in constraint if we create the object every time vs one time

In reply to Etrx91:

It is possible the two examples produce the same results with randc, but not guaranteed.
Realize in order to achieve random stability, every unique RNG value returns the exact same solution. If seeding a new object and calling randomize() advances the next RNG in the same manner, they will produce the same cycle of random addr values.

If you are sending this packet into a queue (as you would do as a umm_sequence_item), you are going to need to construct a new object each time it is sent. You can either randomize the same object and clone it before sending, or randomize new objects and send them.

The benefit of randomizing the same object is when you need state information from the previous packet to randomize the next packet. The problem with that is forgetting to clone the object before sending, and debugging why you only see the last packet in the queue.