Unreal Engine 4.23 Released!

[Tinypawparade]

@Solenism

There is some kind of major performance regression related to fairly large landscapes (4k x 4k in my case), particularly if they are in sublevels. I do not have all the steps to reproduce it yet, but at least in my own level, the delay between pressing “Play in Editor” and being able to play the level went up from about 0.3s in 4.22 to about 5s in 4.23. Also, if I move my landscape to the main level, the delay goes down to 1s, which is much more managable, but still significantly more than in 4.22.

If I create a blank project and create a large landscape and move it to a sublevel, the overall delays are lower, but it appears that they still have increased significantly compared to 4.22.

Has anyone else observed something like this, or knows of a fix or workaround?

Anyone found a fix for this yet?

[gozu]

@RiotDen

Hi, what is the reason for this departure. I just fly in level, and my engine crashes. Currently there is Unreal Engine 4.23.1

[2020.01.19-16.17.49:460][962]LogWindows: Error: === Critical error: ===
[2020.01.19-16.17.49:460][962]LogWindows: Error:
[2020.01.19-16.17.49:460][962]LogWindows: Error: Assertion failed: FVector::Distance(InitOptions.ViewRotationMatrix.GetScaleVector(), FVector::OneVector) < (1.e-4f) [File:D:/Build/++UE4/Sync/Engine/Source/Runtime/Engine/Private/SceneView.cpp] [Line: 454]
[2020.01.19-16.17.49:550][962]Log file closed, 01/19/20 21:17:49

Hey, just want you to know that i get this issue as well now, have been battling it all day it’s a complete show stopper.

For me, here is some info:
Same version of the engine for at least a month, without the problem. 4.23.1 from git.
Only happens in a particular level (using world comp, if that matters)
Happens even when just the “persistent” level is loaded.

All i have to do to trigger it, is load the level, then rotate the camera lots, and it crashes in about 10 seconds.

Only thing i can think of is perhaps its related to an asset, but i turned all logging on, ran the editor in debug, and basically nothing happens, it just logs the opening of the level, then logs the crash (boo)

Going to try and replicate it in a clean project tomorrow as my brain is fried right now.

Please let me know if you discover anything about your own one!

Cheers!

[RiotDen]

@gozu

Hey, just want you to know that i get this issue as well now, have been battling it all day it’s a complete show stopper.

For me, here is some info:
Same version of the engine for at least a month, without the problem. 4.23.1 from git.
Only happens in a particular level (using world comp, if that matters)
Happens even when just the “persistent” level is loaded.

All i have to do to trigger it, is load the level, then rotate the camera lots, and it crashes in about 10 seconds.

Only thing i can think of is perhaps its related to an asset, but i turned all logging on, ran the editor in debug, and basically nothing happens, it just logs the opening of the level, then logs the crash (boo)

Going to try and replicate it in a clean project tomorrow as my brain is fried right now.

Please let me know if you discover anything about your own one!

Cheers!

Hi, I was able to get rid of this failure partially. Failure began to occur much less.

You ask how I fixed it? - it’s all just, I just switched to version 4.24.1 and the crash on the flight of the camera disappeared, but partially as I wrote above.

Try also go to 4.24.1 and run your project there, or an empty project and see if there is a problem or not.

[anonymous_user_deb0406f]

I can confirm that this happend in UE 4.24.2

I am using 1024x600 windows mode (not sure if this is related) and FPS is limited to 30. This is just Game Launcher.

My friend tested it and have problems with Avast. He need to add exception for this launcher/game.

EDIT: game (launcher) does not crash when it’s added as exception.

[NilsonLima]

@Mr.Wood

I can confirm that this happend in UE 4.24.2

I am using 1024x600 windows mode (not sure if this is related) and FPS is limited to 30. This is just Game Launcher.

My friend tested it and have problems with Avast. He need to add exception for this launcher/game.

I have Avast installed aswel and I don’t have any issues with it. I have both Avast Free and Avast Premium Security installed among the machines. There could be a false positive thou, mainly because quite often I am having DXGI_ERROR_INVALID_CALL when running packaged games in DX11, but them don’t happen when running in DX12.

[anonymous_user_deb0406f]

Yes, it is false positive (still annoying). I will try with DX12.
However, Avast shows this when I start the game via launcher and it probably detect something. I run the game via launcher with parameters received from the backend (so game could not start without launcher). Probably that is the cause.

[anonymous_user_deb0406f]

I did more testing and installed Avast free version on my computer. When I started the game launcher for the first time Avast stopped file from running due to scan and game/launcher crashed. I tried to start launcher again (without nothing added as exception) and it just started without problems. I uninstalled Avast…and during uninstall I back to folder where the game was. Avast already deleted executable without prior notice . lol

This was related to anti virus, not UE4.

[NilsonLima]

[USER=“947258”]Mr. Wood[/USER] I just checked my machines and I did noticed there was an added exception in Avast config for several folders where I usually place my projects and also where I do packaging, so I probably did that long time ago.

PS: also added exception for the UE4 installations.

[honya15]

For people having problem with DXGI_ERROR_INVALID_CALL:
I had the same problem, getting increased reports from people playing my game that they crash when using full screen or when alt tabbing with the same message.
After checking the fix they pushed to the branch, I found a quite easy way to solve the problem without modifying one single line in code.

Go to your project folder, Config,DefaultEngine.ini, go to the end of [/Script/Engine.RendererSettings] block, and write the following line:

r.D3D11.UseAllowTearing=0

Package your game, and no more crashes.