StitcherException crash

[jdsi1]

Crashing using SevTech all versions

• Mysterious Bug that just showed up after playing 12 hours of the pack

• 

[artdude543]

Can you pastebin your client log please!

[jdsi1]

My client wont let me view my crash report....

[justinrusso]

@artdude543 I've run into this a lot during development but no one else has mentioned it ever.

Here is one of the crashes: https://gist.github.com/justinrusso/e67f02ec1a18a4af370d0b3f21f204ca

Theres are all texture stitching exceptions:

[jdsi1]

Alright I don't know what any of that means so I will just wait for a solution

[kragnoth]

Could this be due to the fact that you are using the native launcher, which is using a massively outdated minecraft version? IE seems to have quite a few bugs if you are using java 8 25. Maybe try running with the jar launcher by going into twitch settings and changing to jar launcher, and loading latest version.

Just a suggestion, but that looks GUI related on the arc furnace, and alot of the GUI issues are due to the version of java that mojang uses in their sandboxed native launcher.

[wyndman]

Your client is having issues rendering block from the chisel mod, if you're using a texture pack try loading it without one. Justinrusso is having similar issues from the looks of it, the IE stuff has had odd texture crashes since 1.10, best to report it to the IE author as well. You might be able to MCedit out the block if it continues to crash you.

[jdsi1]

I was able to fix this issue because I was not using my dedicated graphics card. But I am now getting this issue -

[justinrusso]

@wyndman this isnt just IE though. theres many mods that do it, and is unrelated to one specific mod. IT eventually bogs down and I need to restart, its been the only "fix".

[deanec64]

this happens on both Native and Jar versions of minecraft. with No texture pack installed and latest Java.

[WildFTW]

Try allocate more ram to the pack. But this issue has been around for years, I've seen reports of this being an issue all the way back to 2013, with people saying it could be optifine version not being compatible with forge versions to the computer not being able to run 64bit java. To turning the max memory setting for 32bit to 1500M. To be honest this issue seems to be nearly impossible to fix no one has seem to have found a way to fix this. I hope this helps.

[cjm721]

This issue stems from having to many mods that all load textures. Most textures have to be loaded into a single texture map (for performance reasons). During pack load is when the entire texture map is loaded. The max size of this texture map is determined by your graphics hardware . This is why switching from your CPU graphics to the dedicated fixed it as the dedicated one has a larger max texture size.

There are some possible solutions for this issue for others that run into it:

• Use a lower resolution texture pack (You can find texture packs with lower resolution then the vanilla one)
• Overloaded has high res dynamic textures that you can limit the size of. In Overloaded config turn down:
  • maxTextureWidth This one controls the compressed blocks max texture size, it will have the most impact.
  • blockResolution This one effects all the standard blocks in the mod
  • multiArmorResolution This one effects the armor / multi tool

There are other mods that use lots of the texture map but Overloaded you can change how much you allow it to use just by changing those config values.

Your horsepower crash is unrelated to the first.

[Jandakast]

This is NOT a pack specific issue. The issue is actually related to the number of textures in the pack and the amount of GPU RAM that is needed to load/handle the textures. Texture Stitching crashes are generally related to running out of RAM for GPU functions, and is separate from the ram you dedicate to Java/Minecraft. Some things to try.

• If you have a dedicated GPU make sure that java is using the Dedicated GPU and not the integrated GPU
• Try using a lower resolution texture pack or no texture pack at all
• Although very rare, it could also be related to a corrupt texture file. If it is this, then it could be resolved by downloading a fresh instance of the pack and moving your save to it

If the Horsepower crash is not a net.minecraft.client.renderer.StitcherException we will need a crash log and it needs to be opened as a new issue to be properly tracked. Thank you

[cjm721]

GPU ram is 99% not going to be the issue. Minecraft only has one texture map which is only a few MB in size. What I posted (and included link) shows exactly what the limits are per GPU. For two clients using default textures the map will be the same so can easily determine what GPU will work on standard settings.

[justinrusso]

Interesting... why would it be that it just suddenly happens after many game restarts?

In addition, when I close out of my browser, it begins to load past that point again for a while, then refuses to work again until my pc is restarted.

Ive been pack deving like this for months... rinse and repeat the process

[cjm721]

The original issue was about 100% crash on load.

If you are having a similar issue intermittently it is most likely a compounding of several causes. Especially since you mentioned closing other programs had an effect.

Also @justinrusso , your GPU has a max size of 16384x16384 which is much larger then the majority of players.