Factorio Forums

hi,

game runs in 60 FPS all the time, and I can build complex thing on planets, but in space I get really bad performance, only when a ghost is visible.

The larger the ghost, the lower performace.

• Cut n paste of any larger area of a space platform results in a <20fps.
• Even having a bigger ghost of space platfroms will result in this drop of fps (see example of 9fps).

Save File: https://drive.google.com/file/d/1PhMdEr ... sp=sharing

Computer specs:

* AMD Ryzen 7 7800X3D
* 32GB RAM
* 4070 Ti SUPER

This is not Unique to Space Platforms; that is just the most egregious example. Try blueprinting a large, Complex combinator setup on Nauvis with thousands of entities - it slows down drawing too. Space Platforms are implemented with a lot of Layers and overdrawing of Decoratives, while Ground surfaces usually have simpler textures. Even a “powerful” GPU shrieks at the idea of millions of 2D draw calls per second.

Some things that help:
- Zoom out to the smallest “Map view” level while holding the Blueprint (where it changes from Sprites to Map). You can usually still see things with enough detail to place the Blueprint in the right spot, but it is much easier to move around
- Disable the Ghost Animations - they add extra Drawing calls to each frame
- Turn down your sprite textures from Highest. Unless you are always zoomed-in to Maximum it doesn’t really add anything, even at 4K
- Disable Shadows & Clouds & Smoke. Less things to render


Good Luck!

thanks for you input, I tested your suggestions but no luck.

I think this is a bug, as a simple blueprint with 16 solarpanels lower the FPS to 30, and 25 solar panels lowers it to 15 FPS.

This performance dip is due to the crazy amount of asteroid collectors on the platform you're looking at. Each entity being built is checking if any of the tiles it overlaps intersects with the asteroid collector front area. Given you have roughly 1800 of them on this platform, every tile in the blueprint is checking against 1800 asteroid collectors each frame.

This is now fixed for the next release.

Amazing, thank you!