Advertisement
CatRabbit499

How to patch textures!

Jun 9th, 2016
305
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.88 KB | None | 0 0
  1. 1. Download a copy of Sphax 1.5.2 from bdcraft.net in your desired resolution (512x is EXTREMELY demanding, a beefy GPU is advised)
  2. 2. Unzip it and create a new folder called "mods" in the top level directory
  3. 3. Google "<Mod Name> Sphax" and download the 1.5.2 version in your desired resolution
  4. 4. Merge the downloaded mods folder with the "mods" folder you created earlier in your texture pack
  5. Note: If there is no 1.5.2 version you will have to do some more work to patch that mod's textures:
  6. - Download the closest version number to 1.5.2 (later patches are preferred)
  7. - Unzip the downloaded mod patch
  8. - Open your mods folder in your /.technic/modpacks/bigdig/ directory
  9. - Either extract the JAR with the default extractor by saving it as a ZIP file or open it with a utility such as WinRAR or 7-Zip
  10. - Find the folder called "assets" (1.6+)
  11. Note: If that folder does not exist you will have to do even more work to patch that mod's textures:
  12. - Find the directory(s) where the mod stores its texture files.
  13. - Mirror the folder structure(s) in your extracted Sphax texture pack (it's OK to merge folders in this process)
  14. - Continue with the directions as instructed.
  15. 5. Place your patched pack in the texturepacks folder of your bigdig directory
  16. 6. Switch to your patched pack ingame :D
  17.  
  18. WARNING: If you are going to be hot swapping in new textures you MUST switch to default textures before you click on your pack again or you will run out of RAM and CRASH. This crash is because of the way the Minecraft TextureManager switches packs; it loads every texture into memory again before it unloads the old textures. The larger number of mod patches you have installed the more RAM it tries to use, and if Technic runs out of memory you crash. Don't be lazy. Its just not worth it. I have crashed my client with this before; it used up every bit of the 15G that I have dedicated to Technic.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement