Can't run any modpack

  • Tech Support section is for getting help with FTB related problems. If there's a repeatable issue that can be labeled as a bug, then please use the issue tracker for the pack or the app at GitHub issue trackers - If there's no repository for a pack that means that the pack is old and/or will not be updated. Bugs for older packs will not be fixed, unless they are critical.
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Haider

New Member
Jul 29, 2019
4
0
0
Title:
Can't run any modpack
Launcher Version:
MAC 1.4.8
Modpack:
All FTB & 3rd party modpacks
Modpack Version:
1.6.4/1.7.10
Log Link:
Details of the issue:
MacBook Pro (Retina, 15-inch, Mid 2014)
Processor 2.5 GHz Intel Core i7
Memory16 GB 1600 MHz DDR3
GraphicsNVIDIA GeForce GT 750M 2048 MB

I just changed the ram usage from 4gb to 6.5gb(of course I changed it before from 1gb to 4gb)
after the problem I return it to 4gb
 

Moasseman

New Member
Jul 29, 2019
1,679
-2
1
Did it work before you changed the RAM allocation to 6.5? Because the only thing I see with a quick glance is that you have an "_" in your file path (Bo_7dra). That's never a good idea, since special symbols are known to cause issues.

I suggest you move the installation somewhere else.
 

Haider

New Member
Jul 29, 2019
4
0
0
Did it work before you changed the RAM allocation to 6.5? Because the only thing I see with a quick glance is that you have an "_" in your file path (Bo_7dra). That's never a good idea, since special symbols are known to cause issues.

I suggest you move the installation somewhere else.
Yes it did,even with the"_" in it.

I will try to change the installation folder.

Thanks for your response.:)
 

Haider

New Member
Jul 29, 2019
4
0
0
Did it work before you changed the RAM allocation to 6.5? Because the only thing I see with a quick glance is that you have an "_" in your file path (Bo_7dra). That's never a good idea, since special symbols are known to cause issues.

I suggest you move the installation somewhere else.
Unfortunately it didn't work:(
 

Haider

New Member
Jul 29, 2019
4
0
0
I just Shutdown the macbook and start it again and it works....Before you blame me, yes I did restart and didn't work, but I didn't know that shut it down completley will work.
Weirdo_O