Jump to content

[SOLVED] [1.17.1] Custom block with transparent parts makes block behind invisible


Recommended Posts

Posted (edited)

Hey guys!

I encountered the following problem when updating my mod from 1.16 to 1.17: If I place a block of my mod (e.g. stairs) in front of another block, the hidden side of the back block is not rendered.

eKAThcd.png

It worked perfectly on 1.16, the problem only appeared when I moved to 1.17. I have already tried setting the render layer of the blocks from translucent to solid and to cutout, but nothing has changed.

The main feature of my mod is that the blocks of my mod (frames) can take the texture of any block. If I then take a transparent block (e.g. red stained glass) and "disguise" the frame stairs with it, you can see that on all sides that are completely covered by the stairs, the blocks behind them become invisible. (see 2nd picture) But on the side that is only covered to 3/4, the grass block behind is visible through the "red stained glass stairs" (see 3rd picture), which is correct.

AeHEZUa.png

LPSbZII.png

For the stairs used in the first picture, a classic json model is used; when the stairs are disguised (2nd and 3rd picture), I created a BakedModel.

 

Please let me know, if you need more information or specific code parts. It looks to me like I'm missing on something very obvious, so I'm sorry if this question is stupid... please don't be mad at me

 

Here's my github repository: https://github.com/PianoManu/BlockCarpentry/tree/Forge-1.17

The block's main class is mod.pianomanu.blockcarpentry.block.StairsFrameBlock

The class where I created the baked model is mod.pianomanu.blockcarpentry.bakedmodels.StairsBakedModel

I'm setting the render layers in mod.pianomanu.blockcarpentry.setup.RenderSetup

All blocks and items are registered in mod.pianomanu.blockcarpentry.setup.Registration

 

 

Thanks in advance!!

Regards, Manu

Edited by PianoManu
Posted

You need to set the block's render type in your client setup.

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Posted
public class RenderSetup {
    public static void setup() {
      ...
        ItemBlockRenderTypes.setRenderLayer(Registration.STAIRS_FRAMEBLOCK.get(), RenderType.translucent());
      ...
    }
}

Here's what I'm currently doing in my setup class. And the setup() method is called when the FMLClientSetupEvent is fired. The "..." are similar lines I removed, because the only things that change, are the blocks in the first parameter...

 

As I said, I already used RenderType.solid() and RenderType.cutout() and although it changed the model's appearance, it did not fix the problem. Or perhaps I misunderstood you? In that case, could you please be more specific, what I should do?

Many thanks for your help!

Regards, Manu

  • PianoManu changed the title to [SOLVED] [1.17.1] Custom block with transparent parts makes block behind invisible

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.