Difficulty with Custom Mesh

[ClaudiusMinimus]

I am having difficulty getting my custom mesh to render correctly. The mesh processes my recipes just fine, though I would like for it to look correct as well. I also want to add a couple more meshes, but would like to get this one right before I do.

Thank you and I appreciate your help!

Details listed below:

• Minecraft: 1.19.2
• Forge: 43.2.3
• Create: 1.19.2-0.5.0.h
• Create Sifter 1.19.2-1.3.3.g

This what the mesh is supposed to look like from BlockBench.

This is how it renders in game

In order to get the mesh to work and render as well as it does I had to do the following:

1. In BlockBench, create the kubejs/assets/createsifter/models/block/meshes/amethyst_mesh.json
2. In BlockBench, create, edit and apply the textures found in kubejs/assets/createsifter/textures
3. Copy kubejs/assets/createsifter/textures to kubejs/assets/kubejs/textures

Attached are the pertinent files kubejs.zip

[ClaudiusMinimus]

Also, do you have a discord server that you could invite me to?

[oierbravo]

Hi! I've updated the mod to patch I and fixed rendering issues. I think your problem may be resolved.

[ClaudiusMinimus]

Definitely a set in the right direction! Would be nice if they were rotated to the same plane as the sifter. :smile: Also, the border frame as shown in the above BlockBench example still needs rendering. Thank you very much for working on this!

[oierbravo]

Hi! I'm reworking the models and doc to simplify the process. In the meantime... could you try please:

StartupEvents.registry('item', event => {
    // Register new items here
    // event.create('example_item').displayName('Example Item')
    event.create('amethyst_mesh','createsifter:mesh').displayName('Amethyst Mesh').parentModel("createsifter:block/meshes/custom_mesh").texture("1","kubejs:item/amethyst_mesh").texture("0","kubejs:block/coal_block");
})

It just adds the custom model and texture overrides.

[ClaudiusMinimus]

Looks GREAT! Thanks! I look forward to the update!

[github-actions[bot]]

This issue has been marked as stale because it has been inactive for 3 weeks. It will be closed if it remains inactive for another 3 weeks.

[github-actions[bot]]

This issue has been closed since it has been inactive for 3 weeks since it was marked as stale.