Auto Mass Fab Feedback/Discussion
-
Deribus is right.
For all those reading this, we're working on a UI that helps you identify what the current status quo is of the mass fabricators. See also:
We'll also introduce a threshold that no fabricators are turned off when you have more than 50K of energy in storage, while they can be turned on again. This means that if you have 15+ energy storages you effectively 'disable' the behavior.
-
A yellow pause button could work
-
As said above i just noticed integrated fab behaviour is so stupid as it is now...
https://forms.gle/w1JcLTs4Pt1pL8d56
Lets do a quick poll about it and decide what to do after it. -
I find this post slightly frustrating.
Lets do a quick poll about it and decide what to do after it.
The poll is meaningless - depending on who you share it with the poll can have a completely different outcome. I will refuse to listen to the outcome - we've been open for feedback, and to some extent even searching for feedback since the very start. See the changelogs, for example:
The only topic that provided some kind of feedback is this one:
Which, after 20 days - is not a lot of feedback. Other feedback came in through voice chats (like the developers session organized by BlackYps) or by people talking to us directly. All of the feedback that we've been given can be summarized in one paragraph:
- Can you make it tune the behavior using game options -> no, that can cause desyncs.
- Can you change the parameters -> yes, but you ought to give us a good idea why you think the other parameters you suggest are better. And generally we get zero rationale beyond that it fits their playstyle
Meanwhile we did identify some issues, such as people being unable to see the current state of their fabricators. We're working on that and the pull request is almost finalized:
That should make the situation a lot less frustrating as you can identify that the majority of your fabricators are turned off (or on) at any given moment.
We're also tuning the parameters slightly to allow people to disable the behavior if they have sufficient energy storage. As an example, regardless of the ratio of your storage - as long as you have more than 40K (9+ energy storages) then your fabricators will not turn off and remain turned on. This guarantees that Overcharge remains fully functional, and gives sufficient room for the fabricators to turn themselves off when you're in dire need of energy.
-
This thread should be closed and any feedback should go in the relevant thread.
@jip said in I couldnt help but notice all that movements with mass fabs....:
I find this post slightly frustrating.
You are way too nice to even have wasted this much time writing such a well-structured post when this person clearly didn't spend more than five seconds on it.
-
@deletethis I did spend more than 5 seconds creating poll.
But on a serious note automanaging fabs was meant to make this part of a game done by ai and not human hands. So as of now it is me manually managing fabs that decide to turn off when my e storage is almost full and i am once again manually managing fabs. Thats why i came to WHINE on forums. All you have to do is take part in a poll or just wait results of a poll. Because you would actually know what people think about autofabs. -
@yellownoob said in I couldnt help but notice all that movements with mass fabs....:
All you have to do is take part in a poll or just wait results of a poll. Because you would actually know what people think about autofabs.
But that is not the case
. Depending on who you share it with the results will be completely different. If we'd want an accurate poll then:- (1) The development on the fabricator behavior should be finalized
- (2) The poll is shared in the news, forums and every other place imaginable to get an accurate sample of the community
Neither of those are true. And neither are relevant, as we're very much open to structured feedback.
So as of now it is me manually managing fabs that decide to turn off when my e storage is almost full and i am once again manually managing fabs.
By all means - that is not what the behavior should be doing. You can share replays, your expectations and suggestions on what to adjust to the parameters of the behavior in this topic:
The pull request that was mentioned earlier was literally about to be merged, it is available on FAF Develop. I'd encourage you to give it a spin. Note that you can move the UI using your middle mouse button. And we're open for feedback on the UI too
. -
@jip Thanks for the hard work.
-
Can someone explain why 90% I’d prefer somthign closer to 50%-75% of storage filled personally.
-
The value was set to 90% with the idea that:
- We prefer a full storage over an empty one (for overcharge)
- As only one fabricator is turned on / off at a time, it guarantees sufficient time to enable / disable then accordingly
The current proposed changes (see this pull request) changes this to:
- A ratio-based threshold of 80%
- A storage-based threshold of 40K (40K+ more energy in storage) that takes precedence over the ratio based
The latter means that as long as you have more than 40K energy in storage (which is what you need for a full overcharge) then no fabricators are turned off - they will be turned on / remain turned on regardless of your storage ratio. This allows people to 'turn off' the behavior if they have sufficient energy storages (10+, reliably at 20+), while still allowing the behavior to kick in if they turn out being low on power.
-
I would like to increase this number up to 60k (full overcharge)
-
I thought that was 40K - my mistake
. I'll adjust it. -
If you want full overcharge you need 60k energy, but it only uses up to 90% of your storage, so it will need at least 66,666 energy. So that should be the threshold.
-
We really need a on/auto/off kind of behavior because everyone is going to have a different preference on the % and everyone is right too.
-
And a way to see if what is import and what you produce yourself. In half the cases where I make tele SCU's from air or eco slot, the naval player goes empty on E...
-
C Ctrl-K referenced this topic on
