IS THIS BLUE OR PURPLE?!?!?

• Kazusa Touma wrote on 2015-06-14 16:53

  Quote from Yai;1278394:

  Since the red hex value is more than 0 it is purple. Even if very slightly.
  
  If you look at the closest pixel Rydian mentions earlier, it is #1D2FB5.

  
  
  Rydian's pixel is incorrect. The pixel you should be looking at for the color is one of the following 3 (I can't remember which one exactly but I believe it's the one on the right side of the red box), none of which have the R or G value at above 0:
  
  

  [Image: http://imageshack.com/a/img537/592/xBCyx8.png]

  
  
  Also, even if the R value wasn't 0 I wouldn't necessarily call it purple unless you want to be super technical about it.
• Bunny wrote on 2015-06-14 17:30

  Quote from Kazusa Touma;1278405:

  Rydian's pixel is incorrect. The pixel you should be looking at for the color is one of the following 3 (I can't remember which one exactly but I believe it's the one on the right side of the red box), none of which have the R or G value at above 0:
  
  

  [Image: http://imageshack.com/a/img537/592/xBCyx8.png]

  
  
  Also, even if the R value wasn't 0 I wouldn't necessarily call it purple unless you want to be super technical about it.

  
  
  Incorrect.
  I have this dye (the screenie OP posted is mine.)
  The hex of the dye is #1527AD (21, 39, 173)
  
  The values that are presented with your image for those pixels is far off.
  Rydian's pixel is the best and closest way of determining the actual hex. So, he is correct. Note: I'm talking about the actual hex, not the "appearance" for lack of a better word.
• Rydian wrote on 2015-06-14 18:38
  I tested multiple dyes, none of the colors on a dye's icon with a luminosity above 25 will match the actual color exactly.
  
  But dyes show their hex colors without mods now, so...
• Kazusa Touma wrote on 2015-06-14 19:36

  Quote from Bunny;1278409:

  Incorrect.
  I have this dye (the screenie OP posted is mine.)
  The hex of the dye is #1527AD (21, 39, 173)
  
  The values that are presented with your image for those pixels is far off.
  Rydian's pixel is the best and closest way of determining the actual hex. So, he is correct. Note: I'm talking about the actual hex, not the "appearance" for lack of a better word.

  
  
  In that case, I've missed it by 1 pixel. We should be using the pixel to the right outside of the box. While Rydian's is closest in value for this dye specifically and some others, for some dyes it will be off by more than the pixel diagonally under the dye's highlight, most noticeable when any one or more of the RGB values are 0 or very very close to 0.
  
  I've always seen people say and specifically draw a diagram showing that the nearest value is somewhere right under/diagonally under the highlight on the dye, I just couldn't remember exactly where. Based on your post and this example alone, I thought that people had been spreading misinformation on the nearest value pixel on the dye, but using the pixel diagonally under the highlight (or any of the others in boxed in green) does seem to be the way to go now that I went and checked some of my fixed dyes.
  
  edit: Actually you know what, it doesn't even matter at this point. I've always read that it's one of the pixels near the highlight, but it doesn't really work for dyes on the lighter end, and the pixel near the bottom doesn't really work for dyes on the darker end/purer RGB dyes. Suffice to say we just need the actual code on the dye, which we're given in-game now anyway.
• Rydian wrote on 2015-06-15 01:11
  File_InvImage="item_ampul"
  So grabbing the inventory image and assuming that middle grey is neutral that has the least tinting, #7F7F7F is the target.
  
  No pixels are that color, of course.
  
  The closest is #7B7B7B, which should be these pixels.
  
  

  [Image: http://i.imgur.com/5wAErqg.png]

  
  
  So yeah, there's something slightly off about the way Mabi does color blending for inventory icons.
• Zekkii wrote on 2015-06-15 02:46
  I have to wonder what the devs were thinking when they programmed this.
• Rydian wrote on 2015-06-15 10:49
  First thought: that people wouldn't care this much about having the exact hex color, especially since so many different colors can look the same. With 16.7 million possible colors, there's bound to be plenty of visual overlap in most cases. Too bad we're so sensitive to stuff like white and pure red though.
  
  
  
  So right now I'm trying to mod the dye inventory icon itself to stick a square of "neutral" grey in the middle to see if that being colored will work more reliably.
  
  I did this...
  

  [Image: http://s3.postimg.org/tgean0p6r/inv_edit1.png]

  
  
  And my dyes show up like this!
  
  

  [Image: http://s11.postimg.org/uuupjnxe7/dyes.png]

  
  
  However, upon close inspection we end up with this instead.
  
  

  [Image: http://s3.postimg.org/e8yb2nxc3/inv1.png]

  
  
  Oh... looks like I forgot that DXT compresses based on 4x4 blocks of pixels. This helps explain why dye colors are more off than we thought, since the image compression itself doesn't keep pixel-perfect colors (a reason they use RAW images for the fossil minigame which is pixel-perfect for example).
  
  So it looks like I'll have to tweak the original some more.
  
  

  [Image: http://s30.postimg.org/4w40u3goh/inv_edit2.png]

  
  
  Let's see if this one survives the compression!
  
  

  [Image: http://s11.postimg.org/7f8njy577/inv2.png]

  
  Game: #515159/#7D3100/#F1177D/#079389/#8DB1E3
  Color: #53525B/#7F3300/#F2197E/#08948B/#8FB2E5
  
  Survives but the colors don't match. Interesting results though, every apparent color is ~ 0x02 darker than it should be in each color value.
  
  So if I change the "neutral grey" center to #818181 instead to account for the -2...
  
  

  [Image: http://s12.postimg.org/si86uipx9/inv3.png]

  
  
  Game: #57575F/#833705/#F71D83/#0D998F/#93B7E9
  Color: #53525B/#7F3300/#F2197E/#08948B/#8FB2E5
  
  Damnit, overshot it. #808080 perhaps? And the whole dye this time just to be sure. If this doesn't work then...
  
  

  [Image: http://s2.postimg.org/ehp3nwynt/inv4.png]

  
  Game: #57555F/#833505/#F71B83/#0D978F/#93B5E9
  Color: #53525B/#7F3300/#F2197E/#08948B/#8FB2E5
  
  Nope, not only did it not get the desired results, but it looks like the texture compression is introducing artifacts even in areas of solid color (I flood-filled and pixel-drew to be safe beforehand).
  
  

  [Image: http://s17.postimg.org/ixpchngrj/artifacts.gif]

  
  
  So it actually looks like it's not that Devcat purposely fiddled with dye colors, but a side-effect of the DXT compression (which is unsafe for pixel-perfect things, it's meant for textures, not images... but it is/was the standard texture format for DirectX.).
  
  
  
  
  P.S. This looks neat at least.
  

  [Image: http://s3.postimg.org/ljq53sm7z/neat.png]