Jump to content

Recommended Posts

Posted

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.

Posted

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/

Posted
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

Posted

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)

Posted

This isn't mekanism's problem or gravity gun it's forges problem.  I tried both mods independently on the same forge version and they all had the same issue.  This is forge's problem not mekanism's or gravity gun's problem.

Posted (edited)

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)

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

    • When I first heard about Bitcoin back in 2018, I was skeptical. The idea of a decentralized, digital currency seemed too good to be true. But I was intrigued as I learned more about the technology behind it and its potential. I started small, investing just a few hundred dollars, dipping my toes into the cryptocurrency waters. At first, it was exhilarating to watch the value of my investment grow exponentially. I felt like I was part of the future, an early adopter of this revolutionary new asset. But that euphoria was short-lived. One day, I logged into my digital wallet only to find it empty - my Bitcoin had vanished without a trace. It turned out that the online exchange I had trusted had been hacked, and my funds were stolen. I was devastated, both financially and emotionally. All the potential I had seen in Bitcoin was tainted by the harsh reality that with decentralization came a lack of regulation and oversight. My hard-earned money was gone, lost to the ether of the digital world. This experience taught me a painful lesson about the price of trust in the uncharted territory of cryptocurrency. While the technology holds incredible promise, the risks can be catastrophic if you don't approach it with extreme caution. My Bitcoin investment gamble had failed, and I was left to pick up the pieces, wiser but poorer for having placed my faith in the wrong hands. My sincere appreciation goes to MUYERN TRUST HACKER. You are my hero in recovering my lost funds. Send a direct m a i l ( muyerntrusted ( @ ) mail-me ( . )c o m ) or message on whats app : + 1 ( 4-4-0 ) ( 3 -3 -5 ) ( 0-2-0-5 )
    • You could try posting a log (if there is no log at all, it may be the launcher you are using, the FAQ may have info on how to enable the log) as described in the FAQ, however this will probably need to be reported to/remedied by the mod author.
    • So me and a couple of friends are playing with a shitpost mod pack and one of the mods in the pack is corail tombstone and for some reason there is a problem with it, where on death to fire the player will get kicked out of the server and the tombstone will not spawn basically deleting an entire inventory, it doesn't matter what type of fire it is, whether it's from vanilla fire/lava, or from modded fire like ice&fire/lycanites and it's common enough to where everyone on the server has experienced at least once or twice and it doesn't give any crash log. a solution to this would be much appreciated thank you!
    • It is 1.12.2 - I have no idea if there is a 1.12 pack
  • Topics

×
×
  • Create New...

Important Information

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