Stone Rhino

Trying to help out a friend who has never used a modded game of MC. To help, I'm bringing him on with BigDig. He runs a mac and after a bit of explaining, I got the launcher on his machine and walked him through starting it. After some difficult explaining (in french, and I dont speak it well) I get the launcher going and modpack selected. Now comes the difficult part. The old "Hello" window which is now known as the FML loading screen, opens up, does its thing, then goes white. After a few seconds, it closes to desktop without even hitting the Mojang logo. I'm a PC, and I dont know how to work a Mac. I've suggested updating his Java. Anything else I miss?

Axe module of power glove does not work. Equals fist regardless of OC.

UEC's are great, but do loose power over time (i think elites do not). However I am finding them unreliable as it requires chunkloading to operate when offline. Even then, its iffy at best. REC's require no chunkloading to emit.

works, but there are a lot of texture problems with many of the mods. IMO, this is a deal breaker if I cant see what I'm crafting.

I've not tried the construct mod yet, but Thermal Expansion makes incredible use of BuildCraft Pipes. The machines are however not that efficient, so to make them run at peak performance, you will need a healthy bit of power being generated.

That might be my problem as well.

Will check that, but Ive had this problem before with other pure JRE apps. I'll run thing through the wash tomorrow. Just got back into town.

I'm starting to think java 1.7_21 has a horrible memory leak. I can play for about 30 minutes creative, or 1 hour in survival mining until RAM usage exceeds the imposed limit and CPU usage spikes to 100% on all 8 cores. The client will stop functioning until MC flushes its cache and everything's great for 30 seconds. Then I glitch into a wall, suffocate and die. This is happening for multiple users on my server. I open task manager and perfmon and can clearly see the swapfile is heavily active. Also I can see java.exe pulling far more than I tell it.

The windmills from UE seem to bug out when you put more than 3 in an area.

Okay, it seems your map is very incompatible with the current build. Now its Forestry causing the problem. Did you try starting a fresh world with all mods enabled?

So true, but the suits are quite overpowered. Since Big Dig is about being lazy, I can see why its using the vanilla recipes. But like you, I feel that my server denizens should not be handed everything on a platinum platter. Iron is bountiful beyond belief. "Customers are like bars of Latinum, cherish them always."

*Thinks of FO:NV.... Shudders*

TheMrRafus, please don't sign your posts. Although its polite, the moderators here don't like it for some reason. Lets tackle the problem here by eliminating a few variables. Try starting the server up without your world files that you are importing, essentially a fresh world. If it loads successfully, then it is something in your world files that is preventing it from loading. Likely the logistics pipes are according to the crash log. If it fails, then there is a conflict with one of the plugins. Try that and let us know.

This seems to reference logistic pipes in your crash file. Also it looks like you've added craftbukkit and mcpc into the mix. Is this a fresh map or one you've imported?

I'll happily deal with the distance loss and cost vs bleeding out.

MC is sensitive to events like this. Run "chkdsk /r" or run a disk check from the drive's properties, tools tab. From that window, make sure both boxes are checked and click OK. If its the C: drive, then yes, you want to schedule it at startup. If your drive is huge (1 to 3TB), you're going to be there a LONG time. Just let it do its thing overnight while you sleep. Your server. Does it have any kind of raid? Like RAID 0, 1, or 5?

I did, thats the strange part. I'll try compiling the jar on another machine.

Okay, after ripping out all of the UE blocks and pipes and reconnecting it all in a pure redstone conduit, no more "Leaking" power. Now, if I isolate the UE power with a tesseract, and allow it to use the Universal cable to the tesseract, and on the receiving end use nothing but redstone conduit, it too works fine. But the instant I connect Universal cable to the same REC as redstone conduit, it freaks out and starts jettisoning power into nothingness.

I just hooked up redstone conduit to an REC and powered furnace. It "lost" as many MJ's as I could output and a continuous rate. I had to set the REC to 5MJ/t output to stop it all from bleeding out. Correct, the ratio is 1:10 after looking in the config file. For some odd reason though, the machines are consuming more than what they did in tekkit. Im using the same system of steam engines producing 40MJ/t and its like im running 10 quarries. It vaporizes the REC's storage in two or three minutes.

Oddly I cannot repeat this in singleplayer.

Redstone Energy cell powering Universal Cable. Assembly table and required laser were in operation when I stepped on charging pad connected to same cable. http://pastebin.com/LQvCt1Ft and http://pastebin.com/1qM7Ygy7 <FML Log>

I've noticed a lot of how-to videos using the MJ term as "Mega Joules" when referencing a lot of the thermal expansion equipment. It is however not that, as the M stands for Minecraft. The Universal Electricity mod uses Joules rated in MJ, kJ, and J. The rate of conversion is 1600 MJ (Minecraft Joules, not 1.6 Giga-Joules) = 112,000 Joules or 112kJ in UE power. Because of this, you may notice some of your machines pulling more power than usual, and that the redstone conduit "Leaks" when connected to certain machines (Consumes power, but does not transfer it). ME Controller for example.

You would paste that inline, like this: java -XX:MaxPermSize=1024M -Xmx8G -jar BigDig.jar nogui --log-limit 100000 I've increased the permgen size out of testing purposes. Please retain the 256M size

Either I'm screwing up something or WinRAR doesnt handle .jar files right. used winzip and 7zip. both apparently corrupt the minecraft.jar file

So this is actually stable now?