[MC-1313] macOS: Incorrect sign surface normal causes the text colour to not be applied properly Created: 30/Oct/12  Updated: 23/Aug/20  Resolved: 03/Oct/19

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.2, Minecraft 14w26c, Minecraft 14w27b, Minecraft 14w28b, Minecraft 1.8, Minecraft 1.8.1, Minecraft 1.8.3, Minecraft 1.8.4, Minecraft 1.8.7, Minecraft 1.9 Pre-Release 3, Minecraft 1.9 Pre-Release 4, Minecraft 1.9, Minecraft 1.9.1, Minecraft 1.9.2, Minecraft 16w15b, Minecraft 1.9.3 Pre-Release 1, Minecraft 1.9.4, Minecraft 16w20a, Minecraft 16w21a, Minecraft 16w21b, Minecraft 1.10 Pre-Release 1, Minecraft 1.10 Pre-Release 2, Minecraft 1.10, Minecraft 1.10.2, Minecraft 16w32a, Minecraft 16w33a, Minecraft 1.11.2, Minecraft 1.12.2, Minecraft 1.13-pre3, Minecraft 1.13-pre4, Minecraft 1.13-pre5, Minecraft 1.13-pre6, Minecraft 1.13-pre7, Minecraft 1.13-pre8, Minecraft 1.13-pre9, Minecraft 1.13-pre10, Minecraft 1.13, Minecraft 18w30a, Minecraft 18w30b, Minecraft 18w31a, Minecraft 18w32a, Minecraft 18w33a, Minecraft 1.13.1-pre1, Minecraft 1.13.1-pre2, Minecraft 1.13.1, Minecraft 1.13.2, Minecraft 18w48a, Minecraft 18w48b, Minecraft 18w49a, Minecraft 18w50a, Minecraft 19w02a, Minecraft 19w03c, Minecraft 19w04a, Minecraft 1.14 Pre-Release 1, Minecraft 1.14, Minecraft 1.14.1 Pre-Release 1, Minecraft 1.14.2 Pre-Release 1, Minecraft 1.14.2 Pre-Release 2, Minecraft 1.14.2 Pre-Release 3, Minecraft 1.14.2 Pre-Release 4, Minecraft 1.14.2, Minecraft 1.14.3 Pre-Release 1, Minecraft 1.14.3 Pre-Release 3, 1.14.4, 19w39a
Fix Version/s: Minecraft 1.8, 19w39a

Type: Bug
Reporter: Jordin Smith Assignee: Unassigned
Resolution: Fixed Votes: 11
Labels: Mac, MacBook, MacBookPro, Macintosh, MacintoshComputer, OSX, SignText, Signs, Text, color, colour, macOS, normal, rendering, surface
Environment:

Processor: 2.4 GHz Intel Core i5
Graphics: Intel HD Graphics 3000 512 MB

Java SE 6 64-Bit Version: 1.6.0_33-b03-424
Java SE Runtime Environment 7u80
Java SE Development Kit 7u80
Java SE Runtime Environment 8u181
Java SE Development Kit 8u181
Mojang-included Java

OS X Mountain Lion
OS X Mavericks
OS X Yosemite
OS X El Capitan
macOS Sierra
macOS High Sierra
macOS Mojave


