Min (int),(float) bug

anonymous_user_bac224d7 · July 14, 2016, 8:57am

Min (int), (float) dont work correctly

anonymous_user_e729f54e · July 14, 2016, 1:22pm

Hello urkqsrk,

I have few questions for you that will help narrow down what issue it is that you are experiencing.

Quick questions:

Could you elaborate further on the issue that you are having and as to how the results you are getting or at an inverse to what you are expecting?
I noticed that you are using a Random Integer in Range Node, could you explain in what way the random numbers are unexpected?

anonymous_user_bac224d7 · July 14, 2016, 5:34pm

When random integer give any number plus integer this give new number. Then why min (int) make new number ? I can use this

but why when min(int) have this numbers from int + int it make this?

anonymous_user_e729f54e · July 14, 2016, 6:49pm

I have a test I would like for you to run. I have provide an example blueprint below. Could you create this blueprint and let me know the results?

Example:

anonymous_user_bac224d7 · July 14, 2016, 7:00pm

Now this give numbers like a 1111, 2222, 3333, 4444, … 9999

anonymous_user_e729f54e · July 14, 2016, 7:53pm

That is expected. The “Random integer in Range” only provides a new number when it is called. This means that the value that is being read will be the same for each reference that is pulled off the pin of the “Random integer in Range”. Does this answer your question? If not, could you explain further what it is exactly that you are having an issue with?

anonymous_user_e729f54e · July 19, 2016, 1:27pm

Hello urkqsrk,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will follow up.

Thanks,