Factorio Forums

Hi Devs,

When landing on a planet from space, the rocket has something wrong with the alpha mask when rendered on top of clouds which results in a jarring box around the rocket sprite. It breaks the immersion in an otherwise beautiful game. I'm hoping it is a quick fix!

Please see a screenshot of the bug below.



Thanks in advance for fixing the bug!

- Kyle

Thanks for the report.
This is unusual (have not seen it be like that neither on our computers nor in player videos/streams), can you post your log please? (3638)

Hi posila,

Thanks for the reply! Sorry about the log file missing. Please find it attached.

Hopefully it helps reveal where the problem is!

Thanks for the log. To be honest, it made even mind boggling, I thought you were playing on some obscure hardware or Linux with weird build of graphics driver. I did not expect Win 11 with RTX 4060 Ti

Yes, nothing unusual with my setup. Did you need my save too? I was landing on Fulgora with that screenshot.

When I get the chance, I was going to try it on some different computers.

Edit: I just tried it on another computer. Windows 11, Geforce 1660S, i5-10400 with the same results.

posila wrote: Tue Nov 12, 2024 5:12 pm Thanks for the log. To be honest, it made even mind boggling, I thought you were playing on some obscure hardware or Linux with weird build of graphics driver. I did not expect Win 11 with RTX 4060 Ti

Curiously I've also seen the exact same issue on my M3 Pro MacBook Pro. It doesn't do it 100% of the time, but I definitely did see it the first time I went to my first new planet (also Fulgora), which was circa Factorio 2.0.12. I haven't changed any of the graphical settings since then.

I had noticed something similar with curved rails in Factorio 1.1 having a visible tint to the transparent area of their sprites.

edit: updated log below

Hi Devs,

Please find my save attached so you can hopefully reproduce the issue. I am in space at the start of the save but you'll see it once you go down to Fulgora.

Thanks again!

FWIW that save also reproduces for me on my Mac on 2.0.17.

I also tried on a Windows 11 PC with a 3050 and i5-9400 with the same bug being displayed. See log attached.

And here is the log with the 1660s which also displays the same bug.

Thanks for the save, I can see the problem in it too.

Thanks for the report.
Fixed for 2.0.22