Duplicating a widget with a color property doesn't copy its alpha value

Describe the bug:

How do you cause this bug?

  • Create a locator and add a widget with a color property.
  • Change its alpha value to something other than 255.
  • Duplicate the widget: its alpha value is now 255 on the new one.

Screenshots / video of bug:

Which platform: PC & Stadia

Which input: Keyboard + Mouse

Your Crayta username: unairf

Game seen in (including “Hub” or “Editor for XYZ”): Editor of Project H v1

How regularly do you see this? : 3/3

Time + date seen: April 20 2022 15:20 GMT+1

Version number (found in Help tab in Settings): 0.f3.28.120518

dear Unairf,
Thank you for you report.
This issue has been resolve and should be coming soon to a patch near you.

Have an amazing day!

2 Likes

Hey Kat,

I wanted to add a couple of extra details to this report.

It seems that the alpha value of color properties in widgets is not saved in templates. For example, if you have a widget with an alpha value of 120, and you terminate the editor session and load back in - That widget’s alpha value will go back to 255.

I’ve also noticed that if you ‘Copy to template’, the alpha value will not be copied over but rather it will stay the same and the widget will change from Screen to World on its own, sometimes causing crashes.

I’m guessing that both of these issues are related to Unairf’s issue/report here, so perhaps these have already been resolved and we are still awaiting the patch… But I wanted to mention them nonetheless just in case.

Platform: Epic Games
Game seen in: Editor of any game
Time + data seen: 5/18/2022
Version number: 0.f3.28.120518

Thank you so much!

1 Like

hey there !
for some reason only the dev knows the alpha color property wasn’t saving at all… but i just checked the copy the template thing and it has also been fixed.
The fix should make it’s way to you guys in a future patch.

Cheers <3

1 Like

Hi Kat,

The issue with alpha values has been resolved in the latest patch! :partying_face: Thanks for your help!

I’ve run into a very similar bug here, but this time with the ‘type’ property. The resolution on the dev side of things here might be similar to the resolution of the alpha property bug.

If you change the ‘type’ property on a widget from World → Screen, then ‘Copy to template’, the widget will revert back to World (rather than keeping it’s ‘Screen’ value) more often than not.

Steps to reproduce:

  • Create an empty/test widget and template it
  • Change Type property from ‘World’ to ‘Screen’
  • Click on Copy to template button
  • The Type property will usually revert back to ‘World’