its on PTS already.
but it seems more that the priority setting is working again as it initially was supposed to do -
aka, if i have 3 connections, and only 1 has a demand, it will get the full "maximum output", and not only 1/3rd.
i don't know if the behaviour i watched two weeks ago was limited to Standard/T1 energy nodes, because now i don't see that happening on my T3 nodes (someone killed my T1 base so i have to set up something again.)
Update:
I can see both things happen... thats hell of confusing!
a backbone (6000max) with two 50% connections will send max 3000 AP to either of the connected nodes
an energy node (1000max) with four 50% connections will send the full 1000AP to either node in case no other one has a demand.
Update2:
this is really not consistent. now i got a energy node do both things. one time it only sends a fraction of its max, the next cycle it sends the full number.
and the more i play around with it, i blame that "efficiency" multiplier for messing up things.
so, suggestions:
instead of caclulating a theoretical AP value out of the priority number, let me type in higher numbers then 100, and display the resulting ratio.
so in case of the initial example, i type in the 500:50:50:50 - and the respective priority window will show me 76.92%:7.69%:7.69%:7.69%.
that way i can type in the expected demand, and it will make it work
*Disclaimer: This post can contain strong sarcasm or cynical remarks. keep that in mind!Whining - It's amazing how fast your trivial concerns will disappear