DigiDak Posted July 6, 2013 Share Posted July 6, 2013 My Big Dig gets stuck on the mojang screen for about an hour before it will start. Link to comment Share on other sites More sharing options...
chami Posted July 6, 2013 Share Posted July 6, 2013 1. This is the wrong section for this, might want to go to the bug report section. You also give absolutely no information as to what computer you're using, what OS you're running, and so on and so forth. All that is important if you want people to actually figure out what's going wrong. 2. That being said, open the Technic Launcher, click on the cogwheel in the upper-right hand side, bump up the allocated ram to 2 GB and make sure "Increase PermGen Size" is checked. If it still doesn't work after that, post a bug report with a crashlog in the bug report section. Link to comment Share on other sites More sharing options...
DigiDak Posted July 6, 2013 Author Share Posted July 6, 2013 OK Well, I'm on windows 7 64 bit, a Intel Centrino 2 processor, a GeForce 9600m GT. with 3.75GB ram and the 7u25 version of java (32 and 64bit installed). I have allocated 3 GB of ram to the launcher and I have Checked off "Increase PermGen Size". Log:http://pastebin.com/wxsWH6JK Link to comment Share on other sites More sharing options...
chami Posted July 7, 2013 Share Posted July 7, 2013 As far as I recall, if the Mojang screen shows up, it's out of the Launcher's hands. You might want to post the latest Forge logs, not the Launcher logs. It should be in the big dig folder. Unfortunately, I'm not good with Windows - hopefully someone can help you on the Windows end. Link to comment Share on other sites More sharing options...
Thoran Posted July 7, 2013 Share Posted July 7, 2013 Reset the Big Dig Pack, sounds like one of the mods got corrupted. Open the Technic Launcher, click the gear button next to the BigDig icon (its the screen you can change your version in) and click on Reset Pack. This will delete everything in the BigDig folder and force a new download for the files. It should be in the big dig folder. Unfortunately, I'm not good with Windows - hopefully someone can help you on the Windows end. Its the same on windows on linux thanks to Minecraft being a Java program. Link to comment Share on other sites More sharing options...
Vivacity Posted July 7, 2013 Share Posted July 7, 2013 Reset the Big Dig Pack, sounds like one of the mods got corrupted. Open the Technic Launcher, click the gear button next to the BigDig icon (its the screen you can change your version in) and click on Reset Pack. This will delete everything in the BigDig folder and force a new download for the files. Its the same on windows on linux thanks to Minecraft being a Java program. I'm fairly certian directly isn't the same. It would be %appdata%/.technic/bigdig on windows Link to comment Share on other sites More sharing options...
Thoran Posted July 7, 2013 Share Posted July 7, 2013 I'm fairly certian directly isn't the same. It would be %appdata%/.technic/bigdig on windows Thats only the default path, you can set it to be E:\Tekkit\bigdig or whatever. But I wasn't talking about that, i meant the files inside the .technic folder including bigdig. I this case it means the Forge Logfiles are directly in the bigdig folder on both Linux and Windows. Link to comment Share on other sites More sharing options...
Vivacity Posted July 8, 2013 Share Posted July 8, 2013 As far as I recall, if the Mojang screen shows up, it's out of the Launcher's hands. You might want to post the latest Forge logs, not the Launcher logs. It should be in the big dig folder. Unfortunately, I'm not good with Windows - hopefully someone can help you on the Windows end. The Mojang Screen showing up means it was able to load forge and core mods. Everything else is loaded afterwards and could be caused by anything. Link to comment Share on other sites More sharing options...
DigiDak Posted July 19, 2013 Author Share Posted July 19, 2013 Well i'm back and I reset my pack and I'm now on launcher version 253 and here's the new logs (it takes 45 minutes to start up.) http://pastetool.com/pastebin/119009.htm Link to comment Share on other sites More sharing options...
JCarr1028 Posted July 22, 2013 Share Posted July 22, 2013 I found out the problem: Forrestry! DELETE IT! Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now