Jump to content

Recommended Posts

Posted

I recently made a custom 1.7.10 mod pack but when I hit the play button it looks like it loads, disappears, and then reappears. I have tested all of the mods in the actual minecraft launcher and they all worked together so it is a problem with the launcher. I have also made another 1.6.4 mod pack that works fine so it might be a problem with a 1.7.10. Any help would be appreciated!

Here are the links to my Technic Pack Download and the Drop box.

  • Discord Moderator
Posted
  • Your pack settings indicate a 1.7.10 modpack but you have included the 1.6.4 version of Forge.
  • You should not be including the /journeymap/ folder in your pack. This will overwrite local player options when the pack updates.
  • You should be using the latest beta of AE2rv2.
  • You should not be including the IC2 API in your pack.
  • Millenaire mod is not installed correctly. Open the ZIP and follow the author's instructions.
Posted

Thank you those problems cleared up the issue I had with it disappearing than reappearing. Now I for some reason have a new issue, the launcher will disappear and then the minecraft loading screen will start then for some reason it crashes and goes back to the launcher. I have retested it in the real minecraft launcher and it worked fine even with all the mod changes. Thanks in advance!

New link to Dropbox

  • Discord Moderator
Posted
  • You have changed your modpack archive but have not changed/incremented the pack version number. The Launcher is not notified that a new version of the pack is available unless the pack version number changes.
Posted

Updated the pack version and still not working, and by the way what forge download should I be using in the bin folder installer or universal because I have been using universal.

  • Discord Moderator
Posted

You should be using the Forge universal binary JAR file.

As for your pack, I am able to add it to my launcher and start the pack. If you are not able to do so please provide your logs (crash-report, FML logs, etc.) in a pastebin service and put the link here.

Posted

Actually that might not be the right here I got that one from the the actual launcher I found this one from the the modpack folder in my .technic. Logs

  • Discord Moderator
Posted

Looks like your graphics card or drivers don't like one of the mods in your pack. Are you certain your video drivers are up to date?

  • Discord Moderator
Posted

Scratch that. I missed this the first time through:

[b#283] 2015/03/16 12:44:40 [iNFO]  java.lang.OutOfMemoryError

How much memory are you allocating in the Launcher?

Posted

I do not know how to add more memory and if you could tell me that would be great. I did however find the problem, I had a old version of java like version 7u75 and it was 32 bit even though my computer is 64. So I updated to the new java version 8u40 and it is know working but I would still like to know how to get more memory!

  • Discord Moderator
Posted

That's not going to be enough to launch a pack of that size. You'll need to allocate 2G. I also highly recommend setting your Launcher to close after starting a pack and keep as few other things running as possible. You only have 4G of RAM total and between the custom modpack and Windows there won't be a lot left over.

  • Discord Moderator
Posted

Ahh, if you have 8G then setting the Launcher to close isn't an issue.

Launcher Options (top right) -> Java Settings (2nd tab) -> Memory (set to 2GB)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...