For whatever reason now what should show as white no longer shows as white in Designer... Help

[phila3]

Consider me stumped. I have been working on a number signs for a customer that I created with white backgrounds on and I opened the file tonight to add some additional signs that they requested. And originally I know that the whites were white but then I noticed that the white on all my signs were not actually white any more but the creme color you see in the screen shot (A below) As you can see from C below I have the house shape selected and fill is selected in the color panel (B below)and everything is set to 0 in CMYK and I still have a creme color. Every thing that should be white in my document is this creme color. I have 100% opacity set. I have the background set to gray in screen shot but I can go to preferences and set it to actual white. You can even see image in the layers panel is white and not creme color.

So what else can I check to get my whites in my art boards back to white. Thanks in advance for your incite and help.

 

Since writing the initial paragraph I opened a new document which has the same problem. I also shutdown Designer and restarted and the problem continues to persist. So does anyone have an idea how I can solve this. Thanks in advance for your input.

 

[NotMyFault]

Any chance you can upload the file?
One possibly is you assigned a color on group level by mistake, or set a blend mode, or blend range.

Which color profile is assigned to the document?
if you use the color picker (pipette symbol), what color is shown (CMYK values)?

There are more layers nested to the group, which can modify the colors (like HSL, curves, …)
 

[G13RL]

Make sure that the color profile of your Affinity application is "sRGB IEC61966-2.1". You may also want to check the monitor profile.

[Pšenda]

 

[ashf]

You posted the same question.
Like already mentioned by others, it's a bug of Windows.
(Search "Color Management" with the Windows Search on the Task bar.)
Set the device color profile to sRGB.

 

[walt.farrell]

1 hour ago, BofG said:

I suspect it's an Affinity bug related to profiles that contain a white point element and a chadtag.

Serif seems to believe it's a misconfigured Windows system, from the FAQ and other topics on this.

Also, what is a "chadtag"?

[G13RL]

13 minutes ago, walt.farrell said:

Serif seems to believe it's a misconfigured Windows system, from the FAQ and other topics on this.

I would tend to agree with this, I have never had this problem, either with W8 or W10, on two different computers, nor has my daughter on her machine.

[NotMyFault]

4 hours ago, Pšenda said:

 

This FAQ does not match. White (see screenshot of canvas and color panel) is shown correctly. 

It seems too many (reply by others) rush over analysis phase. Would love to see the file before judging about the cause

[walt.farrell]

47 minutes ago, NotMyFault said:

White (see screenshot of canvas and color panel) is shown correctly. 

The OP's screenshot does not show a canvas. It shows (I think) two Artboards, and the Artboard background color.

But it does show what the OP says is White in the Artboard, and that it shows as a true White in the Layers panel thumbnail. That is another version of what the FAQ is talking about, I think.

[Pšenda]

2 hours ago, NotMyFault said:

White (see screenshot of canvas and color panel) is shown correctly. 

Really? I guess I have a different idea of what white color looks like.

[Pšenda]

2 hours ago, NotMyFault said:

It seems too many (reply by others) rush over analysis phase.

If you have done a thorough analysis of the problem, then you have certainly noticed that the OP does not solve this problem with a faulty/incorrect icc profile for the first time.

 

[walt.farrell]

11 minutes ago, Pšenda said:

If you have done a thorough analysis of the problem, then you have certainly noticed that the OP does not solve this problem with a faulty/incorrect icc profile for the first time.

From that other thread, @phila3 did solve the problem 4 years ago by changing their Windows Display profile setting. Perhaps they need to check that again; maybe some system update reverted the change they made previously. Or perhaps they're using a different machine with a similar problem.

[Pšenda]

8 minutes ago, walt.farrell said:

From that other thread, @phila3 did solve the problem 4 years ago by changing their Windows Display profile setting. Perhaps they need to check that again; maybe some system update reverted the change they made previously. Or perhaps they're using a different machine with a similar problem.

In any case, this points to the fact that the assumption of an incorrectly set icc profile is justified and "unrushed".

[NotMyFault]

24 minutes ago, Pšenda said:

If you have done a thorough analysis of the problem, then you have certainly noticed that the OP does not solve this problem with a faulty/incorrect icc profile for the first time.

 

I did not intend to offend you. I explicitly mentioned „others“, not your post.

ad: If you have done a thorough analysis of the problem

This is my point. There was no chance for a thorough  analysis at all. We have only the original post, and multiple answers by forum users with „definite“ solutions despite  questions to the OP not yet answered. 

• we cant see the canvas
• we dont have the original file
• we dont know the color profiles of system and document (seems cmyk btw).

So i would recommend to let the OP follow up and then continue with more facts.

it does not help if 7 forum users fire in parallel to one question. 
i do not want to set any claim or hold others back, but if 3 answers are already given without a reply from OP it might be an option to lean back.

 

[ashf]

This happens even if the device profile is proper one sometimes. and often happens after installing Semi Annual Windows Update.
I saw many people had this after Windows 10 20H1 is released.
this affect not only Affinity but also other apps such as Windows Photo Viewer / Media Player.
Thus it is considered as a bug of Windows. not because of misconfigured.

[phila3]

In fact I found the solution in setting the the proper ICC profile in the Windows Color Management screen for both my monitors to sRGB IEC61966-2.1. The only thing I can figure is that an update reverted the settings back to a wrong default. Thanks for everyone's input. I have now documented the solution so that if it ever happens again I'll know what to do.

The solution is to Right Click the desktop and choose Display Settings. Type Color Management in the search box and it brings up this window (see attachment). Then Make sure the sRGB IEC61966-2.1 profile is set as the default (if you don't see it you can add it and then set it as the default).