[urgent] default textures crashing game

  • Please make sure you are posting in the correct place. Server ads go here and modpack bugs go here
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

jordsta95

New Member
Jul 29, 2019
5,056
-4
1
The OpenMods issue, I THINK is a little thing in the config which you may want to change.
If you look in OpenBlocks' config there should be something that says "we are serious people" or something like that. If that is set to false, or anything around it give the impression that you are not a serious person, what happens is your character will randomly shit a brick.... and that can cause issues with the game, I know it happened to me a few times.
As for the second crashlog, your texture pack doesn't work with Thaumcraft's Warded Glass (a glass block you have warded) and it therefore threw it's hand up and screamed :p
 

mattp_12

New Member
Jul 29, 2019
901
-3
0
The OpenMods issue, I THINK is a little thing in the config which you may want to change.
If you look in OpenBlocks' config there should be something that says "we are serious people" or something like that. If that is set to false, or anything around it give the impression that you are not a serious person, what happens is your character will randomly shit a brick.... and that can cause issues with the game, I know it happened to me a few times.
As for the second crashlog, your texture pack doesn't work with Thaumcraft's Warded Glass (a glass block you have warded) and it therefore threw it's hand up and screamed :p
Ok I set the thing to false and took off my resource pack... Let's see
 

jordsta95

New Member
Jul 29, 2019
5,056
-4
1
Ok I set the thing to false and took off my resource pack... Let's see
You set it to false o_O

You "Tomfoolery" should be like this to avoid the 'bricking your pants' feature:
tomfoolery {
# You know, THAT thing! That you shouldn't do in public!
B:doItWhileTyping=false

# Blacklist for effects used by flim-flam enchantment
S:flimFlamBlacklist <
>

# Allow only flimflams that don't cause death (or at least very rarely)
B:safeOnly=false

# Are you serious too?
B:weAreSeriousPeople=true
}

If you get a different crash report from OpenBlocks, then obviously link it.
But don't post until you have these settings too, as these are the least buggy (IMO)
 

mattp_12

New Member
Jul 29, 2019
901
-3
0
You set it to false o_O

You "Tomfoolery" should be like this to avoid the 'bricking your pants' feature:
tomfoolery {
# You know, THAT thing! That you shouldn't do in public!
B:doItWhileTyping=false

# Blacklist for effects used by flim-flam enchantment
S:flimFlamBlacklist <
>

# Allow only flimflams that don't cause death (or at least very rarely)
B:safeOnly=false

# Are you serious too?
B:weAreSeriousPeople=true
}

If you get a different crash report from OpenBlocks, then obviously link it.
But don't post until you have these settings too, as these are the least buggy (IMO)
I have crashed again: http://pastebin.com/kGp8upzm I have changed the config to what you had in your previous message.
 

jordsta95

New Member
Jul 29, 2019
5,056
-4
1
Now that one is interesting... it doesn't like your chisel blocks.
Just spawn a new world, a superflat world, and see if you get the same issue. If not, then what it is, is chisel is playing up (assuming you have chisel blocks in the world you are loading)
"Chisel:templemossy/stand-mosaic-top - size: 16x16 - Maybe try a lowerresolution resourcepack?"
In English:
Mossy brick (I think) that has been used with chisel to make it a "temple mossy brick" at the top of a mosaic (not sure how chisel works, I don't usually use it) is having issues loading using the resource pack you are using... Which is default, so chisel is being a PITA :p
 

mattp_12

New Member
Jul 29, 2019
901
-3
0
Now that one is interesting... it doesn't like your chisel blocks.
Just spawn a new world, a superflat world, and see if you get the same issue. If not, then what it is, is chisel is playing up (assuming you have chisel blocks in the world you are loading)
"Chisel:templemossy/stand-mosaic-top - size: 16x16 - Maybe try a lowerresolution resourcepack?"
In English:
Mossy brick (I think) that has been used with chisel to make it a "temple mossy brick" at the top of a mosaic (not sure how chisel works, I don't usually use it) is having issues loading using the resource pack you are using... Which is default, so chisel is being a PITA :p
I'll try taking it out and playing. Im not the best with building anyway ;D[DOUBLEPOST=1410991047][/DOUBLEPOST]Also, I cant even spawn in a world. The game crashes after about 15 seconds of loading
 

jordsta95

New Member
Jul 29, 2019
5,056
-4
1
Ok, so I think it's safe to say your game is just spewing out "texture error" for everything.
What mods do you have installed?
Also, what RAM, and PermGen are you giving Minecraft? And are you using the vanilla launcher, FTB launcher, or...?
 

mattp_12

New Member
Jul 29, 2019
901
-3
0
In the meantime, ill go download fresh copies of EU and chisel[DOUBLEPOST=1410991567][/DOUBLEPOST]
Ok, so I think it's safe to say your game is just spewing out "texture error" for everything.
What mods do you have installed?
Also, what RAM, and PermGen are you giving Minecraft? And are you using the vanilla launcher, FTB launcher, or...?
Im using vanilla. Im givig MC 3gigs. Couldnt you see the mods in the crash report?
 

jordsta95

New Member
Jul 29, 2019
5,056
-4
1
Yeah, just I tend to like reading them in a list, as a crashlog is annoying to read. But I looked through, I didn't see any mods that I would have thought caused it, I have never used battlegear or mine and blade though, so I don't know what they are like.
But your java parameters may be causing the crashes:
-Xmx4G -XX:MaxPermSize=256m
Is how I have mine you have yours as:
-XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx4G -XX:permSize=512m
according to the crash report
 

mattp_12

New Member
Jul 29, 2019
901
-3
0
Yeah, just I tend to like reading them in a list, as a crashlog is annoying to read. But I looked through, I didn't see any mods that I would have thought caused it, I have never used battlegear or mine and blade though, so I don't know what they are like.
But your java parameters may be causing the crashes:
-Xmx4G -XX:MaxPermSize=256m
Is how I have mine you have yours as:
-XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx4G -XX:permSize=512m
according to the crash report
So what should I change my parameters to?
 

jordsta95

New Member
Jul 29, 2019
5,056
-4
1
-Xmx4G -XX:MaxPermSize=256m
^
Just Copy+paste that into JVM arguments section under the "edit profile" bit of the vanilla launcher
 

jordsta95

New Member
Jul 29, 2019
5,056
-4
1
Well, unless your crashlog is lying to me here are the other potential issues:
Java, get updating that shizz, it seems a hella lot outdated.
RAM, you only have 3.5 gigs o_O Lower the RAM requirements to 2GB
-Xmx2G -XX:MaxPermSize=256m

Other than that, I wouldn't be able to tell...
 

jordsta95

New Member
Jul 29, 2019
5,056
-4
1
Well do you have any mods that are 1.7.2, not 1.7.10? If so, you should check they work with 1.7.10