Help, unidentified Error and Warning.

Archive
1
:information_source: Attention Topic was automatically imported from the old Question2Answer platform.
:bust_in_silhouette: Asked By earlroxas
:warning: Old Version Published before Godot 3 was released.

So, in my recent projects I have this warning. This warning also appear in the console when the engine enter Project List. In the description it says about sRGB, so I assume that something wrong with the images (including the project icon, so warning appear in the Project List too), but i dont know. (Note: The images created with GIMP)

Warning Image

And when i run one of my project, the errors below always accompanying the warning. I dont know it is related or not.

Error Image

So, what is this Warning or Error about?
BTW, This is my machine (Laptop):
CPU: Intel i3
GPU: nVidia
OS: Win 8.1 Pro
Godot Version: 2.0 stable (The official stable build)

More information about the project is needed.
Duplicate the project and start removing stuff to determine the node/s with problems so you can show the minimum stuff possible near the issue.

I think the det error is related to Transform, maybe bad values somewhere.

eons | 2016-12-23 00:17

4
:bust_in_silhouette: Reply From: aozasori

The warning happens because you have images saved with a bad color profile. The other errors are probably not related, caused by something else.

To fix the color profiles, for each image:
Open in GIMP.
Go to: Image → Mode → Assign Color Profile...
Choose RGB workspace (sRGB built-in) from the dropdown menu and push Assign.
Export image.

Oh, you right. The warning disappeared. Thanks.

earlroxas | 2016-12-23 03:01

5
:bust_in_silhouette: Reply From: earlroxas

I played around with my project since then. And apparently the Error showed up because I scale the Control node to (0,0) (scaling is from the animation node, I want to make a popup-like animation from scale (0,0) to (1,1)), so I edit it to (0.1,0.1) and the error never show up again.

The scaling is made by a method of matrix transformations and that does not allow zero, Node2D caps at a small float, it seems that Control (and Spatial) don’t apply that “fix”.

eons | 2016-12-26 03:39