It's working great for me except for the annoying lag spikes I get every 15 seconds. You don't add a shaders folder since it's already there. Just replace the files inside the folder. I put the bumpmapping pngs at GLSL zip and texture pack zip just in case. I didn't check the better grass.
I added the shaders folder w/ the bumpmapping shaders because the default shaders don't have bumpmapping enabled.
I don't think it's my installation that's wrong though :/
For the impatient people out there, the terrain_nh and terrain_s are available for direct download.
Note that those are just the 2 files, so you will need to have a bit of a understanding on how to install GLSL and add shaders that allow parallax occlusion to work.
If you don't, wait untill they will appear as download in this thread, possibly with a vid/text tutorial. Since setting GLSL up is more difficult then just setting up a texturepack, be warned =P.
Blargh...
I had MCPatcher working fine with GLSL yesterday, but now that you release the awesome bumpmapping it refuses to launch.
Black Screens ftl...
Must.... fix....
EDIT:
OK, so maybe I'm just making a really stupid mistake.
Recapping what I did.
First, I open MCPatcher, everythings checked (HD Textures, HD Font, Better Grass).
I then add the GLSL folder, put the two bumpmapping PNGs into a zip and add that, add the shaders folder to a zip and add that, put them all at the bottom, and click PATCH.
Then I go in-game, it launches fine and goes to the main menu.
Then when I go to texture packs and choose an HD pack the menu disappears, I only see the background, and eventually it goes black.
I get this error
java.lang.NoSuchMethodError: ji.setTileSize(Lnet/minecraft/client/Minecraft;)V
at ik.a(SourceFile:36)
at de.a(SourceFile:124)
at lg.a(SourceFile:164)
at ft.a(SourceFile:68)
at px.b(EntityRenderer.java:451)
at net.minecraft.client.Minecraft.run(Minecraft.java:534)
at java.lang.Thread.run(Unknown Source)
Oh, and I can't use the Test Minecraft button in MCPatcher, I get this error
Launching C:\Users\Administrator\AppData\Roaming\.minecraft\bin\minecraft.jar
java -cp C:\Users\Administrator\AppData\Roaming\.minecraft\bin/minecraft.jar;C:\Users\Administrator\AppData\Roaming\.minecraft\bin/lwjgl.jar;C:\Users\Administrator\AppData\Roaming\.minecraft\bin/lwjgl_util.jar;C:\Users\Administrator\AppData\Roaming\.minecraft\bin/jinput.jar; -Djava.library.path=C:\Users\Administrator\AppData\Roaming\.minecraft\bin\natives -Xmx2048M -Xms512M net.minecraft.client.Minecraft
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
Minecraft exited with status 1
I suspect this is all related to my Windows installation being corrupted.
I did get my hands on that USB drive, but I plan on getting two new hard drives, and would wind up reinstalling windows on those anyway.
So rather than doing it twice, I'm just going to wait the 15 days to get them, and then install it then.
So here goes 15 days without Windows functionality.
I do have the 1.5GB to allocate. I tried 1GB too and the same thing happens.
EDIT: I'm using the compressed pack. The regular x128 lags really badly as well.
You only have 2GB of total RAM... Your OS and other background software are probably using more than 500MB...
Get more RAM, upgrade to 64-bit, and then it should work :tongue.gif:
Scuttles, I tried increasing my heap size to 1.5GB (I have 2GB RAM) but the issue persists. Not only that, I'm getting the white box problem which I didn't have before.
It's probably because you don't have the 1.5GB to allocate...
Any idea why anything above 64 resolution gives me horrendously choppy lag? My FPS will maintain above 50 but it just chops like crazy. My PCs a beast and I followed all the instructions.
Yeah... I have a NASA computer and it's SOOOOO chopy.
Some investigation needs to be done as to why the Test function of Mcpatcher is almost guaranteed to work but using the same allocation settings on the standalone version gives out of memory errors. Plus s to whoever can figure it out.
Try launching MC with increased memory via command line instead of java allocation.
realy an survey im fine with the ad fly **** but com on the survey is redeculous...can u plz fix it
Ps not trying to flame or be a **** just saying
Please tell Scuttles how he can fix Ad Fly.
I'm sure he would be more than happy to do so.
Until you can provide that information please read and either use the direct mediafire links Scuttles kindly posted or the method another user posted on the same page to bypass the survey.
The ADFLY link worked fine for me.....lol at people who dont use AdBlocker Plus.
Normally I would agree, but this isn't blocked with Adblock Plus or any of my advanced ad blockers.
This can only be solved by adfly it seems... need to wait for them to fix it :/
That's strange, I can play 512x terrain.png with optifog+optimine, but not with HD patcher? I thought Scuttles said you can with HD patcher. I'm getting average 120-140 fps with 512x.
Maybe Optifog+Optimine make it require less memory, allowing it to work.
In theory launching MC with >2GB should do the trick :tongue.gif:
I guess it is possible. I used the 512x for a few minutes. 60fps average though some things didn't look right. Maybe it's because I was using optifog+optimine instead of mcpatcher for hd textures. x)
'THE' 512x?
Are there any native 512x512 released textures available for 1.7.3? I would love to try one again. :tongue.gif:
0
It works fine (or so it seems) when I install GLSL before patching with MCPatcher.
0
I added the shaders folder w/ the bumpmapping shaders because the default shaders don't have bumpmapping enabled.
I don't think it's my installation that's wrong though :/
0
Blargh...
I had MCPatcher working fine with GLSL yesterday, but now that you release the awesome bumpmapping it refuses to launch.
Black Screens ftl...
Must.... fix....
EDIT:
OK, so maybe I'm just making a really stupid mistake.
Recapping what I did.
First, I open MCPatcher, everythings checked (HD Textures, HD Font, Better Grass).
I then add the GLSL folder, put the two bumpmapping PNGs into a zip and add that, add the shaders folder to a zip and add that, put them all at the bottom, and click PATCH.
Then I go in-game, it launches fine and goes to the main menu.
Then when I go to texture packs and choose an HD pack the menu disappears, I only see the background, and eventually it goes black.
I get this error
Oh, and I can't use the Test Minecraft button in MCPatcher, I get this error
I suspect this is all related to my Windows installation being corrupted.
I did get my hands on that USB drive, but I plan on getting two new hard drives, and would wind up reinstalling windows on those anyway.
So rather than doing it twice, I'm just going to wait the 15 days to get them, and then install it then.
So here goes 15 days without Windows functionality.
0
Optifog
0
Not with Mipmapping :sad.gif:
I really want SOMEONE to release a 512x512 pack... :/
0
You only have 2GB of total RAM... Your OS and other background software are probably using more than 500MB...
Get more RAM, upgrade to 64-bit, and then it should work :tongue.gif:
0
It's probably because you don't have the 1.5GB to allocate...
Yeah... I have a NASA computer and it's SOOOOO chopy.
(POST YOUR COMPUTER SPECS)
0
You still didn't read the previous page AT ALL.
0
Try launching MC with increased memory via command line instead of java allocation.
Please tell Scuttles how he can fix Ad Fly.
I'm sure he would be more than happy to do so.
Until you can provide that information please read and either use the direct mediafire links Scuttles kindly posted or the method another user posted on the same page to bypass the survey.
0
Nice going, reading the rest of the page. :biggrin.gif:
0
Normally I would agree, but this isn't blocked with Adblock Plus or any of my advanced ad blockers.
This can only be solved by adfly it seems... need to wait for them to fix it :/
0
You owe me a new pair of pants!
That picture gets me every time...
I wish we could get it like that :/
0
Revo Uninstaller? :biggrin.gif:
0
Maybe Optifog+Optimine make it require less memory, allowing it to work.
In theory launching MC with >2GB should do the trick :tongue.gif:
0
You only need it for 64x64 packs and above.
It's also recommended for 32x32 packs for full compatibility, but not 100% required.
'THE' 512x?
Are there any native 512x512 released textures available for 1.7.3? I would love to try one again. :tongue.gif: