Unreal Engine 4.23 Released!

[anonymous_user_2709d010]

So is this a recognized problem now? Because my game uses a huge tiled landscape and as long as I don’t hear that problem is solved, I’m not going to leave 4.22 behind

[qinwangking]

@Bigfoist

After installing the 4.23.1 update my packaged game is now locked at 60 fps (was around 170-180 before update) I have tried playing around with smooth frame rate settings as well as ‘set frame rate limit’ in blueprint. Nothing seems to work. Any ideas would be gratefully received …

Any idea now? Is this a Bug?

[qinwangking]

After installing the 4.23.1 update, the packaged game( win64 ) now locked at 60 fps. t.MaxFPS not working. Any help?

[Curs0]

@Slavq

but now it doesn’t tick in the editor like the Placed Editor Utility Base was. In-editor ticking is very important for my project, how can I restore this functionality?

what about setting “realtime” in editor viewport options?

[Slavq]

@Curs0

what about setting “realtime” in editor viewport options?

Viewport was realtime, the BP just doesn’t tick anymore after 4.23 - but there is a workaround for that, now we can use timers to achieve ticking behavior inside Editor Utility Actor BPs. Set Timer By Function Name, with looping enabled, with name of an event that has Call in Editor checkbox on.

[Curs0]

@Slavq

Viewport was realtime, the BP just doesn’t tick anymore after 4.23 - but there is a workaround for that, now we can use timers to achieve ticking behavior inside Editor Utility Actor BPs. Set Timer By Function Name, with looping enabled, with name of an event that has Call in Editor checkbox on.

sorry I was talking about widgets, they don’t tick unless you flag “realtime”

[anonymous_user_d750d84a]

@jfharp125

Got a Direct3D error, something about vertex mapping, when clicking “Create Geometry Collection” with Chaos using first shooter template and ue4 cube. Tried updating graphics driver, no worky. Still on on Window 7 pro with dual 980 ti cards. Not sure how to fix.

4.21.2 works without the error, but no Chaos either.

Still getting this error in 4.23.1 source

To be specific: I followed this guide: Destruction Overview | Unreal Engine 5.3 Documentation

to where it says select mesh and click create geometry collection button…then error message below. I used the ue cube for the mesh. I also had to place
bCompileChaos = true; in my GameNameEditor.Target.cs which was not mentioned in the guide above to get the uproject to build the 1st time. This was a c++ created project. I also enabled the plugins as stated in the guide. Beyond this, I don’t know where to look.

[RabbitHoleAvert]

@Edwardes

Thanks for the tip! I spent a while trying to reproduce this based on the assumption that it is an issue around levels being included in sub levels in addition to the persistent level. I found that with my project I can reproduce it if I have two child levels, which each include each other - if I remove the circular dependency from the sub levels, the assertion problem goes away.

However, when trying to make a clean project to reproduce this I wasn’t able to under the same conditions - I was trying to do that to submit the bug for Epic to fix. I am hoping someone else has managed that - I will stick with 4.22.3 for now.

