Unreal Engine 4.14 Preview


A Preview of the upcoming 4.14 release is available now on the Launcher and Github. We have made this Preview available so that our developer-community can help us catch issues before the final release. As fixes are implemented, we will release updated previews throughout the development cycle. Please be aware that the preview releases are not fully quality tested, that they are still under heavy active development, and that they should be considered as unstable until the final release. Developers should not convert their projects for active development on preview releases. Please test on copies of your project instead.

We encourage users to check out the preview to try new features and inform us of any issues which we may not have caught. Links to known and fixed issues for this release are provided below. If you discover any additional issues with this preview release, please report them using the guidelines in the link: How to Report a Bug.

Known & Fixed Issues

4.14 Preview Summary

This list provides a brief summary of updates in this Preview which may benefit from additional testing. Full release notes will be made available with the final 4.14 release. We may not be able to provide additional information about updates at this time.

  • Rendering Updates:

    • A Forward Shading Renderer for VR (Experimental) that supports high-quality lighting features, enables Multisample Anti-Aliasing, and is faster than the Deferred Renderer in select projects.

      • To use this, enable ‘Forward Shading’ in the Rendering Project settings and restart the editor.

      • To use MSAA, set the default Anti-Aliasing Method in the Rendering Project settings.

      • DBuffer Decals, Dynamic shadows and Capsule shadows do not handle MSAA properly yet and may exhibit artifacts along object edges.

      • Not yet supported in the Forward Renderer:

        • Screen space techniques (SSR, SSAO, Contact Shadows)

        • Shadow casting Movable Lights

        • Dynamically shadowed translucency

        • Translucency receiving environment shadows from a Stationary light

        • Light functions and IES profiles

    • Automatic LOD generation for static meshes can now be accomplished without middleware plugins.

      • The high level settings for controlling the generated LODs are in the static mesh viewer under LOD Settings.

      • “LOD Group” provides a list of presets. These can be changed per project in BaseEngine.ini under [StaticMeshLODSettings]. The use of LOD groups is suggested.

      • If modifying details of auto generation for each LOD, they can be found under Reduction Settings.

    • Reflection Capture lightmap mixing improvements.

      • The engine mixes the indirect specular from the Reflection Capture with indirect diffuse from lightmaps. This helps to reduce leaking.

      • Lightmap mixing is no longer done on very smooth surfaces.

      • Reflection Captures and SSR match much better and it’s harder to spot transitions.

      • This affects existing content - in cases where you had reflection leaking on smooth surfaces, that leaking will be much more apparent. To solve this, place additional reflection probes to reduce the leaking. Levels should have one large spherical capture at a minimum. You can also revert to the old lightmap mixing behavior with a rendering project setting: “Reduce lightmap mixing on smooth surfaces”

    • The Contact Shadows feature helps provide sharp detailed shadows at the contact point of geometry.

      • You can enable these by setting the Contact Shadow Length property. This controls the length of the ray cast in screen space where 1 is all the way across the screen. Large values can degrade quality and performance so try and keep the length to the minimum that achieves your desired look.

    • A Live GPU Profiler is available which provides per-frame stats for the major rendering categories. To use it, enter the console command: stat gpu.

      • The GPU stats can be recorded to a file when the title is running for analysis later. As with existing stats, you can use the console commands stat startfile and stat stopfile to record the stats to a ue4stats file, and then visualize them by opening the file in the Unreal Frontend tool.

    • The new Vector Noise material graph node adds several functions with 3D or 4D vector results. Due to the run-time expense of these functions, it is recommended that once a look is developed with them, all or part of the computation be baked into a texture using the Draw Material to Render Target Blueprint feature

    • NVIDIA Ansel support is now exposed as a plugin. Once you have enabled the plugin you can access Ansel in a standalone game session. Please read the included Ansel documentation for instructions on how to whitelist your in-development application.

    • A few new Material Graph Nodes have been added to the graph editor. Each is intended to improve workflow and increase readability.

      • GetMaterialAttributes - This node is a compact replacement for BreakMaterialAttributes

      • SetMaterialAttributes - This node is a compact replacement for MakeMaterialAttributes

      • BlendMaterialAttributes - This is a new node to allow easier blending of Material Attributes structures.

  • Framework Updates:

    • Animation Tools have been split into separate asset editors rather than using one editor with multiple modes. Functionality that is common to each of the editors is now generally found in the viewport.

    • Default Post-Process Animation Blueprint allows you to assign an Animation Blueprint to a Skeletal Mesh that will always be run after any Animation Blueprint assigned in the component. This allows for dynamics, controllers, IK or any other anim blueprint feature to be related to a mesh and not have to be duplicated in every animation blueprint intended to be used on that mesh.

    • The engine is updated to use PhysX 3.4, which enables a lot of features which will be exposed over time. Current available improvements: kinematic objects update faster, CCD support for kinematic objects, and faster convex hull cooking.

    • Vehicle Improvements have been made with wheel forces and the addition of SimpleWheeledVehicleMovementComponent.

    • Skeletal Mesh to Static Mesh Conversion lets you right-click actor(s) in the level viewport and convert their current state to a new Static Mesh asset.

    • Simplygon SDK integration has been updated to version 8.1.

    • Cloth Skinning improvements have been made by calculating our own mesh-to-mesh skinning data for clothing within the engine rather than using exported render data. This resolves issues where normals could sometimes appear incorrect, and there is no longer a restriction to one UV channel.

    • Streamlined GameMode and GameState Classes by adding GameModeBase and GameStateBase classes as parents of existing classes GameMode and GameState. Core features needed by all games are now in the Base classes, while legacy and shooter-specific features are in the GameMode/GameState

    • Improved Cable Component by adding simple collision, stiffness setting, sockets at each end, and the ability to set either end as “free”.

    • Improved PoseDriver animation node by allowing it to drive bone transforms as well as Morph Targets, adding an option to use translation of the driving bone, and showing more information in debug drawing.

    • Virtual Bones can be added to a skeleton, which can be used to make it easier to retarget or change reference frames for controllers.

    • Child Anim Montages can be created based on a parent Montage, allowing you to replace animation clips while maintaining overall timing.

  • Core Updates:

    • Cooked builds can now use a completely new Event Driven Loader (Experimental) which is far more efficient than the old streaming code. Games using the EDL should see the load times drop by about 50%. The Event Driven Loader comes with an unified code path for loading assets. This means that all packages will be loaded using the new async path instead of the old blocking path. EDL is currently an experimental feature and is disabled by default but can easily be enabled through Project Settings.

  • Editor/Tools Updates:

    • Support has been added for editing TMap and TSet properties from the Details Panel.

      • Sets are similar to Array but Sets will ensure that all contained elements are unique.

      • Maps will have a key and a value and you can edit both within the details panel. Like Sets, all keys must be unique.

    • Multitouch Support in Windows has been added. Touch events will now be generated in Windows 7, 8, and 10 when using a touch screen. This will enable touch enabled games and experiences on new Windows tablets and also enables testing touch controls for mobile games without having to deploy to a target device.

    • Outlines on Fonts can be applied in UMG and Slate.

  • Network Updates:

    • Replication Performance has been improved by as much as 40% by refactoring how the engine replicates properties from the server to connected clients. It now shares the work for all types of properties (not only unconditional ones), which means the work done to check when properties have changed (and need to be sent) happens much less often.

  • Build Updates:

    • Visual Studio “15” is now supported, in addition to Visual Studio 2015. If you have multiple versions of Visual Studio installed, you can select which to use through the ‘Source Control’ section in ‘Editor Preferences…’.

  • Sequencer Updates:

    • The Camera Rig Crane has been updated to mimic the movement of a physical crane.

    • Record audio from a microphone while recording into a sequence.

    • Drag and drop files from your computer into the Media Player’s viewport.

  • VR Updates:

    • Multiview Support (Experimental) for the Mobile Forward Rendering path improves performance by reducing hitches of instanced stereo. You can enable this under Project Settings > Rendering > VR > Mobile Multi-View, then re-start the editor.

  • VR Editor Updates:

    • Landscape Editing in VR can now occur using motion controllers.

    • You can instantly Reset the world’s scale to its default by tapping the touchpad button while gripping the world. This makes it easy to get back to your “player’s size” while editing.

  • Mobile Rendering Updates:

    • Mobile games ship with Vulkan support and can now be enabled or disabled using device profiles, with fallback to ES 3.1 and ES2

    • Custom Depth is now supported on mobile. Custom Post-process materials can now sample from SceneDepth and CustomDepth as well as SceneColor.

    • The Scene Capture Source settings that output Inverse Opacity and Depth values are now supported on mobile.

    • The Mobile Patch Utilities Blueprint library now included contains all the functionality required to allow a mobile game to download and install game contents and patches from a cloud website instead of being distributed as part of the initial download from the App Store. Both Android and iOS are supported.

  • Landscape Updates:

    • Landscape Mirror Tool now supports rotated mirroring to create diagonally-opposed multiplayer maps.

  • Platform Updates:

    • Amazon GameCircle Plugin for Kindle Fire is included. Enabling the plugin will provide access to a new Amazon GameCircle project settings panel under the Plugins category. Changes to the AndroidManifest.xml for Fire TV may be enabled here.

    • Initial Support for Android on Linux thanks to pull requests from the community. CodeWorks for Android from Nvidia for Linux is the easiest way to set up the NDK and SDK tools needed. In addition, OpenJDK 1.8 should be installed; set JAVA_HOME to point to your install. Please note Android Vulkan on Linux is not supported at this time.

    • SDK Updates for XboxOne, PS4, HTML5, MacOS 10.12, iOS/tvOS 10.0.

