My automatic Variants still will not run correctly. It keeps pooping up with the Heap error but when I actually run the 32-bit MoreHeapSpace through ModOrganizer, I run it and then it immediately closes without running the patcher. Nothing happens a all. When i go into the file to run it, it will run the patcher fine but it refuses to run through Mod Organizer. The thing is that I have had not troubles with either ASIS or Dual Sheath Redux as those ran perfectly fine.
Could I get a video on this because I run the file and AV pops up with no textures and when I exit I get an error. What am I supposed to do? This is giving me a ginormous headache so im going to sleep for a few hours and try to figure it out later.
Not too many videos out there. Sorry. This is only a memory fix- however there is a lot of good general resource over here. Don't forget: "If you have a 64 bit operating system, make sure you download both the 32 bit and 64 bit versions of Java. This should fix issues with the java program not functioning in some cases." Hope it helps.
The "32bit" batch file will tell the Java instance to use a max of 1GB of RAM and the "64bit" file a max of 2GB of RAM; which is great considering that the default max is 256MB of RAM! A slight tangent but: if you've ever setup a custom batch file to launch a Minecraft server, you can use many of those same options/flags here but you must keep the "-NOSTREAM" flag in order for it to play nice with Mod Organizer and NMM, or anything that uses virtual file systems or child processes, etc.
@lmstearn - If you wanted to have the "64bit" batch file prefer to run in 64-bit Java workers, you can use the "-d64" option. You may also want to consider not only configuring the max RAM with -Xmx but also the starting/initialization RAM with an -Xms option (e.g. -Xms1024M). By default, both x86 and x64 Java workers only start off with 64MB of RAM allocation and that can also be a source of issues.
Oh, and before anyone asks, you MUST use 32-bit Java and a max of 1024MB of RAM if you're using Mod Organizer. In that case, you'd edit the saved executable and in the "Arguments" field put "-Xmx 1024M " before the -jar option (with a space in between the two) and then at the end, add another space and then put in "-NOSTREAM". So the arguments field would look something like this:
How does this work do I download with manager? screenshots would really help as i'm a bit newbie to modding thank you and love the mod (the heap space error making me cows blue)
Give Feedback
22 comments
Thank you so much works perfectly.
THANK YOU!, THANK YOU SO VERY MUCH!. Now i can finally run this fucking .jar!!!
Don't forget:
"If you have a 64 bit operating system, make sure you download both the 32 bit and 64 bit versions of Java. This should fix issues with the java program not functioning in some cases."
Hope it helps.
The "32bit" batch file will tell the Java instance to use a max of 1GB of RAM and the "64bit" file a max of 2GB of RAM; which is great considering that the default max is 256MB of RAM! A slight tangent but: if you've ever setup a custom batch file to launch a Minecraft server, you can use many of those same options/flags here but you must keep the "-NOSTREAM" flag in order for it to play nice with Mod Organizer and NMM, or anything that uses virtual file systems or child processes, etc.
@lmstearn - If you wanted to have the "64bit" batch file prefer to run in 64-bit Java workers, you can use the "-d64" option. You may also want to consider not only configuring the max RAM with -Xmx but also the starting/initialization RAM with an -Xms option (e.g. -Xms1024M). By default, both x86 and x64 Java workers only start off with 64MB of RAM allocation and that can also be a source of issues.
Cheers,
~Morbic
-Xmx1024M -jar "X:\<your path here>\Automatic Variants\SkyProc Patchers\Automatic Variants\Automatic Variants.jar" "-NOSTREAM"
It looks like the NOSTREAM flag is a construct of the Skyproc engine. Not a lot of info available on it unfortunately.