Jump to content

Trying to play RLcraft and minecraft crashes


Shyhud

Recommended Posts

Around one month ago, i was playing rlcraft until suddenly it crashed on loadingentityrenderer. Sometimes I can get on the title screen, but no further then that. I have recently tried got into minecraft modding, but same thing happens there. I followed this tutorial, https://www.youtube.com/watch?v=rmWBP5ifDlw&t=410s but i don't know if this is the cause. the crashing happened around the time that i finished the first tutorial. here is the end of the crash log. I can't upload the whole thing because it says -200 and i think its an error.

[B#590]  [17:27:56] [Sound Library Loader/INFO]: Starting up SoundSystem...
[B#590]  [17:27:56] [Thread-8/INFO]: Initializing LWJGL OpenAL
[B#590]  [17:27:56] [Thread-8/INFO]: (The LWJGL binding of OpenAL.  For more information, see http://www.lwjgl.org)
[B#590]  [17:27:56] [Thread-8/INFO]: OpenAL initialized.
[B#590]  [17:27:56] [Client thread/INFO]: [pl.asie.foamfix.coremod.FoamFixTransformer:spliceClasses:111]: Spliced in METHOD: net.minecraftforge.client.model.ModelLoader$VanillaModelWrapper.bakeNormal
[B#590]  [17:27:56] [Sound Library Loader/INFO]: Sound engine started
[B#590]  [17:28:11] [Client thread/WARN]: Unable to resolve texture due to upward reference: #item in traverse:models/block/itemblock
[B#590]  [17:28:11] [Client thread/INFO]: [BetterFoliage] Registered 5 grass textures
[B#590]  [17:28:11] [Client thread/INFO]: [BetterFoliage] Registered 2 snowed grass textures
[B#590]  [17:28:11] [Client thread/INFO]: [BetterFoliage] Registered 4 mycelium textures
[B#590]  [17:28:11] [Client thread/INFO]: [BetterFoliage] Registered 2 cactus arm textures
[B#590]  [17:28:11] [Client thread/INFO]: [BetterFoliage] Registered 3 lilypad root textures
[B#590]  [17:28:11] [Client thread/INFO]: [BetterFoliage] Registered 2 lilypad flower textures
[B#590]  [17:28:12] [Client thread/INFO]: [BetterFoliage] Registered 4 reed textures
[B#590]  [17:28:12] [Client thread/INFO]: [BetterFoliage] Registered 4 algae textures
[B#590]  [17:28:12] [Client thread/INFO]: [BetterFoliage] Registered 6 coral textures
[B#590]  [17:28:12] [Client thread/INFO]: [BetterFoliage] Registered 4 coral crust textures
[B#590]  [17:28:12] [Client thread/INFO]: [BetterFoliage] Registered 3 netherrack textures
[B#590]  [17:28:12] [Client thread/INFO]: [BetterFoliage] Registered 2 soul particle textures
[B#590]  [17:28:12] [Client thread/INFO]: Max texture size: 8192
[B#590]  [17:28:21] [Client thread/INFO]: Created: 2048x1024 textures-atlas
[B#590]  [17:28:22] [Client thread/ERROR]: MultiModel minecraft:builtin/missing is empty (no base model or parts were provided/resolved)
[B#590]  [17:28:22] [Client thread/ERROR]: MultiModel minecraft:builtin/missing is empty (no base model or parts were provided/resolved)
[B#590]  [17:28:23] [Client thread/INFO]: Clearing ModelLoaderRegistry cache (16534 items)...
[B#590]  [17:28:23] [Client thread/INFO]: Cleared 16529 objects.
[B#590]  [17:28:23] [Client thread/INFO]: Deduplicating models...
[B#590]  [17:28:23] [Client thread/INFO]: Deduplicating models...
[B#590]  [17:28:24] [Client thread/INFO]: Deduplicated 106720 (+ 43837) objects.
[B#590]  [17:28:28] [Client thread/INFO]: Found method net.minecraft.client.renderer.chunk.RenderChunk.func_178581_b (FFFLnet/minecraft/client/renderer/chunk/ChunkCompileTaskGenerator;)V (matching rebuildChunk)
[B#590]  [17:28:28] [Client thread/INFO]: [BetterFoliageLoader] Applying RenderChunk block render override
[B#590]  [17:28:28] [Client thread/INFO]: [BetterFoliageLoader] Applying RenderChunk block layer override
[B#590]  #
[B#590]  # A fatal error has been detected by the Java Runtime Environment:
[B#590]  #
[B#590]  #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000325bf1cb60, pid=2540, tid=0x00000000000022d0
[B#590]  #
[B#590]  # JRE version: Java(TM) SE Runtime Environment (8.0_261-b12) (build 1.8.0_261-b12)
[B#590]  # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.261-b12 mixed mode windows-amd64 compressed oops)
[B#590]  # Problematic frame:
[B#590]  # C  [ig75icd64.dll+0x1cb60]
[B#590]  #
[B#590]  # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
[B#590]  #
[B#590]  # An error report file with more information is saved as:
[B#590]  # C:\Users\didi\AppData\Roaming\.technic\modpacks\shivaxi-rlcraft\hs_err_pid2540.log
[B#590]  #
[B#590]  # If you would like to submit a bug report, please visit:
[B#590]  #   http://bugreport.java.com/bugreport/crash.jsp
[B#590]  # The crash happened outside the Java Virtual Machine in native code.
[B#590]  # See problematic frame for where to report the bug.
[B#590]  #
[B#590]  AL lib: (EE) alc_cleanup: 1 device not closed
[B#590] Starting download of http://cdn.technicpack.net/platform2/pack-icons/1530385.png?1588115247, with 3 tries remaining

 

Link to comment
Share on other sites

1.12 is no longer supported on this forum.

Please update to a modern version of Minecraft to receive support.

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.

Announcements



×
×
  • Create New...

Important Information

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