Game hang on launch

[DaraSilverDragon]

Title:

Game hang on launch​

Launcher Version:

1.4.6​

Modpack:

Infinity (also occurs on all others tested)​

Modpack Version:

1.3.4 (also occurs on all others tested)​

Log Link:

http://paste.feed-the-beast.com/view/6125d597​

Details of the issue:

After hitting Launch, the launcher disappears as normal - then the console gets to an error about aromacore and codechickencore and the whole thing just stops
The javaw.exe instance remains in the process list using resources, but nothing ever pops up after.
I also tested this with the 1.3.3 and 1.4.1 versions of the infinity pack, the recommended versions of the Direwolf20 and Trident packs, and the Infinity pack as downloaded from the Curse launcher (which adds it's own Java 8 u25 runtime), and the same exact thing happens every time no matter what the download.
I also tried fresh installs of Java 8 u45 and Java 7 u79, with the same exact results.

disabling the aromacore modremoves that message from the chat log, but disabling codechickencore (as you would imagine) breaks things considerably. I also tried disabling the native codechickencore and replacing it with downloads of everything from v28 through v37, all with the same result of zero change.

So... Help?​

 

[DaraSilverDragon]

It should also be noted that I tested out my vanilla instance with the javapath set to the same javaw.exe file as FTB, and it worked fine. The issue seems to be with how the launcher is handling core mods.

 

[DaraSilverDragon]

bump >>

 

[Lord Laraby]

[02:18:27] [DEBUG] LaunchFrame.runGameUpdater:604: installPath: F:\Program Files (x86)\minecraft\data\FTB

This is likely your problem. You really do not want to install into a space or '()' containing path. I read the log and noticed the error relating to install folder, so it is perhaps obvious what caused the issue.

 

[DaraSilverDragon]

[02:18:27] [DEBUG] LaunchFrame.runGameUpdater:604: installPath: F:\Program Files (x86)\minecraft\data\FTB

This is likely your problem. You really do not want to install into a space or '()' containing path. I read the log and noticed the error relating to install folder, so it is perhaps obvious what caused the issue.

Yeah, but that's been my install directory for YEARS. I've never once had a problem with it until just this week. Nothing changed there.

Plus I have my vanilla game installed in the same directory one level up, and that still runs just fine.

 

[Lord Laraby]

I'm obviously clueless then. Carry on.

 

[DaraSilverDragon]

Solved.
Apparently the Evolve client (www.evolvehq.com) updated recently, and was disrupting how some of the coremods were being read.
Closing the program and making the modpack do a forced update allows the game to run normally again.