GoldenArbiter
-
Posts
10 -
Joined
-
Last visited
Posts posted by GoldenArbiter
-
-
I was curious so I downloaded MCP for 1.4.6 and looked up the mappings. yc is the World class, and the "h" function isn't named anything fancy or informative. so yeah, got no clue. some array in the world class is out of bounds for one reason or another.
edit: I just realized that the file names are right there in the error log (world.java). still, MCP would have been where I needed to look for function or field info I guess.
I have no idea what that means :)
-
that error is unfortunately very generic, and I can't find what yc.h does or handles via some quick googling. thanks mojang, for continuing to obfuscate your code so stack traces are goddamn unreadable and useless.
Well, if you don't feel like keeping up the search, that's fine be me. You've helped me more than enough, and if you were some sort of service professional, I would give you a gold star :)
-
uhh well, it sounds like MCedit did a number on stuff which is probably the cause of the new errors. I'll be honest, I don't know what to do about that =/
Well, thank's for trying. I'm just gonna build a new world, and ignore everyone's complaints. Especially my own
Actually, one more thing you could do to help me.
That's the crash report for my 0.5.1 server. If you have any idea how to fix that... well, it'll make everyone involved a lot happier, me thinks.
-
a little looking around and some guesswork tells me that the most likely issue is a BC tank that is holding something that no longer exists, like creosote oil. were there any creosote oil filled BC tanks hanging around? if so, use worldedit to go in and remove them. hopefully that will fix the problem.
Next level of error reports:
Honestly, I think it might be easier to start a new bloody world... which I really don't want to do... Recommendations? (also, using MCedit turned most of our things into other things. But that's probably because of the 4096 error thing...)
-
a little looking around and some guesswork tells me that the most likely issue is a BC tank that is holding something that no longer exists, like creosote oil. were there any creosote oil filled BC tanks hanging around? if so, use worldedit to go in and remove them. hopefully that will fix the problem.
Creosote no longer exists? Really? Wait... was that a part of railcraft?
Anyway, I'll get around to doing that tomorrow... Then I'll let you know what happens. Thanks for the tip.
-
This is a fantastic example of why providing incomplete information is a terrible idea. That is clearly bc tanks as you mentioned. I'm not at home right now, but I'll check your log out later when I get a chance
Admittedly, I didn't know that railcraft had tanks... So there is that, but yah, I probably should have provided the error logs from the get-go, eh?
-
that's all well and good, but if you are getting errors about "tanks" being unable to render, I've got news for you: there's only 2 tanks in tekkit and we don't have any kind of modern war vehicle mods. it's unlikely that it is BC tanks that are dying, sooo RC is what's left.
if you want more detail than that, an actual error log will be required. if you post one though, please use pastebin or something.
Well, the first line of crash report two is "at buildcraft.factory.render.RenderTank.a(RenderTank.java:96)" So... I think it is buildcraft tanks. But I only got that error once.
And after looking at the other crash reports, it seems all three have that in common... To pastebin!
Note, these only apply for when I was using 0.5.2
-
well you have part of it right. what it means by "ticking world entity" is that it is updating, or ticking, some object and that object is exploding in a most terrible fashion because of it. except for the exploding part, this is what happens every tick normally. every machine/object/thing has a function that is called when a tick happens that it uses to update itself. when that function is running, the entity is ticking.
I'm going to guess you had some railcraft stuff, didn't notice that the new tekkit lite doesn't include railcraft, upgraded, and now it has no idea what to do with railcraft tanks and other stuff (like the special carts, etc).
Nope. I pretty much forbade my users from using railcraft as I knew it was gonna be removed. However, I also got this problem in the 0.5.1 server, near the end of its life.
I'm going to assume it refers to TPS, meaning ticks per second. Normally, it should be 20 TPS, the default MC ticks. When it's lower it means that either the CPU is having trouble keeping up or the I/O is bottlenecking. Of course it could be any other hardware or software cause, but these are the most common.And how do I go about solving this, when everything has been fine for the past week? None of hardware is acting up, and I have installed no new software... And I almost never have the 'server cannot keep up' dialogue. And when I do, it's because I have like, 50 internet tabs open doing research on how to do things in tekkit.
-
Between myself and several users on a private server, we have achieved several different errors that get us instantly removed from the server.
the three I have seen so far are: Ticking world entities, Could not render 'tanks', and of course 'Unexpected Error'. I only have the last two crash reports if anyone wants them.
Anyway, I would go back to 0.5.1, except after about 10 minutes of running, the server crashes do to ticking world entities. I have had the server running for... at least a week now, and we have experimented with Mystcraft, IC2, Red Power, computer craft, and most recently, buildcraft.
Can someone please tell me what a ticking world entity is?
(sorry if this question has already been asked and answered, I am just having a crap day, and I don't want to search a forum.)
Tekkit Lite 0.5.2 log in errors, and Ticking world entities.
in Tekkit Lite Discussion
Posted