Please sp614x answer this
Why you didn't plan some kind of patcher?(which is a little bit different from installer)
A patcher like "copy files to minecraft.jar" is planned and may be released soon.
A patcher like "merge differences between mod and vanilla classes" may be problematic for OptiFine, because it makes a lot of changes.
A patcher like "copy files to minecraft.jar" is planned and may be released soon.
A patcher like "merge differences between mod and vanilla classes" may be problematic for OptiFine, because it makes a lot of changes.
Minecraft has stopped running because it encountered a problem.
If you wish to report this, please copy this entire text and email it to [email protected].
Please include a description of what you did when the error occured.
--- BEGIN ERROR REPORT b6885038 --------
Generated 14.12.11 11:18
Minecraft: Minecraft Beta 1.8.1
OS: Windows XP (x86) version 5.1
Java: 1.6.0_27, Sun Microsystems Inc.
VM: Java HotSpot(TM) Client VM (mixed mode), Sun Microsystems Inc.
LWJGL: 2.4.2
OpenGL: GeForce 7025 / nForce 630a/PCI/SSE2/3DNOW! version 2.1.2, NVIDIA Corporation
NotImplementedException
at WorldWithLayers.c(WorldWithLayers.java:309)
at cv.<init>(SourceFile:28)
at bv.updateRenderer(WorldRenderer.java:130)
at bv.a(WorldRenderer.java:90)
at i.a(RenderGlobal.java:1382)
at iw.a(EntityRenderer.java:997)
at iw.b(EntityRenderer.java:812)
at EntityRendererProxy.b(EntityRendererProxy.java:15)
at net.minecraft.client.Minecraft.run(Minecraft.java:522)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT b711a977 ----------
Additionally I have MC Forge 1.1.2
Install Optifine after installing Modloader, and then add all the other mods.
A patcher like "copy files to minecraft.jar" is planned and may be released soon.
A patcher like "merge differences between mod and vanilla classes" may be problematic for OptiFine, because it makes a lot of changes.
As of now, I use MCPatcher to install all my mods. I just uncheck the HD stuff, bettergrass and randommobs and add all the mods I want.
Would be great if you made a patcher for OptiFine that has this feature to add mods to it. :smile.gif:
It just renders snow for some blocks (fence, tall grass, mushroom, etc) when the surrounding blocks also have snow on top. The snow is not existing, it can not be collected with shovel, etc. But it looks nice.
It just renders snow for some blocks (fence, tall grass, mushroom, etc) when the surrounding blocks also have snow on top. The snow is not existing, it can not be collected with shovel, etc. But it looks nice.
Must the snow be covering all 4 sides of a none-snow block?
How does the none-snow block look like? The regular snow blocks is just grass with a snow-layer on top, does that snow-layer appear on the none-snow block?
Must the snow be covering all 4 sides of a none-snow block?
How does the none-snow block look like? The regular snow blocks is just grass with a snow-layer on top, does that snow-layer appear on the none-snow block?
One side is enough, otherwise fences and several flowers together will not show the snow.
Only the snow layer is shown, the block below is not affected.
I'm loving that fences/snow feature. It makes the game look as it really ought.
On a related note, would it be possible to allow bettergrass without snow-sided blocks? With grass, you can safely assume that any block that looks like grass is dirt, but when you do the same with snow it becomes impossible to distinguish a snow block from one that is simply covered in snow.
One side is enough, otherwise fences and several flowers together will not show the snow.
Only the snow layer is shown, the block below is not affected.
What happens if you make a path in the snow? Like a 2 block wide path, will that be grass or appear to be snow?
Last time I tried, patcher works fine with optifine.
Love this mod. It is a godsend. Thanks for continuing to support it.
It does work, But I would like sp614x making one that also could merge files together and stuff like that. Can be a bit unessesary though cause there is MCPatcher already :smile.gif:
If you disable fire animations, fire doesn't look like fire but looks like a texture missing problem.
Can this be ameneded?
Non animated Fire can just be 1st frame of Fire animation IMO.
I don't believe that "Plus" versus "Extended" would really make any difference. People would still incorrectly see "Extended" as needing to be added to the "Basic" Edition. Either way is fine for me but "Plus" is shorter and (to me, at least) kind of illustrates better that it has all the features of the basic edition "plus" (as would be listed in the description anyhow) the added benefit of FPS smoothing rather than extending a list of features.
OptiFine 1.0.0 BASIC B2
Includes built-in support for HD Textures, HD Fonts, and Better Grass!
MCPatcher NOT Needed!
Adds MANY features to improve the Performance, Look, and Functionality of Minecraft!
OptiFine 1.0.0 PLUS B2
All the features of the Basic Edition plus FPS Smoothing to reduce lag spikes!
OptiFine 1.0.0 PLUS B2 WITH MULTI-THREADING
All the features of the Plus Edition but also uses the second core on multi-core processors for even better performance!
On a Single-Core Processor: FPS much smoother, no more stuttering and freezes.
On a Multi-Core Processor: 3x faster world loading, which also does not decrease the FPS.
OptiFine 1.0.0 AA/AF Version B2
Support for Anti-Aliasing and Anisotropic Filtering!
Something like that. :smile.gif:
~ iiiHuman ~
If I could interject on this whole naming scheme, I have to agree that changing "Plus" to "Extended" does not change the meaning for the majority of users. More advanced English speakers may read "plus" as being more of an additive term than an inclusive term and think it needs to be thrown on top of Basic in order to work but extended creates a very similar idea. The real problem is that despite what may or may not be common for a website full of engineers to do, the naming scheme of this mod is confusing and the scheme you want to change it to does not really help the situation.
The biggest problem I have with Optifine's naming scheme is how it orders itself. Let's take OptiFine 1.0.0_HD_AA_B2 as an example to start with.
You start with the name of the mod, which implies the information following it is completely related to describing the mod. Then you follow it with the Minecraft version string, which is not directly related to the mod. This is followed by "HD", which seems to be a further extension of the Optifine name. This is followed by the mod edition, "AA" in this case. Then finally B2, which is apparently Optifine's version number.
I'm sorry guys, but as a programmer and as a person that loves using tons of mods for other games, even I find this incredibly confusing. My personal suggestion is to not actually change the name, so much as reorganize the information. Something along the lines of the following:
Optifine HD_B2_AA Edition for Minecraft 1.0.0
or
Optifine HD_B2_AA for 1.0.0
That way the information is more clearly organized in a readable form that makes sense to the majority of people. It starts with the mod name "Optifine", then moves to the name extension "HD", followed by the version "B2", then the edition "AA", and finally what it's for "for 1.0.0". This way you naturally progress in a left to right manner from the point to which all of these are most related "Optifine" to the point in which they are most unique "AA". Others would then follow the same structure.
Optifine HD_B2 for 1.0.0
Optifine HD_B2_S for 1.0.0
Optifine HD_B2_AA for 1.0.0
Optifine HD_B2_MT for 1.0.0
Of course you could expand on the acronyms a little more to make it easier to read, by saying something like:
Optifine HD B2: Smooth Edition for 1.0.0
Optifine HD B2: Multi-Threaded Edition for 1.0.0
Only when things are properly organized into an easy to comprehend form would I then worry about changing the name. To extend your "plus" idea:
Optifine HD B2: Basic Edition for 1.0.0
Optifine HD B2: Plus Edition for 1.0.0
Optifine HD B2: Plus Multi-Threading Edition for 1.0.0
Or to follow the original argument for "extended" which I believe may be slightly better than "plus":
Optifine HD B2: Basic Edition for 1.0.0
Optifine HD B2: Extended Edition for 1.0.0
Optifine HD B2: Extended Multi-Threaded Edition for 1.0.0
However, if it were up to me I would name it something like this:
Optifine HD B2: Standard Edition for 1.0.0
Optifine HD B2: Advanced Edition for 1.0.0
Optifine HD B2: Advanced Multi-Core Edition for 1.0.0
Here "Standard" indicates a normal version, and "Advanced" indicates a clear step up without implying that it should be installed on top of "Standard". Where as "Basic" implies a bare bones release that, in conjunction with "Plus" or "Extended" carries the idea of one being layered on top of the other.
Anyway this is just my two cents on the whole naming scheme for Optifine. Personally my experience starting out with the current overall scheme was quite a lot of confusion. I have written mods from scratch for Command and Conquer Generals: Zero Hour and just installed both The Oblivion Script Extender and Graphics Extender for TESIV the day prior to attempting to install Minecraft mods. In comparison I found Optifine incredibly frustrating to understand. I think any of the changes I have outlined, or at least similar changes, would make everyone's time with Optifine a lot easier.
Now, I realize that this is "only a mod" and by extension is yours and not mine, and normally I do not go about telling people how to name things they make. However, Optifine is an essential mod which texture pack users, and GLSL shaders users rely upon in order to play Minecraft the way they want to or on the systems they want to. This means that the majority of people that use mods or texture packs will want to use Optifine. This means that the ease of use regarding the downloading and installation of Optifine is the key to success for a large amount of the extended modding / texture pack community. My point is, if I had trouble understanding Optifine you can bet many others will have trouble, and many of those people will not have the understanding or the patience to keep trying when Optifine mysteriously doesn't work. Human error is a lot more common when things are not presented clearly, and the average person will not create a forum account to ask a question like I did.
Bottom line: It will benefit everyone if the Optifine naming scheme were a lot easier to understand.
Personally, I think "Enhanced" would work better than "Advanced", as "Advanced" implies more advanced settings to configure, or that it's for more advanced users, when in fact it's just got a more advanced way of rendering. "Enhanced", on the other hand, feels more like it describes the product rather than the usage.
Otherwise, that's a very well thought out post and you make some good points. Your new names are certainly more readable and more clear what it is.
Original idea is here.
Why you didn't plan some kind of patcher?(which is a little bit different from installer)
A patcher like "copy files to minecraft.jar" is planned and may be released soon.
A patcher like "merge differences between mod and vanilla classes" may be problematic for OptiFine, because it makes a lot of changes.
:sad.gif: too bad
Install Optifine after installing Modloader, and then add all the other mods.
As of now, I use MCPatcher to install all my mods. I just uncheck the HD stuff, bettergrass and randommobs and add all the mods I want.
Would be great if you made a patcher for OptiFine that has this feature to add mods to it. :smile.gif:
Ooooohhhh, I like!
~ iiiHuman ~
Coming soon...
How does it work?
It just renders snow for some blocks (fence, tall grass, mushroom, etc) when the surrounding blocks also have snow on top. The snow is not existing, it can not be collected with shovel, etc. But it looks nice.
Must the snow be covering all 4 sides of a none-snow block?
How does the none-snow block look like? The regular snow blocks is just grass with a snow-layer on top, does that snow-layer appear on the none-snow block?
One side is enough, otherwise fences and several flowers together will not show the snow.
Only the snow layer is shown, the block below is not affected.
Last time I tried, patcher works fine with optifine.
Love this mod. It is a godsend. Thanks for continuing to support it.
On a related note, would it be possible to allow bettergrass without snow-sided blocks? With grass, you can safely assume that any block that looks like grass is dirt, but when you do the same with snow it becomes impossible to distinguish a snow block from one that is simply covered in snow.
What happens if you make a path in the snow? Like a 2 block wide path, will that be grass or appear to be snow?
It does work, But I would like sp614x making one that also could merge files together and stuff like that. Can be a bit unessesary though cause there is MCPatcher already :smile.gif:
Can this be ameneded?
Non animated Fire can just be 1st frame of Fire animation IMO.
thanks.also is this compatibal with adventurecraft?
Now i play on my usually laggy server, and nothing!
Perfect mod!
Thank you!!!
If I could interject on this whole naming scheme, I have to agree that changing "Plus" to "Extended" does not change the meaning for the majority of users. More advanced English speakers may read "plus" as being more of an additive term than an inclusive term and think it needs to be thrown on top of Basic in order to work but extended creates a very similar idea. The real problem is that despite what may or may not be common for a website full of engineers to do, the naming scheme of this mod is confusing and the scheme you want to change it to does not really help the situation.
The biggest problem I have with Optifine's naming scheme is how it orders itself. Let's take OptiFine 1.0.0_HD_AA_B2 as an example to start with.
You start with the name of the mod, which implies the information following it is completely related to describing the mod. Then you follow it with the Minecraft version string, which is not directly related to the mod. This is followed by "HD", which seems to be a further extension of the Optifine name. This is followed by the mod edition, "AA" in this case. Then finally B2, which is apparently Optifine's version number.
I'm sorry guys, but as a programmer and as a person that loves using tons of mods for other games, even I find this incredibly confusing. My personal suggestion is to not actually change the name, so much as reorganize the information. Something along the lines of the following:
Optifine HD_B2_AA Edition for Minecraft 1.0.0
or
Optifine HD_B2_AA for 1.0.0
That way the information is more clearly organized in a readable form that makes sense to the majority of people. It starts with the mod name "Optifine", then moves to the name extension "HD", followed by the version "B2", then the edition "AA", and finally what it's for "for 1.0.0". This way you naturally progress in a left to right manner from the point to which all of these are most related "Optifine" to the point in which they are most unique "AA". Others would then follow the same structure.
Optifine HD_B2 for 1.0.0
Optifine HD_B2_S for 1.0.0
Optifine HD_B2_AA for 1.0.0
Optifine HD_B2_MT for 1.0.0
Of course you could expand on the acronyms a little more to make it easier to read, by saying something like:
Optifine HD B2: Smooth Edition for 1.0.0
Optifine HD B2: Multi-Threaded Edition for 1.0.0
Only when things are properly organized into an easy to comprehend form would I then worry about changing the name. To extend your "plus" idea:
Optifine HD B2: Basic Edition for 1.0.0
Optifine HD B2: Plus Edition for 1.0.0
Optifine HD B2: Plus Multi-Threading Edition for 1.0.0
Or to follow the original argument for "extended" which I believe may be slightly better than "plus":
Optifine HD B2: Basic Edition for 1.0.0
Optifine HD B2: Extended Edition for 1.0.0
Optifine HD B2: Extended Multi-Threaded Edition for 1.0.0
However, if it were up to me I would name it something like this:
Optifine HD B2: Standard Edition for 1.0.0
Optifine HD B2: Advanced Edition for 1.0.0
Optifine HD B2: Advanced Multi-Core Edition for 1.0.0
Here "Standard" indicates a normal version, and "Advanced" indicates a clear step up without implying that it should be installed on top of "Standard". Where as "Basic" implies a bare bones release that, in conjunction with "Plus" or "Extended" carries the idea of one being layered on top of the other.
Anyway this is just my two cents on the whole naming scheme for Optifine. Personally my experience starting out with the current overall scheme was quite a lot of confusion. I have written mods from scratch for Command and Conquer Generals: Zero Hour and just installed both The Oblivion Script Extender and Graphics Extender for TESIV the day prior to attempting to install Minecraft mods. In comparison I found Optifine incredibly frustrating to understand. I think any of the changes I have outlined, or at least similar changes, would make everyone's time with Optifine a lot easier.
Now, I realize that this is "only a mod" and by extension is yours and not mine, and normally I do not go about telling people how to name things they make. However, Optifine is an essential mod which texture pack users, and GLSL shaders users rely upon in order to play Minecraft the way they want to or on the systems they want to. This means that the majority of people that use mods or texture packs will want to use Optifine. This means that the ease of use regarding the downloading and installation of Optifine is the key to success for a large amount of the extended modding / texture pack community. My point is, if I had trouble understanding Optifine you can bet many others will have trouble, and many of those people will not have the understanding or the patience to keep trying when Optifine mysteriously doesn't work. Human error is a lot more common when things are not presented clearly, and the average person will not create a forum account to ask a question like I did.
Bottom line: It will benefit everyone if the Optifine naming scheme were a lot easier to understand.
Otherwise, that's a very well thought out post and you make some good points. Your new names are certainly more readable and more clear what it is.