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
sg.<commands> works.
For instance Ultra view distance is a value of 100 on the sg.ResolutionQuality.
I'm gonna be looking up commands for other Unreal engine games that people are used to modding to see if the codes carry over.
https://steamcommunity.com/sharedfiles/filedetails/?id=1313703067
for example inside engine.ini you put this and the following code to enable temporal AA over FXAA for older games:
Note that r.* commands are for 'renderer' for Unreal Engine, this should carry over to UE5 or uses different commands altogether.
So it's UE5 and using Nanite but not Lumen, hence why it's likely so performance heavy.
There is no engine.ini and even if you create one the game doesn't read it so the inis in the archive files most likely have priority, putting your ini files in a .pak mod or something like will most likely work but i don't really know enough about UE5 modding unfortunately.
Also PAK files are encrypted and locked tight, else if it can be cracked people can do more modding work to the whole game. Like messing with multiplayer to allow 6 players or something.
Like:
r.fog=0
r.atmosphere=0
But I dunno if these commands still work since I looked it up and it's UE4 commands.
EDIT: Found a link to some documentation on the command lines...
https://docs.unrealengine.com/5.2/en-US/scalability-reference-for-unreal-engine/