I'm not entirely sure if I should have put this in either here or support, but support doesn't have a section for the launcher so i'm putting this here. In packs that use the new Forge Launcher Loading Screen (Horizons Daybreaker for example), the loading screen mod included with the custom launcher conflicts HEAVILY. By that I mean at stage 3 of the forge loading screen, it just starts taking forever and starts flickering between the forge and mym launcher loading screen and ends up taking forever to finish. With the MyM launcher startup times can take up to 15 minutes, while on Curse, it only takes 1-2 minutes max. Basically what i'm suggesting is removing the mod that adds the extra loading screen.
This: It pops up when using the mym launcher but not curse, and I'm not sure what mod adds it, so I assume it's launcher related.
This is liteloader which is required for tabby chat and the other liteloader mods. We can't remove it. The extra loading time is odd and most likely depended to your system. Is there anything special about it?
I just realized that kind of yes it does. When Forge hits stage 3, the liteloader thing starts doing it's thing, then when it finishes, it goes back to the Forge one which then finishes it's thing. Anyway, here's a log. I cut out all of the bits before "Phase 3" as they weren't really important. But as you can see it just starts to do nothing for minutes on end, and if I launch it on curse, it takes waay less time.
Interesting it is taking nearly 5 minutes for liteloader to fully load all its mods. What are your computer specs? (cpu, ram, disk the instances are on/also how full )
I would doubt it'd be my specs, but here they are anyway: CPU: i7-4700MQ @ 2.4 GHz Graphics Card: GTX 770M RAM: 16 GB Hard Drive Space: 115 Gigs free of 688.
Also check your java version and bit (32 or 64). I had this issue as the launcher was preferring 32 over 64 (have both). I fixed it by specifying the path to 64 bin jre and it loads quick and fine now.
I added a path to my 64 bit java since there wasn't a path set before, however it did not fix the problem.
@Billybobjoey does it change something if you change loadingbar=true to false in /minecraft/liteconfig/liteloader.properties?
Currently trying everyone's solutions. Without changing my memory settings, it does not. The loading bar still flickers between the two. This made it not hang for as long, but liteloader is still taking ages. Think I'll just stick with Curse for now, I don't really use Tabbychat or the Voxel mods anyway.
could you please open up the terminal (cmd.exe on windows), type in "java -version" and screenshot the output?
Something surprising happened. I was going to take a video of both instances' startup time, and of course when I get it on video it works fine now. Don't know what changed, but it's suddenly quick now. Oh well. Thanks for everyone's help.