Attachments: PNG File 2012-10-30_09.18.12.png     PNG File 2012-10-30_09.18.18.png     PNG File 2016-02-24_14.36.21.png     PNG File 2016-02-24_14.36.43.png     PNG File 2016-03-31_16.06.49.png     PNG File 2016-03-31_16.06.56.png     PNG File 2016-12-29_15.37.35.png     PNG File 2018-06-18_18.11.05.png     PNG File 2018-06-18_18.11.08.png     PNG File 2018-06-18_18.19.29.png     PNG File 2018-06-18_18.19.33.png    
Issue Links:
Duplicate
is duplicated by MC-8710 Sign Bug Resolved
is duplicated by MC-12135 Signs only coloured at extreme viewin... Resolved
is duplicated by MC-21319 [Servers] While on a Mac, if there is... Resolved
is duplicated by MC-25081 Graphics Glitch Resolved
is duplicated by MC-27073 Sign colours can't be seen Resolved
is duplicated by MC-30564 Sign colors Resolved
is duplicated by MC-31191 When I am in a Minecraft server, colo... Resolved
is duplicated by MC-42520 I cannot see colored signs in Minecra... Resolved
is duplicated by MC-45620 Random signs are displayed too dark Resolved
is duplicated by MC-60270 Coloured Signs Not Rendering Properly... Resolved
is duplicated by MC-72174 I Cant See Colour On Signs!!! Resolved
is duplicated by MC-76261 SMP Sign Colors Resolved
is duplicated by MC-80146 OSX: Cannot see colored signs from fr... Resolved
is duplicated by MC-81474 Sign Color Broken for Mac OSX Yosemit... Resolved
is duplicated by MC-104 Color of text on signs only appears a... Resolved
Relates
relates to MC-95044 Graphics Card and Sign Colors Resolved
relates to MC-33304 Sign Colors Fading (NOT vanishing!) w... Closed
CHK:
Confirmation Status: Confirmed
Category:
Rendering

 Description   

Bug Description

While viewing a sign with coloured text, you are unable to see the text colour from the front of the sign on macOS / OS X. This effects every Minecraft version to date (with coloured sign text of course), regardless of macOS version, Java version, or graphics driver version. This bug seems to only effect older mac processors. This bug does not effect Minecraft running on Windows or any version of Linux (that I know of).

Bug Example

Simply spawn in a sign with coloured text on macOS / OS X and observe the colour of the text while viewing the front of the sign straight-on and from a sharp angle.

Bug Cause

This bug is caused by incorrectly defining the surface normal vector of the front of the sign while rendering the text on a sign. This causes the surface "face" to be defined as the back of the sign, rather than the front (where the text is visible). The OpenGL implementation on Windows and Linux appears to have a relaxed policy for applying colour to the surface, while the OpenGL implemenation on macOS has a stricter policy for applying the colour. It appears that OpenGL on macOS does not apply the colour if the surface is not "visible", which is why the colour is only applied on sharp angles to the sign, where part of the surface would be visible.

Bug Fix

This bug can easily be fixed by properly defining the surface normal while rendering the text on the sign. This change does not break rendering behaviour on Windows and Linux (tested on Windows 10 and Arch Linux), while fixing the text rendering on macOS (tested on OS X Mountain Lion, OS X Mavericks, OS X Yosemite, OS X El Capitan, macOS Sierra, macOS High Sierra, and a beta of macOS Mojave).

How to Fix - MCP Mappings

Minecraft 1.12.2

  • Navigate to: net.minecraft.client.renderer.tileentity.TileEntitySignRenderer
  • Find line 76: GlStateManager.glNormal3f(0.0F, 0.0F, -0.010416667F);
  • Change line 76 to: GlStateManager.glNormal3f(0.0F, 0.0F, 0.010416667F);

How to Fix - Obfuscated Game

Minecraft 1.13.1 (Same obfuscation as Minecraft 1.13.1-pre2)

  • Navigate to: cwg
  • Find line 43: ctz.a(0.0F, 0.0F, -0.010416667F);
  • Change line 43 to: ctz.a(0.0F, 0.0F, -0.010416667F);

Minecraft 1.13.1-pre2 (Same obfuscation as Minecraft 1.13.1-pre1)

  • Navigate to: cwg
  • Find line 43: ctz.a(0.0F, 0.0F, -0.010416667F);
  • Change line 43 to: ctz.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.13.1-pre1

  • Navigate to: cwg
  • Find line 67: ctz.a((float)0.0f, (float)0.0f, (float)-0.010416667f);
  • Change line 67 to: ctz.a((float)0.0f, (float)0.0f, (float)0.010416667f);