“Multitouch Support in Windows”, this is kind of funny, since I am just in the middle of a windows multitouch app development and was searching for a solution for multitouch on windows 10 :slight_smile:

This version supports Nintendo Switch??

Ohhh, Multiview for mobile VR !!! Sweet!! Thanks Epic.

Are there any plans to fix Blueprints and the /Engine/Transient bug? I switched my project to be mostly C++ now due to that “error” happening in every single blueprint.

NVIDIA Ansel. Yum.

Physical units for directional and skylight for 4.14 please.

Been using the forward render lately. Godlike upgrade for VR projects.

More than one UV map on APEX Cloth Meshes. Thank you Epic :slight_smile: . Solves one of my actual problems.
I hope you’ll also consider adding an option to split up root motion to let you choose to only use specific parts of root motion (like X-Axis movement or Y-Rotation). Would be really useful.

EDIT: What about making the Editor UI High-DPI compatible without the Windows-internal compatibility scaling that blurs the whole window?

Any improvements to Alembic’s UV problems?

Probably doesn’t as Switch was just announced and it will be coming in March of 2017. On plus side it uses custom Nvidia Tegra SoC, so it’s gotta be OpenGL / Vulkan compliant out of the box.

NES support yes, SNES will be in 4.15


This is the single best thing in this entire update for me. All that shooter/UnrealTournament-specific pollution in the code has been bugging me since forever. Even if it didn’t actually have any negative effect in theory, it just made everything feel… dirty. I’m so glad you guys did this. Possibly Actor could get the same treatment too in the future? (removing the Damage functions, etc… so that we have an ActorBase with only the bare necessities and no bloat)

Great job!

It was annunced to the public, I’m pretty sure Epic under strict NDA knew about it long ago :smiley:

This would be really awesome! I hope they add this.

Will we have a way (when using forward) to exclude objects from motion blur ? This is badly needed on vehicles etc.

I just read up on Nvidia Ansel - no stereo 360 deg. shots, all mono? :confused:

I have two questions about 4.14 Preview 1:

  1. Is simulate mode viewport updating broken for anyone else? On my computer it doesn’t update viewport at all unless I keep mouse left clicking on it… 4.14 promoted builds didn’t do this.

  2. Any plans on getting any kind of dynamic shadows on 4.14 forward when static lighting is disabled? I’d mainly want to have directional light (sun on outdoor levels). Only way I can get dynamic shadow casting on 4.14 forward is if I keep static lighting enabled and put directional light into stationary.

Try to use FXAA instead of Temporal AA. It helps for wheels at least.

Virtual bones sounds useful !