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
1) Because maps are an entirely different process. Any non-Source map basically has to be either remade from scratch or ported as a model (which has massive limitation)
2) Because it's bigger than Source can actually support. It's about three kilometres per side, whereas Source can only support maps about one kilometre per side at absolute most.
And secondly, a Fortnite map is likewise probably also very different from a Fortnite model. While people may have figure out how to extract Fortnite's models from the game to use in 3D modelling tools, the same may not hold true for Fortnite's map(s?) at all.
Edit: And thirdly, as Marco Skoll mentioned, it's way too big for Source to handle at the proper scale.