McRegion version 5 is out. Version 5 uses Deflate compression by default instead of GZIP, which should increase speed slightly. Old saves will still work. A version number of 2 the chunk data header indicates zlib compressed chunk data.
So if I want to stop using this mod, everything on the map will be reverted to before I used it, but my position and inventory will be the same. How can I remove this mod and stilll get my map back...
Got it back. I just really wish it would save a map so I can use mapviewers and stuff... otherwise, thanks.
The conversion tool lets you uninstall the mod and still keep your map.
Quote from vordhosbn »
anyone else see this?
java.lang.ClassFormatError: Incompatible magic value 1347093252 in class file RegionFile$ChunkBuffer
Somehow, the file RegionFile$ChunkBuffer in your minecraft.jar got corrupted. Try redownloading this mod and minecraft.jar, then reapplying it.
And yes, I was running Chrome and Pidgin while testing, so the framerate was marginally lower because of this, but I had it open the whole time - both Vanilla and with this mod. Same tabs were open, same everything, same background programs. Basically a controlled testing environment.
Is it possible that there was a tab open in Chrome that was using a decent amount of CPU? Maybe something with Flash in it?
Quote from HypertextEye »
I can't say anything good or bad about it. It didn't improve anything and it didn't degrade anything.
It sounds like you're more limited by a poor graphics card than by a slow CPU / slow RAM.
Hello gent. Just curious if you would be willing to address this. It would be very appreciated.
The root problem is that there's not a good general mod manager done yet that does patching on runtime, which would automatically handle problems like this. I hope that changes soon.
I wish I could be another success story here, but it honestly dropped my fps by about 10...
From about 25 average to about 15 average, and more frequently dipping down into the <1 range. :X
This is with a vanilla install of Minecraft.
This is with v4? What graphics card do you have? I'm at a loss to how this could decrease performance. Are you sure you didn't have anything else running at the time?
Quote from Pimp Sword »
I share Minecraft save files a bunch. Will this mod make my saves incompatible with their computers that (unfortunately) lack this mod?
You're doing fantastic work, but what I'd also really like to see a fast, robust *single file* world format. I'd like to turn the paging library I have into a minecraft mod for doing just that.
I don't really care to write my own full-featured filesystem. I trust the creators of NTFS/EXT4/HFS+ to handle space allocation, fragmentation of single files, and caching more efficiently than I could myself. The goal of McRegion is to make Minecraft saves behave better with optimizations like lookahead caching already present in modern operating systems.
If not, could you possibly point me in the right direction for modding minecraft myself? I *think* I see all the changes you made to dd.java and nk.java, but even just a short list of all the methods you had to change would be *very* helpful.
Instructions:
1) Locate your minecraft.jar file. On Windows, it's in %APPDIR%/.minecraft/bin
2) Create a backup of minecraft.jar
3) Open minecraft.jar in an archive editor (WinRar/7-Zip/etc) 4) Delete the META-INF folder.
5) Copy the files from the downloaded zip file into the jar file (overwriting nk.class).
6) Run Minecraft and test!
It kinda decreased my fps from 80 to 34 (on short render let me get some screenies ) (using v3)(minecraft beta 1.1_02) doesn't seem to do anything but lower my fps :|for v3 (on sp)
That's really odd, are you sure you had the same render options for both?
I tested with the fancy option and my fps boosted up to 90(which is the normal fps without the mod so it works but not as i expected it)
So long as it doesn't decrease performance for people who already have good performance, it's good. Also, did you test v4?
This sounds like a great mod to improve performance. Will you be making this compatible with the better light and better grass mod in the future? I've seen this question asked a couple of times in the thread but haven't seen a definitive answer. Thanks and very nice work.
I'm in contact with the creator of BetterLight, so hopefully it will be compatible by the next version.
(Also I added a donate link in case anyone wants to help me pay for college)
After updating on OS X, I get the following error. Any ideas what could be causing this?
java.lang.SecurityException: SHA1 digest error for f.class
Re-read the instructions.
Quote from Trainspotting »
I've tried to do this, but when I do, Minecraft gets stuck at "Done Loading."
I found the minecraft.jar in the appdata folder, and I extracted it, replaced the files, deleted metaINF, zipped, then renamed it back to a .jar file. What am I doing wrong?
My minecraft is vanilla, apart from this.
I'm not sure, that sounds like the correct steps. Maybe try a special jar editing utility like http://www.codeland.org/ ?
Concept: The minimum unit of storage on hard drives is 4KB. 90% of Minecraft chunks are smaller than 4KB. 99% are smaller than 8KB. Write a simple container to store chunks in single files in runs of 4KB sectors.
Each region file represents a 32x32 group of chunks. The conversion from chunk number to region number is floor(coord / 32): a chunk at (30, -3) would be in region (0, -1), and one at (70, -30) would be at (3, -1). Region files are named "r.x.z.data", where x and z are the region coordinates.
A region file begins with a 4KB header that describes where chunks are stored in the file. A 4-byte big-endian integer represents sector offsets and sector counts. The chunk offset for a chunk (x, z) begins at byte 4*(x+z*32) in the file. The bottom byte of the chunk offset indicates the number of sectors the chunk takes up, and the top 3 bytes represent the sector number of the chunk. Given a chunk offset o, the chunk data begins at byte 4096*(o/256) and takes up at most 4096*(o%256) bytes. A chunk cannot exceed 1MB in size. If a chunk offset is 0, the corresponding chunk is not stored in the region file.
Chunk data begins with a 4-byte big-endian integer representing the chunk data length in bytes, not counting the length field. The length must be smaller than 4096 times the number of sectors. The next byte is a version field, to allow backwards-compatible updates to how chunks are encoded. Currently the version is always 1, which represents a gzipped NBT file. The gzipped data is the chunk length - 1.
0
You need to make sure you overwrite all the old files from McRegion.
0
0
http://mod.ifies.com/f/110106_RegionTool_source.zip
Also, a new version of RegionTool that permits packing/unpacking from one directory to another:
http://mod.ifies.com/f/110106_RegionTool.jar
0
The conversion tool lets you uninstall the mod and still keep your map.
Somehow, the file RegionFile$ChunkBuffer in your minecraft.jar got corrupted. Try redownloading this mod and minecraft.jar, then reapplying it.
0
Is it possible that there was a tab open in Chrome that was using a decent amount of CPU? Maybe something with Flash in it?
It sounds like you're more limited by a poor graphics card than by a slow CPU / slow RAM.
0
The root problem is that there's not a good general mod manager done yet that does patching on runtime, which would automatically handle problems like this. I hope that changes soon.
0
This is with v4? What graphics card do you have? I'm at a loss to how this could decrease performance. Are you sure you didn't have anything else running at the time?
This doesn't touch save files.
0
I don't really care to write my own full-featured filesystem. I trust the creators of NTFS/EXT4/HFS+ to handle space allocation, fragmentation of single files, and caching more efficiently than I could myself. The goal of McRegion is to make Minecraft saves behave better with optimizations like lookahead caching already present in modern operating systems.
The MCP thread has lots of good information.
0
You need to delete META-INF in minecraft.jar, not Minecraft.jar.
0
0
Could you paste the error message?
0
So long as it doesn't decrease performance for people who already have good performance, it's good. Also, did you test v4?
0
I'm in contact with the creator of BetterLight, so hopefully it will be compatible by the next version.
(Also I added a donate link in case anyone wants to help me pay for college)
0
Re-read the instructions.
I'm not sure, that sounds like the correct steps. Maybe try a special jar editing utility like http://www.codeland.org/ ?
0
Concept: The minimum unit of storage on hard drives is 4KB. 90% of Minecraft chunks are smaller than 4KB. 99% are smaller than 8KB. Write a simple container to store chunks in single files in runs of 4KB sectors.
Each region file represents a 32x32 group of chunks. The conversion from chunk number to region number is floor(coord / 32): a chunk at (30, -3) would be in region (0, -1), and one at (70, -30) would be at (3, -1). Region files are named "r.x.z.data", where x and z are the region coordinates.
A region file begins with a 4KB header that describes where chunks are stored in the file. A 4-byte big-endian integer represents sector offsets and sector counts. The chunk offset for a chunk (x, z) begins at byte 4*(x+z*32) in the file. The bottom byte of the chunk offset indicates the number of sectors the chunk takes up, and the top 3 bytes represent the sector number of the chunk. Given a chunk offset o, the chunk data begins at byte 4096*(o/256) and takes up at most 4096*(o%256) bytes. A chunk cannot exceed 1MB in size. If a chunk offset is 0, the corresponding chunk is not stored in the region file.
Chunk data begins with a 4-byte big-endian integer representing the chunk data length in bytes, not counting the length field. The length must be smaller than 4096 times the number of sectors. The next byte is a version field, to allow backwards-compatible updates to how chunks are encoded. Currently the version is always 1, which represents a gzipped NBT file. The gzipped data is the chunk length - 1.
tl;dr approximate C struct version:
struct RegionFile { struct ChunkOffset { int sector_number : 24; char sector_count; } chunk_offsets[1024]; struct Sector { int length; char version; char data[length - 1]; } sectors[file_length / 4096 - 1]; }