Unreal Engine 4.22 Released!

[markmarker]

@robob3ar

guys I won’t complain and swear at (basically) free software - come your ******* down

• however I will report that the hotfix update still didn’t fix the freezing issue with the raytracing on 20180ti with multiple gpus and monitors - no workaround worked for me yet, either not on main monitor, all on main monitor etc… any workarounds appreciated as well, and again on default settings UE will just choose crappiest gpu for some reason to render on, instead of the newest one… and also I get the gizmo tool disappearing for some reason - have to switch to a new viewport where it shows up (or is this some new feature?)

Looks like it’s somehow related to dx12 issue on laptops with optimus. No matter how hard i try editor hangs after a few seconds.

[tahayaki]

@markmarker

Looks like it’s somehow related to dx12 issue on laptops with optimus. No matter how hard i try editor hangs after a few seconds.

did you report an issue, epic team couldnt reproduce it with me, maybe youll have better luck.

[anonymous_user_214a5b82]

“Bug Fix: Fixed an issue where the splash screen was closed too quickly when not using startup movie or early preload screen, leaving several seconds of black before the level loaded”.

I have encountered this error on the phone. In version 4.22 it was notified of repair. Hope it works well. yayaya!

[one.nonplus]

Does 4.22.1 now allow Masked Materials with Raytracing?

[ZioYuri78]

@one.nonplus

Does 4.22.1 now allow Masked Materials with Raytracing?

Yep according with docs.

[gozu]

@gozu

I also have this issue, trying to run a packaged “developer” build. Works fine in editor, just a packaged build.
Error also still happens in 4.22.1 (just tested)

Hmmm…

This bug reported now.
Bless whomever did that

The Unreal Engine Issues and Bug Tracker

[TriNityGER]

@drichardson

Don’t know but you can vote/track the issue here.

Uhh nice catch! Unfortunately it says: Target fix: 4.23

[AnimatedT (Tarun)]

Another crash scenario, can’t submit because it seems specific to my level. :?

Getting this after rendering out frames is done in the sequencer.

Assertion failed: [File:D:\Build++UE4\Sync\Engine\Source\Runtime\Engine\Private\UnrealEngine.cpp] [Line: 1895] Detected negative delta time - on AMD systems please install AMD Athlon 64 X2 Dual Core Processor Driver Version 1.3.2.0053 for Windows XP and Windows Server 2003 (x86 and x64) - DeltaTime:-42.367134, bUseFixedFrameRate:1, bTimeWasManipulatedDebug:1, FixedFrameRate:24.000000

[tero83]

i installed ue 4.22 update 4.22.1 now it stucks 45% loading, i have waited 30 minutes is it normal or what to do? why these updates are so broken

[ExtraLifeMatt]

@tero83

i installed ue 4.22 update 4.22.1 now it stucks 45% loading, i have waited 30 minutes is it normal or what to do? why these updates are so broken

45% is when it starts compiling shaders. If you open up Task Manager you should see a bunch of ShaderCompiler jobs spun up. Depending on your hardware, that may take a bit.

[tero83]

hmm, i have nvidia 980, 8gb ram and never had that kind problems, waited 1,5 hours then ended it via task manager, it hasnt earlier take as long so it should now take so long

[eblade]

@tero83

hmm, i have nvidia 980, 8gb ram and never had that kind problems, waited 1,5 hours then ended it via task manager, it hasnt earlier take as long so it should now take so long

It’s not broken, and it does take that long. I don’t intend to be mean, so please don’t take this as such, but your expectations are off base.

Your machine specs are not at all adequate for a complete shader rebuild to be fast. You’re looking at I think somewhere around 1k shaders to be rebuilt before the editor comes up, then all the shaders in your project itself will get rebuilt as well. For comparison to my machine, which just did this update this morning … it took a bit over 20 minutes to get the editor up, and then another 20 minutes to get all my project shaders rebuilt. My hardware:

Core i7-4770k oc’d to 4.8ghz
32 gig system ram
2x Nvidia 1060 6GB video cards

[Dave.Roberts2]

Hi all, my UE source build is complaining about the openxr_loader-0_90.lib is not there for linking to create the openXRInput.dll. There is no source hirdparty\openxr\loader directory in the distribution zip file (4.22.1) – Anyone else seeing this? Is this supposed to be built locally?

