Support: MFS Unit Not Outputting

    I don't know if I have a major concept error or if this is just a bug.


    Using the latest version of Industrial Craft and Forge. This is on my SMP server that is hosted on my computer. The SMP server also has latest version of forge and Industrial craft. Industrial Craft and Forge are the ONLY mods installed with the exception of ModLoader on the client end (which is the latest version).


    Screenshot


    The above screenshot shows what is happening. It's a very basic setup, I have input coming into the MFS which is charging it, and then some HV cable coming off the bottom where the output is (the single dot). As you can see, testing the HV cable says there's no current going through it. The MFS has stored energy, however it's not outputting to my MFE at the other end of the string of HV cable (With a MV transformer in between the two of course). Mind you it's been awhile since I've played MineCraft and Industrial Craft for that matter, has there been some sort of change I'm not aware of or is this simply a bug?


    The only error that seems to be coming up is:


    Code
    Received a TileEntityData packet for a location that did not have a TileEntity: <304, 52, 211> 1: 52, 0, 0


    Not sure if that has anything to do with this issue, anyone know?

    Quote from AliasXNeo

    The MFS has stored energy, however it's not outputting to my MFE at the other end of the string of HV cable (With a MV transformer in between the two of course). Mind you it's been awhile since I've played MineCraft and Industrial Craft for that matter, has there been some sort of change I'm not aware of or is this simply a bug?

    Fixed link


    Check you're not trying to input the eu on the output face of the MFE.

    Quote from CiderCraft

    Fixed link


    Check you're not trying to input the eu on the output face of the MFE.


    That was somewhat the issue. I was using the old 1.2.4 version with the 1.2.5 hack, so there was some texture issues and when I upgraded to the latest 1.2.5 version I noticed that I was in fact trying to input into the input.