Then maybe we would get gpu acceleration and proper chunk loading
This new unofficial test version is about 3 times slower then 1.2.5 and 5 times slower then 1.8
i used to get 20 fps on a core2 duo 2.66 ghz, but sadly enough i only get around 5 fps on my core i7
sandy bridge 3.4 ghz.
So something is definitely up with the code optimization.
I'm not having any such issues. There is no fundamental difference between the 1.2.5 release (MCEdit 0.1.1) and the 1.3 release (MCEdit 0.1.2). The only true difference is including the new 1.3 blocks. No real changes were made to the code otherwise, how it renders, etc.
If you edit a sign and put in Color codes, after you save it you can't open it. You get an error if you try to edit a sign which has color codes in it. It's easy to reproduce, though I can provide the error if you want.
As I said above, I'm not a python coder by trade, but if you provide the error I may be able to fix some of the more basic errors that occur like this. With the full error, it will tell me which line of code causes the issue and unless it requires some sort of big rewrite, I should be able to handle fixing small issues.
That snippet is missing a lot of important details, including the actual error. What you posted is a small piece of the stack trace. I'm not super familiar with Python but if you post all of the log from the error I might be able to correct it.
My github also has a download of Tectonicus 2.14 with a slight tweak. After editing my map a bunch, I found tectonicus would no longer render it because biome IDs were missing from some chunks. The build in my github fixes the issue. It's a bug in both McEdit (Not saving biome IDs) and Tectonicus (Not tolerating missing biome IDs). I've reported the issue to both projects.
Indeed. Mcedit 64-bit last night was the first time I've actually pushed this machine past 50% memory in use, and actually managed to get it up to 76%. 16Gigs
Just spent a bit tinkering and finding all the dependancies as 64-bit. I've uploaded my 0.1.2 Win32 build from the other day as well as a 0.1.2 Win64 build to github now.
These are built from TK's 0.1.2 files, so they probably won't work on Intel GPUs. However, they do have the Minecraft 1.3.1 blocks from the updated pymclevel.
I've sent this to TK, and I don't know if there's other reasons he might be waiting on releasing the win32 build, such as bugs I'm not aware of. But in the meantime, this should work for everyone. Let me know if you get any dependancy issues and I'll try to resolve. I used it yesterday to make a large number of edits to a creative flat 1.3.1 Anvil world. The new blocks are there from the updated pymclevel.
It has the same memory leak issues as 0.1.1 so if you get a crash due to out of memory, that's not an issue with the 0.1.2 build and I cannot help.
1
I'm not having any such issues. There is no fundamental difference between the 1.2.5 release (MCEdit 0.1.1) and the 1.3 release (MCEdit 0.1.2). The only true difference is including the new 1.3 blocks. No real changes were made to the code otherwise, how it renders, etc.
As I said above, I'm not a python coder by trade, but if you provide the error I may be able to fix some of the more basic errors that occur like this. With the full error, it will tell me which line of code causes the issue and unless it requires some sort of big rewrite, I should be able to handle fixing small issues.
0
0
2
Link again: https://github.com/ferret99gt/mcedit/downloads
Downloads available:
0
0
2
https://github.com/ferret99gt/mcedit/downloads
These are built from TK's 0.1.2 files, so they probably won't work on Intel GPUs. However, they do have the Minecraft 1.3.1 blocks from the updated pymclevel.
0
Sure it does. I'm using Win7 Pro 64-bit with no issues.
0
It has the same memory leak issues as 0.1.1 so if you get a crash due to out of memory, that's not an issue with the 0.1.2 build and I cannot help.
http://www.ferretbox.com/MCEdit-0.1.2.win32.zip