Heyo! In debug build, we clear framebuffer under tiles to red to make bugs like this more apparent. In release we clear it to black.

I think it's seam between vertices of tile quads, which should not happen to my best understanding of the math of calculating vertex positions, but for some reason ...

Thanks for the report.
Fix for 127086 seems to fix this one too, even though I am not sure why (because I don't understand why it was not working in your case in the first place)

Thanks for the report.
Fixed for 2.0.38 by making minimum atlas size to be 4096 even when sprite resolution is set to "medium"

Also fixes: 123060

Thanks for the report.
In the next release, it's gonna be improved, but I am not gonna claim it's fixed.

Due to bot optimization in 2.0, which reduces their update rate when moving to once per 20 ticks, their real position is somewhere outside of screen but their rendering position should be on ...

Right, thanks but I'm well aware that the computer isn't fast, hence me comparing it to the normal views that are all 60 fps unless there's a lot going on and the space view that always runs slow...

But if it's expected that space view is slower then all is good :thumbs_up:


I don't know if you ...

Thanks for the report.
I don't know what to do with this, and it doesn't seem to be a big issue (we expect most players who play modded already played vanilla and are not target audience for minitutorials)

No time wasted, I was just confused by the request and wanted to understand

I'm restricted to noiseless/inorganic feeling methods to set the position and velocity for the new objects?
I don't understand what do you mean by this, or rather why do you think offset and offset_deviation makes things organic in a way that you can't do by setting position and velocity yourself ...

Thanks for the report.
We narrowed it down to the texture compression shader and found a workaround for the issue.
It should be fixed in 2.0.34

Thanks for the report.
Fixed for 2.0.34

I added IconData::floating bool to fix this.

The armor modifier icon now overlaps bar bellow the icon, but it was the same in 1.1, so it's officially a feature.

So, I wanted to add a separate option for ping display duration, but found out, the system is more entangled with chat system than I thought, so I am moving this to minor issues.

As it is now "Chat message delay" needs to be non-zero for pings to show up on map.

Thanks for the report.
Fixed for 2.0.33

I was not aware we have this function, so at first I wanted to improve it to be more in-line with how 2.0 interprets icon definitions and how it renders them (in GUI - it tries to shift and scale it, so that entire icon fits the slot, not just the first layer ...

Thanks for the report.
The building previews are rendered shifted 40 render layers up so they are don't "disappear" existing building or trees, rocks, etc.

Thanks for the report.
Fixed for 2.0.33

Thanks for the report.
Fixed for 2.0.33

Thanks for the report.
We probably won't fix this. Lava shader intentionally interprets tile effect maps differently than water shader, for which the tile effect maps were created initially, and character tile effect map uses blue color channel, which lava shader interprets as there should be ...

So that's the problem. In the code, pings are considered "chat item" and use the same setting for how long they should be displayed as the chat. Since it's set to 0, they don't show up at all.

Hello, thanks for the report.
In Interface settings, is your "Chat message delay" setting set to 0 seconds?

Inserter hands are intentionally rendered in layer above machines to appear as reaching over the machines, otherwise even assemblers would draw over them. This applies to trains too ... so the cargo wagons have doors on top, not on sides.

Thanks for the report.
Fixed for 2.0.33