Post by Aya Shameimaru on Mar 27, 2016 22:14:57 GMT -5
Greetings ^-^
So, a few of you told me that the modpack was very laggy, this is a problem for some computers, and thats why I made this thread. Its very important that you read all of it, for the sake of your computer :3
INSTALL OPTIFINE its easy
This pack contains Fastcraft, by Player, enabled by default. Fastcraft enhances Minecraft with increased performance. Bug reports being made directly to Mod Authors should state Fastcraft is enabled.
Render Distance:
The render distance is set to 6 by default.
-If you have problems with chunk loading lagg(12-20 fps), Change to a render distance of 4 or less
-If you dont have any lagg, and want to use up to 7 or more render distance, I suggest you allocate more than 2GB of RAM to your game
How to allocate more RAM
Why should I use more than 1GB of RAM?
Because Technic launcher has an integrated function, known as "permgen", that allows the modpack to load faster, the only way to affect permgen is to allocate memory to the launcher, anything between 1-2 gigs should be fine
Fancy or Fast?
Use Fast! This is very obvious, the more details the slower.
Smooth Lightning
Again, the more details, the slower your game.
Texture/Resource Packs
They dont affect your game that much, unless its a very detailed one.
Vsync
Dont use it! It limits your Graphics to output frames as high as the refresh rate of your monitor. But can introduce input lagg. It should only be used if you experience screen tearing, don't use it in any other case.
For Optifine users
Use OptiFine_1.7.10_HD_U_D3 Download here
You can change anything to get a better berformance or more details, the only limitation is not to use the Smooth or Multi-Core chunk loading.
Advanced by Player:
So, a few of you told me that the modpack was very laggy, this is a problem for some computers, and thats why I made this thread. Its very important that you read all of it, for the sake of your computer :3
INSTALL OPTIFINE its easy
This pack contains Fastcraft, by Player, enabled by default. Fastcraft enhances Minecraft with increased performance. Bug reports being made directly to Mod Authors should state Fastcraft is enabled.
Render Distance:
The render distance is set to 6 by default.
-If you have problems with chunk loading lagg(12-20 fps), Change to a render distance of 4 or less
-If you dont have any lagg, and want to use up to 7 or more render distance, I suggest you allocate more than 2GB of RAM to your game
How to allocate more RAM
Why should I use more than 1GB of RAM?
Because Technic launcher has an integrated function, known as "permgen", that allows the modpack to load faster, the only way to affect permgen is to allocate memory to the launcher, anything between 1-2 gigs should be fine
Fancy or Fast?
Use Fast! This is very obvious, the more details the slower.
Smooth Lightning
Again, the more details, the slower your game.
Texture/Resource Packs
They dont affect your game that much, unless its a very detailed one.
Vsync
Dont use it! It limits your Graphics to output frames as high as the refresh rate of your monitor. But can introduce input lagg. It should only be used if you experience screen tearing, don't use it in any other case.
For Optifine users
Use OptiFine_1.7.10_HD_U_D3 Download here
You can change anything to get a better berformance or more details, the only limitation is not to use the Smooth or Multi-Core chunk loading.
Advanced by Player:
Memory (RAM, -Xmx startup option)
- The default amount of memory Java allocates is insufficient for modded Minecraft. 1200 Megabytes is about the minimum reasonable (-Xmx1200M), 2000-3000 Megabytes should work well.
- Never allocate too much RAM to Minecraft, there has to be enough remaining for the Operating System, other programs and Minecraft's off-heap data. This off-heap data doesn't count towards the Xmx setting, it's used by program code, texture/geometry buffers etc. More memory also means garbage collection has to do more work.
- Some mods leak large amounts of memory. If your game happens to slow down over time, sometimes as soon as a few minutes in, you may be suffering from a memory leak. Sometimes this can be observed by watching "Used memory" (F3 screen). The value will frequently hug the upper ceiling (100%) and only decrease marginally each time, possibly accompanied by a lag spike.
General
- Use 64-Bit Java and the most recent version.
- Be careful with custom startup options, many of those aren't helpful.
- The FastCraft config provides extra tweaking options.
Client
- Reduce the view distance as needed, helping CPU, GPU and RAM usage.
- Build performance intense structures (farms, effect heavy or dynamically rendered blocks etc.) further away. Chunks next to the player are the most expensive, they don't have their render cache updates throttled and the game won't try to cull costly geometry. Moving structures completely out of the view distance is even better.
- Mini map mods have severe issues regarding performance and/or faulty threaded world accesses.
- Disable V-Sync, doing so may cause tearing artefacts, but it prevents the fps to be limited to a divisor of your monitor's refresh rate (e.g. 60/30/20/15 fps).
- Try setting "Max Framerate" to unlimited.
- Reducing particles, turning clouds off, setting smooth lighting to off, disabling mip maps (=level 0) or using the "fast" graphics mode can help. -FastCraft
- The default amount of memory Java allocates is insufficient for modded Minecraft. 1200 Megabytes is about the minimum reasonable (-Xmx1200M), 2000-3000 Megabytes should work well.
- Never allocate too much RAM to Minecraft, there has to be enough remaining for the Operating System, other programs and Minecraft's off-heap data. This off-heap data doesn't count towards the Xmx setting, it's used by program code, texture/geometry buffers etc. More memory also means garbage collection has to do more work.
- Some mods leak large amounts of memory. If your game happens to slow down over time, sometimes as soon as a few minutes in, you may be suffering from a memory leak. Sometimes this can be observed by watching "Used memory" (F3 screen). The value will frequently hug the upper ceiling (100%) and only decrease marginally each time, possibly accompanied by a lag spike.
General
- Use 64-Bit Java and the most recent version.
- Be careful with custom startup options, many of those aren't helpful.
- The FastCraft config provides extra tweaking options.
Client
- Reduce the view distance as needed, helping CPU, GPU and RAM usage.
- Build performance intense structures (farms, effect heavy or dynamically rendered blocks etc.) further away. Chunks next to the player are the most expensive, they don't have their render cache updates throttled and the game won't try to cull costly geometry. Moving structures completely out of the view distance is even better.
- Mini map mods have severe issues regarding performance and/or faulty threaded world accesses.
- Disable V-Sync, doing so may cause tearing artefacts, but it prevents the fps to be limited to a divisor of your monitor's refresh rate (e.g. 60/30/20/15 fps).
- Try setting "Max Framerate" to unlimited.
- Reducing particles, turning clouds off, setting smooth lighting to off, disabling mip maps (=level 0) or using the "fast" graphics mode can help. -FastCraft