Minecraft 18w33a

  • Navigate to: cwf
  • Find line 67: cty.a((float)0.0f, (float)0.0f, (float)-0.010416667f);
  • Change line 67 to: cty.a((float)0.0f, (float)0.0f, (float)0.010416667f);

Minecraft 18w32a (Same obfuscation as Minecraft 18w31a)

  • Navigate to: cwe
  • Find line 67: ctx.a(0.0F, 0.0F, -0.010416667F);
  • Change line 67 to: ctx.a(0.0F, 0.0F, 0.010416667F);

Minecraft 18w31a

  • Navigate to: cwe
  • Find line 64: ctx.a(0.0F, 0.0F, -0.010416667F);
  • Change line 64 to: ctx.a(0.0F, 0.0F, 0.010416667F);

Minecraft 18w30b

  • Navigate to: cvz
  • Find line 64: cts.a(0.0F, 0.0F, -0.010416667F);
  • Change line 64 to: cts.a(0.0F, 0.0F, 0.010416667F);

Minecraft 18w30a

  • Navigate to: cvy
  • Find line 64: ctr.a(0.0F, 0.0F, -0.010416667F);
  • Change line 64 to: ctr.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.13

  • Navigate to: cvw
  • Find line 64: ctp.a(0.0F, 0.0F, -0.010416667F);
  • Change line 64 to: ctp.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.13-pre10

  • Navigate to: cvu
  • Find line 64: ctn.a(0.0F, 0.0F, -0.010416667F);
  • Change line 64 to: ctn.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.13-pre10

  • Navigate to: cvu
  • Find line 64: ctn.a(0.0F, 0.0F, -0.010416667F);
  • Change line 64 to: ctn.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.13-pre9 (Same obfuscation as Minecraft 1.13-pre8)

  • Navigate to: cvs
  • Find line 64: ctl.a(0.0F, 0.0F, -0.010416667F);
  • Change line 64 to: ctl.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.13-pre8

  • Navigate to: cvs
  • Find line 64: ctl.a(0.0F, 0.0F, -0.010416667F);
  • Change line 64 to: ctl.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.13-pre7

  • Navigate to: cvi
  • Find line 64: ctb.a(0.0F, 0.0F, -0.010416667F);
  • Change line 64 to: ctb.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.13-pre6

  • Navigate to: cva
  • Find line 64: cst.a(0.0F, 0.0F, -0.010416667F);
  • Change line 64 to: cst.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.12.2 (Same obfuscation as Minecraft 1.12.1)

  • Navigate to: bxf
  • Find line 75: bus.a(0.0F, 0.0F, -0.010416667F);
  • Change line 75 to: bus.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.12.1

  • Navigate to: bxf
  • Find line 75: bus.a(0.0F, 0.0F, -0.010416667F);
  • Change line 75 to: bus.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.12

  • Navigate to: bxd
  • Find line 75: buq.a(0.0F, 0.0F, -0.010416667F);
  • Change line 75 to: buq.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.11.2 (Same obfuscation as Minecraft 1.11.1)

  • Navigate to: bss
  • Find line 75: bqg.a(0.0F, 0.0F, -0.010416667F);
  • Change line 75 to: bqg.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.11.1

  • Navigate to: bss
  • Find line 75: bqg.a(0.0F, 0.0F, -0.010416667F);
  • Change line 75 to: bqg.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.11

  • Navigate to: bsq
  • Find line 75: bqe.a(0.0F, 0.0F, -0.010416667F);
  • Change line 75 to: bqe.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.10.2 (Same obfuscation as Minecraft 1.10.1)

  • Navigate to: bqm
  • Find line 75: bob.a(0.0F, 0.0F, -0.010416667F);
  • Change line 75 to: bob.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.10.1 (Same obfuscation as Minecraft 1.10)

  • Navigate to: bqm
  • Find line 75: bob.a(0.0F, 0.0F, -0.010416667F);
  • Change line 75 to: bob.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.10

  • Navigate to: bqm
  • Find line 75: bob.a(0.0F, 0.0F, -0.010416667F);
  • Change line 75 to: bob.a(0.0F, 0.0F, 0.010416667F);

