Minecraft 1.3.2 Forge 4.0.0 Bug

[Yaseen]

Well, Minecraft 1.3.2 was working fine and I installed forge on it and now i get this error, I tried gooling it for about 45 mins and I resulted in nothing. and My Drivers are up to date, so I was wondering if anyone could help me here since, forge was giving me the error. :

 

Bad video card drivers!

-----------------------

 

Minecraft was unable to start because it failed to find an accelerated OpenGL mode.

This can usually be fixed by updating the video card drivers.

 

 

 

--- BEGIN ERROR REPORT 7fe0271 --------

Generated 25/08/12 06:47

 

- Minecraft Version: 1.3.2

- Operating System: Windows XP (x86) version 5.1

- Java Version: 1.7.0_04, Oracle Corporation

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

- Memory: 18050696 bytes (17 MB) / 50487296 bytes (48 MB) up to 1060372480 bytes (1011 MB)

- JVM Flags: 2 total; -Xincgc -Xmx1024m

- LWJGL: 2.4.2

- OpenGL: ~ERROR~ NullPointerException: null

- Is Modded: Definitely; 'forge,fml'

- Type: Client

- Texture Pack: ~ERROR~ NullPointerException: null

- Profiler Position: N/A (disabled)[failed to get system properties (java.lang.NullPointerException)]

 

 

org.lwjgl.LWJGLException: Pixel format not accelerated

at org.lwjgl.opengl.WindowsPeerInfo.nChoosePixelFormat(Native Method)

at org.lwjgl.opengl.WindowsPeerInfo.choosePixelFormat(WindowsPeerInfo.java:52)

at org.lwjgl.opengl.WindowsDisplay.createWindow(WindowsDisplay.java:185)

at org.lwjgl.opengl.Display.createWindow(Display.java:311)

at org.lwjgl.opengl.Display.create(Display.java:856)

at org.lwjgl.opengl.Display.create(Display.java:784)

at org.lwjgl.opengl.Display.create(Display.java:765)

at net.minecraft.client.Minecraft.a(Minecraft.java:390)

at net.minecraft.client.Minecraft.run(Minecraft.java:734)

at java.lang.Thread.run(Unknown Source)

--- END ERROR REPORT 38ac021e ----------

[luacs1998]

Bad video card drivers, nothing to do with Forge.

[OvermindDL1]

Update Video Drivers usually helps.

[Yaseen]

I did update

[darchangel89]

I have been experimenting with two different versions of 1.3.2 minecraft.  One has modloader (no forge), and the other has the new forge universal. In the forge version, any time I try to log into the game with a texture pack selected, the game crashes. I have to switch to default texture pack every time I log out, or I cant log in again without manually removing the texture packs from their folder. Once Im in the game, I can switch to a texture pack and it runs fine. I just cant log in with any pack selected.

Also, two mods Ive found that I cant get to work with forge are:

http://www.minecraftforum.net/topic/818831-132-fbl-flat-bedrock-layer/

http://www.minecraftforum.net/topic/943697-132gloughts-mods-superflat-132-no-grass-block-spreadingcrystal-storage/

 

I'll post more if I come across them.

Thanks for all your hard work!

[LexManos]

There should be nothing in Forge/FML that would cause your GL drivers to error like they are, we do not touch anything related to the initalization of the gl drivers.

Also I am unable to find anyone that can reproduce this error.

[Yaseen]

Idk I thought it might have something to do with forge cause My Minecraft works fine without forge and as soon as I put it on I get the error

[Aarchel]

You should try allocating more memory or less memory to Minecraft depending on the machine the solution could be either one.  In my case less memory has solved the same issue.  On these garbage computers where I work most of the time the default memory allocation of Minecraft causes issues so I just set it to 512MB and the problem goes away, although occasionally the system may crash if MC asks for more memory then it is allotted.  If you're using something like MagicLauncher or MultiMC it should be no problem to change the amount of memory allocated to Minecraft.  If you're modding your .jar directly then you will need to change the environment variables for Minecraft which I forgot how to do after I made a .bat file for it.

 

Personally I had the same issue with 1.3.2, Vanilla was fine but the moment I added FML/Forge it would just hang and crash with the Bad Drivers error.  I used to have the same problem with Vanilla MC back in Alpha 1.2 but since 1.0 I haven't needed to mess with the memory allocation.  I totally forgot about that and chimed in on an earlier thread about this issue, but just yesterday it occurred to me that Forge/FML might somehow be pushing up the memory requirement over Vanilla.  On any system I personally own this is not an issue, but with these garbage Intel Graphics from 3-5 years ago it's a problem.

 

 

 

 

[Yaseen]

  On 8/27/2012 at 10:30 PM, Aarchel said:

You should try allocating more memory or less memory to Minecraft depending on the machine the solution could be either one.  In my case less memory has solved the same issue.  On these garbage computers where I work most of the time the default memory allocation of Minecraft causes issues so I just set it to 512MB and the problem goes away, although occasionally the system may crash if MC asks for more memory then it is allotted.  If you're using something like MagicLauncher or MultiMC it should be no problem to change the amount of memory allocated to Minecraft.  If you're modding your .jar directly then you will need to change the environment variables for Minecraft which I forgot how to do after I made a .bat file for it.

 

Personally I had the same issue with 1.3.2, Vanilla was fine but the moment I added FML/Forge it would just hang and crash with the Bad Drivers error.  I used to have the same problem with Vanilla MC back in Alpha 1.2 but since 1.0 I haven't needed to mess with the memory allocation.  I totally forgot about that and chimed in on an earlier thread about this issue, but just yesterday it occurred to me that Forge/FML might somehow be pushing up the memory requirement over Vanilla.  On any system I personally own this is not an issue, but with these garbage Intel Graphics from 3-5 years ago it's a problem.

Im sorry I didnt understand. How did u fix it