This is not a bug. The belt is split because there’s a drill loading onto it 4 tiles before that point. This also happens with inserters, and when adding control behaviors to belts. Anything that forces a split in the belt will let side loading add when there’s normally not space.


The drill is ...

https://forums.factorio.com/viewtopic.php?p=701557

This bug is actually a bug and also not a duplicate. I think it was mislabeled a bug because it was mistaken for the case when there are compacted belt loops and/or different speed belts and it's effectively a race to see which will go first ...

This should not be marked as not a bug. This is absolutely a bug. It's also something that changed recently as pre 2.0 this would literally never happen except in very strange edge cases.

Thanks for the report.

For 2.0.21, I added "Occlude light sprites" graphics option to switch back to 1.1 light rendering. The feature is currently required for tile glow to work, and I thought I'll need to also implement alternative lava glow effect for when the option is turned off. I still will ...

I see this got moved to assigned, does that mean that it's being worked on or is on the schedule to be worked on? Not that familiar with how the forum works.

And lastly, when you write things like "I wish more playtesting had been done before release" I read "You didn't do good enough job." No, I stand by my work, this is not a bug (but I acknowledge it is an issue that deserves to be improved), another year of playtesting wouldn't change a thing ...

If you have an assembler that produces say firearm magazines, and you insert 99 iron plates into inventory of the assembler, you can insert another stack of 100 into the inventory to reach 199. However if you swap the order and insert the stack of 100 first, you can't insert the 99 as it claims ...

If you're not holding any of a building and pipette a ghost, it shows red squares over the ghost that you just pipetted from, but if you copy that same ghost, it shows up as blue when trying to place on top of that ghost. These two behaviors should be the same.

I burst out laughing watching your video. The way it just runs away.

One of the great things about Factorio was how well optimized it was, but that seems to have taken a huge hit in this new version. I wish more playtesting had been done before release.
Well, I think it is still well optimized, it's just optimized for different kind of hardware than you have and ...

It's not actively worked on at the moment. It is difficult issue, I don't know what we are gonna do about it yet.


At least for the moment, I've found a workaround is to disable smoke which seems to make the issue basically disappear, so that may be related. I'm worried about when I reach the ...

Feel free to create separate bug report.
As for prioritizing, the game runs and your saves and blueprints are not getting corrupted, so I am gonna solve the issues I know how to solve quickly, to get them out of the way and then I am gonna dive into issue I don't know how to solve, because I don't ...

Thank for the report.
I can confirm this scene renders in less than 60 FPS on my MacBook Air M1 when I match your resolution.
Sadly, it renders at 120 FPS on PC with GTX 1050 Ti (albeit only in 2560x1400)


It's worth noting that this is the native resolution of MacBook Air M1. The screen size ...

To be nitpicky, not that you don't have an issue, but the zooms aren't exactly the same.
(There are two pre-set zooms bound to F9 ( Reset zoom level ) and Ctrl+F9 ( Set zoom level to 2x ) keys. But possibly somewhat different on Macintoshes ?)


I did max zoom on both, apparently it changed ...

To be nitpicky, not that you don't have an issue, but the zooms aren't exactly the same.
(There are two pre-set zooms bound to F9 ( Reset zoom level ) and Ctrl+F9 ( Set zoom level to 2x ) keys. But possibly somewhat different on Macintoshes ?)


I did max zoom on both, apparently it changed ...

collinvandyck wrote: Sun Nov 03, 2024 2:05 pm Are you using an external monitor? I have also experienced this but more frequently when using an external display with my M2 MBP. There are at least a few threads about this floating about and they seem to share the external display factor.

Nope just using the internal monitor.

I read the pinned post and here's more precisely what is requested in the screenshot, and the log file is also attached:
Also here again is that same situation in 1.1.110:

I'm getting absolutely massive performance regressions versus 1.1.110 with simple rendering of entities. It happens when you zoom into some entities. My machine isn't exactly powerful (Macbook Air M1) but it was able to run a 1k spm megabase on 1.1.110 at 60 fps. Now at green science in 2.0 I'm ...

Heck, I'm seeing massive game performance regression even without the ghosts. I have a very small base (just got to green science) and I'm already losing fps sometimes. On 1.1.110 I built a small megabase (1k spm) and was running constantly at 60 fps. With this small base on 2.0 I'm already dropping ...

I will be looking into a fix this week. I've fished out my toaster laptop to verify.

The glitch effect is relatively cheap, but I suspect it splits batches of real vs ghost entities which increases the drawing workload more than the calculation of the effect itself.

I will probably resort to ...