Jump to content

Rendering Bug


Mxnmnm

Recommended Posts

https://gist.github.com/mxnmnm/2eff660af666af6cce487720d271453c

 

Whenever I hold an item with a 3d model such as a gravity gun or flame thrower from mekanism they are invisible starting with forge version 14.23.5.2781 and beyond.  The item is invisible in my inventory, JEI, and in my hand.  The items still function but them not being rendered can be really distracting especially when you think your inventory has an empty slot but it's really full with one of those items.  I checked the forge changelog and I found this in forge version 14.23.5.2781

mezz: Implement rendering for item models with emissive quads (#5047)

so I'm guessing that has a lot to do with it.  I'm not sure what else I should do but hopefully this can be fixed and if I need to give more information please let me know.

Link to comment
Share on other sites

Honestly idk whats going on. Try to use the latest version of forge and to update the mekanism files.

Mekanism only has 3 files but it is showing up 5. Try using the non api version of the files

[22:53:43] [Client thread/DEBUG] [FML]: MekanismAPI|util(API: MekanismAPI|util:9.0.0): Mekanism-1.12.2-9.4.13.349.jar ()

[22:53:43] [Client thread/DEBUG] [FML]: MekanismAPI|gas(API: MekanismAPI|gas:9.0.0): Mekanism-1.12.2-9.4.13.349.jar ()

[22:53:43] [Client thread/DEBUG] [FML]: MekanismAPI|core(API: MekanismAPI|core:9.0.0): Mekanism-1.12.2-9.4.13.349.jar ()

[22:53:43] [Client thread/DEBUG] [FML]: MekanismAPI|laser(API: MekanismAPI|laser:9.0.0): Mekanism-1.12.2-9.4.13.349.jar ()

[22:53:43] [Client thread/DEBUG] [FML]: MekanismAPI|infuse(API: MekanismAPI|infuse:9.0.0): Mekanism-1.12.2-9.4.13.349.jar ()

[22:53:43] [Client thread/DEBUG] [FML]: MekanismAPI|transmitter(API: MekanismAPI|transmitter:9.0.0): Mekanism-1.12.2-9.4.13.349.jar ()

[22:53:43] [Client thread/DEBUG] [FML]: MekanismAPI|energy(API: MekanismAPI|energy:9.0.0): Mekanism-1.12.2-9.4.13.349.jar ()

http://aidancbrady.com/mekanism/download/

Link to comment
Share on other sites

7 hours ago, BBGamer2012 said:

Honestly idk whats going on. Try to use the latest version of forge and to update the mekanism files.

Mekanism only has 3 files but it is showing up 5. Try using the non api version of the files

[22:53:43] [Client thread/DEBUG] [FML]: MekanismAPI|util(API: MekanismAPI|util:9.0.0): Mekanism-1.12.2-9.4.13.349.jar ()

[22:53:43] [Client thread/DEBUG] [FML]: MekanismAPI|gas(API: MekanismAPI|gas:9.0.0): Mekanism-1.12.2-9.4.13.349.jar ()

[22:53:43] [Client thread/DEBUG] [FML]: MekanismAPI|core(API: MekanismAPI|core:9.0.0): Mekanism-1.12.2-9.4.13.349.jar ()

[22:53:43] [Client thread/DEBUG] [FML]: MekanismAPI|laser(API: MekanismAPI|laser:9.0.0): Mekanism-1.12.2-9.4.13.349.jar ()

[22:53:43] [Client thread/DEBUG] [FML]: MekanismAPI|infuse(API: MekanismAPI|infuse:9.0.0): Mekanism-1.12.2-9.4.13.349.jar ()

[22:53:43] [Client thread/DEBUG] [FML]: MekanismAPI|transmitter(API: MekanismAPI|transmitter:9.0.0): Mekanism-1.12.2-9.4.13.349.jar ()

[22:53:43] [Client thread/DEBUG] [FML]: MekanismAPI|energy(API: MekanismAPI|energy:9.0.0): Mekanism-1.12.2-9.4.13.349.jar ()

http://aidancbrady.com/mekanism/download/

These are not the API files, I downloaded them off of curse forge and I just downloaded these ones and they are the exact same file (although it does say it's a developer version so I'm not sure how to take care of that or if it even matters that much anyways.  Keep in mind that this also happens with iChun's gravity gun mod so I doubt that mekanism is the issue here.  I'll use the latest version of forge and I'll add all of mekanism's addons to show you that it still happens.
 

https://gist.github.com/mxnmnm/b33d53daaf15424e2a30aab0bcb71f15

Link to comment
Share on other sites

Create an issue on Mekanisms issue tracker (on GitHub I believe) 

About Me

Spoiler

My Discord - Cadiboo#8887

My WebsiteCadiboo.github.io

My ModsCadiboo.github.io/projects

My TutorialsCadiboo.github.io/tutorials

Versions below 1.14.4 are no longer supported on this forum. Use the latest version to receive support.

When asking support remember to include all relevant log files (logs are found in .minecraft/logs/), code if applicable and screenshots if possible.

Only download mods from trusted sites like CurseForge (minecraft.curseforge.com). A list of bad sites can be found here, with more information available at stopmodreposts.org

Edit your own signature at www.minecraftforge.net/forum/settings/signature/ (Make sure to check its compatibility with the Dark Theme)

Link to comment
Share on other sites

It is mod’s responsibility to stay compatible with Forge, if most items render, I would say it is more likely that Mekanism is doing something that is no longer supported than that Forge is broken. I think that it’s better to report it to Mekanism first, if the developer says that it’s forge that is broken, then report it to forge

Edited by Cadiboo

About Me

Spoiler

My Discord - Cadiboo#8887

My WebsiteCadiboo.github.io

My ModsCadiboo.github.io/projects

My TutorialsCadiboo.github.io/tutorials

Versions below 1.14.4 are no longer supported on this forum. Use the latest version to receive support.

When asking support remember to include all relevant log files (logs are found in .minecraft/logs/), code if applicable and screenshots if possible.

Only download mods from trusted sites like CurseForge (minecraft.curseforge.com). A list of bad sites can be found here, with more information available at stopmodreposts.org

Edit your own signature at www.minecraftforge.net/forum/settings/signature/ (Make sure to check its compatibility with the Dark Theme)

Link to comment
Share on other sites

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



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • They were already updated, and just to double check I even did a cleanup and fresh update from that same page. I'm quite sure drivers are not the problem here. 
    • i tried downloading the drivers but it says no AMD graphics hardware has been detected    
    • Update your AMD/ATI drivers - get the drivers from their website - do not update via system  
    • As the title says i keep on crashing on forge 1.20.1 even without any mods downloaded, i have the latest drivers (nvidia) and vanilla minecraft works perfectly fine for me logs: https://pastebin.com/5UR01yG9
    • Hello everyone, I'm making this post to seek help for my modded block, It's a special block called FrozenBlock supposed to take the place of an old block, then after a set amount of ticks, it's supposed to revert its Block State, Entity, data... to the old block like this :  The problem I have is that the system breaks when handling multi blocks (I tried some fix but none of them worked) :  The bug I have identified is that the function "setOldBlockFields" in the item's "setFrozenBlock" function gets called once for the 1st block of multiblock getting frozen (as it should), but gets called a second time BEFORE creating the first FrozenBlock with the data of the 1st block, hence giving the same data to the two FrozenBlock :   Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=head] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@73681674 BlockEntityData : id:"minecraft:bed",x:3,y:-60,z:-6} Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=3, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=2, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} here is the code inside my custom "freeze" item :    @Override     public @NotNull InteractionResult useOn(@NotNull UseOnContext pContext) {         if (!pContext.getLevel().isClientSide() && pContext.getHand() == InteractionHand.MAIN_HAND) {             BlockPos blockPos = pContext.getClickedPos();             BlockPos secondBlockPos = getMultiblockPos(blockPos, pContext.getLevel().getBlockState(blockPos));             if (secondBlockPos != null) {                 createFrozenBlock(pContext, secondBlockPos);             }             createFrozenBlock(pContext, blockPos);             return InteractionResult.SUCCESS;         }         return super.useOn(pContext);     }     public static void createFrozenBlock(UseOnContext pContext, BlockPos blockPos) {         BlockState oldState = pContext.getLevel().getBlockState(blockPos);         BlockEntity oldBlockEntity = oldState.hasBlockEntity() ? pContext.getLevel().getBlockEntity(blockPos) : null;         CompoundTag oldBlockEntityData = oldState.hasBlockEntity() ? oldBlockEntity.serializeNBT() : null;         if (oldBlockEntity != null) {             pContext.getLevel().removeBlockEntity(blockPos);         }         BlockState FrozenBlock = setFrozenBlock(oldState, oldBlockEntity, oldBlockEntityData);         pContext.getLevel().setBlockAndUpdate(blockPos, FrozenBlock);     }     public static BlockState setFrozenBlock(BlockState blockState, @Nullable BlockEntity blockEntity, @Nullable CompoundTag blockEntityData) {         BlockState FrozenBlock = BlockRegister.FROZEN_BLOCK.get().defaultBlockState();         ((FrozenBlock) FrozenBlock.getBlock()).setOldBlockFields(blockState, blockEntity, blockEntityData);         return FrozenBlock;     }  
  • Topics

×
×
  • Create New...

Important Information

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