The past three updates have been a slow battle on making the mod compatible with shaders. The only thing that changes is how the model is rendered, and I explain that in a post on the forums. If you really want to know the current state, just look at the OP. I update that each time I update the mod.
How is that going? From what i understand it's not something you can personally fix, as it's more of a bug from the way shaders works? Have you tried contacting the guys over at optifine about the issue (or who's responsible)? Any feedback ?
1.10.2 I also discovered the culprit: Mo' Bends. That is to blame for
the hands still remaining there but the shield? I have no clue. I don't
think I have any resource pack to modify them and even if i did, it
shouldn't be a problem...
Oddly enough, shaders never really clicked with me. My old lappy that I do 80% of my work on can barely handle 32x32 texture packs, much less shaders, so I never really got into them. I do have a beefy computer that can run anything I throw at it (except made-for-PC games, they tend to crash ), so I can run shaders, I just never got used to doing so. I do need to go take some pictures for another mod, so maybe it's time to get back into them. Couple those with Soartex or Chroma Hills and Minecraft doesn't even look like Minecraft anymore!
Anyhoo, you didn't post here to share shaders stories, you posted to ask for an update. I'm happy to say that version 8.0 is up on Curse now. I've removed the Shift+F1 shaders mode and instead changed up the body rendering to switch between 3D and 2D arms, and HUD/ no HUD. The latter modes work better with shaders, but the former modes are more realistic. Check the OP for an explanation of each mode if you're confused.
Thanks again for doing this! Downloading now! Can't wait to see my legs again
EDIT: well s**t, something somewhere isn't right, because the new mode only makes the weapon in my main hand disapear and nothing else. Here: http://imgur.com/a/l6yPD
You know, I never thought about doing it the other way! That would work incredibly well, as I could change the modes from shaders/no-shaders to 2D-arms/no-2D-arms. It'd give players a way to partially disable the mod, and it completely circumvents the shaders issue as I'm not trying to disable the 2D arms in the first place. Plus, having the arms would allow me to render the player and still have the arms out for maps and stuff, which would replace mode 3 on the F1 cycle.
You should expect a version with that functionality out by the end of the day.
Im glad to hear that i helped out ^.^ I loved this mod so much way back in the past when it first came out, and i've missed it ever since, but in the meantime shaders became a mainstream thing (i remember the time i had the water mod, which basically added a very rough and buggy reflection to the water surface ) and now i got so used to them i can't go back (or to be honest i don't really want to )
I just got an idea that may help users (like me) that want to use shaders. How about you disable the arms too ? If i understand correctly you already did that with the player head, and disabling the arms will fix the double arm problem, and still have the advantage of seeing your body when looking down and who nows, maybe it will be even better this way ! If you consider how other games that include the body do it, you often have hands rendered as separate things from the rest of the body (see Crysis for example, or L4D) It would be great if you could implement this !
My problem still persists, any idea what may be causing it ?
EDIT: FINALLY got it to work. No idea how to be honest, but it seems the latest removal of the .cfg and letting the mod remake it did the trick. I have tried this before and it didn't work, on multiple ocasions... Either way, glad to finally get it working
And are you planning on upating it any time soon ? At least to solve the recent problems with liteloader ? Don't wanna sound like i'm berating you, but i want to know if i need to find an alternative or not...
if this launcher dies i will stop playing minecraft...that is how much i hate the vanilla "launcher"
In all fairness, the vanilla launcher is not THAT bad, yes it lacks the nice ui and the social features that this one has, the biggest minus is the ability to enable/disable mods without having to move files around... Meanwhile i guess the default launcher will have to suffice.
This log message was added with new forge version (it was not logging it before). It will be fixed in next excore version.
And no, it's not due to breaking url path... It's due to something a bit more complex...
Well, now you got me curious, what caused it then ? I mentioned it as a potential error on your side because before coming here, when i was trying to find the culprit, I searched for the said error and it came up with a couple of pastebin's and posts from other users with similar errors in thier logs.
There's four different versions of that error in your log, all referencing a different imgur image. There's 2 of each.
Oh, right Either way, i meanwhile tested with just BF and Optifine installed and STILL no settings stick... i have no idea what else to do, i'm on latest forge build (beta because certain mods whined about the stable one being too old) and using Magic Launcher if that's of any importance...
I wasn't aware of that... But what changed? Clearly it worked in 1.9? Do you know of any other launcher with similar functionality (managing mods, java parameters)?
Not sure if this is on the liteloader side or the Magic Launcher's but im gonna post here anyway since on the ML forum there was no answer.
I recently updated to 1.10.2 Forge+Liteloader and when i try to run the game via Magic Launcher i get this error:
[20:12:45] [main/INFO]: Registering discovery module EnumeratorModuleClassPath: [<Java Class Path>]
[20:12:45] [main/INFO]: Registering discovery module EnumeratorModuleFolder: [C:\Users\Vlad\AppData\Roaming\.minecraft\mods]
[20:12:45] [main/INFO]: Registering discovery module EnumeratorModuleFolder: [C:\Users\Vlad\AppData\Roaming\.minecraft\mods\1.10.2]
[20:12:45] [main/INFO]: Registering enumerator plugin DefaultEnumeratorPlugin: [com.mumfrey.liteloader.core.api.DefaultEnumeratorPlugin@37191ef0]
[20:12:45] [main/INFO]: Discovering tweaks on class path...
[20:12:45] [main/INFO]: Baking listener list for EnumerationObserver with 1 listeners
[20:12:45] [main/INFO]: Discovering valid mod files in folder C:\Users\Vlad\AppData\Roaming\.minecraft\mods
[20:12:45] [main/INFO]: Discovering valid mod files in folder C:\Users\Vlad\AppData\Roaming\.minecraft\mods\1.10.2
[20:12:45] [main/INFO]: Initialising LiteLoader Mixins
[20:12:45] [main/INFO]: LiteLoader PREINIT complete
[20:12:45] [main/INFO]: Injecting required class transformer 'com.mumfrey.liteloader.transformers.event.EventProxyTransformer'
[20:12:45] [main/INFO]: Injecting required class transformer 'com.mumfrey.liteloader.launch.LiteLoaderTransformer'
[20:12:45] [main/INFO]: Injecting required class transformer 'com.mumfrey.liteloader.client.transformers.CrashReportTransformer'
[20:12:45] [main/INFO]: Queuing required class transformer 'com.mumfrey.liteloader.transformers.event.EventTransformer'
[20:12:45] [main/INFO]: Queuing required class transformer 'com.mumfrey.liteloader.common.transformers.LiteLoaderPacketTransformer'
[20:12:45] [main/INFO]: Queuing required class transformer 'com.mumfrey.liteloader.client.transformers.MinecraftTransformer'
[20:12:45] [main/INFO]: Queuing required class transformer 'com.mumfrey.liteloader.transformers.event.json.ModEventInjectionTransformer'
[20:12:45] [main/INFO]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLTweaker
[20:12:45] [main/INFO]: Forge Mod Loader version 12.18.1.2011 for Minecraft 1.10.2 loading
[20:12:45] [main/INFO]: Java is Java HotSpot(TM) 64-Bit Server VM, version 1.8.0_101, running on Windows 10:amd64:10.0, installed at C:\Program Files\Java\jre1.8.0_101
[20:12:45] [main/INFO]: Loading tweak class name org.spongepowered.asm.launch.MixinTweaker
[20:12:45] [main/INFO]: Loading tweak class name org.spongepowered.asm.mixin.MixinEnvironment$EnvironmentStateTweaker
[20:12:45] [main/INFO]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker
[20:12:45] [main/INFO]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLDeobfTweaker
[20:12:45] [main/INFO]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker
[20:12:45] [main/INFO]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker
[20:12:45] [main/INFO]: Calling tweak class org.spongepowered.asm.launch.MixinTweaker
[20:12:45] [main/INFO]: Initialised Mixin FML Remapper Adapter with net.minecraftforge.fml.common.asm.transformers.deobf.FMLDeobfuscatingRemapper@6240651f
[20:12:45] [main/INFO]: Calling tweak class org.spongepowered.asm.mixin.MixinEnvironment$EnvironmentStateTweaker
[20:12:45] [main/INFO]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper
[20:12:46] [main/ERROR]: Patcher expecting non-empty class data file for net.minecraft.entity.projectile.EntityThrowable, but received empty.
[20:12:46] [main/ERROR]: Unable to launch
java.lang.RuntimeException: java.lang.RuntimeException: Patcher expecting non-empty class data file for net.minecraft.entity.projectile.EntityThrowable, but received empty, your vanilla jar may be corrupt.
at net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper.injectIntoClassLoader(CoreModManager.java:168) ~[forge-1.10.2-12.18.1.2011.jar:?]
at net.minecraft.launchwrapper.Launch.launch(Launch.java:115) [launchwrapper-1.12.jar:?]
at net.minecraft.launchwrapper.Launch.main(Launch.java:28) [launchwrapper-1.12.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_101]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_101]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_101]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_101]
at magic.launcher.Launcher.main(SourceFile:214) [MagicLauncher.exe:?]
Caused by: java.lang.RuntimeException: Patcher expecting non-empty class data file for net.minecraft.entity.projectile.EntityThrowable, but received empty, your vanilla jar may be corrupt.
at net.minecraftforge.fml.common.patcher.ClassPatchManager.applyPatch(ClassPatchManager.java:114) ~[forge-1.10.2-12.18.1.2011.jar:?]
at net.minecraftforge.fml.common.patcher.ClassPatchManager.getPatchedResource(ClassPatchManager.java:77) ~[forge-1.10.2-12.18.1.2011.jar:?]
at net.minecraftforge.fml.common.asm.transformers.deobf.FMLDeobfuscatingRemapper.getFieldType(FMLDeobfuscatingRemapper.java:217) ~[forge-1.10.2-12.18.1.2011.jar:?]
at net.minecraftforge.fml.common.asm.transformers.deobf.FMLDeobfuscatingRemapper.parseField(FMLDeobfuscatingRemapper.java:191) ~[forge-1.10.2-12.18.1.2011.jar:?]
at net.minecraftforge.fml.common.asm.transformers.deobf.FMLDeobfuscatingRemapper.setup(FMLDeobfuscatingRemapper.java:160) ~[forge-1.10.2-12.18.1.2011.jar:?]
at net.minecraftforge.fml.common.asm.FMLSanityChecker.injectData(FMLSanityChecker.java:189) ~[forge-1.10.2-12.18.1.2011.jar:?]
at net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper.injectIntoClassLoader(CoreModManager.java:163) ~[forge-1.10.2-12.18.1.2011.jar:?]
... 7 more
[20:12:46] [main/INFO]: [magic.launcher.Launcher:main:226]: java.lang.reflect.InvocationTargetException
[20:12:46] [main/INFO]: [magic.launcher.Launcher:main:226]: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[20:12:46] [main/INFO]: [magic.launcher.Launcher:main:226]: at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
[20:12:46] [main/INFO]: [magic.launcher.Launcher:main:226]: at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
[20:12:46] [main/INFO]: [magic.launcher.Launcher:main:226]: at java.lang.reflect.Method.invoke(Unknown Source)
[20:12:46] [main/INFO]: [magic.launcher.Launcher:main:226]: at magic.launcher.Launcher.main(SourceFile:214)
[20:12:46] [main/INFO]: [java.lang.Throwable:printStackTrace:-1]: Caused by: net.minecraftforge.fml.relauncher.FMLSecurityManager$ExitTrappedException
[20:12:46] [main/INFO]: [java.lang.Throwable:printStackTrace:-1]: at net.minecraftforge.fml.relauncher.FMLSecurityManager.checkPermission(FMLSecurityManager.java:49)
[20:12:46] [main/INFO]: [java.lang.Throwable:printStackTrace:-1]: at java.lang.SecurityManager.checkExit(Unknown Source)
[20:12:46] [main/INFO]: [java.lang.Throwable:printStackTrace:-1]: at java.lang.Runtime.exit(Unknown Source)
[20:12:46] [main/INFO]: [java.lang.Throwable:printStackTrace:-1]: at java.lang.System.exit(Unknown Source)
[20:12:46] [main/INFO]: [java.lang.Throwable:printStackTrace:-1]: at net.minecraft.launchwrapper.Launch.launch(Launch.java:138)
[20:12:46] [main/INFO]: [java.lang.Throwable:printStackTrace:-1]: at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
[20:12:46] [main/INFO]: [java.lang.Throwable:printStackTrace:-1]: ... 5 more
Patcher expecting non-empty class data file for net.minecraft.entity.projectile.EntityThrowable, but received empty, your vanilla jar may be corrupt.
With the vanilla launcher on the other hand everything works perfectly. What is happening ?
Also in the setup tab The Minecraft.jar is marked as "not found".
I have to mention that on 1.9 with the same setup (forge+liteloader) it worked without any problems. Also forge or liteloader by themselves work perfectly, only when merged together i get this...
All I get from that log are these pictures, that were encrypted in the number of spaces, comma's and dots in the logs and the word "regrowableleaves", which was revealed to me by a medium to be your long lost great grandfather..
I already figured that part out, it was from excore framework/mod that i had installed (as i mentioned at the end of my message "aaand its from the excore mod. Ignore it. Filed a bug report to the author." Ill upload a new log with that error out of the wasy so as its not so cluttered, meanwhile i "fixed" the issue of settings not saving by editing the config files by hand. I'll have to test if my theory about the auto step up mod still stands from the previous game version; beccause if thats the one interfering with BF then i guess that guy has to do something about it...
As a side note, where did you get the last 3 images from ? the url points to the first one (the green "x" thing). I'm curious.
EDIT: scratch that, not even editing them by hand gets them to stick, it's like they are ignored completely, testing without the suspected mod now... nope, nothing, i have to start from scratch with just bf installed. Sigh, why can't those things ever have a simple solution...
Took forever to trace it to your mod, sheesh, either way, your excore thing is flooding with errors about a missing image due to you ****ing up the url path, here:
0
How is that going? From what i understand it's not something you can personally fix, as it's more of a bug from the way shaders works? Have you tried contacting the guys over at optifine about the issue (or who's responsible)? Any feedback ?
0
1.10.2 I also discovered the culprit: Mo' Bends. That is to blame for
the hands still remaining there but the shield? I have no clue. I don't
think I have any resource pack to modify them and even if i did, it
shouldn't be a problem...
0
Thanks again for doing this! Downloading now! Can't wait to see my legs again
EDIT: well s**t, something somewhere isn't right, because the new mode only makes the weapon in my main hand disapear and nothing else. Here: http://imgur.com/a/l6yPD
0
Im glad to hear that i helped out ^.^ I loved this mod so much way back in the past when it first came out, and i've missed it ever since, but in the meantime shaders became a mainstream thing (i remember the time i had the water mod, which basically added a very rough and buggy reflection to the water surface
) and now i got so used to them i can't go back (or to be honest i don't really want to 
)
1
I just got an idea that may help users (like me) that want to use shaders. How about you disable the arms too ? If i understand correctly you already did that with the player head, and disabling the arms will fix the double arm problem, and still have the advantage of seeing your body when looking down and who nows, maybe it will be even better this way ! If you consider how other games that include the body do it, you often have hands rendered as separate things from the rest of the body (see Crysis for example, or L4D) It would be great if you could implement this !
0
My problem still persists, any idea what may be causing it ?
EDIT: FINALLY got it to work. No idea how to be honest, but it seems the latest removal of the .cfg and letting the mod remake it did the trick. I have tried this before and it didn't work, on multiple ocasions... Either way, glad to finally get it working
0
And are you planning on upating it any time soon ? At least to solve the recent problems with liteloader ? Don't wanna sound like i'm berating you, but i want to know if i need to find an alternative or not...
0
In all fairness, the vanilla launcher is not THAT bad, yes it lacks the nice ui and the social features that this one has, the biggest minus is the ability to enable/disable mods without having to move files around... Meanwhile i guess the default launcher will have to suffice.
0
Well, now you got me curious, what caused it then ? I mentioned it as a potential error on your side because before coming here, when i was trying to find the culprit, I searched for the said error and it came up with a couple of pastebin's and posts from other users with similar errors in thier logs.
0
I have a feeling that Magic Launcher is dead...
0
Oh, right
0
I wasn't aware of that... But what changed? Clearly it worked in 1.9? Do you know of any other launcher with similar functionality (managing mods, java parameters)?
0
Not sure if this is on the liteloader side or the Magic Launcher's but im gonna post here anyway since on the ML forum there was no answer.
I recently updated to 1.10.2 Forge+Liteloader and when i try to run the game via Magic Launcher i get this error:
With the vanilla launcher on the other hand everything works perfectly. What is happening ?
Also in the setup tab The Minecraft.jar is marked as "not found".
I have to mention that on 1.9 with the same setup (forge+liteloader) it worked without any problems. Also forge or liteloader by themselves work perfectly, only when merged together i get this...
0
I already figured that part out, it was from excore framework/mod that i had installed (as i mentioned at the end of my message "aaand its from the excore mod. Ignore it. Filed a bug report to the author." Ill upload a new log with that error out of the wasy so as its not so cluttered, meanwhile i "fixed" the issue of settings not saving by editing the config files by hand. I'll have to test if my theory about the auto step up mod still stands from the previous game version; beccause if thats the one interfering with BF then i guess that guy has to do something about it...
As a side note, where did you get the last 3 images from ? the url points to the first one (the green "x" thing). I'm curious.
EDIT: scratch that, not even editing them by hand gets them to stick, it's like they are ignored completely, testing without the suspected mod now... nope, nothing, i have to start from scratch with just bf installed. Sigh, why can't those things ever have a simple solution...
0
Took forever to trace it to your mod, sheesh, either way, your excore thing is flooding with errors about a missing image due to you ****ing up the url path, here: