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
- Nanite is not optimized for a game meant to be played at a bird's eye view.
- With large maps you'll need low quality LoD models because, which partially defeats the purpose of Nanite.
- If you want to load tons of custom assets with very high quality meshes that will make vram requirements to skyrocket. In a case like the Matrix UE demo you can get away with it because many models are used as kind of "lego parts", but if we're talking about totally custom and completely independent very high quality meshes that would disallow large quantities of custom models both from a hardware perspective of just not being technically feasible to store that many of them, and from a custom asset creator perspective as well because the amount of work required for decent results that fit with already existing content.
- Besides custom assets UE is not mod friendly.
- UE is proprietary. Haven't we learned anything about that with the Unity fiasco?. Epic could do something similar in a few years. Probably they won't but they could, they have that same capability of doing it as Unity.
UE is not a good fit for CS, at least in my opinion.