Windows .exe Direwolf 20 1.6.4 Crash to Launcher

[Jason Peter Souchak]

Hey guys,

I've been playing the Direwolf pack, and have been really enjoying it. I was pretty far into a world, when it started crashing, and even though I could get to the world select screen, it would fail to load the world. I had been moving my save between computers, so I chalked it up to a bug related to that. I also wasn't too happy about how my world was turning out.

So, I decided to start a new world. I've been playing this world, called Reloaded, for a few days. I didn't transfer the file between computers. Everything was working fine. Al together I probably played about 20 hours. Today it suddenly crashed. It did not pass go, did not collect $200, just went right back to the launcher.

It was a fairly new world, so there weren't too many crazy thing going on. I cheated in one chunk loader in the Nether, that was keeping a portal spawner active But that was many hours ago. The game crashed right as I put a logistics pipe onto a redstone furnace.

I tried loading the world 3 times after the first crash, and it keeps going back to the launcher.

In the process of trying to fix the first world, I completely removed FTB, and redownloaded it, including the Appdata stuff.

The file dated 1-15 is from the "Reloaded" world, and the one dated 1-13 is from the world I was swapping between machines.

Thanks is advance for your help!

-Jason

Win 8.1
Java 45(?) I just manually updated from the site
GTX650M
i7 3630
8 GB ram

 

[Jason Peter Souchak]

Well, I've found a solution. Not 100% perfect, but it works.

Because the game crashed right as I placed the logistics pipe, I thought maybe something with that mod was broken. I disabled logistics pipes from the mod pack, and was able to load the world. Obviously, the logistics stuff was gone. I re enabled the mod, and was still able to load the world, but all the logistics stuff is still gone. I backed up my save before trying this. I put the backed up save back in, and had the same crash. I fixed it again in the same way, and things seem to be working. I'm going to cheat the lost stuff back in.

For everyone's information, this is exactly what I did when the crash happened:
I had just moved my redstone furnace to a more permanent room, and finally out of the way. I was testing the LP network by smelting a bit of cobblestone into smooth stone. The furnace worked fine,and kept the stone in output inventory. I set the furnace to output to the back. I had an extractor pipe on it (mk2 chasis with module), but I was experimenting to see if I could do the same with the much less expensive basic LP. As soon as I connected the basic pipe, the game crashed.

I'll keep the back up save files for a bit. If there is any interest, I can upload them. Maybe for bug testing? If anyone has a better solution, I'd like to hear it!

Thanks.

 

[JamiePhonic]

again: i shall post this for people who need to know:

i thought i'd type this up instead of constantly repeating myself. perhaps @Ashzification could add this to an FE/RC (Frequently Experienced/Reported Crashes) thread?

FOR ANYONE WHO'S GAME CRASHES WHEN USING LOGISTICS PIPES WITH THERMAL EXPANSION MACNINES:
the crash that occurs when connecting almost any logistics pipe DIRECTLY to the OUTPUT of a thermal expansion machine is a know bug.
2 solutions can be found below.

Spoiler: Solution 1 (Recommended)

the easiest way to fix this problem put a chest between the output of the furnace and the logistics pipe. this is usually good practice anyway as it will give you TE machines a sort of buffer. In the mean time, you will need to use MCEdit to remove the offending pipe(s) to recover your world

Spoiler: Solution 2

you can also update the mod to build #89, where this problem has been fixed. its not recommended and you will still need to use MCEdit to remove the offending pipe(s) to recover your world, but if you still want to update the mod, download it from Here, then open the launcher, select your modpack then hit "edit modpack" at the top and select "add mod" and point it at the new file. make sure you disable the older version or your game WILL crash.
if you do this, you WILL NOT be able to connect to any multiplayer servers, unless they have updated it too.

if your interested, here's the reason i think the crash happens:

Spoiler

from what i remember, thermal expansion machines will try to output anything they create to an adjacent inventory, but since logistics pipes is technically an add-on to buildcraft, it follows that it may share some code with buildcraft.
i know from testing that thermal expansion machines can output directly into a buildcraft pipe and a basic logistics pipe, so it follows that the furnace will try to output into the supplier logistics pipe too.
i suppose the crash happens because the code says the supplier pipe is supposed to make the request for items to enter the network, not to have them inserted into it, and because no one requested a gold bar or whatever, it doesn't know why its there and just crashes

Note: all that could be completely and utterly wrong, its just my guess

 

[Jason Peter Souchak]

Thanks for the reply, I'll keep in mind the TE can't connect to LP directly.

I fixed it the way I said above. Fortunately, I had just started using LPs in my world, so it didn't take too long to fix everything. There are some blocks that are bugged, where the LPs were originally, and I can't place anything in them. I'll try MCEdit, and see if I can fix anything with that, if not I'll just work around it since it isn't so much.

If anyone has a way to contact Direwolf, maybe he should make a note in his Let's Play series telling noobs like me not to do this. Just a quick word of warning would help a lot.

Thanks!

-Jason