MFFS fortron capacitor not linking to anything

[joseff amador]

Upgraded to Monster 1.0.7 and it works. Please delete/close this thread

Monster 1.0.5

The Coercion driver is full of power, but it won't send any power to the Fortron capacitor. Both are "blue" (showing that they are turned on), and both are set to the same frequency. The Capacitor IS within range (it's only a few blocks away from the Coercion driver...)

Simply put, the Fortron Capacitor says "Linked devices: 0". it's showing zero linked devices, even though there's 2 nearby MFFS machines, all turned on, and all sharing the same frequency.

I have tried using default frequency (0 - simply put down the machine and don't touch it).
I've tried using a Frequency card to link the machines
I've tried changing to my own custom frequency (by typing the freq. manually on each machines' GUI)
I've tried using a randomly assigned frequency , via shift - rightclicking the Freq. card in mid-air

The Fortron. Capacitor simply won't link to any machines. it says "Linked device: 0"

Anyone willing to load up creative mode and see if you can get it working?

 

[KingTriaxx]

Break and replace?

 

[kaovalin]

While not really a fix per say, you can technically use fluid pipes on the MFFS machines and pipe the fortron to where ever you want in the meantime. I always put my machines in testing environments to freq 1. I dont trust freq 0 to do the job.

Additionally I know DW20 1.0.11 pack has a buggy version of MFFS that wouldnt generate anywhere near the right amount of fortron from the energy provided. It's possible the energy being created is being used up by the upkeep on any upgrades you are putting into the coercion derriver before the capacitor can get even get a taste.

 

[joseff amador]

Break and replace?

Tried many times. Even in creative mode. no matter what I do, the Fortron Capacitor simply says "Linked devices: 0" (zero)

even though clearly, it's set to the same frequency as the Coercion deriver

 

[joseff amador]

Please, is anyone actually using monster 1.0.5 and gotten this to work?