Okay I've given up trying to solve this on my own, can someone please tell me why the exact same block is rendering like this?
As the picture shows, the blocks on the left are rendering as they should, while the blocks on the right have a much darker hole in them. This problem only appears in deserts as far as I can tell, and it's only visible at some camera angles, so if I move the camera the block will render right
here is the code that's currently doing that:
public boolean renderWorldBlock(IBlockAccess world, int x, int y, int z, Block block, int modelId, RenderBlocks renderer) {
if(ClientProxy.rabbitHolePass == 0){
renderer.renderStandardBlock(Block.grass, x, y, z);
}
else{
renderer.renderFaceYPos(DontStarve.rabbitHole, x, y, z, DontStarve.rabbitHole.getTopIcon());
}
return true;
}
If someone has any idea why this is happening, please help!
If you are using a piece of code to display that and not a texture file, use a texture file and overlay it on a block 1 pixel up, and I see you are making a don't starve mod for MC, if that doesn't work, try to put a different block there with a texture like it is
Rollback Post to RevisionRollBack
http://pcpartpicker.com/p/2kUq0
the average script-follower/lack of common sense: http://www.techtales.com/tftechs.php?m=200504#8418
windoge 8 has the saddest excuse for a BSOD, it just tells you the type of error, no stop code, no nothing, just "something went wrong, all your unsaved work has now been lost to the void that is volatile memory"
As the picture shows, the blocks on the left are rendering as they should, while the blocks on the right have a much darker hole in them. This problem only appears in deserts as far as I can tell, and it's only visible at some camera angles, so if I move the camera the block will render right
here is the code that's currently doing that:
If someone has any idea why this is happening, please help!
http://pcpartpicker.com/p/2kUq0
the average script-follower/lack of common sense: http://www.techtales.com/tftechs.php?m=200504#8418
windoge 8 has the saddest excuse for a BSOD, it just tells you the type of error, no stop code, no nothing, just "something went wrong, all your unsaved work has now been lost to the void that is volatile memory"