Search results

In the railcraft.cfg, set the ID for Block.Hidden to 0.

Uh...what? Recalculation should happen on a totally different time scale than that. I may go talk to CP and see what's going on there.

Oh yeah it's too late now. Gotta MC edit. The taint from those things persists. It's not CJ's fault necessarily; though at this point, he should really remove them from the mod given that he *knows* about these issues.

1) Crashlog or this is basically yelling fire in a crowded theater. 2) Can't replicate this. 3) If you have Railcraft, disable the hidden blocks - that is about 103% likelihood of the crash.

Actually, the Forge team was on the ball this last go round (for 1.6 - Forge 1.6 has been out for 5 months), and we almost have a working Forge for 1.7 already. Simple fact is that a lot of major mods did major rewrites. So at this point, hard to say.

Oh wow, hah. Yeah got it - that is a crazy corner case issue - you are standing in exactly the miniscule blind spot between client and server gui sync! It's resolved in dev, but I just pushed a b10a a moment ago. Sorry, I don't consider it quite critical enough to handle right this second. But...

I normally don't do this, I really don't, so forgive the snark in advance. But this one has been coming up so much and so frequently that I have to do this: Fixed that for you. Disable your heat blocks. Seriously I cannot emphasize how bad the interaction is there - Vanilla does NOT handle...

Okay. That is a strange one. It's also one I can't replicate. The furnace is definitely still working though. Hrm.

Aaaanddd b10 is out! This should fix basically every outstanding verifiable issue, including the conduit grid connection bug. Upgrades at the moment are slated for 3.1. Don't worry, 3.1 might not be as far off as you think. All dynamos were boosted to 80 RF/t, yeah. It felt a bit stupid to...

There's an issue with grid formation in a couple of cases which frankly account for just about everything you're talking about here. You'll notice if you reload the chunk in any way, they are fixed. Use covers to prevent conduits from connecting - the wrench thing was a horrible kludge...

Yeah we don't see the Steam bug in any of our testing; it's an inter-mod issue. Basically whichever mod is getting ahold of Steam first is registering a bad icon to it. We're just going along with whatever Steam is registered.

Some bows, or all bows? I'd be interested to see some screenshots here.

After thinking about it, I have an alternate way of handling this. :) Should work properly with pipes now on Send or Receive! This is caused by a Forge bug + Tile entity remnant issues - the new version of Forge will fix this. cpw especially built a new one just to fix this issue. Fluiducts...

There are a couple of corner cases where specific grid formations cause the grid not to be added to the tick handler. However, they are corner cases and it's a far cry from "not working at all." Fix is pending. Tesseracts are infact inventories, they just don't eject into BC pipes due to...

Filters are working properly in all of my tests. Please post screenshots of your setup. It's possible that there's a corner case, but in the general cases - they are absolutely working.

Steam Dynamos can accept steam from a RailCraft boiler.

The Extruder -> Crucible thing wasn't sustainable in TE2 without tweaking the configs. You can tweak the same values in TE3 though, if you really want, but that's a bit hackish. Netherrack is a pretty good source of RF, and you get it really really fast with a Flux-Infused Pickaxe. ;)

Will see what I can do. Trying not to keep a changelog for beta to be honest, just having the wiki guys update what is going on. We're nearing the end of beta though. :P Hrm. I did tweak a few things that were happening on a really base level; apparently AE and Ender IO had some intermod...

You know, we have an issue tracker. This is the first I've heard of it, at all. Period. Filters are working in b9c as far as I know, and b9d as well. If you can show us a setup, that would help a lot. Thanks. :)

FMP isn't causing that. FMP is just being assigned all of this blame because people don't understand it yet. It is an API, much in the same way that Forge is. In future versions of FMP, the covers will be separated out into other jar files to help distinguish this fact. We cannot make it...