Announcement

Collapse
No announcement yet.

Unreal Engine 4.23 Released!

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • replied
    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:
    Code:
    r.D3D11.UseAllowTearing=0
    Package your game, and no more crashes.

    Leave a comment:


  • replied
    Mr. Wood 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.

    Leave a comment:


  • replied
    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.

    Leave a comment:


  • replied
    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.

    Leave a comment:


  • replied
    Originally posted by Mr. Wood View Post
    I can confirm that this happend in UE 4.24.2
    Click image for larger version  Name:	Untitled1.jpg Views:	0 Size:	34.1 KB ID:	1723309
    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.

    Click image for larger version  Name:	Untitled2.jpg Views:	0 Size:	32.6 KB ID:	1723310
    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.

    Leave a comment:


  • replied
    I can confirm that this happend in UE 4.24.2
    Click image for larger version  Name:	Untitled1.jpg Views:	0 Size:	34.1 KB ID:	1723309
    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.

    Click image for larger version  Name:	Untitled2.jpg Views:	0 Size:	32.6 KB ID:	1723310

    EDIT: game (launcher) does not crash when it's added as exception.
    Last edited by Mr. Wood; 02-19-2020, 10:07 AM.

    Leave a comment:


  • replied
    Originally posted by gozu View Post


    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.

    Leave a comment:


  • replied
    Originally posted by RiotDen View Post
    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

    Code:
    [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!

    Leave a comment:


  • replied
    Originally posted by Solenism View Post
    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?

    Leave a comment:


  • replied
    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

    Code:
    [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 kernel32.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

    Leave a comment:


  • replied
    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.
    Last edited by MarcinTrybus; 12-17-2019, 02:52 PM.

    Leave a comment:


  • replied
    Originally posted by MarcinTrybus View Post
    Is 4.23.2 coming any time soon? This "fullscreen" bug is a big issue for us
    If you are mentioning this https://issues.unrealengine.com/issue/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.

    Leave a comment:


  • replied
    Is 4.23.2 coming any time soon? This "fullscreen" bug is a big issue for us

    Leave a comment:


  • replied
    Originally posted by teak421 View Post

    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.

    Leave a comment:


  • replied
    Originally posted by Sleeper. View Post

    It is. Also the effects of the issue combine with this issue:
    https://issues.unrealengine.com/issue/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

    Leave a comment:

Working...
X