Awesome, no problem!

Hello, I think I know what the problem is.


...
Bugfixes

...
Fixed possible memory management error when initializing GPU device counters with Metal. (https://forums.factorio.com/128505)
Fixed texture initialization on low-memory Macs with the Metal graphics backend. (https://forums ...

Hello! Thanks for the report, video, logs, and saves. I believe this is a duplicate of https://forums.factorio.com/122891, which should have been fixed in 2.0.44. However, if you're still experiencing this issue in a version >= 2.0.44, please let us know by updating this thread or opening a new bug ...

Hello, can you share a screenshot (or two or three) and your game's log file, as per these instructions?

Thanks for the report and videos. I'm not sure exactly how your remote view ended up in this state, but I did find one method of reliably reproducing it, which will be fixed in 2.0.50. If it happens again on or after 2.0.50, please let us know by filing a new bug. Also, if it happens again, it ...

2.0.50 will fix another potential cause of failing demolisher consistency checks and will recover existing saves suffering from such failing checks.

Hello, thank you for the report and save files. This will be fixed in 2.0.50.

Thank you for providing the save files and logs; I was able to reproduce the crash on startup with version 2.0.48 and have found the culprit to be some changes related to the modding API and solar panels, which is affecting the "Solar Array Wings" mod that you have installed. 2.0.49 will check mods ...

Got another instance of the error with below save, Factorio 2.0.47.

[Split from https://forums.factorio.com/126642]


While I look into the cause of the consistency failure, here's a repaired version of your save.

Also, please share your log file containing the consistency failure; it will help ...

Hello, yes, please attach your log file and any affected save files so that we can reproduce the issue further, as per these instructions

0n0w1c wrote: Mon May 12, 2025 12:20 pm With 2.0.48, switching to Metal backend, while making no other changes, works for me now without issue, thank you!

Awesome, thanks for letting me know! If something does crop up, feel free to create another bug report/technical support post or update this thread.

Thanks for the report, video, and logs. I believe this is a duplicate of 122891, which should have been fixed in 2.0.44. However, if you're still experiencing this issue in a version >= 2.0.44, please let us know by updating this thread or opening a new bug report.

No problem! We were able to reproduce the issue with the new save you sent us.

Hi, is this the correct save? It doesn't seem to have any of the mods that are listed in your log file.

In addition to other fixes, 2.0.48 will disable native resolution rendering by default for the baseline Apple M-series GPUs (M1, M2, M3, M4, non-Pro, non-Max, and non-Ultra chips). Obviously, players are free to change the default setting further if needed.

2.0.48 will include a fix for the magenta screens when using the Metal backend and will reduce the default graphics settings for Macs with 8GB or less of unified memory.

If this issue is observed again after 2.0.48, feel free to either update this thread or open a new one.

Have you encountered this issue in versions prior to 2.0.45 or when the graphics backend is set to OpenGL? Or does it only occur when the Metal backend is enabled?

Hello, thank you very much for the feedback and logs. In addition to introducing the Metal backend, 2.0.45 also reclassifies Apple GPUs as being more capable than past integrated GPUs and enables higher graphics settings by default for these machines. However, it's clear that further tuning is ...

berggen wrote: Tue May 06, 2025 3:47 pm I'm hoping that also comes with ability to read/modify their territory?

Of course!

Excellent, thank you for the feedback. A subsequent update will contain adjustments to the default settings for devices similar to yours so that manual adjustments are no longer required, and a fix for the magenta screens. Further updates will be posted to 128458.