Jump to content

[1.12.2] CCL has caught an exception whilst rendering a block


Recommended Posts

Today i saw a video from direwolf20 (Increase Modded Minecraft FPS) about improving modded minecraft FPS, in his video he shows an option in Forge "Force Threaded Chunk Rendering", this option enabled shows a huge performance boost at least with him.

When i set this option to true, appear a error in chat "ccl has caught an exception whilst rendering a block". And then my minecraft don't load any more chunks or blocks. Someone know how to make this work?

 

 

 

 

 

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



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • 역삼텐프로 ♬BCGAME88·COM▣ 후암텐프로 고흥텐프로 구로텐프로 운니텐프로 vbb96 서린텐프로 논산텐프로 천연텐프로 광명텐프로 eiy23 효자텐프로 동빙고텐프로 송현텐프로 홍지텐프로 rwd14 적선텐프로 양화텐프로 훈정텐프로 신당텐프로 tlu56 강릉텐프로 논현텐프로 학방텐프로 창녕텐프로 hsh84 가락텐프로 창동텐프로 와룡텐프로 원서텐프로 jgp43 안성텐프로 화동텐프로 청암텐프로 춘천텐프로 pwp13 의정부텐프로 의왕텐프로 오금텐프로 청운텐프로 osv34 행당텐프로 남양주텐프로 수표텐프로 홍은텐프로 ugr41 여주텐프로 구의텐프로 태안텐프로 통의텐프로 myp53 흥인텐프로 만리텐프로 화곡텐프로 삼청텐프로 mtk86 명일텐프로 동해텐프로 둔촌텐프로 송정텐프로 lky75 학방텐프로 용산텐프로 신창텐프로 동작텐프로 jwe06 우이텐프로 창신텐프로 장사텐프로 포항텐프로 rhq01 하왕십리텐프로 파주텐프로 김해텐프로 용강텐프로 rdw49 광주텐프로 송정텐프로 정릉텐프로 동해텐프로 ydq84 대치텐프로 무교텐프로 구리텐프로 중화텐프로 pqm55 면목텐프로 내곡텐프로 용인텐프로 중림텐프로 fro55 운니텐프로 목동텐프로 수색텐프로 인사텐프로 xdp93 개포텐프로 금천텐프로 무안텐프로 용강텐프로 nfe30 안산텐프로 거창텐프로 원남텐프로 남영텐프로 lga42 저동텐프로 연건텐프로 천연텐프로 마곡텐프로 xek59 인천텐프로 종암텐프로 역삼텐프로 구리텐프로 vfd02
    • 삼성호스트바 ☜kbox1·com♨ 수표호스트바 창녕호스트바 마포호스트바 서교호스트바 jjb20 제천호스트바 회기호스트바 중림호스트바 진주호스트바 vgc60 가평호스트바 교남호스트바 일원호스트바 북아현호스트바 dgf03 독산호스트바 마곡호스트바 내발산호스트바 군포호스트바 hrw67 서교호스트바 장충호스트바 무악호스트바 행당호스트바 yfq58 수하호스트바 남산호스트바 신촌호스트바 팔판호스트바 jpf41 안양호스트바 울산호스트바 신설호스트바 상수호스트바 ofk82 토정호스트바 일원호스트바 내발산호스트바 부천호스트바 hml59 안양호스트바 관훈호스트바 연남호스트바 서교호스트바 lha26 봉천호스트바 진관호스트바 창녕호스트바 상수호스트바 bbl69 천호호스트바 낙원호스트바 의정부호스트바 한강호스트바 wse93 예장호스트바 시흥호스트바 하계호스트바 저동호스트바 cwo89 창녕호스트바 장위호스트바 소격호스트바 신영호스트바 gpn15 오쇠호스트바 여수호스트바 동작호스트바 청운호스트바 nmi40 목동호스트바 배방호스트바 용인호스트바 군산호스트바 dkk90 팔판호스트바 자곡호스트바 청주호스트바 산림호스트바 drt37 율현호스트바 잠실호스트바 회현호스트바 원주호스트바 wen22 충정호스트바 초동호스트바 휘경호스트바 명일호스트바 hhg53 노원호스트바 칠곡호스트바 수유호스트바 마장호스트바 vqj99 당인호스트바 대치호스트바 갈현호스트바 홍지호스트바 jwd98 청진호스트바 이방호스트바 북가좌호스트바 화순호스트바 ard15 해남호스트바 고양호스트바 구미호스트바 고척호스트바 pil39 남창호스트바 대현호스트바 영천호스트바 창천호스트바 wwj41
    • Delete the config file of nochatreports If there is no change, remove this mod
    • Remove animatedrecipebook from your server It is a client-side-only mod   If this is not working, add the new crash-report Add crash-reports with sites like https://paste.ee/ and paste the link to it here
    • i also finally managed to get it working heres my finished colorHandler that works currently for 1.18.2 and from what i can tell should work post version 1.12   //code start package com.zer0_the_wolf.layeredarmor.item.custom; import com.zer0_the_wolf.layeredarmor.item.LayeredArmoritems; import net.minecraft.client.color.item.ItemColor; import net.minecraft.client.color.item.ItemColors; import net.minecraft.nbt.CompoundTag; import net.minecraft.world.item.DyeColor; import net.minecraft.world.item.DyeableArmorItem; import net.minecraft.world.item.DyeableLeatherItem; import net.minecraft.world.item.ItemStack; import net.minecraftforge.client.event.ColorHandlerEvent; import net.minecraftforge.eventbus.api.SubscribeEvent; public class ColorHandlers { @SubscribeEvent public static void registerItemColors(ColorHandlerEvent.Item event) { event.getItemColors().register(ColorHandlers::getColor, LayeredArmoritems.LEATHERCHAINHELMET.get(), LayeredArmoritems.LEATHERCHAINCHESTPLATE.get(), LayeredArmoritems.LEATHERCHAINLEGGINGS.get(), LayeredArmoritems.LEATHERCHAINBOOTS.get()); } private static int getColor(ItemStack pStack, int tintIndex) { CompoundTag compoundtag = pStack.getTagElement("display"); if (tintIndex == 0) { return compoundtag != null && compoundtag.contains("color", 99) ? compoundtag.getInt("color") : 10511680; } return 0xFFFFFF; } } //end code do note that you have to add a listener should be same place you added a listener for the event bus. mine looks like. eventBus.addListener(ColorHandlers::registerItemColors);
  • Topics

×
×
  • Create New...

Important Information

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