[1.15.2] Cannot create translucent blocks

[Alex Sim]

I'm trying to create transparent/translucent blocks in Minecraft 1.15.2 (Forge v. 31.1.30).

 

The leaves and flowers in the screenshot below should have cutout spots, while the blue blocks on the right should be translucent (semi-transparent) like glass or ice.

 

 

And yes I am using the notSolid() property, I have overridden getAmbientOcclusionLightValue, propagatesSkylightDown, isNormalCube and isSideInvisible, I have even tried using the default GlassBlock class for the blue block on the right (same result).

 

I am trying to port a mod from 1.14.4, the blocks looked fine in that version

Edited March 30, 2020 by Alex Sim

[Draco18s]

https://www.minecraftforge.net/forum/search/?q="1.15" transparent&type=forums_topic&updated_after=any&sortby=relevancy&search_and_or=and

Fourth result.

[Alex Sim]

1 hour ago, Draco18s said:

https://www.minecraftforge.net/forum/search/?q="1.15" transparent&type=forums_topic&updated_after=any&sortby=relevancy&search_and_or=and

Fourth result.

 

Wow that's an unnecessarily complicated change

 

Thank god I can use Kotlin extension properties... And I'm already using reflection for registration ?

Edited March 30, 2020 by Alex Sim

[Alex Sim]

2 hours ago, Draco18s said:

https://www.minecraftforge.net/forum/search/?q="1.15" transparent&type=forums_topic&updated_after=any&sortby=relevancy&search_and_or=and

Fourth result.

Need some extra info: how would I go about making an armor set translucent?

[desht]

15 hours ago, Alex Sim said:

 

Wow that's an unnecessarily complicated change

 

Thank god I can use Kotlin extension properties... And I'm already using reflection for registration ?

A little more complicated, but not unnecessary.  It's down to how 1.15 handles rendering, basically by combining all operations for particular render type together, which greatly reduces the number of OpenGL state changes needed.  It's a big performance boost.

[Alex Sim]

5 minutes ago, desht said:

A little more complicated, but not unnecessary.  It's down to how 1.15 handles rendering, basically by combining all operations for particular render type together, which greatly reduces the number of OpenGL state changes needed.  It's a big performance boost.

What I find unnecessary is the fact that this can't be set though a block property (eg. setRenderType(RenderType)) and handled during block registration; after all it's very similar to what I'm doing now with reflection so it's definitely possible

Edited March 31, 2020 by Alex Sim