Unreal Engine 4.19 Preview

Mr_Tea_Rexx · March 13, 2018, 6:58am

Guys please up Vote this, needs to be Fixed

3D widgets not able to Receive Click Events in Multiplayer

Thread Issue
https://answers.unrealengine.com/que…om-client.html

Bug Report

Sn_a_ke · March 13, 2018, 8:37am

https://answers.unrealengine.com/questions/767689/ue-54530-fscreenspacedata-in-material-custom-node.html
?

amoser · March 13, 2018, 8:49am

Raziel:

I think I’m missing something here… So I was under he impression that the temporal upsampling feature is similar to checkerboard rendering, which should allow you to get higher frame-rates with minimal loss in quality. So I thought, hey, this would be perfect to use on the MacBook where the frame-rate suffers. However, while the loss in quality is very minimal, I’m finding that the frame rate drops when I enable this feature, even at the lowest screen percentage of 50%. In the editor, this is what I’m seeing:
Temporal AA enabled @ 50% screen size: 45fps
Temporal AA enabled @ 100% screen size: 38fps <- this I expected as there is a cost to enabling the feature
Temporal AA disabled @ 100% screen size: 47fps <- this is not expected, higher fps with feature disabled and screen size @ 100%

So after this I disabled high-dpi mode as I figured that maybe it’s enabling the retina display mode for the 3D window or something that could be affecting performance, but from there I’m finding a drop from 67FPS with TAA disabled, to 50fps with TAA enabled with a screen size of 50%. In other words, I end up with a frame rate lower than simply disabling this feature and not using temporal upsampling at all.

What am I missing here? Is the feature simply a conceptual feature which isn’t actually useful in the real world yet, or is there something else I should be doing in addition to enabling temporal upsampling in the project settings and dropping my screen size to reap the benefits?

If I understand correctly, you might be better off comparing TemporalAA+Upsampling at 50% to TemporalAA enabled but with no upsampling at 100%. Disabling TemporalAA altogether will certainly make the scene render more quickly, but that’s probably mostly due to the overhead of the TemporalAA itself rather than the upsampling.

So far I’ve had pretty good luck with the performance of upsampling vs. rendering at full resolution.

Raziel · March 13, 2018, 11:25am

TemporalAA+Upsampling at 50% to TemporalAA enabled but with no upsampling at 100% <– this is exactly what I have done and the frame rate is actually lower with upsampling enabled at 50%. I have not disabled temporal AA in any of my tests, sorry for the confusion, I should have written temporal AA upsampling in my original post rather than just temporal AA…

Out of interest sake which platform have you tried it on and what were the rough FPS results? I’m wondering if it’s maybe functional but not well implemented on the Mac platform. Would be nice getting a list of official results of performance boosts on different hardware configurations.

smbv1 · March 13, 2018, 4:00pm

Who supports Image-based tracking now? ArKit or ArCore?

I found it’s been released with Arkit 1.5
https://developer.apple.com/documentation/arkit/recognizing_images_in_an_ar_experience

Z-enzyme · March 14, 2018, 7:23am

Found 2 things that might be an issue.

1: Can’t set map from class defaults, it worked perfectly in 4.18

2: Assertion failed error occurs randomly in one of my VR projects, can’t firgure out what causes it.

Anyone help?

MothDoctor · March 14, 2018, 2:41pm

According to this report, the issue appeared in 4.14 and has been fixed… in 4.20

anonymous_user_de23abbb · March 14, 2018, 3:18pm

My body is ready, gimmie that 4.19 goodness.

But seriously, is a release before GDC still likely?

Stephen_Ellis · March 14, 2018, 3:55pm

RELEASE!

4.19.0 is now available: Unreal Engine 4.19 Released - Announcements and Releases - Unreal Engine Forums

I’d like to thank everyone once again who helped us test during this preview, we were able to catch and address a number of issues thanks to you.

I am now closing this post, please continue any 4.19 discussions on the new thread. And remember, please report any new issues you find to the bug submission form.

Cheers