Optifine problems should be posted on the Optifine page.
If you are using Optifine & MCPatcher together, then you will have problems as they are incompatible with each other.
I'm using only Optifine. Sorry for posting here as I made the assumption ctm is the same for both Optifine and Mcpatcher. I've narrowed the problem down to creating metablocks for Quartz blocks with a metadata of above 4. Should this be working or has something changed in ctm that I'm not aware of.
Rollback Post to RevisionRollBack
~------* =There use to be something here...=*------~
Quick question: does the "Random Mobs" mechanic support NBT tags?
Would be great for boss mobs, as all it would take is a custom name in order for the mob to use a different texture.
Not yet. It's probably the most requested feature standing, and I'm fairly sure that Kahr has said that he'd work on it after all of the update craziness settles down.
I upaded my world to the new mcpatcher and received the following error message:
---- Minecraft Crash Report ----
Time: 3/24/14 8:18 AM
Description: Tesselating block in world
java.lang.NullPointerException: Tesselating block in world
at com.prupe.mcpatcher.mal.biome.BiomeAPI$V3.getBiomeGenAt_Impl(BiomeAPI.java:229)
at com.prupe.mcpatcher.mal.biome.BiomeAPI.getBiomeGenAt(BiomeAPI.java:104)
at com.prupe.mcpatcher.mal.biome.BiomeAPI.getBiomeIDAt(BiomeAPI.java:96)
at com.prupe.mcpatcher.ctm.TileOverride.getTileWorld(TileOverride.java:467)
at com.prupe.mcpatcher.ctm.TileOverrideIterator$IJK.getTile(TileOverrideIterator.java:138)
at com.prupe.mcpatcher.ctm.TileOverrideIterator.go(TileOverrideIterator.java:111)
at com.prupe.mcpatcher.ctm.CTMUtils.getBlockIcon(CTMUtils.java:106)
at btf.a(SourceFile:1008)
at btf.a(SourceFile:750)
at btf.b(SourceFile:357)
at btf.a(SourceFile:221)
at bsw.b(SourceFile:922)
at brx.a(SourceFile:163)
at bsj.a(SourceFile:1437)
at bsc.a(SourceFile:1097)
at bsc.b(SourceFile:937)
at beo.ai(SourceFile:828)
at beo.f(SourceFile:755)
at net.minecraft.client.main.Main.main(SourceFile:121)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at com.prupe.mcpatcher.mal.biome.BiomeAPI$V3.getBiomeGenAt_Impl(BiomeAPI.java:229)
at com.prupe.mcpatcher.mal.biome.BiomeAPI.getBiomeGenAt(BiomeAPI.java:104)
at com.prupe.mcpatcher.mal.biome.BiomeAPI.getBiomeIDAt(BiomeAPI.java:96)
at com.prupe.mcpatcher.ctm.TileOverride.getTileWorld(TileOverride.java:467)
at com.prupe.mcpatcher.ctm.TileOverrideIterator$IJK.getTile(TileOverrideIterator.java:138)
at com.prupe.mcpatcher.ctm.TileOverrideIterator.go(TileOverrideIterator.java:111)
at com.prupe.mcpatcher.ctm.CTMUtils.getBlockIcon(CTMUtils.java:106)
at btf.a(SourceFile:1008)
at btf.a(SourceFile:750)
at btf.b(SourceFile:357)
at btf.a(SourceFile:221)
-- Block being tesselated --
Details:
Block type: ID #7 (tile.bedrock // amh)
Block data value: 0 / 0x0 / 0b0000
Block location: World: (18896,0,24256), Chunk: (at 0,0,0 in 1181,1516; contains blocks 18896,0,24256 to 18911,255,24271), Region: (36,47; contains chunks 1152,1504 to 1183,1535, blocks 18432,0,24064 to 18943,255,24575)
Stacktrace:
at bsw.b(SourceFile:922)
at brx.a(SourceFile:163)
-- Chunk being rebuilt --
Details:
Renderchunk location: 18896, 0, 24256
Stacktrace:
at bsj.a(SourceFile:1437)
at bsc.a(SourceFile:1097)
-- System Details --
Details:
Minecraft Version: 14w10c
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.7.0_51, Oracle Corporation
Java VM Version: Java HotSpot™ 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 618948880 bytes (590 MB) / 967311360 bytes (922 MB) up to 5726797824 bytes (5461 MB)
JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx6G
IntCache: cache: 0, tcache: 0, allocated: 13, tallocated: 95
Launched Version: 14w10c-mcpatcher
LWJGL: 2.9.1
OpenGL: GeForce GTX 580/PCIe/SSE2 GL version 4.4.0, NVIDIA Corporation
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Anisotropic filtering is supported and maximum anisotropy is 16.
Shaders are available because OpenGL 2.1 is supported.
Is Modded: Very likely; Jar signature invalidated
Type: Client (map_client.txt)
Resource Packs: [Soartex_Fanver.zip]
Current Language: English (US)
Profiler Position: N/A (disabled)
Anisotropic Filtering: Off (1)
Any help would be appreciated. Thanks.
I posted this on March 24 and have not received any replies. What is a Tesselating block? Does anyone else have this error message? I would appreciate any help as I have no clue??
I'm using only Optifine. Sorry for posting here as I made the assumption ctm is the same for both Optifine and Mcpatcher. I've narrowed the problem down to creating metablocks for Quartz blocks with a metadata of above 4. Should this be working or has something changed in ctm that I'm not aware of.
Optifine's CTM & MCPatcher's CTM act differently. How differently they act, I don't truly know because I don't use Optifine anymore. But SOME of the major features(somewhat) are the same. But back to your problem:
No, creating .properties files for Quartz blocks with a metadata above 4 SHOULD work. If you can post your .properties file, we might be able to help you more.
Quick question: does the "Random Mobs" mechanic support NBT tags?
Would be great for boss mobs, as all it would take is a custom name in order for the mob to use a different texture.
Not yet. It's probably the most requested feature standing, and I'm fairly sure that Kahr has said that he'd work on it after all of the update craziness settles down.
Please be patient.
If I'm correct, Kahr has mention once about possibly adding NBT data support for Random Mobs. But like Alvoria has said, he (Kahr) might work on it after all the Minecraft code changes settles down.
I posted this on March 24 and have not received any replies. What is a Tesselating block? Does anyone else have this error message? I would appreciate any help as I have no clue??
I would love to help you, but I don't know how as I never got the message nor can I understand the crash message.(I almost never understand crash messages).
I posted this on March 24 and have not received any replies. What is a Tesselating block? Does anyone else have this error message? I would appreciate any help as I have no clue??
BUT what I can make out is that something with the MCPatcher's Biome Feature (aka BiomeAPI) & the CTM feature. The block being "tesselated" is a Bedrock block. So I ASSUME (but don't know for sure) that the crash was caused by a Bedrock block. I looked to see if the resource pack "Soartex Fanver" caused it, but there isn't anything that involves CTM or any of the Biome features that apply to Bedrock. Did you use any other resource pack besides "Soartex Fanver"?
Oh & Tessellation:
In computer graphics, the term "tessellation" is used to describe the organization of information needed to render to give the appearance of the surfaces of realistic three-dimensional objects.
BUT what I can make out is that something with the MCPatcher's Biome Feature (aka BiomeAPI) & the CTM feature. The block being "tesselated" is a Bedrock block. So I ASSUME (but don't know for sure) that the crash was caused by a Bedrock block. I looked to see if the resource pack "Soartex Fanver" caused it, but there isn't anything that involves CTM or any of the Biome features that apply to Bedrock. Did you use any other resource pack besides "Soartex Fanver"?
Oh & Tessellation: Provide via Wikipedia: Page Here
Thanks for the reply. The same error occurred with 4.3.2_02. I do not get the error message with Misa's pack. I posted the message on the Soartex forum and received the following explanation:
"Oftentimes this snapshot support is buggy- in this case MCPatcher seems to attempt to retrieve the current biome in order to implement biome specific CTM, and fails. This may only occur with Soartex because other packs are not using this feature."
I am flummoxed what this means, only it does not work. Would waiting for 1.8 make it any better?
Thanks for the reply. The same error occurred with 4.3.2_02. I do not get the error message with Misa's pack. I posted the message on the Soartex forum and received the following explanation:
"Oftentimes this snapshot support is buggy- in this case MCPatcher seems to attempt to retrieve the current biome in order to implement biome specific CTM, and fails. This may only occur with Soartex because other packs are not using this feature."
I am flummoxed what this means, only it does not work. Would waiting for 1.8 make it any better?
It's saying basically that MCPatcher is failing at applying Biome CTM features & is creating the crash.
It applies the textures tiles to the where the 2 torches (on the back of the comparator) are at. It also doesn't update the textures when it changes from unpowered to powered & vice versa. But the base texture (the one I was trying to change) does work as intended & the front torch on the comparator isn't affected.
Also with the Horizontal rule & Vertical rule CTM the texture is applyed to the top layer & bottom layer(the tops & bottoms of the blocks). Which it shouldn't do.
For instance, before I had my bookshelf.properties file look like this.
tiles=0-3
connect=tile
#the connect rule doesn't matter, it's just how I had it in my .properties file
metadata=0
#metadata doesn't matter either, it's just how I had it in my .properties file
method=Vertical
matchTiles=sandstone_normal
#minecraft:sandstone
If it means anything, the Horizontal Rule is applied to the top & bottom layers & connects it going east & west, while the Vertical Rule is applied to the top & bottom layers & connects it going North & South.
Also I think Biome-based or the matchTiles rules are acting weird, because my beacon textures(the center part of the beacons) & my fire won't work with I go into the Nether (beacon won't work in the Sky biome either), were their textures are suppose to change, but my Nether Portal textures are working though. I don't know why.
Here is my codes for my fire:
(Yes, I know "matchBlocks=" is suppose to be "matchBlocks=" but I left it, because MCPatcher should use that line, because it doesn't recognize that rule).
Here is my codes for my beacon:
/ctm/beacon/beacon.properties
matchTiles=beacon
method=fixed
faces=all
tiles=2
#minecraft:beacon
(now this file isnt used because I commented all the lines making MCPatcher use the beacon texture from /minecraft/texture/block/beacon.png)
/ctm/beacon/beaconHell
matchTiles=beacon
method=random
faces=all
symmetry=all
tiles=1 4
biomes=Hell
#minecraft:beacon
/ctm/beacon/beaconSky.properties
matchTiles=beacon
method=fixed
symmetry=all
faces=all
tiles=5
biomes=Sky
#minecraft:beacon
Here is my codes for my Nether Portals:
/ctm/Portal/block90.properties
method=fixed
biomes=Hell
tiles=netherportal
matchTiles=portal
#matchTiles isn't really needed as the block90 is the .properties file name, so without the matchTiles rule specified, MCPatcher will automatically use it for any block with an ID of 90, which is a Nether Portal block
#minecraft:portal
/ctm/Portal/block90a.properties
method=fixed
tiles=overworldportal
#minecraft:portal
Still applies with 4.3.2_02
Also my Mobspawners work fine too though(oddly enough).
Mobspawner codes:
Optifine's CTM & MCPatcher's CTM act differently. How differently they act, I don't truly know because I don't use Optifine anymore. But SOME of the major features(somewhat) are the same. But back to your problem:
No, creating .properties files for Quartz blocks with a metadata above 4 SHOULD work. If you can post your .properties file, we might be able to help you more.
Thankyou for replying.
Here's the .properties file:
A Random-Method CTM could (theoretically) still work with just one texture tile, but I don't know if it does or not (I haven't tested it). Using a Fixed-Method CTM work just like Random, but with only one tile. Try changing the method to Fixed & see if you still have the same problem.
A Random-Method CTM could (theoretically) still work with just one texture tile, but I don't know if it does or not (I haven't tested it). Using a Fixed-Method CTM work just like Random, but with only one tile. Try changing the method to Fixed & see if you still have the same problem.
I tried changing it to fixed before, but tried it again for reassurance and there's still no different result
Rollback Post to RevisionRollBack
~------* =There use to be something here...=*------~
Odd. It might just be Optifine. I don't know for sure.
Al right. So I started up Mcpatcher, and can now confirm this problem is exclusive only to Optifine.
I'll leave a reply on the Optifine post to make this problem known.
Sorry for any inconvenience and thanks
Rollback Post to RevisionRollBack
~------* =There use to be something here...=*------~
Al right. So I started up Mcpatcher, and can now confirm this problem is exclusive only to Optifine.
I'll leave a reply on the Optifine post to make this problem known.
Sorry for any inconvenience and thanks
Thanks for update, but i must say... those vertical CTM's still not working :(.
The John Smith Legacy 1.7.5 v1.2.14 vertical CTM for Cactus and Reeds both now work in the latest release (mcpatcher-4.3.2_02 and Minecraft 14w11b), maybe check your properties files.
Is anyone else having a problem with version 4.3.2_02 (latest version) not recognizing the pre-release 1.7.6 that just came out?
Log:
MCPatcher version is 4.3.2_02
OS: Windows 8 6.2 x86
JVM: Oracle Corporation 1.7.0_51 (32 bit)
Classpath: C:\Users\gabel_000\Desktop\Minecraft\mcpatcher-4.3.2_02.exe
Fetching https://s3.amazonaws...ersions.json...
java.io.IOException: No installed unmodded versions found
at com.prupe.mcpatcher.ProfileManager.rebuildLocalVersionList(ProfileManager.java:138)
at com.prupe.mcpatcher.ProfileManager.refresh(ProfileManager.java:65)
at com.prupe.mcpatcher.MainForm$18.runImpl(MainForm.java:576)
at com.prupe.mcpatcher.MainForm$UIWorker.run(MainForm.java:1066)
Is anyone else having a problem with version 4.3.2_02 (latest version) not recognizing the pre-release 1.7.6 that just came out?
Log:
MCPatcher version is 4.3.2_02
OS: Windows 8 6.2 x86
JVM: Oracle Corporation 1.7.0_51 (32 bit)
Classpath: C:\Users\gabel_000\Desktop\Minecraft\mcpatcher-4.3.2_02.exe
Fetching https://s3.amazonaws...ersions.json...
java.io.IOException: No installed unmodded versions found
at com.prupe.mcpatcher.ProfileManager.rebuildLocalVersionList(ProfileManager.java:138)
at com.prupe.mcpatcher.ProfileManager.refresh(ProfileManager.java:65)
at com.prupe.mcpatcher.MainForm$18.runImpl(MainForm.java:576)
at com.prupe.mcpatcher.MainForm$UIWorker.run(MainForm.java:1066)
Possibly because either the patcher doesn't support that version yet, or it's getting confused by the name "1.7.6-pre1"
I've found something odd today, the sides of grass blocks are a strange green colour. It's on all of my packs and cant be a Minecraft bug (I'm playing in 1.7.5) so I've deduced its a mcpatcher problem. But i cant seem to find what. I was gunna add a pic but i cant work it out.
Does it happen when you are playing only with MCPatcher(&no other mods installed)?
Does it happen when you are using just the Vanilla textures(you have no resource pack installed)?
I've found something odd today, the sides of grass blocks are a strange green colour. It's on all of my packs and cant be a Minecraft bug (I'm playing in 1.7.5) so I've deduced its a mcpatcher problem. But i cant seem to find what. I was gunna add a pic but i cant work it out.
If I may also ask, did you turn on Better Grass when you patched the game?
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I'm using only Optifine. Sorry for posting here as I made the assumption ctm is the same for both Optifine and Mcpatcher. I've narrowed the problem down to creating metablocks for Quartz blocks with a metadata of above 4. Should this be working or has something changed in ctm that I'm not aware of.
-
View User Profile
-
View Posts
-
Send Message
ModeratorPlease be patient.
I posted this on March 24 and have not received any replies. What is a Tesselating block? Does anyone else have this error message? I would appreciate any help as I have no clue??
Optifine's CTM & MCPatcher's CTM act differently. How differently they act, I don't truly know because I don't use Optifine anymore. But SOME of the major features(somewhat) are the same. But back to your problem:
No, creating .properties files for Quartz blocks with a metadata above 4 SHOULD work. If you can post your .properties file, we might be able to help you more.
If I'm correct, Kahr has mention once about possibly adding NBT data support for Random Mobs. But like Alvoria has said, he (Kahr) might work on it after all the Minecraft code changes settles down.
I would love to help you, but I don't know how as I never got the message nor can I understand the crash message.(I almost never understand crash messages).
BUT what I can make out is that something with the MCPatcher's Biome Feature (aka BiomeAPI) & the CTM feature. The block being "tesselated" is a Bedrock block. So I ASSUME (but don't know for sure) that the crash was caused by a Bedrock block. I looked to see if the resource pack "Soartex Fanver" caused it, but there isn't anything that involves CTM or any of the Biome features that apply to Bedrock. Did you use any other resource pack besides "Soartex Fanver"?
Oh & Tessellation: Provide via Wikipedia: Page Here
Thanks for the reply. The same error occurred with 4.3.2_02. I do not get the error message with Misa's pack. I posted the message on the Soartex forum and received the following explanation:
"Oftentimes this snapshot support is buggy- in this case MCPatcher seems to attempt to retrieve the current biome in order to implement biome specific CTM, and fails. This may only occur with Soartex because other packs are not using this feature."
I am flummoxed what this means, only it does not work. Would waiting for 1.8 make it any better?
It's saying basically that MCPatcher is failing at applying Biome CTM features & is creating the crash.
Still applies with 4.3.2_02
Also my Mobspawners work fine too though(oddly enough).
Mobspawner codes:
Note: NormalSpawner.png is a 16x240 animation texture with a NormalSpawner.png.mcmeta file saying this:
{ "animation": { "frames": [ { "index": 0, "time": 2 }, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, { "index": 14, "time": 4 }, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1 ] } }Thankyou for replying.
Here's the .properties file:
block155.properties
tiles=190
metadata=5
method=random
If you want to apply 1 texture tile to a block, you can just do this instead:
A Random-Method CTM could (theoretically) still work with just one texture tile, but I don't know if it does or not (I haven't tested it). Using a Fixed-Method CTM work just like Random, but with only one tile. Try changing the method to Fixed & see if you still have the same problem.
I tried changing it to fixed before, but tried it again for reassurance and there's still no different result
Odd. It might just be Optifine. I don't know for sure.
Al right. So I started up Mcpatcher, and can now confirm this problem is exclusive only to Optifine.
I'll leave a reply on the Optifine post to make this problem known.
Sorry for any inconvenience and thanks
No problem, we are here to help.
The John Smith Legacy 1.7.5 v1.2.14 vertical CTM for Cactus and Reeds both now work in the latest release (mcpatcher-4.3.2_02 and Minecraft 14w11b), maybe check your properties files.
http://www.johnsmithlegacy.co.uk/ - John Smith Legacy for Java Minecraft
Log:
Possibly because either the patcher doesn't support that version yet, or it's getting confused by the name "1.7.6-pre1"
Putting the CENDENT back in transcendent!
Does it happen when you are playing only with MCPatcher(&no other mods installed)?
Does it happen when you are using just the Vanilla textures(you have no resource pack installed)?
If I may also ask, did you turn on Better Grass when you patched the game?