How to reproduce:
1. Open the attached “IN-97135” project
2. Open the “SampleScene” and make sure “New Sub Scene” is enabled
3. Enter Play mode
4. In the Hierarchy, select the “Sphere” GameObject, under “New Sub Scene”
5. In the Inspector change “Initial Speed” property in the “Bullet Authoring” Script component
6. Click anywhere on the Game view
7. Observe output in the Console
8. Repeat steps 5-7

Expected result: Log messages appear consistently in the Console with very similar float3 values
Actual result: Log messages appear inconsistently in the Console with varying float3 values

Reproducible with: 1.0.8 (2022.3.60f1, 6000.2.0a7), 1.4.0-exp.2 (2022.3.60f1, 6000.0.44f1, 6000.1.0b12, 6000.2.0a7)

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

Notes:
- Depending on set “Initial Speed” value collisions are: expected (“Plane” GameObject hit), unexpected (ghost collisions near “Cube” GameObject), no collision detected
- In 1.4.0-exp.2 version if the “Cube” GameObject is removed or moved further from “Sphere” GameObject's trajectory, collisions are no longer detected
- In 1.3.10 (or older) versions if the “Cube” GameObject is removed or moved further from “Sphere” GameObject's trajectory, collisions are sometimes detected with the “Plane” GameObject
- In the Scene, three GameObjects (Expected collision, Unexpected collision 1, Unexpcted collision 2) can be enabled to visualize approximate locations collisions are detected