So, I've had a small...okay, big...problem with Huge Trees.
Whenever I load up a natural world, I would hit the Savings Chunks screen after a couple of minutes. I ran Minecraft in offline through the .cmd function, and It would work fine, then whenever I hit the savings chunks screen, it would spam the following until I closed the program:
Ok, note to self, and everyone else. NEVER use a whole tree axe on one of the huge trees, especially when the part of the trunk you cut is underwater... Oh god the lag >.>
On the plus side I easily have a full inventory of logs... and about 20 full inventories full on the ground/still falling 10 minutesan hour later.
Yeah... there are some things you just shouldn't use in custom trees...
Cactus, reeds, etc - you will be reduced to 1 frame per 30 seconds, any time that chunk is loaded.
Sand, gravel - you will get extreme lag for a few minutes, and probably forever after. It does make interesting spiky mounds though.
Yeah... there are some things you just shouldn't use in custom trees...
Cactus, reeds, etc - you will be reduced to 1 frame per 30 seconds, any time that chunk is loaded.
Sand, gravel - you will get extreme lag for a few minutes, and probably forever after. It does make interesting spiky mounds though.
Anything that generates light is probably a bad idea, too. Your CPU will be molested by all the light updates.
I'd like to see a few more options in the config file, namely disabling custom trees, as cool as they are.
So, I've had a small...okay, big...problem with Huge Trees.
Whenever I load up a natural world, I would hit the Savings Chunks screen after a couple of minutes. I ran Minecraft in offline through the .cmd function, and It would work fine, then whenever I hit the savings chunks screen, it would spam the following until I closed the program:
Wut do.
That's my config file function going retarded... Delete the config file.
That's my config file function going retarded... Delete the config file.
Alright. Anything that you're going to/need to fix in the next version, or is my luck just bad enough for everything to turn horrible for me? I never touched the Config file, so I either did something in-game or it screwed itself up.
Edit: Um, still getting the savings chunks screen. Hold on, going to run Minecraft on .cmd again...
Edit edit: Okay I just ran it, and it's doing the exact same thing... I definitely did delete the Config file...and it's not there...so I have no idea. Might have to just uninstall the mod until I figure out what to do. O_o
Is there any chance you could lower the massive tree spawnrate just a bit? It's nice having huge trees, they make impressive sights (and awesome treehouses), but having 2-5 spawning within a few chunks of eachother gets kind of annoying when travelling, as there is a huge lagspike while they are loaded.
:ohmy.gif: work harder! better! faster! stronger..... -starts dancing...-
but seriously, keep it up :biggrin.gif:
also, if you do an exclusion list... you might make it throw an in game 'error' something like "You are not allowed to make a tree out of this material."
as long as that isn't too difficult considering how notch programs :tongue.gif:
:ohmy.gif: work harder! better! faster! stronger..... -starts dancing...-
but seriously, keep it up :biggrin.gif:
also, if you do an exclusion list... you might make it throw an in game 'error' something like "You are not allowed to make a tree out of this material."
as long as that isn't too difficult considering how notch programs :tongue.gif:
I will do an exclusion list, and I will do that :smile.gif:
And a lot of the delay is because I am simultaneously working on the new shtuff for v2.0
(multithreading, different tree forms)
Whenever I load up a natural world, I would hit the Savings Chunks screen after a couple of minutes. I ran Minecraft in offline through the .cmd function, and It would work fine, then whenever I hit the savings chunks screen, it would spam the following until I closed the program:
Wut do.
WHAT?!
Danger zone.
On the plus side I easily have a full inventory of logs... and about 20 full inventories full on the ground/still falling
10 minutesan hour later.Cactus, reeds, etc - you will be reduced to 1 frame per 30 seconds, any time that chunk is loaded.
Sand, gravel - you will get extreme lag for a few minutes, and probably forever after. It does make interesting spiky mounds though.
Anything that generates light is probably a bad idea, too. Your CPU will be molested by all the light updates.
I'd like to see a few more options in the config file, namely disabling custom trees, as cool as they are.
-Nicolas Negroponte
That's my config file function going retarded... Delete the config file.
Alright. Anything that you're going to/need to fix in the next version, or is my luck just bad enough for everything to turn horrible for me? I never touched the Config file, so I either did something in-game or it screwed itself up.
Edit: Um, still getting the savings chunks screen. Hold on, going to run Minecraft on .cmd again...
Edit edit: Okay I just ran it, and it's doing the exact same thing... I definitely did delete the Config file...and it's not there...so I have no idea. Might have to just uninstall the mod until I figure out what to do. O_o
WHAT?!
Danger zone.
How can I fix this?
Reinstall, does it crash if you grow a sapling?
cmon u can do it just a little click
but seriously, keep it up :biggrin.gif:
also, if you do an exclusion list... you might make it throw an in game 'error' something like "You are not allowed to make a tree out of this material."
as long as that isn't too difficult considering how notch programs :tongue.gif:
I will do an exclusion list, and I will do that :smile.gif:
And a lot of the delay is because I am simultaneously working on the new shtuff for v2.0
(multithreading, different tree forms)
Threads won't ever conflict (I think)And basically /all/ the lag comes from the 59,000ish blocks placed for each tree.
Working on it (v2.0)