Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://i.imgur.com/QXhiSbj.png
Personally, I try to make all my blueprint near the equator. This way I have found the least issues when pasting blueprints closed to poles.
The planets are spheres, and so things bunch up as you move towards the poles. Spacing that worked near the equator can be too tight as you move away from it (or blueprints that worked fine further from it might spread enough that some buildings are too far from power if you place it closer to the equator)
And if you cross a 'fault line' where the grid adjusts you can only place that blueprint straddling that same fault line. (And conversely if you create a blueprint that doesn't cross a fault line it's illegal to place it down over one)
So you can be limited in where you can place them; and folks don't always document that.
Oh, and I've found a few instances where the game will let me place, say a spray coater, very close to a sorter but when I take a blueprint and try to place it back in the exact same spot it'll say there's an illegal collision.
(Which, again, would be caught if people tested placing their blueprints and verified that they work over a reasonable range of placements -- but I'm guilty of failing to do that myself. OTOH I generally don't publish my blueprints so the only one I'm hurting by poor testing is myself)
1) pick which latitude band you want it in (though sufficiently narrow designs can work in both the equatorial band and the next one out)
2) create the design you're going to blueprint as far from the equator as you can within that zone (so the buildings are as close as possible)
3) after capturing the blueprint test placing it both in its original location and as close to the equator as you can
3a) when testing don't just see if it places down -- fire it up and make sure all components are fully working; everything's getting power, you captured all the necessary belts & sorters, and generally nothing went weird.
(Sandbox mode can be useful for creation and testing since you can build nearly instantly, use auto-create/destroy on materials so you don't need to worry about setting up mining or the state of your other production lines; nor about the design jamming up due to nothing consuming its output. So you can place multiple copies and test them without having to use your factory to produce all those buildings and belts)
me: .... <sounds of the shift and enter key getting demolished ..>
Game "use the shift + enter key to force build"
me:..... -opens blueprint menu and creates yet another blue print because "lines don't Match" ...
Game: <simpsons Nelson voice> HA HA
(right now i am going for the "finish the game without using foundations.... yeah .... all my blueprints are useless on the home planet LOL ) i wish they could blend lat. lines a bit better when creating blue prints i started naming my prints with the Lat Line i copied it from
If the blueprint calls for placing a sorter but the target belt or building isn't there (yet) the sorter get silently omitted. (But that's the only way I've personally seen sorters not get placed)
But belt; belts can be tricky to blueprint if you need to turn a factory into a jigsaw of overlapping blueprints.
Belts can only stitch together if they have exactly a single 1 grid square overlap, and that overlap is flat.
* Have a blueprint that ends with a belt segment forming a 'T' intersection with an existing belt? that's a collision (two 1 grid square overlaps on the same square); and forcing placement will omit a belt segment.
* Have a blueprint that tried to add a single belt dot to the middle of an existing belt (or vice versa)? (Really easy to do when you have belts arching or flying over each other) that's a collision too.
* Have a blueprint with a two belt segment overlap of an existing belt? Collision and forced placement causes a gap.
* Have a blueprint that ends on a belt sloping up or down? That's a collision and forced placement causes a gap.
These issues seem, in my experience, to go away once you can create and place larger blueprints; which are self-contained and only import material through distributors, PLS, or ILS -- and you've no need to mess with splitting them into jigsaws and stitching them back together.