[1.8.7] Forge 1450 & 1487 crashes on startup; no Shader support

[LordDrikon]

I have an old computer with no hardware shader support. The video drivers are as updated as an old machine will have them. A new PC or new video is not an option for me.

 

Minecraft 1.8.7 (and earlier) vanilla works without crashing. With a clean Minecraft install and using the 1450 or the 1487 Forge "installer" installs fine. With no mods or such clicking "Play" in the Minecraft launcher crashes it.

 

I don't know what is causing it to crash but I suspect it crashes because Forge seems to now have higher graphics requirements than the Vanilla Minecraft (at this time), I am guessing. My fear is that now that MC 1.6 and lower is no longer supported by Forge and I fear 1.7.10 not too far behind, that Minecraft with mods will no longer be a sensible game option for me. If it is not an issue of Forge no longer supporting pre-shader graphics, great!

 

 

 

 

---- Minecraft Crash Report ----

// I just don't know what went wrong

 

Time: 7/10/15 1:43 PM

Description: Initializing game

 

net.minecraft.client.renderer.StitcherException: Unable to fit: missingno - size: 16x16 - Maybe try a lowerresolution resourcepack?

at net.minecraft.client.renderer.texture.Stitcher.func_94305_f(Stitcher.java:79)

at net.minecraft.client.renderer.texture.TextureMap.func_110571_b(TextureMap.java:267)

at net.minecraft.client.renderer.texture.TextureMap.func_174943_a(TextureMap.java:96)

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 net.minecraft.client.renderer.texture.Stitcher.func_94305_f(Stitcher.java:79)

at net.minecraft.client.renderer.texture.TextureMap.func_110571_b(TextureMap.java:267)

at net.minecraft.client.renderer.texture.TextureMap.func_174943_a(TextureMap.java:96)

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 XP (x86) version 5.1

Java Version: 1.8.0_25, Oracle Corporation

Java VM Version: Java HotSpot Client VM (mixed mode), Oracle Corporation

Memory: 78403264 bytes (74 MB) / 272191488 bytes (259 MB) up to 523501568 bytes (499 MB)

JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M -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 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.1487.jar)

UCH Forge{11.14.3.1487} [Minecraft Forge] (forge-1.8-11.14.3.1487.jar)

Loaded coremods (and transformers):

GL info: ' Vendor: 'Intel' Version: '1.3.0 - Build 4.14.10.4363' Renderer: 'Intel 865G'

Launched Version: 1.8-Forge11.14.3.1487

LWJGL: 2.9.1

OpenGL: Intel 865G GL version 1.3.0 - Build 4.14.10.4363, Intel

GL Caps: Using GL 1.3 multitexturing.

Using GL 1.3 texture combiners.

Not using framebuffer objects because OpenGL 1.4 is not supported, EXT_blend_func_separate is supported, OpenGL 3.0 is not supported, ARB_framebuffer_object is not supported, and EXT_framebuffer_object is not supported.

Shaders are not available because OpenGL 2.1 is not supported, ARB_shader_objects is not supported, ARB_vertex_shader is not supported, and ARB_fragment_shader is not supported.

VBOs are available because ARB_vertex_buffer_object is supported.

 

Using VBOs: No

Is Modded: Definitely; Client brand changed to 'fml,forge'

Type: Client (map_client.txt)

Resource Packs: []

Current Language: English (US)

Profiler Position: N/A (disabled)

 

 

[LordDrikon]

I don't use any graphics intensive mods. I tend to use mods like NEI, Treecapitator, Checkpoints, stuff like that. 1.7.10 is almost playable, 1.8.7 is barely playable. But I love the Custom world gen options in 1.8.7 for how and where ore is found. And don't forget MC 1.4.7 and lower worked fine on these old PCs. To me Minecraft is not so much about nice graphics, it's about exploring and building. I'll get back on the startup screen thing. I would be nice if the startup screen wasn't hardware shader depenant (if that's the issue.)

 

 

[LordDrikon]

That did the trick,

enabled=false

