Windows .exe Mod disabling bug with 1.3.0 launcher

[Gemoron]

Hello

I try to play the new DW20 pack but every time I start it minecraft closes with the following error:

>---- Minecraft Crash Report ----
>// I just don't know what went wrong
>
>Time: 15.12.13 11:32
>Description: Registering texture
>
>java.lang.OutOfMemoryError

My PC has 3GB ram with 1 GB reserved for Minecraft.

As I can't load all the graphics I started to deactivate some of the larger mods like Biomes O plenty or Ars Magica. It worked with the previous launcher.

The bug:

I used the Mod Pack Editor to deactivate some of the Mods but the mod shows up as enabled after every restart (compare to uploaded screenshot). I can't activate nor deactivate them anymore.

Is this a bug or working as intended?

Does anyone has another workaround for my Out Of Memory Error? I used -xmx and -xms already.

 

[UniZero]

You will need more memory to be able to play the dw20 at least 2gb. But since you only have 3gb in total that is not going to be possible. I would suggest, unless you want to get more ram for your system, waiting for the new lite pack to appear.

If you only have a 32bit os then adding more ram won't help because you will only ever be able to allocate 1gb of ram to the launcher.

There may be a fix coming for the memory problem but at present the new packs require a lot of memory.

 

[lavarthan]

Edit3: Look here for Jadedcat's video about this issue. Towards the end might be the reason for your issue. The one about multiple minecraft or launcher still being open.

Edit2: -xmx is already passed by the launcher and will give you an error if you try to use it unless you do it on a server.

Edit: Sorry not sure about not being able to disable mods. Try following the recommended setup guide for the launcher carefully and precisely.

I agree with UniZero. Try disabling mods like MapWriter and opis if you have not already. I've heard those use a lot of memory. You might also have to do without Biomes O' Plenty or disable about half the mods. 102 mods is a lot for a 32bit system to handle.

 

[UniZero]

lol larvarthan lots of edits.

 

[Gemoron]

Thanks UniZero and larvathan for your help.

My problem is not a duplication problem, it is about disabling mods to lower requirements.

I am currently trying to fix the problem. Here are my steps:

-I uninstalled FTB and the whole FTB-folder, downloaded a new launcher file.
-Downloaded and started the new DW20 pack. It crashed Minecraft as expected.
-Restarted the launcher, moved mods I don't want to disabled. this time I added Opis
All mods I disabled are now called modname.zip.disabled.
-Started the pack again. After another crash I checked the folder again. now I see the disabled and the nondisabled filed.

I guess it is the duplicate problem does take an effect here by replacing the now missing file. I expected the launcher to see both, disabled and available files before downloading again.

Okay, back to start, unninstall, redownload.

Now I modified the modpack how I want it to be using the Mod Pack Editor and renamed the modpack folder.
Well, now I need to find the Minecraft start data to start the modpack without using the launcher and it should work.

SUMMARY:
The Edit Modpack function is broken! Mods can't be disabled.