Railcraft: 1.12 crash with IC2

[Spenny519]

and I don't get this crash when I just have ic2 and railcraft installed on the instance

[Spenny519]

This is the modlist I am using btw

[Chocohead]

Looks like detector is empty, battery and machine are checked first.

[Spenny519]

well the thing is that it was working with no crash yesterday and the this morning, without any changes to anything, it started crashing

[Spenny519]

how do I fix it?

[liach]

I do not know how this happens at all since the stack returned should be fine. Or should I register in regular recipes instead of ic2 crafting registry @Chocohead ?

[Spenny519]

once I disabled the ic2 mod compatibility in the railcraft configs, I got it to load up without it crashing

[liach]

I do not know what is wrong with the detectors. They are enabled in theory.

[Spenny519]

oh btw @Chocohead do you have any plans on updating Advanced machines to 1.12 anytime soon?

[Chocohead]

Changing to registering as a normal recipe won't fix the underlying issue that it couldn't find the detector, but without any concrete ability to reproduce the crash that's not especially possible. Have you disabled any particular Railcraft modules in the config that might have stopped it finding the detector?

As for Advanced Machines, it'll be ready when it's ready. It could do with more internal clean up, which by putting off in favour of more interesting projects has let it slip a little.

[Spenny519]

Yes when i disabled the ic2 module in the railcraft config, it stopped crashing and now works

[Chocohead]

But without disabling the IC2 module (ie having everything enabled) it does crash?

[Spenny519]

Yes if i dont disable it, i crash

[Spenny519]

But with the ic2 module disabled and everything else enabled, i dont crash

[Chocohead]

Quite strange, it shouldn't be able to suddenly break itself without anything changing. We'll probably need additional logging to be able to narrow down on what's wrong, but given we can't directly give you a jar that does make the process more complicated. If I created a branch with some additional logging and protection around the IC2 module would you be ok with compiling and testing with it?

[Spenny519]

Yeah im up to doing that to help out with it

[border999]

this is a 1.12 version for Railcraft yes? Would there be any means by which I may procure this?

[Spenny519]

@border999 it is an unofficial version with many bugs

[liach]

@border999 Direct message to me on discord if you really want.

[Chocohead]

That branch should have enough to get an idea why it isn't happy, unless it suddenly starts working again then we'll have no idea what ever went wrong.

[Spenny519]

Okay when i get a chance i will compile it and test it out in a new instance with all the same mods

[liach]

uh no, wrong issue. Should be #1136

[liach]

Anyways I will close this one. When I ran ic2 with railcraft this never happened; no other users reported so.

[gball19]

If you use liteloader, the same issue is shown and seems to be repeatable.

[xJon]

I can confirm this happens with LiteLoader and is fixed by using @asiekierka's Extra Foam For LiteLoader.