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
This also applies to staff buildings that you cannot place them too close to the fence (because it cannot modify terrain), but if they are already standing, you can add the fence really close.
The problem is that when you add a road or building, the object automatically levels a small area around it. If this area is related to a fence you will not add any object.
My typical solution is to temporarily remove part of the fence, place some road or building, and add the fence again.
But you can try to raise the road or building slightly above ground level. If the ground is not modified, it should be possible to place the object closer to the fence without removing it.
Second: If you don't mind squared-off enclosures, put your paths on the grid and THEN place barriers to eliminate some of the wobbly guesswork.
When one places a path said path requires a buffer zone around it of greater than one meter.
Paths are not actual tiles but edge segments that are placed and the path between generated from them.
In your scenario, when a path is connected to an existing path the existing path is replaced with parts that create the junction of the two path segments. This is why one must move that barrier a short way from the path being worked on.