Maximum value of Unity.Mathematics.Random.NextFloat is not excluded when using the method with a Unity.Mathematics.Random object initialized with the seed 1783403415

Package: Unity Mathematics

As Designed

6.4.X

We don't think it's possible to change the behavior described without sacrificing performance, so instead we've updated the docs to reflect the current behavior.

How to reproduce:

1. Open the attached "IN-82833" project
2. Observe the Console output window

Expected result: The console logs False for the "1.5f == rand.NextFloat(1f, 1.5f)" expression
Actual result: The console logs True

Reproducible in: 1.2.6 (2021.3.43f1, 2022.3.43f1), 1.3.2 (2021.3.43f1, 2022.3.43f1, 6000.0.16f1)

Reproducible on: Windows 11
Not reproducible on: No other environments tested

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Issues you vote on will appear here

Maximum value of Unity.Mathematics.Random.NextFloat is not excluded when using the method with a Unity.Mathematics.Random object initialized with the seed 1783403415

Package: Unity Mathematics

Statuses

As Designed

Resolution Notes

6.4.XAs DesignedWe don't think it's possible to change the behavior described without sacrificing performance, so instead we've updated the docs to reflect the current behavior.

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Maximum value of Unity.Mathematics.Random.NextFloat is not excluded when using the method with a Unity.Mathematics.Random object initialized with the seed 1783403415

Package: Unity Mathematics

Statuses

As Designed

Resolution Notes

6.4.XAs DesignedWe don't think it's possible to change the behavior described without sacrificing performance, so instead we've updated the docs to reflect the current behavior.

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?