'Random Pitch Angle' not working when 'Collision with World' is enabled for Foliage instance settings

The 'Random Pitch Angle' setting within the Foliage instance settings are being overridden or ignored when 'Collision with World' is also enabled.

This occurs in the binary releases of 4.12.5, 4.13.2, and 4.14.3.

1. Open attached project.
2. Select the Foliage mode (Shift+4)
3. Drag the Conifer_Desktop from the Content Browser into the foliage window.
4. Set the 'Random Pitch Angle' to 35.0
5. Paint on either the Static Mesh or Landscape surface.
6. Notice how the trees are randomly set at an angle from 0 to 35.
7. Now check the 'Collision with World' option.
8. Repeat Step 5.

Outcome The tree meshes no longer adhere to the Random Pitch Angle, and almost seem to have that angle reduced as it still slightly angles the pitch during placement.

Expected A collision check in the world is run, and then the mesh is placed with a random angle in degrees from 0 to 35.

How does TextureRenderTarget2D get TArray<uint8> type data?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

Why does the REMOVE method of map container remove elements have memory leaks?

How to delete some elements correctly when deleting an array loop?

UMG RichText not appear image when packaged

What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?

Where can I download the source address of the deployment cotum service associated with the PixelStream plugin?

What is the difference between Camera and CineCamera?

How does TArray loop correctly remove elements in blueprints?

In UE5.4, custom variables in the level blueprint cannot be set to default values, and the eyedropper tool is also unavailable, whereas in UE4.27, these features work normally.