Thanks.

[LordDrikon]

"Another side note: Forge does not run on 1.8.7 yet, only 1.8." Arg!

 

Although I got it started atm in 1.8.7 I suppose 1.8.7 with current Forge 1450/1487 will crash or something. At that point I guess I'll try 1.8.0 then.

 

Thanks a bunch! Your and LexManos and other's have given my kids and I lots of joy over the last 2 years.

[LordDrikon]

"No, you haven't "  Hey look at that! Forge snuck that past me. I didn't have 1.8 installed before then. Nice feature!

[LexManos]

Post you full logs there is debug text that I want to see.

There shouldn't be any reason this is giving you an issue.

[LordDrikon]

LexManos, I noticed almost a month later from your request for the logs. The settings in splash.properties did resolve my issue of crashing however, meaning I can play the game. Here are the logs anyway.

 

Crash Report

http://pastebin.com/QvteL03p

 

Game Output (within Launcher)

http://pastebin.com/D1M1P26f

 

If there are "more" logs I don't know where those files are located or their name.

[LexManos]

*minecraft folder*\logs\fml-client*.log

Those are the ones we need.

[LordDrikon]

I cleared out my logs directory before rerunning.

These where the only three files in the logs folder.

 

Above is a crash-report, seems only the date is different.

 

The issue happens with Forge/FML-1502 as well, as that is what I'm using now.

 

Here they are. Hope it helps.

 

latest.log

http://pastebin.com/1ZJWMkeV

 

fml-junk-earlystartup.log

http://pastebin.com/WQ6bzS6U

 

fml-client-latest.log

http://pastebin.com/9KmZ7Dza

 

By the way I just found this URL (related issue?):

https://github.com/MinecraftForge/FML/issues/644

 

If I had seen that URL before-hand I likely could have not wasted anyone's time as it seems related.

Perhaps a link to this reply in the tracker would help others.

 

For those that are tuning in late, I have Minecraft 1.8.0 with Forge/FML-1502 working with the splash.properties setting as mentioned in a previous reply.

 

[LexManos]

 

[00:21:54] [Client thread/INFO] [FML/]: Max texture size: -1

Something is REALLY fucking up your graphics card... You should never get this value...

[LordDrikon]

I knew that would catch your attention.

 

This either brings up a memory or a delusion but...

 

I've seen that before on another old PC I had just when Minecraft 1.5.? came out.

 

I was able to play Minecraft 1.4.7 with forge and a slew of mods just fine. DirectX 9.0C was end of life, I think, and graphics hardware just started using more texture stuff. I couldn't play Minecraft 1.5.x Vanilla at all on it.

I wasn't able to play Minecraft at home until Minecraft 1.6.4 was release. Other people complained about the issue, I think on minecraftforums.

 

So I drilled down into the LWGL or OpenGL C code from somewhere and low and behold there was a function that returned -1 if it failed to receive a result from a properties query to the graphics card on initialization regarding texture support.

 

I believe this wasn't a Minecraft issue but a Java library. Instead of the coder returning a ZERO for no texture hardware is was coded as -1. Older versions of that code returned a zero. And I think I may have posted here on the issue. 

 

When DirectX 10 came out, another two games gave similar errors with "shader" errors; albeit textures seemed to be the issue. The other game errors pointed to the same -1 return value.  Query failed for texture support (and get a crash) as opposed to query succeeded with no texture support and end game or render the slow way.

 

Rhetorically, wasn't there a time if you had no hardware shader support, things would render through software, as Minecraft does even now? That warning about OpenGL 2.0 coming soon... plays on my mind.

 

I play minecraft because it used 8-bit graphics as its lowest common denominator. It's what attracted me to the game. One day either a new PC or start a new hobby.

 

I speculate. Its been many years since I coded professionally.

 

BTW I can still play games like LOTR, SOF2, Everquest I but not II. Old yeah, but no crashes or glitches with my graphics for old games, meaning I don't think the card is messed. I imagine current graphics libraries discount graphics cards without basic modern hardware.