I just hit the same !bCleanedUpWorld build error. I was able to resolve it thanks to this discussion. For anyone else wrestling with it, in my case there wasn’t a circular dependency, it was more like what RafaLL92 described](https://forums.unrealengine.com/unreal-engine/announcements-and-releases/1658668-unreal-engine-4-23-released?p=1664465#post1664465). My level structure (ignoring non-problematic levels) was as follows:

• Base level (persistent)

• Level A

• Level B

• Level C

• Level A

• Level B

Loading Level C in the editor to remove Level A and B from its “Levels” tab was all it took. Thanks for figuring that out!

[VictorBurgos]

Where is 4.23.2 at? I need the fullscreen game fix they broke in 4.23.1

[teak421]

@VictorBurgos

Where is 4.23.2 at? I need the fullscreen game fix they broke in 4.23.1

Since its only the source build version that has the error, couldn’t you change what’s in the commit: https://github.com/EpicGames/UnrealEngine/commit/c5acf47b55d495aa16ca86a0e6a75e8460933dcd – Looks like a simple change… then, build once it’s changed?

teak

[Sleeper_1]

@VictorBurgos

Where is 4.23.2 at? I need the fullscreen game fix they broke in 4.23.1

+1

literally every VR project I’m working on is broken right now
if only we could downgrade projects to 4.22

[VictorBurgos]

It’s not only source build… that’s the problem… most definitely launcher builds were affected.

[teak421]

@VictorBurgos

It’s not only source build… that’s the problem… most definitely launcher builds were affected.

Looks like the issue is wrong: Unreal Engine Issues and Bug Tracker (UE-81742)

[Sleeper_1]

@teak421

Looks like the issue is wrong: Unreal Engine Issues and Bug Tracker (UE-81742)

It is. Also the effects of the issue combine with this issue:

The Unreal Engine Issues and Bug Tracker

So the fix for UE-81377 is to set fullscreen resolution… which results in a crash due to UE-81742

It has been driving me nuts for 3 months now.

[teak421]

It is. Also the effects of the issue combine with this issue:
Unreal Engine Issues and Bug Tracker (UE-81377)

So the fix for UE-81377 is to set fullscreen resolution… which results in a crash due to UE-81742

It has been driving me nuts for 3 months now.

Not good… 4.24 is coming next week… when will they release 4.23.2? Once a new version has been released I’ve never seen them release a patch for a previous version…

teak

[gozu]

@teak421

Not good… 4.24 is coming next week… when will they release 4.23.2? Once a new version has been released I’ve never seen them release a patch for a previous version…

teak

I know rite. I’ve seen them do it once.
But 4.23 feels like a lost cause. I’ve been tracking the target fixes for 4.23 and they basically have not changed in 3-4 weeks.
Commits are being made, but a lot of the known issues don’t seem to be getting resolved.

I really really really hope that 4.24 does not have such bad bugs.

[anonymous_user_cd7ab5a0]

Is 4.23.2 coming any time soon? This “fullscreen” bug is a big issue for us

[NilsonLima]

@MarcinTrybus

Is 4.23.2 coming any time soon? This “fullscreen” bug is a big issue for us

If you are mentioning this Unreal Engine Issues and Bug Tracker (UE-81742) it is part of UE4.24 and from what I could read at the GitHub commit it can’t be part of UE4.23 because it changes public header files, so by definition it can’t be released while in 4.23.

[anonymous_user_cd7ab5a0]

Ah, that’s a shame, I saw that the target fix was 4.23.2 so I had assumed it’d come as part of it eventually. Oh well, time to upgrade then. Thanks for the info.

[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:460][962]LogWindows: Error: 
[2020.01.19-16.17.49:460][962]LogWindows: Error: 
[2020.01.19-16.17.49:460][962]LogWindows: Error: 
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000007fefd9ca06d KERNELBASE.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000007fed9e3a367 UE4Editor-Core.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000007fed9e3cbc4 UE4Editor-Core.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000007fed9c31ada UE4Editor-Core.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000007fed9b867a3 UE4Editor-Core.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000007fed9b86eb0 UE4Editor-Core.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000007fed37f083f UE4Editor-Engine.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000007fed37ed7a4 UE4Editor-Engine.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000007fecf5ffd39 UE4Editor-UnrealEd.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000007fecf990b0b UE4Editor-UnrealEd.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000007fecf6086a5 UE4Editor-UnrealEd.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000007fed3af72d6 UE4Editor-Engine.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000007fecf570fc1 UE4Editor-UnrealEd.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000007fecf56e6a8 UE4Editor-UnrealEd.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000007fecfdc5296 UE4Editor-UnrealEd.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000000013f967b0a UE4Editor.exe!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000000013f97a91c UE4Editor.exe!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000000013f97a9fa UE4Editor.exe!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000000013f98b92c UE4Editor.exe!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x000000013f98e60e UE4Editor.exe!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x0000000077aa59cd .dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: [Callstack] 0x0000000077c0383d ntdll.dll!UnknownFunction ]
[2020.01.19-16.17.49:460][962]LogWindows: Error: 
[2020.01.19-16.17.49:504][962]LogExit: Executing StaticShutdownAfterError
[2020.01.19-16.17.49:511][962]LogWindows: FPlatformMisc::RequestExit(1)
[2020.01.19-16.17.49:550][962]Log file closed, 01/19/20 21:17:49