| 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 Java SE 6 64-Bit Version: 1.6.0_33-b03-424 OS X Mountain Lion |
||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CHK: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Confirmation Status: | Confirmed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Category: |
Rendering
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
| 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 (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. |
| 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 Using 1.9-pre2 obfuscated: |
| Comment by Kumasasa [ 16/Jun/15 ] |
|
Reopened due to |
| 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 |
| Comment by KingSupernova [ 23/Jan/15 ] |
|
That's not what this bug is about. I think you want |
| 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 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. |
| 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 |
| 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 |
| 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. |
| 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. |
| 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 |
| 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. |
| 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. |