Thanks for any input

DR

[teak421]

@ExtraLifeMatt

45% is when it starts compiling shaders. If you open up Task Manager you should see a bunch of ShaderCompiler jobs spun up. Depending on your hardware, that may take a bit.

Agreed. I’ve seen it quite a bit being stuck at 45%… nothing is wrong.

[eblade]

@eblade

It’s not broken, and it does take that long. I don’t intend to be mean, so please don’t take this as such, but your expectations are off base.

Your machine specs are not at all adequate for a complete shader rebuild to be fast. You’re looking at I think somewhere around 1k shaders to be rebuilt before the editor comes up, then all the shaders in your project itself will get rebuilt as well. For comparison to my machine, which just did this update this morning … it took a bit over 20 minutes to get the editor up, and then another 20 minutes to get all my project shaders rebuilt. My hardware:

Core i7-4770k oc’d to 4.8ghz
32 gig system ram
2x Nvidia 1060 6GB video cards

@tero83 i take part of that back – it was only a 20 minute shader recompile when going from 4.22.0 to 4.22.1. I’m having a longer than 1 hour shader recompile on a project that is being moved from 4.9 to 4.22.1. SO, it’s not rebuilding all the shaders, just a lot of them.

[tero83]

@eblade

@tero83 i take part of that back – it was only a 20 minute shader recompile when going from 4.22.0 to 4.22.1. I’m having a longer than 1 hour shader recompile on a project that is being moved from 4.9 to 4.22.1. SO, it’s not rebuilding all the shaders, just a lot of them.

hmm, so i have been waiting for empty project opening at 45% now 6 hours, it will be normal, lol

[northstar]

@northstar

having problems with with shadows on new landscapes also, but i have an old 4.21 landscape that seems to work for now… 1050ti soooo, i will never have raytracing sooooo… well there you go

whoops… my bad… seems the default cascade shading is a bit lower than i usually use… 50000, and 8… bing bang boom… no harm no foul (smile)

[darkxex]

hello, someone could see why the sprites in paper2d are distorted in movement, when you do it from a blank project? the picture is paper2d with gravity.

[Pixelpirates]

I have been using 4.22.0 since its release, and it’s been working great (used mostly DX12/Raytracing with my RTX2080Ti), but since the 4.22.1 hotfix, UE is unusable for me. It can be fine for a minute or so (if I’m lucky), but after that, the screen turns black, I get some flickering tooltip boxes and nothing works.
As I said I have a 2080Ti, the drivers are the latest Creator Ready drivers (same as I used for 4.22.0), latest Windows 10 (1809 I think) and nothing else have changed except the update.
I hope there can be a new hotfix to fix the hotfix, cause I really can’t work with this. Other than this, I’m usually very pleased with Unreal Engine and think 4.22 was a great release until the hotfix.
It seems to work longer if I don’t open the content browser. I use two monitors and usually have my content browser on my second monitor, but in 4.22.1 I just get a copy of the main viewport on my second monitor before the blackness and flickering starts. Then after that it’s good night

Here’s a dump of the crash log

[Syedhs (Syed)]

@Pixelpirates

I have been using 4.22.0 since its release, and it’s been working great (used mostly DX12/Raytracing with my RTX2080Ti), but since the 4.22.1 hotfix, UE is unusable for me. It can be fine for a minute or so (if I’m lucky), but after that, the screen turns black, I get some flickering tooltip boxes and nothing works.
As I said I have a 2080Ti, the drivers are the latest Creator Ready drivers (same as I used for 4.22.0), latest Windows 10 (1809 I think) and nothing else have changed except the update.
I hope there can be a new hotfix to fix the hotfix, cause I really can’t work with this. Other than this, I’m usually very pleased with Unreal Engine and think 4.22 was a great release until the hotfix.
I’ve tried both normal and Raytraced, and I get the same problems with each. It seems to work longer if I don’t open the content browser. I use two monitors and usually have my content browser on my second monitor, but in 4.22.1 I just get a copy of the main viewport on my second monitor before the blackness and flickering starts. Then after that it’s good night

Here’s a dump of the crash log

I think it would be much better if you can download UE4 debugging symbol too. Click on the down arrow at UE4 4.22 and then select option of which you will be presented with window below:-