Unreal Engine 4.16 Preview

[ioFlow_Studios]

@Gwenn;699991

They did say hot reload on VS2015 was broken with linker errors, right in the first post.

2017

…

[anonymous_user_1c9ffeb6]

I just sent about 10 crash reports, using the new nvida driver and this preview, same ole crashes ive had since 4.14+.
Trying to open any of the following = crash.

Starter content particles any of them.
Any third person template animation.
Third person blendspace.
Third person animation blueprint.

All using a fresh just created template using this preview.

Specs
I7
8Gigs of ram
gtx 560ti

[AE_3DFX]

I have not tested it so i am sorry if wrong but is that volumetric really is only screen space effect so looking away from volumetric source location disables volume rays? anyone has more videos about volumetrics? please post.

[intoxicat3]

As for Base Human Control Rig I have issue with eyes. Don’t know how to resolve it.
http://i.imgur.com/glXgCqtm.png
Any ideas?

Edit: I needed to create control rig in skel mesh asset and resave sequence.

btw. any chance to have more control over head bones? eg mouth, eyes for dialogue animations/poses. I think this is doable in current system but no idea how to start.

Feedback: When exporting from Sequence it would be nice to tell which frames should be exported. (all frames, from-to) Basically I’m using this tool for prototype poses and possibility to export exact frame is great.

[DamirH]

@Gwenn;699991

They did say hot reload on VS2015 was broken with linker errors, right in the first post.

Who said anything about hot reload?

[Marc_Audy]

@ExtraLifeMatt;699752

Likely your header file is missing the following includes:

#include "UObject/ObjectMacros.h"
#include "UObject/ScriptMacros.h"

You should no longer have to include those yourself in every header as the generated header files now have those lines emitted in to them.

[Hevedy]

Volumetric Fog with a single light if you look directly give 9ms of cost, 8ms at look other world zone. When is disabled cost 6ms.

There is no a single volumetric system that cost this lots of ms in the market. From 2.5 to 3.5ms

Test using 970GTX on 1080p

[ZacD]

What are the costs in more intensive setups with multiple lights? What about indoor scenes vs landscapes?

[Stephen_Ellis]

@iamjustagamer75;700003

I just sent about 10 crash reports, using the new nvida driver and this preview, same ole crashes ive had since 4.14+.

Thank you. I have tracked down and logged your data for review.

[anonymous_user_1c9ffeb6]

Thanks, just trying to help believe me I want this fixed bad, don’t want to be stuck in 4.13.2 forevermore…

[cyaoeu]

@intoxicat3;699897

I was able to make it work with skel mesh from Engine content.

http://i.imgur.com/TY8RuK0m.png

You need to:

• Add control rig component to your skel mesh,
• In control rig select Base Human,
• Then in Modes select Animation,
• Then Select Skel Mesh you want to control,
• Create new Sequence,

And you should get what I have on the screen.

Hope we can export data from sequence to Animation Sequence and be able to run it using AnimBlueprint. This would be super great for all people prototyping new features depending on poses/animations.

Edit: Yes you can export! Thanks Epic!

@Tom Sarkanen;699918

The new in-editor animation tools are in this release. We aren’t calling them out as they are currently in a very experimental state, but all the features that we were aiming for (including baking to anim sequences) are included. We would love to hear your feedback!

As to binding to your mesh, once the plugin is enabled, you will need to open the new “Control Rig” tab in the skeletal mesh editor to set up bindings to your mesh.

Thanks for the information! I made a feedback thread for now: 4.16 preview Control Rig Sequence feedback - Feedback & Requests - Epic Developer Community Forums

[smbv1]

How about VR Mixer Reality and supporting second camera?

[kgamble]

@ExtraLifeMatt;699752

Did you previously use 4.15? There were a large amount of header changes that came with 4.15, so if you haven’t updated your project to work with that - you’ll have to do it with 4.16.

Likely your header file is missing the following includes:

#include "UObject/ObjectMacros.h"
#include "UObject/ScriptMacros.h"

I was on 4.15. Turns out the issue was that I had put the project into a folder named “4.16” which causes issues since identifiers (such as that define I copied) in C++ can’t start with a number. Renamed the folder and that fixed it.

[SteveElbows]

