Difference between revisions of "Engine:Unreal Engine 4"
(Add info about re-enabling UE4 console) |
m (Not really fair for me to call them hacks...) |
||
Line 42: | Line 42: | ||
===Permanent console-variable (cvar) changes=== | ===Permanent console-variable (cvar) changes=== | ||
{{ii}} Like most engines that use console-variables UE4 has a config file that it can read these variables values from at startup. | {{ii}} Like most engines that use console-variables UE4 has a config file that it can read these variables values from at startup. | ||
− | {{--}} Unlike most engines though the method it uses is a little non-obvious, which resulted in people | + | {{--}} Unlike most engines though the method it uses is a little non-obvious, which resulted in people editing files such as Scalability.ini (which could end up with inputted values being ignored depending on your graphics settings). |
{{++}} Entering cvars into the Engine.ini file instead should ensure the value changes will take place no matter what. | {{++}} Entering cvars into the Engine.ini file instead should ensure the value changes will take place no matter what. | ||
{{Fixbox|description=Add cvar name/values to the Engine.ini file|fix= | {{Fixbox|description=Add cvar name/values to the Engine.ini file|fix= | ||
Line 51: | Line 51: | ||
# Save the file. | # Save the file. | ||
# Now when you next start the game, the cvars should hopefully be set as you entered them.}} | # Now when you next start the game, the cvars should hopefully be set as you entered them.}} | ||
+ | |||
===Entire game besides the HUD and menu elements are white on Linux=== | ===Entire game besides the HUD and menu elements are white on Linux=== | ||
{{ii}} This bug may occur when using a Vulkan beta driver from Nvidia. | {{ii}} This bug may occur when using a Vulkan beta driver from Nvidia. |
Revision as of 09:17, 9 October 2019
Developers | |
---|---|
Epic Games | |
Website | |
https://www.unrealengine.com/ | |
First release date | |
May 2012 | |
Predecessor | |
Unreal Engine 3 | |
Issues unresolved
Smoothed frame rate
- Similar to Unreal Engine 3, many Unreal Engine 4 games (particularly Indie-developed games) use frame rate smoothing with a default value of 62, limiting fps in these games to 62.
- Unlike Unreal Engine 3, the .ini configuration files of Unreal Engine 4 games are by default compressed into encrypted files and not readily accessible. As a result this 62 fps cap cannot be removed through editing of the configuration files unless the developer actively enables the files to be accessible. Most indie developers lack the experience or foresight to do this since Unreal Engine 4 does not do it by default.
- If the developer does allow for the fps limit to be edited, the relevant commands are generally in GameUserSettings.ini.
Issues fixed
Re-enable developer console
- The developer console allows changing various UE4 console-variables at runtime, along with being able to run commands like ToggleDebugCamera to enable a flycam mode, amongst many others.
- Sadly the majority of games ship with the console disabled, even though all the code for it is mostly still in place.
- Fortunately that residual code allows for a simple mod that can bring back the console on most UE4 titles!
Automatically unlock the console with UE4 Console Launcher |
---|
You can make a shortcut to the UE4ConsoleLaunch.exe file, or add it to Steam as a non-Steam game, so that the game will always have the console enabled when you run it. |
Alternatively:
Extract & manually set up UE4 Console Unlocker |
---|
If Tilde key doesn't work try following the instructions in the console unlockers README.txt file. |
Permanent console-variable (cvar) changes
- Like most engines that use console-variables UE4 has a config file that it can read these variables values from at startup.
- Unlike most engines though the method it uses is a little non-obvious, which resulted in people editing files such as Scalability.ini (which could end up with inputted values being ignored depending on your graphics settings).
- Entering cvars into the Engine.ini file instead should ensure the value changes will take place no matter what.
Add cvar name/values to the Engine.ini file |
---|
The Engine.ini file will usually accept cvar name/value pairs inside it, but only if they're entered into a
|
- This bug may occur when using a Vulkan beta driver from Nvidia.
Disable Use Collapsed Arrays option for the game |
---|
Run the game with this Launch Parameter: __GL_GlslUseCollapsedArrays=0 On Steam that would be: __GL_GlslUseCollapsedArrays=0 %command% |
Ultrawide and multi-monitor support
- Unreal Engine games are Vert- by default, unless the developer specifically implements proper Hor+ ultrawide support. See each individual game's entry page for specifics.
- If a game is Vert-, FOV can be increased to give a proper 1:1 Hor+ ultrawide image. See the ultra-widescreen glossary page for details.
- If a game does not allow FOV to be adjusted, and an external mod to implement it does not exist for the specific game in question, then the game does not support a proper ultrawide experience.
- For multi-monitor setups, the resolution may be so wide that the in-game FOV option may not go high enough to achieve a proper 1:1 Hor+ image. See individual game entry pages for work-arounds.