plowmanplow

If you have only forge in your pack and the video is looking messed up, it's likely something wonky with your PC. Drivers, hardware compatibility, Java messed up, something.

JVM Flags: 4 total; -Xmx3072M -Xmx3072M -XX:PermSize=3072m -XX:MaxPermSize=3072m You don't need to have more than 256m of PermSize for this modpack. Setting it to 3G is "bad". You need to update to the latest Cauldron for 1.6.4. There's no point in trying to resolve an issue which may be fixed in an updated server JAR.

You have included too much in your bin folder. Only the modpack.jar file should be in the bin folder. Your Star Wars and OptiFine mods are out of date. I was able to add your pack to my launcher and start a SSP world.

How much memory are you allocating to the client? How much is in your PC? Big packs are piggys

@rockbreath9: While idfixminus can help you get started with the resolutions, it is my experience that you are better off in the long run just fixing them correctly. idfix I have seen major issues when dealing with large and complicated packs. Also, any time you want to have a server for a pack it is vital that you don't use an automated ID fixer.

You have Not Enough Items installed but are missing the required dependency mod CodeChickenCore.

This may help you:

My suggestion is to start with ONLY Forge in your modpack. If that works fine start adding mods in singly or in logical groups (mods with dependencies) until it stops working.

Kind of need this to figure out what's going on.

I would HIGHLY recommend you start from the updated Hexxit beta which is 1.6.4. Making a 1.5.2 pack is an exercise in frustration at this point.

You have cut out most of the useful information from the crash report. Please provide the full crash report (thank you for using a spoiler tag) and the API URL for your custom modpack.

What is your CPU load looking like when this lag happens? It is starting to look like there is something else going on in the background that is sucking down resources.

Just as a test, I set up a new installation of Solder and linked it to a different account I had. Everything worked as expected. Your links looks correct and are returning the correct information. Not sure what else to suggest.

You need to update your Java. You are currently on Java 7_45. The current version is 7_67. Update your video drivers if possible to the latest version available. Update your Forge version to at least 1.7.10 B1207. Your pack works fine for me. I suspect it is something with your local system rather than something with the modpack.

In Forge/MC 1.6+ all mods go in the "mods" folder.

You could use the CoFH config files from AoTB as a reference.

@Braiden89: Don't hijack someone else's thread. Start a new one and provide a link to the API URL for the client modpack you are using.

Note that it says "?dl=1" not "dl=1". There is a question mark in there.

Client Pack: The "Hats" folder should not be included. This folder is created after the pack is launched for the first time. You have no config files in your modpack archive. This is always bad and a fatal oversight when attempting to set up a server for a client modpack. Without the config files there is no way to ensure that the configs are synchronized between the client and server. Without config files you cannot adjust things like balance between mods, mod interactions, etc. Always include config files. You seem to have renamed all the mod files to remove the version information. This is quite bad because it makes it nearly impossible to maintain or debug a pack. You really should re-download all the mods and leave the file names alone. This post on getting mods may help you: Once you fix the above issues you are ready to start on the server. The reason I say that you need to fix the issues is that you will have no end of heartache trying to set up and maintain a server for the client pack if you do not. This post should walk you through making a server for your pack once it is fixed:

What do you mean by "lag": Does it run well and then pause for a noticeable period? Do you have block break/place lag? Is your FPS bad? Do you have chunk loading lag? Are some chunks not loading? The reason I ask these questions is that if you are truly able to allocate 3G in the launcher, you have the current Java 7 JRE and your stated specs it should run wonderfully. Something is "odd".

You have at least a few mods that are 1.7.2 versions where there are 1.7.10 versions available (VoxelMap, EnchantingPlus_beta). The 1.7.10 VoxelMap may require LiteLoader. The reports I'm seeing about that error indicate that it might be related to having older 1.7.2 mods in the pack.

@Braiden89: Don't hijack ancient threads for new problems. MCPC+ is now called Cauldron so that is what you want.

2014-08-22 12:18:41 [INFO] [ForgeModLoader] Forge Mod Loader version 6.4.49.965 for Minecraft 1.6.4 loading You didn't update to the latest Forge for 1.7.10. This is your binmodpack.jar file. Additionally, make sure you have changed your pack settings to be a MC 1.7.10 modpack. Providing the API URL for the pack will allow us to diagnose things more easily.

I don't recall ever seeing anything like that. Where do you see that restriction?

Are you correctly putting the API KEY from your Configure Solder API page into the solder.php config file?