Minecraft 1.9.4 (Same obfuscation as Minecraft 1.9.3)

  • Navigate to: bpq
  • Find line 75: bnf.a(0.0F, 0.0F, -1.0F * ☃);
  • Change line 75 to: bnf.a(0.0F, 0.0F, ☃);

Minecraft 1.9.3 (Same obfuscation as Minecraft 1.9.2)

  • Navigate to: bpq
  • Find line 75: bnf.a(0.0F, 0.0F, -1.0F * ☃);
  • Change line 75 to: bnf.a(0.0F, 0.0F, ☃);

Minecraft 1.9.2 (Same obfuscation as Minecraft 1.9.1)

  • Navigate to: bpq
  • Find line 75: bnf.a(0.0F, 0.0F, -1.0F * ☃);
  • Change line 75 to: bnf.a(0.0F, 0.0F, ☃);

Minecraft 1.9.1

  • Navigate to: bpq
  • Find line 75: bnf.a(0.0F, 0.0F, -1.0F * ☃);
  • Change line 75 to: bnf.a(0.0F, 0.0F, ☃);

Minecraft 1.9

  • Navigate to: bpt
  • Find line 75: bni.a(0.0F, 0.0F, -1.0F * ☃);
  • Change line 75 to: bni.a(0.0F, 0.0F, ☃);

Minecraft 1.8.9

  • Navigate to: bhj
  • Find line 77: GL11.glNormal3f(0.0F, 0.0F, -1.0F * ☃);
  • Change line 77 to: GL11.glNormal3f(0.0F, 0.0F, ☃);

Minecraft 1.8

  • Navigate to: cnv
  • Find line 77: GL11.glNormal3f(0.0F, 0.0F, -1.0F * f3);
  • Change line 77 to: GL11.glNormal3f(0.0F, 0.0F, f3);

Minecraft 1.7.10

  • Navigate to: bmr
  • Find line 54: GL11.glNormal3f(0.0F, 0.0F, -1.0F * f3);
  • Change line 54 to: GL11.glNormal3f(0.0F, 0.0F, f3);

Minecraft 1.6.4

  • Navigate to: bja
  • Find line 53: GL11.glNormal3f(0.0F, 0.0F, -1.0F * f3);
  • Change line 53 to: GL11.glNormal3f(0.0F, 0.0F, f3);

Minecraft 1.5.2

  • Navigate to: bja
  • Find line 50: GL11.glNormal3f(0.0F, 0.0F, -1.0F * f3);
  • Change line 50 to: GL11.glNormal3f(0.0F, 0.0F, f3);

Minecraft 1.4.7

  • Navigate to: bdt
  • Find line 50: GL11.glNormal3f(0.0F, 0.0F, -1.0F * f3);
  • Change line 50 to: GL11.glNormal3f(0.0F, 0.0F, f3);

Minecraft 1.3.2

  • Navigate to: axq
  • Find line 50: GL11.glNormal3f(0.0F, 0.0F, -1.0F * f3);
  • Change line 50 to: GL11.glNormal3f(0.0F, 0.0F, f3);

Minecraft 1.2.5

  • Navigate to: ll
  • Find line 51: GL11.glNormal3f(0.0F, 0.0F, -1.0F * f3);
  • Change line 51 to: GL11.glNormal3f(0.0F, 0.0F, f3);

Minecraft 1.1

  • Navigate to: ku
  • Find line 51: GL11.glNormal3f(0.0F, 0.0F, -1.0F * f3);
  • Change line 51 to: GL11.glNormal3f(0.0F, 0.0F, f3);

Minecraft 1.0

  • Navigate to: aeu
  • Find line 51: GL11.glNormal3f(0.0F, 0.0F, -1.0F * f3);
  • Change line 51 to: GL11.glNormal3f(0.0F, 0.0F, f3);

