Unreal Engine 4.15 Now Available, VR Improvements Include Menu, Number Pad and PSVR Aim Controller support

Loads of new features have been added and its still free.

This Epic Games has released the latest iteration of its popular videogame development software Unreal Engine 4.15.

The last version was only released in November 2016, and since then the studio has been pumping out the preview builds, adding experimental new features whilst ironing out the bugs and glitches. Unreal Engine 4.15 continues Epic’s support of virtual reality (VR), finalising additions like support for PlayStation VR’s Aim controller along with general VR Editor improvements.

PlayStation Aim Controller

Epic’s updated the Quick Menu and Radial Menu in the VR Editor, improving usability and functionality whilst giving them a new look. A new Number Pad UI has been added allowing developers to quickly enter numbers from zero to nine as well as negative and decimal values in text fields

An experimental addition to 4.15 comes in the form of Monoscopic Far Field Rendering which provides a performance boost by only rendering distant objects once. As it is experimental for the moment Monoscopic Far Field Rendering is only supported on mobile platforms for now.

For the full list of features head to the Unreal Engine blog for a concise rundown including support for Nintendo SwitchVRFocus will continue its coverage of Unreal Engine, reporting back with the latest updates.

VR

  • New: Updated the GoogleVR SDK to version 1.01.

  • New: Exposed “Is HMD Connected” to blueprint. This means that HMD hardware is ready to use. UE4 may or may not be using the HMD now.

  • Bugfix: Fixed rendering of Canvas tiles in stereo mode to be rendered for both eyes. This fixes the rendering of the background behind various stats shown by the STAT console command.

  • Bugfix: Fixed threading issue on Oculus Touch controllers, which could cause jittering in some circumstances.

  • Bugfix: Fixed an assertion when using Oculus stereo layers with MSAA, due to binding an unresolved depth surface.

  • New: Added analytics event to Vive HMD initialization.

  • New: Updating Oculus SDKs

    • Oculus PC SDK 1.10.0

    • Mobile SDK 1.0.3

    • Audio SDK 1.0.2

    • Platform SDK 1.10.0

  • Added a missing render target clear when using a VR hidden area mask and a post processing material.

  • Added in a new CVar vr.SteamVR.UsePostPresentHandoff, which defaults to 0. When set to 0, we do NOT use the SteamVR Post Present Handoff, which costs some performance GPU time. When 1, we use the call, and get some extra GPU performance. However, this call is NOT safe for scenes that have frame-behind GPU work, like Scene Capture components and Widget Components.

    • For users that were using 4.14.1, and seeing a GPU timing improvement, that behavior is now off by default.  You can re-enable it by setting vr.SteamVR.UsePostPresentHandoff on your project to get it back.  Be aware that SceneCaptureComponents or WidgetComponents may cause async reprojection in SteamVR to fail in that case.

InvestVR OrangeLady Horizontal

You might also like More from author

Comments