Sam Lyons
- yackaro
- yackaro
- America/New_York
- Yes
- No
8 issues
Key
Summary
Status
Reporter
Assignee
Created
MC-7914
MCPE-5512
Changed Environment:
java SE U45 64 bit running on NVIDIA GeForce 210 and intel core 2 duo running under windows 7 (64 bit duhh)
Added Affects Versions: 0.9.0 Build 1
dl sensor is my term for that new daylight sensor thing in the test version
here's how it needs to be fixed: instead of using sv*w=
##=# like jonathan said it should just read the light level of the half-block above it (it is a half-block) and then give off a redstone signal based off of that valueit get annoying when you find yourself unable to turn easily and you just joined a world in the middle of the night full of zombies and skeletons and stuffs and your not on peaceful mode. death is sure to come unless you realize it quick and r@pe dat pause button before its too late.
please look into this. i think it has something to do with tegra 4 but im not sure
im having this same ANR error on my nvidia shield. no you dont have to pay again, meaning go ahead and download it on all yo phones! the nvidia shield has a tegra 4 chipset in it.... if your phone has a tegra 4-based chipset in it then the problem might beyelling at our faces! but for now keep minecraft backdated to 8.0 using something like aptoide...
i just get an app not responding error with a black background
oh and by the way, this is the same as
MCPE-6658, which i reported.the debug screen crosshair? i had the debug screen on before i switched to spectator mode and the regular cursor was still there. My hardware's been acting up recently anyway so it might have just been like a failed processor update or something.
odd. i had the debug screen up before i switched to spectator mode and i still had regular cursor until i switched to spec mode
mark this as works as intended, because it's the new cursor that appears when you open the F3 debug screen, and you have the F3 debug screen open