Invisible custom rendered block

[RegalBlaze]

Hi all,

 

So I've made a new block called roof. I followed the forge tutorials to set up the block's TileEntity and custom Renderer . I tested placing the block when it had just the block and tileentity classes and everything was fine. After making the custom renderer ,however, the block turned invisble showing just the collision lines. Which of the following classes should I check for the problem?

Roof, TileEntityRoof, RenderRoof, ModelRoof, clientproxy, commonproxy or the main mod file?

 

I can post the codes but it's so much that it would be really nice if it could be fixed without it.

 

Thnx,

 

RegalBlaze

[Naiten]

Sorry, no telepathic people here.

[mnn]

As stated by Naitenne we need code, without the code it's just guessing what you could do wrong/miss... All I can do is throw a few common solutions: make sure your TE is spawned with your block, check if your model isn't misplaced (e.g. being rendered underground), check if you're registering your TE and TE renderer.

[redria7]

I was having this problem earlier this morning/last night. The problem I finally found was that my renderer needed to be initialized. I thought I had properly initialized it in my ClientProxy class but the method was never being called.

 

First, check your ClientProxy class. You need a method in here - it doesn't matter what it's named, but for logic's sake call it InitRendering():

 

@Override
       public void InitRendering()
       {
    	   ClientRegistry.bindTileEntitySpecialRenderer(RoofTileEntity.class, new RoofTileEntityRenderer());
       }

 

This assumes you have named your tile entity class RoofTileEntity, and your rendering class RoofTileEntityRenderer. Change these accordingly.

 

Now go to your CommonProxy class. You extended CommonProxy with ClientProxy and InitRendering() should be overriding a method, so you need a method InitRendering() in the CommonProxy class so you can override it. Add one that does nothing:

 

public void InitRendering()
{
}

 

Now you can use a ClientProxy version of the CommonProxy object to call the real InitRendering() method.

Next comes voodoo black magic I don't understand.

You should already have some code in your main mod class that looks like:

 

@SidedProxy(clientSide = "mods.YourMod.client.ClientProxy", serverSide = "mods.YourMod.CommonProxy")
    public static CommonProxy proxy;

 

Somehow this makes the variable "proxy" a ClientProxy version of CommonProxy. Anyway.

At the end of the load (FMLInitializationEvent event) method in your main mod class, add one extra line of code:

 

proxy.InitRendering();

 

This should finally tell Minecraft where your custom rendering class is. Now you just have to go back and adjust your image path until the renderer can find your .png file. Use the Warning output as a nice indicator of where it is trying to find a file vs where it actually is.

 

Assuming that was your problem. If not, good luck