Hello, i'm new here to the forums so sorry if this is in the wrong spot. I love this mod pack. But it extremely frustrating to go into the Twilight Forest. After about half an hour in there I start getting extreme lag and then I crash. Is my computer not able to handle it or is this a known problem? I'm assuming it's my computer.
Extreme lag then crash.
- Thread starter Djharts
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
You should have the log in the FTB console at the very least.
I have to admit I have no idea without a log, because I don't notice any difference in RAM, or CPU that could cause that kind of lag.
I have to admit I have no idea without a log, because I don't notice any difference in RAM, or CPU that could cause that kind of lag.
I can't really get you a log because when it crashes it just gets stuck on the Shutting Down Internal Server screen. I can't move my mouse so I can't copy the log. It literally only let's me play for about 30 seconds before crashing. Should I re-download?
Oh, that sound more like a question of you telling Minecraft to use more RAM than you actually can allocate to it then.
You should check how much your computer uses without Minecraft, how much you have in total, as well as how much you allocated to Minecraft in the launcher.
If your whole computer freezes because of the game, that is the most plausible explanation.
As a subsidiary question, are you using a texture pack that is higher resolution than the default one?
You should check how much your computer uses without Minecraft, how much you have in total, as well as how much you allocated to Minecraft in the launcher.
If your whole computer freezes because of the game, that is the most plausible explanation.
As a subsidiary question, are you using a texture pack that is higher resolution than the default one?
Can we PLEASE get a log? In the options pane in the launcher, you should to enable 'Show Console?' Another window will open up, and it will allow to automatically pastebin the log.
In the folder where you placed the FTB launcher, there is probably a Direwolf20 folder (unless you changed you install directiry). Look in that, open the "minecraft" folder, and give us the file called "ForgeModLoader-client-0.log". After you reboot after your game crashes.
There should also be a crash-reports folder inside the minecraft folder. Inside there should be a few more crash reports, post those too.
This is a known problem with OSX and FTB. Add this to your advanced options.
Code:
-XX:PermSize=128MIn general, there are no crash logs for this. The forge log may briefly croak about the world being leaked, but generally it feels like some sort of epic losing battle of the garbage collector and the process is not responsive even to kill signals. The log will helpfully say it's so out of memory that it cannot kill itself.
The minecraft we use is not very stable in single player on any platform, as far as I can tell from working with the people on my server. Prefer a client-server (I get better performance running a sever manually on the same computer!) and increase the permgen size on said server.
And if you want to know who the culprit is: it really seems like NEI is strongly related to crashes.
The minecraft we use is not very stable in single player on any platform, as far as I can tell from working with the people on my server. Prefer a client-server (I get better performance running a sever manually on the same computer!) and increase the permgen size on said server.
And if you want to know who the culprit is: it really seems like NEI is strongly related to crashes.