Jump to content

Error: java.lang.IllegalStateException: Failed to create model for minecraft:hanging_sign


Recommended Posts

Posted

Hello. I have encountered an issue whist attempting to play on Forge 1.19.4 on the latest stable release beta as of 05/29/23. Everytime I attempt to load Minecraft Forge with mods installed, I recieve the following crash report: 

 

The game crashed whilst rendering overlay Error: java.lang.IllegalStateException: Failed to create model for minecraft:hanging_sign

 

I have tried:

Deleting all post-install custom installations

Reinstalling Minecraft (deleting all files within Roaming/.minecraft folder and reinstalling)

Updating Java Runtime Environment

Uninstalling Java via Control Panel and downloading and installing newest recommended version (Java 8 Update 371)

 

Below I have included both the crash log I recieved, as well as the debug.log. I hope someone can help!

crash-client.txt

debug.log

Posted
On 5/30/2023 at 9:37 AM, ChampionAsh5357 said:

1.19.4 uses Java 17, not Java 8.

It must be able to run on both, because I have resolved the issue myself. Reading through my debug logs, I found that multiple mods were the problem, including Supplementaries for the initial error, and Blue Skies' reliance on an outated Mixin. Thank you though!

Posted (edited)

UPDATE: As of 05/31/2023, I have resolved the issue(s). I read extensively into my debug.log file and found that two mods in particular were causing my problems.

Supplementaries: Error: java.lang.IllegalStateException: Failed to create model for minecraft:hanging_sign

Blue Skies: Outdated Sponge mixin causing shader-related crash on new versions of Minecraft

Testing Minecraft 1.19.4 with Java 8 Update 371, it seems to work fine both in Vanilla and Forge/Optifine installations (yes I know Optifine is outdated and not recommended. I still like to use it as it wasn't the cause of any of my crashes). So I guess Java 17 isn't necessarily required if you use the most recent version of Java 8? Who knows but maybe that is some useful information to someone.

(Maybe the mods that were the cause of my issues would have worked if I used Java 17, I am unsure and I won't change my Java version now that everything seems to be running fine.)

Edited by Tha_Marshall
Posted
11 hours ago, Tha_Marshall said:

Testing Minecraft 1.19.4 with Java 8 Update 371, it seems to work fine both in Vanilla and Forge/Optifine installations (yes I know Optifine is outdated and not recommended. I still like to use it as it wasn't the cause of any of my crashes). So I guess Java 17 isn't necessarily required if you use the most recent version of Java 8? Who knows but maybe that is some useful information to someone.

 

If you read your logs, it would be using Java 17. I assumed that you modified the JVM installation in the profile. However, it working indicates that you haven't, meaning you were just using the version of Java shipped with the client. I will reiterate that Minecraft 1.19 was compiled with Java 17, which means it will only be forward compatible with newer versions and crash on older versions with a class version error.

  • 8 months later...
Posted

so anyone wondering if you see this error show up and you have Supplementaries installed disable it then run your game, it will then tell you what the actual mod issues is (in marshall's case it was blue skies) then once your fix the issues the hanging sign error should go away, ive had this happen once or twice with my mods not haveing the right version of one of it dependences

 

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

    • I've tried multiple ways to get the chunk coordinates and none of them have worked, so I'm guessing it may be getChunk().  Is there another way to forcibly load a chunk on that same tick? If all else fails I guess I can just delay my action by a tick, but that's a pain in the butt and makes it more complex to provide appropriate feedback... Also welcome, Zander.  If you're searching for a similar solution, I hope this (eventually) helps you too 😅
    • My guess would be that you are not getting the chunk coordinates right, or getChunk dosnt work.
    • Hello, Recently I have been hosting an RLcraft server on Minecraft Forge Version 1.12.2 - 14.23.5.2860 I originally had lag issues and I chalked it up to playing on less than perfect hardware so I moved the server to better hardware(i9-9900k with 64GB of RAM for 1 player.) After lots of troubleshooting I discovered a couple of things. World saving was causing the MSPT to spike to over 2000Miliseconds and was happening every minute. This kind of makes sense as the world was pre-generated and is over 100GB. I learned that I could turn off world saving and just schedule that and that resolved that issue. After that issue was resolved I discovered another issue. It appears that when exploring chunks, any chunks explored stay loaded. They persist. I was originally thinking that this had to be a mod issue, but it didn't seem like anyone was talking about it. This isn't really a problem on packs with few worldgen mods or just few mods in general, but on beefier packs it becomes a problem. I went through forge changelogs and found this line. Build: 1.12.2-14.23.5.2841 - Thu Aug 29 01:58:50 GMT 2019 bs2609: Improve performance of persistent chunk checks (#5706) Is this a related item to what I am dealing with or just something else?   I went ahead and created a new dedicated server with Just Forge 14.23.5.2860, spark reforged, and it's core mods. I was able to replicate the issue and log it with spark. Hopefully you're able to see this spark profile. It basically shows that as I explored the chunk loading persisted(2000 chunks loaded over 10 minutes with one player)The view distance is set to 10 so that should be 200 chunks per player. If I don't move the loaded chunks are 200. I was however able to fix the persistent chunk issue if I save the world more frequently. My question is, is this intended function of the game or is this a bug? Everywhere I read seems to indicate Minecraft servers save every 5 minutes and not every minute. Can chunks not unload if the world does not autosave. Additionally. Autosave specifically appears to fix this issue. Manually running save-all does not resolve the issue.   I realize this is kind of a log one, sorry. Please let me know if you require further information. Thanks in advance for your time. https://spark.lucko.me/NvlMtC39Yt https://imgur.com/a/K0oyukx https://pastebin.com/z0qGu1Vh  
    • Thank you so much, I had originally tried to allocate 16 gb of ram but still had the same issue with the lag, 12 was perfect.
  • Topics

×
×
  • Create New...

Important Information

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