Chefsbrian

I don't believe that EE2 makes any calls to OpenAL (Considering you can run it without OpenAL), but Matmos REQUIRES it for it to function. And your problem frame is # Problematic frame: # C [OpenAL64.dll+0x6220] alSourcei+0x144 which is a source file for OpenAL, being called by MATMos. Glad to see your crashing ceased, but its likely because flying that fast causes MATMOS to be overloaded with altitude and locational changes, since it tracks that all to be able to create realistic sounds.

One of the helmet upgrades that lets you use your powersuit helmet as a galactic craft helmet in space.

Did you try the solution in the common problems and solution thread?http://forums.technicpack.net/threads/common-problems-and-solutions.3405/

Haha, that'll do it. Hopefully we hit the next level soon, if all the mods update in timely fashion

Yea, glad its fixed man. Have fun with it.

You downloaded it into a seperate modpack? or patch it into an existing pack?

Huh. Because the weird thing is, according to that error message, its not the power suit. Or not directly. Its Galacticraft too. More specifically- Caused by: java.lang.RuntimeException: Framebuffers not supported! Points to a JAVA issue at the heart of it. But... You wouldn't have happened to have had the environmental sealing on your helmet, would you have?

Yea, it blends in. As for the lack of crashes, the rebooting with save would definately explain it. When you give Java 15gb of space to occupy, it doesn't bother going through and cleaning up stuff its not using from memory, until it starts to get too full. When you've got too much RAM assigned, it waits until its got an absurd amount of "Garbage" data sitting in memory. Then it tries to clear like, 12 gigs of active memory. At once. Suffice to say, its not really pretty, and usually causes Java to die. However, 4gb is low enough that Java can clean its crap out before getting suicidal. Rebooting when saving Kills Java and clears the memory before it reaches the suicide point.

Deer Lord man (hallowed be thy antlers) Edit button and we can hide that away XD. Anyhow, It looks like one of the conduits might have got corrupted in the crash, if it was halfway through a tick when it died it could cause it. Try taking MC edit and removing the local liquiducts, then launching. And I'd try to follow those crashes too. Fifteen gigs of ram is too much, it will die when it tries to clear unused data. Try dropping to 4gb allocation. That's plenty.

If it was a bad network card, we would have failed download or failed to read errors. Memory maybe, but then it shouldn't be just tekkit dying, I'd expect to see a full bsod.

Dude, this is from February XD. Gratz on making a fix and all, but I don't think this guy is still around.

Try going to the bug reports section of the forum, specifically the launcher bugs section, and fill out the error reports in there. With that info, I can help you. As it is right now, your issue could be anything from Java being out of date to nuclear detonation took out the FML ISP

So when you put in your minecraft.net username and password, it declares it invalid. Try logging into the Minecraft site itself with those credentials, just to rule out any simple issues.

2013-10-08 09:01:21 [sEVERE] [ForgeModLoader] Detected leaking worlds in memory. There are 4 worlds that appear to be persisting. A mod is likely caching the world incorrectly Well, that might be the problem. You've got some world issues. Whatever is messed up in memory is causing the server (or your client) to reject some of the information being passed along. Also, somehow you've been given a Negative length string by the server... I don't even know what could do that... 2013-10-08 09:03:09 [iNFO] [sTDERR] java.io.IOException: Received string length is less than zero! Weird string!

Huh... It tries to access the Netherore's, and its... Its not making any sense of it. Java can't load the file. Try deleting Nether Ores Core and having it redownload. Maybe delete the whole Powercrystals set and redownload that just to be sure XD

All that log file states is that your either trying to change allocated RAM, or that it can't allocate enough RAM to the game. By Can't log in, do you mean that when you put in your minecraft.net password and username, it tells you its invalid?

Something in the world is throwing a fit about that particular block being right there. You'll have to have it removed for you. Mods may find it easier to delete your Space Station's world, so I'd ask the server Admin to simply delete that.

Are you running any sort of Texture Pack?

Are you all using a Texture pack other than Default? Are you all running on 32 bit OS's? Saying your having the same problem doesn't help unless you say what hardware the problem is occuring on.

Well. That's new. I'd recommend sacrificing your Minecraft install to your pagan lord of choice. But for a serious answer, It almost looks like your texture information got all messed up in the vertical axis, Backing up your world, then deleting and re installing Technic Launcher will likely fix the issue.

I can't tell you how to get it into linux, unfortunately, but I can say I've only ever seen that issue when its run in JDK as opposed to JRE.

Its an issue with running JDK instead of JRE. Try installing JRE alongside it and see if that helps.

Well I looked up the documentation on it, seems like its basically a corrupted chunk, there's a Buildcraft tank that when it tries to render, kills the thread by pointing to something impossible Look into MC Edit, and try to use that to remove any buildcraft liquid tanks you have in the area.

Haha, moral of the story, unless its a University that offers decent computer science or 3d based courses, your probably not going to have enough power in it to run modded minecraft.

XD Sorry, that was my point. My old High School machines where joyous windows XP Machines with absolutely nothing in the department of Graphics.