Notice the sign of the z-coordinate of the normal vector. This change will correctly define the surface normal to be the front of the sign, fixing coloured signs on macOS.



 Comments   
Comment by [Mod] Pokechu22 [ 03/Oct/19 ]

Great, thanks for testing!

Comment by Jordin Smith [ 03/Oct/19 ]

I tried to test it yesterday but I was still running an older snapshot for some reason. I attempted to remove those versions when I realized but I guess it didn't work. The only version I am able to change is 1.14.4 (where the bug still occurs), all the others versions are archived and I cannot change them.

I was not able to reproduce this bug in 19w39a or 19w40a.

Comment by [Mod] Pokechu22 [ 03/Oct/19 ]

Any reason you added 19w39a and 19w40a yesterday? Were you able to temporarily reproduce it or something else odd like that? Or was it just by reflex?

Comment by Jordin Smith [ 03/Oct/19 ]

This bug appears to have been fixed in 19w39a. I tested it on my old macbook and the sign rendering was broken in 19w38b but worked fine in 19w39a and 19w40a. Looking at the source, it looks like they removed the offending normal3f() in 19w39a.

Although, with all the changes to the rendering and new issues with signs, I wouldn't be surprised if they reverted this change back, reintroducing the bug. But for now, it appears to be fixed.

Comment by Aiden Kane [ 04/Aug/19 ]

You really seem to know your stuff.

Comment by [Mod] Pokechu22 [ 27/Nov/18 ]

Is this still an issue as of the 1.14 snapshots, now that MC-95044 has been fixed?

