I don't know much about rendering in newer versions (I only mod 1.6.4) but I do know that in 1.8 they moved all the OpenGL calls into "GLStateManager" - you should never be directly calling GL11, as you do for e.g. "GL11.glPushMatrix();", which should instead be "GLStateManager.pushMatrix();"; otherwise, you could end up with GL state inconsistencies (e.g. stack overflow will cause pushMatrix() to fail so the state isn't restored when popMatrix() is called, which in the worst case can completely break all rendering that occurs afterwards. I once managed to break rendering so badly that all textures stopped rendering, even after exiting the world, without any OpenGL errors, which themselves are marginally useful unless you place a lot of "GL11.glGetError()" calls and print out the line number, and even then only actual errors are caught, not unintended state changes). This also presumably makes it easier to update to later versions, which no longer used fixed-function OpenGL (GL11), hence "GLStateManager" (i.e. Mojang could simply update the code in GLStateManager to use newer OpenGL methods).
Also, the best way to see how something is done is to look at vanilla code which does the same thing; e.g. see how item frames render the item in them (they are entities but TESRs are essentially the same).
When i make a TileEntitySpecialRenderer and then use the render function to render the item the item rendered is flickered and it has texture glitches
public class ShelfTileRenderer extends TileEntitySpecialRenderer<TileEntityShelf> { @Override public void render(TileEntityShelf te, double x, double y, double z, float partialTicks, int destroyStage, float alpha) { GL11.glPushMatrix(); GL11.glTranslatef((float)x + 0.5F, (float)y + 1.02F, (float)z + 0.3F); GL11.glRotatef(180, 0, 1, 1); //RenderManager.renderEntityWithPosYaw(this.entItem, 0.0D, 0.0D, 0.0D, 0.0F, 0.0F); //ItemStack is = te.itemInShelf.getStackInSlot(0); RenderItem itemRenderer = Minecraft.getMinecraft().getRenderItem(); //IBakedModel ibakedmodel = itemRenderer.getItemModelWithOverrides(is, te.getWorld(), (EntityLivingBase)null); //IBakedModel transformedModel = net.minecraftforge.client.ForgeHooksClient.handleCameraTransforms(ibakedmodel, ItemCameraTransforms.TransformType.GROUND, false); //itemRenderer.renderItem(is, itemRenderer.getItemModelMesher().getItemModel(is)); //ForgeHooksClient.renderLitItem(itemRenderer, itemRenderer.getItemModelMesher().getItemModel(is), -1, is); ItemStack itemstack = te.itemInShelf.getStackInSlot(0); GlStateManager.enableRescaleNormal(); GlStateManager.alphaFunc(516, 0.1F); GlStateManager.enableBlend(); RenderHelper.enableStandardItemLighting(); GlStateManager.tryBlendFuncSeparate(GlStateManager.SourceFactor.SRC_ALPHA, GlStateManager.DestFactor.ONE_MINUS_SRC_ALPHA, GlStateManager.SourceFactor.ONE, GlStateManager.DestFactor.ZERO); IBakedModel ibakedmodel = itemRenderer.getItemModelWithOverrides(itemstack, te.getWorld(), (EntityLivingBase)null); IBakedModel transformedModel = net.minecraftforge.client.ForgeHooksClient.handleCameraTransforms(ibakedmodel, ItemCameraTransforms.TransformType.GROUND, false); itemRenderer.renderItem(itemstack, transformedModel); GlStateManager.disableRescaleNormal(); GlStateManager.disableBlend(); //Minecraft.getMinecraft().getRenderItem().renderItem(te.itemInShelf.getStackInSlot(0),); GL11.glPopMatrix(); } }Here is the video that shows this weird thing
I don't know much about rendering in newer versions (I only mod 1.6.4) but I do know that in 1.8 they moved all the OpenGL calls into "GLStateManager" - you should never be directly calling GL11, as you do for e.g. "GL11.glPushMatrix();", which should instead be "GLStateManager.pushMatrix();"; otherwise, you could end up with GL state inconsistencies (e.g. stack overflow will cause pushMatrix() to fail so the state isn't restored when popMatrix() is called, which in the worst case can completely break all rendering that occurs afterwards. I once managed to break rendering so badly that all textures stopped rendering, even after exiting the world, without any OpenGL errors, which themselves are marginally useful unless you place a lot of "GL11.glGetError()" calls and print out the line number, and even then only actual errors are caught, not unintended state changes). This also presumably makes it easier to update to later versions, which no longer used fixed-function OpenGL (GL11), hence "GLStateManager" (i.e. Mojang could simply update the code in GLStateManager to use newer OpenGL methods).
Also, the best way to see how something is done is to look at vanilla code which does the same thing; e.g. see how item frames render the item in them (they are entities but TESRs are essentially the same).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?