[4.6 Preview] UMG Colour & Opacity no longer accepts Linear Colour

Kenomica · November 17, 2014, 10:26pm

I’m not 100% sure if this is a bug or not, but I have a system within UMG that changes the colour of the UI text based on gameplay.

If you have >50 bananas the text is green.
If you have <50 it is white.
If you have 0 it is red.

This is set using the Bind Colour and Opacity in UMG. This is fed a linear colour variable which is read from the player blueprint.

In 4.6, Colour and Opacity bindings only accept Slate Colour instead of Linear Colour, and I am unable to set the colour in blueprints with Slate Colour (It is pink no matter what.)

anonymous_user_e729f54e · November 18, 2014, 6:47pm

Hello Kenomica,

I have a few questions for you that will help me narrow down the issue that you are experiencing.

Quick questions:

Can you reproduce this in a clean project?
If it is possible to reproduce in a clean project, could you provide accurate reproduction steps?
Could you provide a screen shot of the blueprints that are involved in the issue?

Kenomica · November 19, 2014, 3:29pm

No problem!

I’ve found that in order to get the correct colour, you now need to:

Change all variables to “Slate Colour” instead of “Linear Colour”
Change all “Output” bindings on opacity and Colour to “Slate Colour” instead of “Linear Colour”
If the variable & output are both “Linear Colour” you will receive a “Signatures Don’t Match” error.
You cannot set the colour as normal in the new variables, you must drag off the pin of “Slate Colour” and -
Select “Make Slate Colour” - Choose the colour.

In a new project, this is still necessary but by default, binding colour and opacity will give a Slate Colour. Old projects need a LOT of reworking to get the colours working as they did in 4.5.1

anonymous_user_e729f54e · November 19, 2014, 7:50pm

Hello Kenomica,

I was able to reproduce the issue. I have written a report ( UE-5645) and I have sent it to the developers for further consideration. Thank you for all of your information and time. I will provide updates with any pertinent information as it becomes available.

Make it a great day

Kenomica · December 3, 2014, 10:10pm

just updated to 4.6 and this issue is still there.

anonymous_user_e729f54e · December 3, 2014, 10:31pm

Hello Kenomica,

I went ahead and double checked for you. There are still no updates on this issue as of yet. The development team been working hard on finalizing the 4.6 build for the release. I will be sure to update you when there have been any changes to the status of the report that I wrote up.

Kenomica · December 4, 2014, 10:55am

Much appreciated. Thank you.

anonymous_user_2709d010 · December 11, 2015, 7:55am

As of 4.10 this bug is still there. If you use the above function, the text goes black, Slate color or not. When you set some degree of transparency, the color you selects comes out to some degree, but if Alpha value is 1, the color is firmly black.

Is there any update on this? This has been over a year now

anonymous_user_e729f54e · December 11, 2015, 2:28pm

Hello ,

I went ahead and double checked for you. This issues status has not yet been updated to fixed as of yet. However, I will bump up the community interest on this issue for you. Thank you for your interest in this issue.

anonymous_user_8c806efd1 · November 9, 2016, 3:54am

I’ve come across this bug in 4.13, has it still not been fixed or could I be having a different issue?

anonymous_user_e729f54e · November 9, 2016, 3:09pm

Hello Umaya,

I have provided a link to the public tracker. Please feel free to use the link provided for future updates.

Link: Unreal Engine Issues and Bug Tracker (UE-5645)

Make it a great day

anonymous_user_204f068d1 · June 8, 2017, 4:22am

An alternate solution for that is when exposing the slate color variable in blueprint, split the struck pin and hook it to the linear color variable.