There are sometimes issues with drivers (AMD, Intel). But completely NOT updating anything for almost 2 years is ...
And my main issue with your posts was that you were:
1. told you probably have old drivers (which you did)
2. told to read compatibility notes, that deal with Intel driver versions
And your response was to talk about how your laptop is only 2 years old. Making it look like you don't know what drivers are, and think it's a hardware issue.
Disclaimer: Yes I have a thing about people ignoring instructions, especially if they have it pointed out and still ignore them. Yes, I can be a jerk about that issue.
Suffice to say, about 2/3 issues reported on this thread are exactly that. People who ignored compatibility notes in the first thread and crashed due to buggy Intel drivers. Or tried running SEUS on IntelHD/Mac. Or ignored Optifine configuration notes and got dissappearing text. Or ...
And so on.
AMEN!
We need a bot on this thread that automatically posts the common fixes (driver version incompatibility, driver version links, known texture pack problems, shaderpack compatibility with certain cards, optifine configuration requirements for D3-D5 in 1.8, etc etc etc).
Let's shoot for at least on the top of every page ... lol
I don't have a notebook, but it overheats once a week.
Well than, you either need to mount more fans in your case (usually 1 or 2 in the front, and 1 or 2 in the back/top), or add/change the thermal paste on the processor.
The processor, power supply, and video card have their own fans. If you don't have any in the front or back of the case, that might explain things -- it's just a huge hotbox. The only thing moving air out is the power supply.
If you have fans and your case is full, bring it to a computer shop (or the place where you bought it), and have them change the thermal paste.
If you know what you're doing, this is easy as well. A phillips screwdriver, and 5 minutes of patience. Even easier if you have arctic clean & the emulsifier, and some arctic silver 5 (or your preferred paste, maybe ppl are still into the thermaltake mx paste).
The fans are all push pin installed, turn the 4 nobs 90% (they are labelled which way to remove), unplug the fan power cable, pull the pins up slightly, and the fan will come off the CPU easily. Make sure your machine is off & unplugged, of course. Clean paste, and re-apply. The paste comes in a syringe. You only need an amount the size of a grain of rice (maybe 2 if it's dual/quad core). Install fan and push the clips into place. Plug the fan back in.
I'n not complaining, I'm disappointed. There is a difference. I was just asking if there was a way to fix it, without updating something that works just fine.
Updated drivers are almost always good. Plus, EXTREMELY easy to update, even for the average user. If you don't know where to find them, pretty simple, just ask.
Intel and AMD have had some rocky points with their driver updates (for Intel builds 3400-3900 & 4081-4250 didn't work, for AMD build 15.7 & 15.7.1 are causing issues). Check in here for what works, and use it. nVidia has been fine all along basically.
On that note, there is no way you can 'fry' your system up by doing updates. If anything (if you turn it off in the middle or you lose battery power) it might corrupt, and you'll have to reload windows.
If your machine 'fried', your hdd failed because it was old or misused (SSDs last millions of writes -- either way -- HDDs & SSDs last easily 5-10 years), it overheated because it wasn't cleaned out properly (notebooks are notorious for overheating because of the design of the fans & fins), or it was cooked due to a power surge. None of these have anything to do with updates.
Chances are you have a 64bit install of Windows, so, use the 2nd one. Download the EXE, and run it.
Hopefully, you don't get the 'your hardware is not compatible'. If you do, go back and download the ZIP one. Extract it to a safe folder (right-click extract, windows has a ZIP extraction tool built in now). You will have to go into the device manager (right-click the start button -> device manager). Click the + on Display Adapters. Right-click on Intel 4600 and click update driver. Click manual. Browse to where you downloaded & extracted the driver. Let it install the driver.
After the driver is updated, you can run the regular EXE setup file now.
Fixed that for you. Forge changed something in build 1469 that required an update in Optifine AND Shader mod.
Aside for the following derp on Jonny's side, you were also told to use Optifine D5 with Forge 1502. You used D1 without checking any other version and made a general complaint "Optifine dun' work at all".
For Minecraft 1.8 the required updates came with Optifine D4 and Shader Mod 2.4.12.
Real bottom line: Everything works just fine with Recommended Forge 1450. You use newer builds? Read all descriptions/release notes carefully.
Well said, grimallq :)!
EDIT: And ... why do you type so fast?! I guess I overexplained myself too :P!
The problem for the average user like me is that we never know what versions of Forge work with what versions of Optifine.
For example if I start with a fresh install of Minecraft now (1.8.8), install the latest Forge, use version 'release 1.8-Forge11.14.3.1502' in my profile, and try 'OptiFine_1.8.8_HD_U_S6.jar' or 'OptiFine_1.8.8_HD_U_E2.jar' by putting them in my mods directory, both end up with crashes even before the Mojang logo screen.
So every time I want to update my Minecraft core, I have to google for what versions of Forge go with what versions of Optifine and what versions of shaders and try to make it work.
At the moment I'm using forge-1.8-11.14.1.1371 with OptiFine_1.8.0_HD_U_D1 and ShadersMod-v2.4.12mc1.8 because I can't get the latest forge (1502) to work with the 1.8.8 version of Optifine.
Getting shaders integrated into Optifine is a great step for end users. And I am amazed that people are actually able to keep working on things like Optifine and Forge for such a long time. But still I wish things like HD textures capability and Forge (for loading mods) can just be part of the Minecraft core already. Integrate Optifine and Forge and build Minecraft Deluxe and I'll happily pay another 20 dollars to buy it if it means I'll never have to worry about using the wrong versions of Forge/Optifine ever again when I update my Minecraft core.
The post you replied to, I specifically said, explicitly, the latest Forge does not work with Optifine1.8.0 for me. It doesn't "all works just fine".
Forge 1502 + Optifine 1.8.0 HD U D1. No other mods. No shaders. Crash Log:
---- Minecraft Crash Report ----
// Quite honestly, I wouldn't worry myself about that.
Time: 2015/8/22 上午 1:13
Description: Initializing game
java.lang.NoSuchMethodError: net.minecraft.client.renderer.texture.TextureMap.<init>(Ljava/lang/String;Z)V
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:468)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:325)
at net.minecraft.client.main.Main.main(SourceFile:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:468)
-- Initialization --
Details:
Stacktrace:
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:325)
at net.minecraft.client.main.Main.main(SourceFile:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
-- System Details --
Details:
Minecraft Version: 1.8
Operating System: Windows 8.1 (amd64) version 6.3
Java Version: 1.8.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 253942544 bytes (242 MB) / 523501568 bytes (499 MB) up to 1060372480 bytes (1011 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
FML: MCP v9.10 FML v8.0.99.99 Minecraft Forge 11.14.3.1502 Optifine OptiFine_1.8_HD_U_D1 3 mods loaded, 3 mods active
States: 'U' = Unloaded 'L' = Loaded 'C' = Constructed 'H' = Pre-initialized 'I' = Initialized 'J' = Post-initialized 'A' = Available 'D' = Disabled 'E' = Errored
UCH mcp{9.05} [Minecraft Coder Pack] (minecraft.jar)
UCH FML{8.0.99.99} [Forge Mod Loader] (forge-1.8-11.14.3.1502.jar)
UCH Forge{11.14.3.1502} [Minecraft Forge] (forge-1.8-11.14.3.1502.jar)
Loaded coremods (and transformers):
Launched Version: 1.8-Forge11.14.3.1502
LWJGL: 2.9.1
OpenGL: GeForce GTX 660/PCIe/SSE2 GL version 4.5.0 NVIDIA 355.60, 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.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.
Using VBOs: No
Is Modded: Definitely; Client brand changed to 'fml,forge'
Type: Client (map_client.txt)
Resource Packs: [[1.8.3]_R3D.CRAFT_SR-64x_v0.2.2.zip] Current Language: English (US)
Profiler Position: N/A (disabled)
Just by changing the core to Forge build 1371 and everything works. Note that all this is even before putting shadersmod in.
I'm not trying to argue that Forge should work with Optifine 1.8.8. I'm not using 1.8.8 anymore. Perhaps you read only my first post in the thread and assumed that I'm that egg-head who refuse to read other people's posts and insist to use 1.8.8 with Forge. No. If you actually read my previous reply, it was about Optifine 1.8.0.
Bottom line, Optifine 1.8.0 crashes with Forge 1502 for me. If it works for you, then I'd love to find out why, because then it's got to be some configuration on my side that's making it crash.
Yes, I was going through your conversation history, and it sure sounded like you were trying to use OF 1.8.8 with Forge 1.8.0.
I can see in the log you posted that in Forge 1502 you are trying to use Optifine 1.8.0 HD U D1.
Optifine 1.8.0 HD U D1 & D2 were posted to work with Forge prior to build 1371.
The whole reason why D3 came out was to support 1371+ (because Forge pushed the new loading screen, which broke stuff). I may be thinking of 1486+, but D3 made some MASSIVE changes to the way textures are loaded, and it caused crashing in ShadersMod plus textures glitches (which isn't really Optifine's problem, it was fixed in the conflicting mods, and by correcting resource-pack problems).
D4 & D5 came out to support newer versions of Forge as well, specifically 1486+.
So, if you are going to run Forge 1486 - 1502, you need to run Optifine 1.8.0 HD U D4 - D5 at least to avoid these crashes.
Another note, if you are upgrading (using the same game folder) 1.7.X to 1.8.0, the options.txt / optionsof.txt are not compatible. Delete them, and let MC re-create them.
Feel free to turn on USE VBOS. You must leave FAST RENDER / ANISOTROPIC FILTERING / ANTI ALIASING / NATURAL TEXTURES all off. Don't play with the render distance much, especially if you are going to run shaders.
I don't know why, but the latest Forge (1502) crashes with Optifine 1.8.0. I had to downgrade Forge to the 11.14.3.1371 build to make it work.
Also I forgot to quote in my previous reply, but I was replying to this:
And I was trying to point out that it wasn't as simple as "install Forge, add Optifine, Shaders". It's actually "google for 'minecraft <current main version> optifine forge shader'" and try to find which exact version of Forge works with which exact version of Optifine. Then download those exact versions and install.
Note that I'm not trying to complain. I appreciate the hard work people are doing out of goodwill and getting almost nothing in return for the time and skill invested into this. I just wish it was a little easier.
It's extremely simple, DO NOT USE OPTIFINE 1.8.8 BUILDS WITH FORGE FOR 1.8.0!
Use Optifine 1.8.0 HD U D1-D5 with Forge 1502 and all works just fine.
If you're going to use ShadersMod with Optifine 1.8.0 HD U D5 and Forge 1502, make sure you turn off Fast Render and Natural Textures first, then put ShadersMod into the mods folder.
As always, never use Anisotropic Filtering or AntiAliasing with ShadersMod.
So, bottom line, the releases are labelled 1.8.0 and 1.8.3 and 1.8.8 FOR A REASON!
WARNING: coremods are present:
ItemPatchingLoader (ItemPhysic Lite 1.1.2 mc1.8.jar)
TMIForgeLoader (TooManyItems2015_02_14_1.8_Forge.jar)
Contact their authors BEFORE contacting forge
// Surprise! Haha. Well, this is awkward.
Time: 19/08/15 1:06 AM
Description: Stitching texture atlas
java.lang.NullPointerException: Stitching texture atlas
at shadersmod.client.ShadersTex.readImage(ShadersTex.java:464)
at shadersmod.client.ShadersTex.readImageAndMipmaps(ShadersTex.java:439)
at shadersmod.client.ShadersTex.uploadTexSubForLoadAtlas(ShadersTex.java:419)
at net.minecraft.client.renderer.texture.TextureMap.func_110571_b(TextureMap.java:354)
at net.minecraft.client.renderer.texture.TextureMap.func_174943_a(TextureMap.java:127)
at net.minecraftforge.client.model.ModelLoader.func_177570_a(ModelLoader.java:109)
at net.minecraft.client.resources.model.ModelManager.func_110549_a(ModelManager.java:29)
at net.minecraft.client.resources.SimpleReloadableResourceManager.func_110542_a(SimpleReloadableResourceManager.java:130)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:474)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:325)
at net.minecraft.client.main.Main.main(SourceFile:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at shadersmod.client.ShadersTex.readImage(ShadersTex.java:464)
at shadersmod.client.ShadersTex.readImageAndMipmaps(ShadersTex.java:439)
at shadersmod.client.ShadersTex.uploadTexSubForLoadAtlas(ShadersTex.java:419)
-- Texture being stitched together --
Details:
Atlas path: textures
Sprite: TextureAtlasSprite{name='missingno', frameCount=1, rotated=false, x=0, y=0, height=64, width=64, u0=1.5625E-4, u1=0.9998438, v0=1.5625E-4, v1=0.9998438}
Stacktrace:
at net.minecraft.client.renderer.texture.TextureMap.func_110571_b(TextureMap.java:354)
at net.minecraft.client.renderer.texture.TextureMap.func_174943_a(TextureMap.java:127)
at net.minecraftforge.client.model.ModelLoader.func_177570_a(ModelLoader.java:109)
at net.minecraft.client.resources.model.ModelManager.func_110549_a(ModelManager.java:29)
at net.minecraft.client.resources.SimpleReloadableResourceManager.func_110542_a(SimpleReloadableResourceManager.java:130)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:474)
-- Initialization --
Details:
Stacktrace:
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:325)
at net.minecraft.client.main.Main.main(SourceFile:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
-- System Details --
Details:
Minecraft Version: 1.8
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.8.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 121834208 bytes (116 MB) / 297574400 bytes (283 MB) up to 1060372480 bytes (1011 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
FML: MCP v9.10 FML v8.0.99.99 Minecraft Forge 11.14.3.1487 Optifine OptiFine_1.8_HD_U_D5 5 mods loaded, 5 mods active
States: 'U' = Unloaded 'L' = Loaded 'C' = Constructed 'H' = Pre-initialized 'I' = Initialized 'J' = Post-initialized 'A' = Available 'D' = Disabled 'E' = Errored
UCH mcp{9.05} [Minecraft Coder Pack] (minecraft.jar)
UCH FML{8.0.99.99} [Forge Mod Loader] (forge-1.8-11.14.3.1487.jar)
UCH Forge{11.14.3.1487} [Minecraft Forge] (forge-1.8-11.14.3.1487.jar)
UCH TooManyItems{1.8} [TooManyItems] (minecraft.jar)
UCH itemphysic{1.1.2} [ItemPhysic] (minecraft.jar)
Loaded coremods (and transformers):
ItemPatchingLoader (ItemPhysic Lite 1.1.2 mc1.8.jar)
com.creativemd.itemphysic.ItemTransformer
TMIForgeLoader (TooManyItems2015_02_14_1.8_Forge.jar)
TMIForgeTransformer
GL info: ' Vendor: 'Intel' Version: '3.1.0 - Build 8.15.10.2476' Renderer: 'Intel(R) HD Graphics Family'
Launched Version: 1.8-Forge11.14.3.1487
LWJGL: 2.9.1
OpenGL: Intel(R) HD Graphics Family GL version 3.1.0 - Build 8.15.10.2476, Intel
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.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.
Using VBOs: No
Is Modded: Definitely; Client brand changed to 'fml,forge'
Type: Client (map_client.txt)
Resource Packs: [Ragecraft Faithful.zip, Ragecraft CTM Addon.zip, Ragecraft ClearG Addon.zip, Ragecraft CGUI Addon.zip] Current Language: English (US)
Profiler Position: N/A (disabled)
I dont know what im doing.
Update forge to 1502. Update ShadersMod to 2.4.12.
Delete optionsof.txt from %appdata%\.minecraft.
You need to update to ShadersMod 2.4.12 and OF 1.8.0 HD U D3-D5 to get rid of that error.
The problem is that ShadersMod is not compatible with these features from OF 1.8.0 HD U D3-D5:
Natural Textures
Fast Render
As always, you cannot use Anisotropic Filtering, or AntiAliasing either.
Thanks for your reply. It already is updated to the most recent version, though.
It could be that the shaderpack was updated and your video card no longer supports the functions in use.
Your ATI Mobility Radeon HD 4500 only supports OpenGL 2.1 (which is what MC itself runs on), shaderspacks use functions from OpenGL 3.2-4.X that your card does not support any more.
Unfortunately, aside from rolling back to MC 1.5.2 (pre SEUS modifications) you aren't going to be able to use shaders.. You might be able to run some Intel-based ones that are extremely basic, like Sildur's Basic 1.04 shaders.
So I downloaded the shader's mod installer...and immediately following the "Make sure Minecraft Launcher and Minecraft are closed," I get this. There is nothing in the drop down menu, and I can't find a single person with a similar issue. At least, not at a half hour hunt. : / Got any solutions?
Anyway. Have you tried to connect to your mother's LAN server in vanilla Minecraft? No Forge, no mods, just the original Minecraft.
If you run into the same problem doing this, then something is wrong/weird about your network setup.
From your description, I have understood that you can see your mother hosting the LAN server, but when you try to connect, you time out.
This could be, as madam Puppyspirit already pointed out, because your, her, or your router's Firewall settings are too high.
This also could be some weird phenomenon that I encountered once at one of my friends':
Back then I could not connect to his LAN game directly from the multiplayer menu, but I could connect by using his computer's LAN IP.
This is how you test if this works. step 1-5 are on your mother's computer:
1. If you open a LAN game, it says something like: "LAN game hosted on port 12345."
2. I hope you are on Windows, if you are not, try googling "how do I find my LAN IP on a Mac/Unix system."
3. In Windows, open Menu Start, type "cmd" and hit Enter. A black and white command window should pop up.
4. In the command window type "ipconfig/all" and hit Enter. A whole list of information should pop up.
5. Search in the list for IPv4 address under the network connection you are actually connected to. This could for instance be wireless, or ethernet. The IPv4 address should look something like "192.168.0.8" and sometimes it says "<Preferred>".
6. In your minecraft, go to multiplayer, direct connect and type in your mother's IPv4 address : the port number. For instance: "192.168.0.8:12345".
7. Connect.
I hope this works.
NOTE: I live in the world of IT, networking, packets, VMs, servers, computers, etc.... A small lesson follows, lol!
Good points!!
You are right, ultimately, Optifine is a client side mod and it doesn't matter or care which servers you connect to. If you open to LAN, Optifine doesn't change or do anything. Also, Optifine is not supported on a private server, it will crash.
I want to say this though: if you are using Forge, any and all mods on the server (be that single player opened to LAN or a full private server) must be installed and working on the client -- and the same version. If she is missing mods, or they are older versions it will not connect.
The next thing, your router only looks at and blocks WAN (internet) -> LAN connections (where all connections are blocked by default). Any LAN -> LAN traffic / WLAN -> LAN traffic / LAN -> WLAN traffic is not monitored and is fully open all the time.
Your computer asks for a connection, the router knows to expect data back, so it stores that connection history in a database and opens the port. When the session is done, it removes that connection from the database and blocks the port again.
So, whether your computer is connected wired or wireless, it doesn't matter. It's all behind the firewall, and in the same 'subnet' (192.168.1.0 / 255.255.255.0) -- so, every computer can talk to each other.
Every Windows computer comes with the 'windows firewall' which also blocks all incoming traffic by default. When you fire up Minecraft, the Open to LAN, or a private server Windows usually asks if it is allowed to receive connections to that program when it is open. You may also have an antivirus/firewall program installed on your computer that replaces the windows firewall.
If you can't see the multiplayer game than windows is probably blocking the connection in the windows firewall.
-----------------
In the screenshot, if you click WINDOWS FIREWALL in the lower left, click ALLOW A PROGRAM THROUGH THE FIREWALL at the top left.
Click CHANGE SETTINGS if you are on Windows 8.1 or 10.
Look for Minecraft or Java(TM) Platform SE binary to see if it is in the list. If not, click ALLOW ANOTHER APP, browse to C:\Program Files\Java\bin\javaw.exe and add it. Check off the PRIVATE and/or PUBLIC buttons. Then hit OK.
You can do the same for:
C:\Program Files\Java\bin\java.exe
C:\Program Files (x86)\Java\bin\javaw.exe
C:\Program Files (x86)\Java\bin\java.exe
You want the (x86) ones if you use 32bit Java on your 64bit computer. You don't really need to add the Minecraft.exe, but you can if you prefer, all connections/downloads are outbound so automatic. You only need the java.exe files if you run a private server.
This happens with the full log block, where every side is the texture of bark.
The block is commonly used in most rock/tree packs, and I'd love to have rounded logs without having to world edit out every single full log block into just regular logs. Also, not sure if this is Better Foliage or Optifine, or the combination of both, but in just the default texture pack this happens:
Generally if a graphical issue appears in Minecraft, and you have Optifine installed, remove it and check. As great as it can be when working correctly, Optifine can be awful with other mods. I've personally had issues with things as different as Ars magica, Better Foliage, and Plant Mega Pack. If all you want is an FPS boost, look up Fastcraft and BetterFPS, though I'm not sure of anything that adds the other upgrades, like enhanced view distances.
I run Optifine and ShadersMod without issues (as do many other people)..
While it has happened in the past, it is rare that you have a graphical issue like this.
It could be that a block needs to be added to the blacklist so that it is not 'rounded', this is usually a problem with Mods, not so much resource packs.
The issue could probably be resolved by editing the texture and resolving the issue of why it couldn't be rounded in the first place. Or, in the case of the new Optifine D2-D5 it could be the mipmapping bug. The textures have to be a power of 2 (exponents), so if they are 24x24 for example, they will either be stretched to 32x32 or blanked.
I did release an updated copy of Better Foliage 1.8 with properly resized textures, OctarineNoise will be hosting it on Curse when he gets a chance.
0
It's not, the 1.8 version is a JAR.
It happens to be an installer if you want to run non-forge.
It also happens to be a forge mod, if you just put the JAR file into %appdata%\.minecraft\mods.
Dual purpose, why bother making 2 separate files?
1
AMEN!
We need a bot on this thread that automatically posts the common fixes (driver version incompatibility, driver version links, known texture pack problems, shaderpack compatibility with certain cards, optifine configuration requirements for D3-D5 in 1.8, etc etc etc).
Let's shoot for at least on the top of every page ... lol
0
Well than, you either need to mount more fans in your case (usually 1 or 2 in the front, and 1 or 2 in the back/top), or add/change the thermal paste on the processor.
The processor, power supply, and video card have their own fans. If you don't have any in the front or back of the case, that might explain things -- it's just a huge hotbox. The only thing moving air out is the power supply.
If you have fans and your case is full, bring it to a computer shop (or the place where you bought it), and have them change the thermal paste.
If you know what you're doing, this is easy as well. A phillips screwdriver, and 5 minutes of patience. Even easier if you have arctic clean & the emulsifier, and some arctic silver 5 (or your preferred paste, maybe ppl are still into the thermaltake mx paste).
The fans are all push pin installed, turn the 4 nobs 90% (they are labelled which way to remove), unplug the fan power cable, pull the pins up slightly, and the fan will come off the CPU easily. Make sure your machine is off & unplugged, of course. Clean paste, and re-apply. The paste comes in a syringe. You only need an amount the size of a grain of rice (maybe 2 if it's dual/quad core). Install fan and push the clips into place. Plug the fan back in.
0
Updated drivers are almost always good. Plus, EXTREMELY easy to update, even for the average user. If you don't know where to find them, pretty simple, just ask.
Intel and AMD have had some rocky points with their driver updates (for Intel builds 3400-3900 & 4081-4250 didn't work, for AMD build 15.7 & 15.7.1 are causing issues). Check in here for what works, and use it. nVidia has been fine all along basically.
On that note, there is no way you can 'fry' your system up by doing updates. If anything (if you turn it off in the middle or you lose battery power) it might corrupt, and you'll have to reload windows.
If your machine 'fried', your hdd failed because it was old or misused (SSDs last millions of writes -- either way -- HDDs & SSDs last easily 5-10 years), it overheated because it wasn't cleaned out properly (notebooks are notorious for overheating because of the design of the fans & fins), or it was cooked due to a power surge. None of these have anything to do with updates.
0
The latest drivers over at Intel.com for your 4th Gen Intel HD work just fine (4251).
https://downloadcenter.intel.com/download/25146/Intel-Iris-Iris-Pro-and-HD-Graphics-Driver-for-Windows-7-8-8-1-32bit
https://downloadcenter.intel.com/download/25143/Intel-Iris-Iris-Pro-and-HD-Graphics-Driver-for-Windows-7-8-8-1-64bit
There are new ones, 4264, but I haven't tested them.
https://downloadcenter.intel.com/download/25233/Intel-Iris-Iris-Pro-and-HD-Graphics-Driver-for-Windows-7-8-8-1-32bit
https://downloadcenter.intel.com/download/25232/Intel-Iris-Iris-Pro-and-HD-Graphics-Driver-for-Windows-7-8-8-1-64bit
Chances are you have a 64bit install of Windows, so, use the 2nd one. Download the EXE, and run it.
Hopefully, you don't get the 'your hardware is not compatible'. If you do, go back and download the ZIP one. Extract it to a safe folder (right-click extract, windows has a ZIP extraction tool built in now). You will have to go into the device manager (right-click the start button -> device manager). Click the + on Display Adapters. Right-click on Intel 4600 and click update driver. Click manual. Browse to where you downloaded & extracted the driver. Let it install the driver.
After the driver is updated, you can run the regular EXE setup file now.
0
My guess would be video card too old, or video driver too old.
0
Install Java 1.8 from www.java.com.
0
Well said, grimallq :)!
EDIT: And ... why do you type so fast?! I guess I overexplained myself too :P!
0
Yes, I was going through your conversation history, and it sure sounded like you were trying to use OF 1.8.8 with Forge 1.8.0.
I can see in the log you posted that in Forge 1502 you are trying to use Optifine 1.8.0 HD U D1.
Optifine 1.8.0 HD U D1 & D2 were posted to work with Forge prior to build 1371.
The whole reason why D3 came out was to support 1371+ (because Forge pushed the new loading screen, which broke stuff). I may be thinking of 1486+, but D3 made some MASSIVE changes to the way textures are loaded, and it caused crashing in ShadersMod plus textures glitches (which isn't really Optifine's problem, it was fixed in the conflicting mods, and by correcting resource-pack problems).
D4 & D5 came out to support newer versions of Forge as well, specifically 1486+.
So, if you are going to run Forge 1486 - 1502, you need to run Optifine 1.8.0 HD U D4 - D5 at least to avoid these crashes.
Another note, if you are upgrading (using the same game folder) 1.7.X to 1.8.0, the options.txt / optionsof.txt are not compatible. Delete them, and let MC re-create them.
Feel free to turn on USE VBOS. You must leave FAST RENDER / ANISOTROPIC FILTERING / ANTI ALIASING / NATURAL TEXTURES all off. Don't play with the render distance much, especially if you are going to run shaders.
1
It's extremely simple, DO NOT USE OPTIFINE 1.8.8 BUILDS WITH FORGE FOR 1.8.0!
Use Optifine 1.8.0 HD U D1-D5 with Forge 1502 and all works just fine.
If you're going to use ShadersMod with Optifine 1.8.0 HD U D5 and Forge 1502, make sure you turn off Fast Render and Natural Textures first, then put ShadersMod into the mods folder.
As always, never use Anisotropic Filtering or AntiAliasing with ShadersMod.
So, bottom line, the releases are labelled 1.8.0 and 1.8.3 and 1.8.8 FOR A REASON!
0
Update forge to 1502. Update ShadersMod to 2.4.12.
Delete optionsof.txt from %appdata%\.minecraft.
You need to update to ShadersMod 2.4.12 and OF 1.8.0 HD U D3-D5 to get rid of that error.
The problem is that ShadersMod is not compatible with these features from OF 1.8.0 HD U D3-D5:
As always, you cannot use Anisotropic Filtering, or AntiAliasing either.
0
It could be that the shaderpack was updated and your video card no longer supports the functions in use.
Your ATI Mobility Radeon HD 4500 only supports OpenGL 2.1 (which is what MC itself runs on), shaderspacks use functions from OpenGL 3.2-4.X that your card does not support any more.
http://www.gpureview.com/Radeon-HD-4550-card-584.html
Unfortunately, aside from rolling back to MC 1.5.2 (pre SEUS modifications) you aren't going to be able to use shaders.. You might be able to run some Intel-based ones that are extremely basic, like Sildur's Basic 1.04 shaders.
0
Yup, simple problem, you need to run Minecraft 1.8 at least once before running the ShadersMod installer.
Also, please be aware, that ShadersMod 2.4.12 is for MINECRAFT 1.8.0! It does not work for 1.8.3-1.8.8!
1
NOTE: I live in the world of IT, networking, packets, VMs, servers, computers, etc.... A small lesson follows, lol!
Good points!!
You are right, ultimately, Optifine is a client side mod and it doesn't matter or care which servers you connect to. If you open to LAN, Optifine doesn't change or do anything. Also, Optifine is not supported on a private server, it will crash.
I want to say this though: if you are using Forge, any and all mods on the server (be that single player opened to LAN or a full private server) must be installed and working on the client -- and the same version. If she is missing mods, or they are older versions it will not connect.
The next thing, your router only looks at and blocks WAN (internet) -> LAN connections (where all connections are blocked by default). Any LAN -> LAN traffic / WLAN -> LAN traffic / LAN -> WLAN traffic is not monitored and is fully open all the time.
Your computer asks for a connection, the router knows to expect data back, so it stores that connection history in a database and opens the port. When the session is done, it removes that connection from the database and blocks the port again.
So, whether your computer is connected wired or wireless, it doesn't matter. It's all behind the firewall, and in the same 'subnet' (192.168.1.0 / 255.255.255.0) -- so, every computer can talk to each other.
Every Windows computer comes with the 'windows firewall' which also blocks all incoming traffic by default. When you fire up Minecraft, the Open to LAN, or a private server Windows usually asks if it is allowed to receive connections to that program when it is open. You may also have an antivirus/firewall program installed on your computer that replaces the windows firewall.
If you can't see the multiplayer game than windows is probably blocking the connection in the windows firewall.
-----------------
In the screenshot, if you click WINDOWS FIREWALL in the lower left, click ALLOW A PROGRAM THROUGH THE FIREWALL at the top left.
Click CHANGE SETTINGS if you are on Windows 8.1 or 10.
Look for Minecraft or Java(TM) Platform SE binary to see if it is in the list. If not, click ALLOW ANOTHER APP, browse to C:\Program Files\Java\bin\javaw.exe and add it. Check off the PRIVATE and/or PUBLIC buttons. Then hit OK.
You can do the same for:
C:\Program Files\Java\bin\java.exe
C:\Program Files (x86)\Java\bin\javaw.exe
C:\Program Files (x86)\Java\bin\java.exe
You want the (x86) ones if you use 32bit Java on your 64bit computer. You don't really need to add the Minecraft.exe, but you can if you prefer, all connections/downloads are outbound so automatic. You only need the java.exe files if you run a private server.
0
I run Optifine and ShadersMod without issues (as do many other people)..
While it has happened in the past, it is rare that you have a graphical issue like this.
It could be that a block needs to be added to the blacklist so that it is not 'rounded', this is usually a problem with Mods, not so much resource packs.
The issue could probably be resolved by editing the texture and resolving the issue of why it couldn't be rounded in the first place. Or, in the case of the new Optifine D2-D5 it could be the mipmapping bug. The textures have to be a power of 2 (exponents), so if they are 24x24 for example, they will either be stretched to 32x32 or blanked.
I did release an updated copy of Better Foliage 1.8 with properly resized textures, OctarineNoise will be hosting it on Curse when he gets a chance.