The wrong colours showing
Jan 23, 2023
I am using a theme to brand our internal content with our own colour pallet. When I come to change the player background colour the oddest thing happens. The player should use the colour #1C2541 which is a dark blue but when I am applying the player settings (using import player) the colour value shows correctly but the colour itself is showing as a lime green! I have attached a screen recording, you can see that it is not just the blue that is wrong.
This is an issue being experience by most of my team, the other interesting thing about this is they are seeing different colours appearing.
I am running the December version of Storyline (see screen capture). My first port of call is to drop down a version.
I should say, I have been using these player settings for about 3 months with no problems at all, it has just started to happen to me today. Has anyone else experienced this problem before? Any suggestions?
4 Replies
A quick update, I have downgraded to the November version of Storyline and it has made no difference.
a have compared my palette (left) with your palette (right) - same color position clicked

left: colors of the palette and clicked color is matching
right: the view of the palette is wrong, if you click - you get the color of the intended palette
you should open a support case
Hi Kai,
I'm sorry to hear that you're experiencing this issue!
I've tested this out on my end, and am unable to replicate it using the most current version of Storyline (Build 3.71.29339.0).
Please let me know if this helps! If you need additional assistance, I'd be happy to take a look at your file. You can upload it here or share it privately in a support case. We'll delete it from our systems once troubleshooting is complete.
Kelly,
This is happening to different files to different people. Each of my team has experienced it and each of them have seen a different colour shown. The issue is not with Storyline file. I have tried downgrading my version of Storyline to the November build and it is still happening. I will have a look at the troubleshooting steps but I suspect this will not be fixed by that.