(Looks like it is since GlStateManager.normal3f(0.0F, 0.0F, -0.010416667F); is still present, in ddp, but I don't have a mac so I cannot test)

Comment by Kumasasa [ 17/Jul/18 ]

Yes, that was before you were set as reporter of this ticket. Now just update the ticket as necessary.

Comment by Jordin Smith [ 17/Jul/18 ]

Sorry, I was only leaving a comment because FVbico told me to, I'll stop leaving them now

Comment by Matthew [ 16/Jul/18 ]

You can update the affected versions yourself, no need to comment.

Comment by Jordin Smith [ 16/Jul/18 ]

This is still an issue for macOS on 1.13-pre9.

Comment by Jordin Smith [ 13/Jul/18 ]

This issue is still present in 1.13-pre8.

Comment by Jordin Smith [ 10/Jul/18 ]

This is still an issue on 1.13-pre7.

Comment by Jordin Smith [ 04/Jul/18 ]

This is still an issue on 1.13-pre6. I also updated the bug report with more details.

Comment by Matthew [ 25/Jun/18 ]

Is this still an issue in 1.13-pre3? Please update the affected versions of your ticket.

Comment by Jordin Smith [ 18/Jun/18 ]

This is still an issue on 1.12.2 and 1.13-pre2 on a Macbook Pro.

Comment by [Mod] Michael Wobst [ 16/Jun/18 ]

Someone with a graphics driver that's up to date please check if that's still an issue in the latest 1.13 pre-release.

Comment by user-f2760 (Inactive) [ 26/May/16 ]

It's better if you just leave a new comment, as those actually show up in the activity feed, you could also remove older comments.

Changing you to reporter.

Comment by Jordin Smith [ 26/May/16 ]

This is still an issue in 16w21b.
Also, do you mods get a notification if I edit a previous comment? I hate spamming this every update. If not, is it ok if I remove the old messages (every one except the latest)?

Comment by Jordin Smith [ 26/May/16 ]

This is also in 16w21a.

Comment by Jordin Smith [ 18/May/16 ]

This is still not fixed on the 1.10 snapshot 16w20a.

Comment by Jordin Smith [ 21/Apr/16 ]

This is still an issue in 1.9.3-pre1 and 16w15b.

Comment by user-f2760 (Inactive) [ 31/Mar/16 ]

Jordin since it's a non "real" version we can't select it anyway

Comment by Jordin Smith [ 31/Mar/16 ]

This is still an issue in 1.9.1 and 1.9.2. I'm not sure if it counts but this issue seems to be fixed in 1.RV-Pre1 The Trendy Update (the 2016 April Fools joke). I believe we should wait until the next actual version comes out before marking this as resolved.

Comment by Jordin Smith [ 29/Feb/16 ]

This is still an issue on full release 1.9.

Comment by Jordin Smith [ 28/Feb/16 ]

Still an issue in 1.9-pre4.

Comment by Jordin Smith [ 24/Feb/16 ]

Yes this is still in 1.9-pre2, and in 1.9-pre3, I added some screenshots showing it (using Attach Files). Later today I can provide the way to fix it in 1.9-pre3.

Comment by user-f2760 (Inactive) [ 24/Feb/16 ]

is this still in 1.9-pre2?

Comment by Jordin Smith [ 21/Feb/16 ]

Happens to me running Java 8 on OS X 10.11 El Capitan. I have found a way to fix it, below is a method of fixing it using MCP mappings:

Go to TileEntitySignRenderer.java
Look for the method: renderTileEntityAt(TileEntitySign, double, double, double, float, int)
Find float f3 = 0.015625F * f;
The third line after that uses this float: GL11.glNormal3f(0.0F, 0.0F, -1.0F * f3); (Probably using GlStateManager but MCP changed it)
Changing this line to not use a negative number fixes it, example:
GL11.glNormal3f(0.0F, 0.0F, 1.0F * f3);
or, more simply:
GL11.glNormal3f(0.0F, 0.0F, f3);
(this is right after you bind the sign texture, right before you disable depth mask)

Using 1.9-pre2 obfuscated:
Go to bps.class
Look for the method: public void a(aqm, double, double, double, float, int)
Find: float \u2603 = 0.015625F * \u2603;
The third line after that uses this float: bnh.a(0.0F, 0.0F, -1.0F * \u2603);
Changing this line to not use a negative number fixes it, example:
bnh.a(0.0F, 0.0F, \u2603);
(this is right after you bind the sign texture, right before you disable depth mask)

Comment by Kumasasa [ 16/Jun/15 ]

Reopened due to MC-81474

Comment by [Mod] Ezekiel (ezfe) [ 08/May/15 ]

I'm resolving this as Invalid. It shouldn't be reopened unless someone running OS X 10.10.3 or later experiences this.

Comment by KingSupernova [ 23/Jan/15 ]

I believe the report was deleted for some reason, I don't know why.

Comment by Harry [ 23/Jan/15 ]

I don't seem to be able to find MC-33304 in the bug tracker? lol

Comment by KingSupernova [ 23/Jan/15 ]

That's not what this bug is about. I think you want MC-33304.

Comment by Harry [ 23/Jan/15 ]

This bug is not fixed, it has been present for years including in version 1.8.1.

Screenshot of video settings: http://prntscr.com/5w6idu
Proof that it is not fixed in 1.8: http://prntscr.com/5w6jem

Look at the signs in the second screenshot, you'll notice that the colored text is barely readable. The exact same problem also happens with the default texture pack.

Comment by Galaxy_2Alex [ 25/Oct/14 ]

Resolved it as Fixed, if anyone still has this issue, leave a comment, and it will be reopened.

Comment by odisseus [ 24/Oct/14 ]

I have not been concerned by this issue since a long time now and everything is still fine with 1.8.1-pre3.
If needed : I'm using an Intel HD 4000, OSX 10.10 and Java 8-release25.

Comment by Galaxy_2Alex [ 24/Oct/14 ]

Is this still a concern in the current Minecraft version 1.8.1 Prerelease 3 / Launcher version 1.5.3 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

(Especially in regards to Yosemite)

Comment by Eoghan Spillane [ 21/Sep/14 ]

Try upgrading to osx maverick, worked for me

Comment by Itouch2 [ 26/Aug/14 ]

Confirmed with an Intel HD 4000 (OS X).

Comment by [Mod] Ezekiel (ezfe) [ 25/Aug/14 ]

Its definitely the HD 3000, but I don't know why 10.9.4 didn't fix it.

Comment by Brennan Tomlinson [ 25/Aug/14 ]

I am running OSX 10.9.4 on a 13-inch, Late 2011 Macbook Pro
Processor: 2.8 GHz Intel Core i7
Memory: 16 GB 1333 MHz DDR3
Graphics Intel HD Graphics 3000 512 MB
Software OS X 10.9.4 (13E28)
Everything besides the memory (which shouldn't effect this issue) came stock with the Macbook Pro.
Ever since I got Minecraft on this device I have been experiencing the exact issue described by this bug report, even after updating to the latest version of OS X. The only time I have been able to normally see the colored signs is with the use of MinecraftLFM, (http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/1286643-minecraftlfm-fixes-colored-signs-entity-rendering) a mod for Minecraft that fixes a variety of graphical glitches including the colored sign issue.

Comment by [Mod] Ezekiel (ezfe) [ 22/Aug/14 ]

This is an OS X Driver issue. I know this because I've seen it completely disappear after an OS X update. If anyone still has this issue after updating to the latest OS X (10.9) I will reopen it.

Comment by Kumasasa [ 18/Jul/14 ]

Reopened MC-33304

Comment by odisseus [ 17/Jul/14 ]

I think it only concerns 2.4 GHz Intel Core i5. I recently switched to a 1.5GHz and I'm not anymore encountering it.
Edit : MC-33304 is NOT the same bug.

Comment by Naor Volkovich [ 17/Jul/14 ]

It's the same problem but you have more info there so I guess it will be better to use that one...

Comment by Kumasasa [ 17/Jul/14 ]

Maybe there are two issues.
Most of the linked issues are OS X issues. Please see if MC-33304 better describes your issue, will reopen that ticket then.

Comment by Naor Volkovich [ 17/Jul/14 ]

Not really... It happened to my friends as we'll and they're using windows

Comment by Kumasasa [ 16/Jul/14 ]

This seems to be only to happen on OS X

Comment by Naor Volkovich [ 15/Jul/14 ]

It doesn't happen all the time... Sometimes it loads it correctly but sometimes it's not and when you use F3+a it's loading it correctly again
It's maybe not happening to all the computers... I don't really know

Comment by Anon Ymus [ 15/Jul/14 ]

Unable to reproduce in 14w28b. Placed a sign and then ran:

/blockdata ~ ~ ~ {Text1:"{\"text\":\"\",\"extra\":[{\"text\":\"TEST\",\"color\":\"blue\"}]}"}
Comment by Kumasasa [ 05/Jul/14 ]

Reopened.
Now possible in vanilla.

Comment by Galaxy_2Alex [ 21/Dec/13 ]

This is NOT a problem in Vanilla Minecraft and cannot be reproduced without any external editors. Therefor it's not a valid report for this tracker.

Comment by Brennan Tomlinson [ 21/Dec/13 ]

PLEASE FIX THIS, THIS IS THE MOST ANNOYING AND INCONVENIENT BUG IVE EVER EXPERIENCED WITH MINECRAFT!!!

Comment by fake fakes [ 22/Jul/13 ]

This happens to me in both singleplayer and multiplayer in 1.6.2 It only happens on my MacBook Air, not on my brothers PC

Comment by Zoomreddin [ 02/Apr/13 ]

Not true actually. Coloured signs are vanilla, they just cannot be placed without an external editor (like MCEdit). You do not have to mod your game for this to happen. Oh, and confirmed on a MacBook Air running Mountain Lion and Minecraft 1.5.1

Comment by Selbram (Tory Clement) [ 30/Oct/12 ]

This venue is for vanilla bugs only. Color text on signs is not in the current release of Minecraft. It has been noted but I will close this as invalid.

Generated at Sun Jan 12 11:54:01 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.