Developer Notes

The Default Values in the Blueprint are set up correctly. Adding some more info, the issue here is not the default Value in the BP itself, but rather clicking on the yellow default button always sets the struct value to '0' , regardless of the Default Value assigned to the struct in the Blueprint.

Description

When using the track builder plugin, the default settings for the track width starts at 1. However, when the yellow arrow is clicked to to restore the track back to default it sets it to zero instead.

Steps to Reproduce

NEW REPRO

  1. Open QAGame in editor.
  2. Create and open a new blueprint struct.
  3. Set the member variable to float.
  4. Set the Default Value to 5.0.
  5. Save and close the struct.
  6. Create and open a new actor blueprint.
  7. Add a variable based on your struct and make it an array.
  8. Mark the variable as editable.
  9. Compile the blueprint.
  10. Add the blueprint to the level.
  11. Select the blueprint instance.
  12. Add an array entry.
  13. Set the float to any value.
  14. Click the Reset to Defaults arrow.

RESULT

The value resets to 0.0 as opposed to 5.0

OLD REPRO

  1. # Open UE4 Launcher
  2. Go to Learn Tab
  3. Download Blueprint Splines Track (if not already downloaded)
  4. Add the plugin to a blank level
  5. Open The blank level
  6. Go to the Blueprints Folder
  7. Drag and Drop a copy of the "Track Generator" into the level
  8. Add a few segments of track by Alt+ Drag
  9. Set the track width to "Default" by clicking the little yellow arrow next to the setting in the Details panel under the Track Setup section
  10. Notice the Track width is set to Zero instead of One (which it started at)

Note: If you Open the TrackGenerator BP and the Road Data Struct you'll notice that the Default TrackWidth is set to '1' and not 0.

Have Comments or More Details?

Head over to the existing Questions & Answers thread and let us know what's up.

1
Login to Vote

Won't Fix
ComponentUE - Gameplay - Blueprint
Affects Versions4.6.14.134.23
CreatedJan 8, 2015
ResolvedAug 18, 2021
UpdatedAug 18, 2021
View Jira Issue