8 replies to this topic

[Jonnehh]

Hi all!

 

So I've been having this problem for a while and I thought that maybe it would get fixed with the FTB Launcher update. Sadly, i was wrong.

 

Everytime I try to "Launch" the FTB Monster modpack (My launcher is 100% up-to-date) it starts up the Minecraft 1.6.4 client, but then says "Mineraft 1.6.4  (Not Responding)". Does anyone know how to troubleshoot this? Because I'd realy like to play FTB Monster.

 

Thanks all, and I hope this might help others!

 

Fellow Minecrafter

Jonnehh

[DiamondDoctor]

Can you post your console log? Also, make sure:

You have AT LEAST 2gb of ram allocated to the launcher (Options menu)

You have a 64bit os (control panel>system and security>system)

You have 64bit java

You post the log here with spoiler tags ([spoiler] and [/spoile r) or on pastebin

[timrem]

Jonnehh, how long have you waited for the game to launch? Even on a good computer, loading all the mods in Monster can take a couples minutes. During parts of the launching process, the Minecraft window will be non-responsive, but this is a standard occurrence. Make sure you have the FTB console open; as long as things are updating there, it's fine for the Minecraft window to say "Not Responding".

[DiamondDoctor]

Jonnehh, how long have you waited for the game to launch? Even on a good computer, loading all the mods in Monster can take a couples minutes. During parts of the launching process, the Minecraft window will be non-responsive, but this is a standard occurrence. Make sure you have the FTB console open; as long as things are updating there, it's fine for the Minecraft window to say "Not Responding".

Especially in monster. there are a LOT of mods, those that you dont use should be removed to improve performance.

[Jonnehh]

Jonnehh, how long have you waited for the game to launch? Even on a good computer, loading all the mods in Monster can take a couples minutes. During parts of the launching process, the Minecraft window will be non-responsive, but this is a standard occurrence. Make sure you have the FTB console open; as long as things are updating there, it's fine for the Minecraft window to say "Not Responding".

I waited for at least twenty minutes. I have quite a good computer and I can load Unleashed instantly.

[Jonnehh]

Can you post your console log? Also, make sure:

You have AT LEAST 2gb of ram allocated to the launcher (Options menu)

You have a 64bit os (control panel>system and security>system)

You have 64bit java

You post the log here with spoiler tags ([spoiler] and [/spoile r) or on pastebin

 

I have 2GB of RAM allocated to it yes. I am currently rrunning Windows 7 with 64-bit Java. I have 64-bit Java. Now it won't even let me launch the client.

[DiamondDoctor]

hmmmm.f if you can spare more than 2 maybe do that

open task manager and change the priority of javaw.exe. use the one using more ram

i found this. it might fix it. if not, undo it.

[dgelessus]

hmmmm.f if you can spare more than 2 maybe do that

open task manager and change the priority of javaw.exe. use the one using more ram

i found this. it might fix it. if not, undo it.

Gee thanks, I think you just solved the problem for over nine thousand crashes. That's where that broken RAM parameter comes from.

 

In case you're wondering, DO NOT DO WHAT IS DESCRIBED IN THAT ARTICLE. It will most certainly prevent any modded Minecraft from starting.

[DiamondDoctor]

Gee thanks, I think you just solved the problem for over nine thousand crashes. That's where that broken RAM parameter comes from.

 

In case you're wondering, DO NOT DO WHAT IS DESCRIBED IN THAT ARTICLE. It will most certainly prevent any modded Minecraft from starting.

I was worried about that. that -512 number looked strangely familiar