Regarding volumetric performance cost, I 've not done my own testing yet but some info from a github commit log was discussed in the volumetric fog thread in the feature requests forum a few weeks back:

Change 3346526 on 2017/03/14 by .Wright

[Copy] Volumetric Fog supports point and spot light shadows

• These lights are injected separately so that per-light resources can be bound (shadow depth map, static shadow depth map)
• Forward lighting of local lights can be forced with ‘r.VolumetricFog.InjectShadowedLightsSeparately 0’
• Shadowed lights come at a cost: 2.9ms for volumetric fog on 970 -> 4.2ms with shadowing

[anonymous_user_11c1b2f9]

@Stephen Ellis;699697

Hi iamjustagamer75.

You are correct that the D3D HUNG crashes are not resolved yet, but this is an important issue to us, and we are working towards a resolution. Both the 4.16 Preview and the upcoming 4.15.2 hotfix contain updates from NVIDIA that will send back additional logging information when these crashes occur. Our hope is that we can use this new information to isolate and resolve the root issue as soon as possible. (note: the new code isn’t functional yet, since it is also dependent on a new NVIDIA driver that should be releasing soon. We will keep everyone posted)

Cheers

Didn’t 4.13.2 come out 7 months ago?

[anonymous_user_848cd6d1]

Can someone enlighten this dum-dum…

A new clothing solver from Nvidia called NvCloth replaces APEX.

I’m still using APEX tools for PhysX 3.3 (up to 4.13), is there an upgrade path to this… maybe opening using PhysX 3.4, saving, or will it be less headache to just import the meshes without apx and just repaint everything in 4.16?

Capsule collision can now be imported from an FBX file. You now use the ‘UCP’ prefix on a capsule poly mesh, and it will be removed on import, and replaced by a corresponding capsule collision shape.

Is this feature where the collision follows the mesh so closely that they’re as good as static mesh collisions? No more flat lizards being driven by tall colliders. I.e. I can make that Shadow of the Colossus clone I’ve always wanted?

[Hevedy]

@boogerton;700101

Can someone enlighten this dum-dum…

I’m still using APEX tools for PhysX 3.3 (up to 4.13), is there an upgrade path to this… maybe opening using PhysX 3.4, saving, or will it be less headache to just import the meshes without apx and just repaint everything in 4.16?

Is this feature where the collision follows the mesh so closely that they’re as good as static mesh collisions? No more flat lizards being driven by tall colliders. I.e. I can make that Shadow of the Colossus clone I’ve always wanted?

If you are not able to add other api or edit the engine physics better then don’t even try to make a game based on physics.

[anonymous_user_ce8ce53d]

The cloth editor tool is not in there yet is it? i played around with 4.16 for a while but couldn’t find it.

[The_Distiller]

@BENEROT;700130

The cloth editor tool is not in there yet is it? i played around with 4.16 for a while but couldn’t find it.

Go to Editor Preferences, then under Experimental enable Clothing Tools.

[SteveElbows]

@AE_3DFX;700005

I have not tested it so i am sorry if wrong but is that volumetric really is only screen space effect so looking away from volumetric source location disables volume rays? anyone has more videos about volumetrics? please post.

It is not just a screen space effect. You can look away so that the source position of light(s) using volumetrics are off-screen, but the rays still work

However there are quite a lot of settings that can make a dramatic difference to this system, and it will take some time for everyone to learn the best settings for various scenarios. For example one of the settings (I forget which one right now) even has a tooltip that explains that it makes a big difference to how much rays will show up when you are viewing them from certain angles, eg if your camera is facing away from directional light direction.

I’m quite confident that there will be plenty of documentation, tutorials and videos of this effect given more time, as it is rather lovely to look at and plenty of people will experiment with it. For now there are just a few short videos and photos that show the results but dont attempt to explain things.

One source of information is from page 5 onwards of the feature request thread in the feedback forum. Once you scroll down page 5 a bit you will see that someone noticed when this feature was added to the github master branch version of UE4 some weeks ago, and various people tried it. There is not huge amounts of info there but it is better than nothing. Just be somewhat wary of some details because a few option names were changed in a later github commit after people already spoke on that thread about the system.

what happened to volumetric lighting / fog