Okay not sure if it's a bug or just a new feature, but it seems that as of 0.17 the "update time" for machines (furnaces, etc.) to display item icons in ALT mode is very long now (up to 1 second) which creates these weird "flashes" whenever new item is created/stacked in the mac...

Has anybody EVER found it useful to be able to detach/attach rolling stocks? I always just assembled the train on the line as needed. I actually use it a lot, so yes. I use a train with random stuff that I manually drive. I can turn around the lead engine by detaching, rotating, and reattaching. Ot...

Tomik wrote: ↑

Fri Feb 01, 2019 5:45 pm

So when can we expect 0.17? Please?

0.17 will be released in 2019.

This looks great! I love the ability to toggle the roboport.
Allowing us to make waypoints makes many of my stations more efficient, which is awesome!

Since everything can already be done with the current and/or system, I feel dev time is much better spent on other things. Brackets would only needlessly complicate the system.

I love the new train GUI, it looks much better! I agree with the point made above that the fuel information can be integrated into the main view though, since it's very tiny and always feels like a chore to navigate to just to check how much fuel my train has left. The combat should become a lot mor...

I agree that the car trunk capacity is very large, maybe unreasonably so. Maybe the new wagons could work the same as train wagons, they can automatically connect to a car or tank. The only issue may be automaticallly disconnecting them, as the only way to similarly remove wagons is to mine them. Y...

It can only read separate sides when both sides hold a different item.

If you like building a rail network, you can try OpenTTD. It's free and has entertained me for many hours.

A conditional skip isn't very complex, even if you haven't played OpenTTD. Consider this very simple example (which doubles as use case), where I've omitted the wait conditions for brevity: 1. Goto "Ore Pickup 1" 2. If Ore >= 2000 jump to 6 3. Goto "Ore Pickup 2" 4. If Ore >= 200...

Another throughput measurement setup. (Read-mode) Outputs 0 if it has full throughput, negative if it's starving, positive if it's saturated. The feedback loop empties due to the splitter priorities. This setup only works properly due to the changes in 0.17. 0eNrNls1uozAQx99lzrDCtGkSbn2OVYUMTMpIYCPb...

As someone who is heavily using circuits I also see nearly no benefit of getting a constant amount of items per belt piece on fully compressed belts - how would that help with anything? Trying to detect full throughput with read mode is now completely impossible, since you will never notice stutter...

As the smelting recipe change, I am proposing the following: - Iron plate, copper plate, stone brick: 3.2 - Steel: 16 That would mean exactly 48 stone furnaces per yellow belt, which is the number that people already build, but some of the last ones flicker with inactivity in 0.16, now all of them ...

Putting both forms of personal roboport behind yellow science will make railworlds (which I exclusively play) a pain to play. As Filias said, building rail networks by hand is not fun at all. I found the bad roboports you'd get using blue science a good first step to at least start using blueprints ...

The crafting machines should definitely be normalized. It makes no sense for the only machine that is able to craft a certain recipe to have a crafting speed other than 1.0. Regarding assembly machines: 1/3 or 2/3 fractions is not a nice thing to calculate with, so I'd be in favor of normalizing to ...

More fixes, nice!

Impressive decline in crashes.

+1

I agree with this, I also often feel the car controls are counter intuitive.

It looks like this would just be complexity for complexity's sake, I do not see how adding this would improve gameplay.
This requires deep changes in the engine, which would take a significant amount of time. I think this time could be better spent elsewhere.

The problem is that the updater does a sequential update. Like this: 16.1 -> 16.2 -> 16.3 -> 16.4 -> 16.5 -> 16.6 Better would be if it would do a direct: 16.1 -> 16.6 update. The issue with this is that there would have to be an update process for every version to update from that specific version...