Unreal Engine 4.24 Released!

[frostic]

@RiotDen

Ok, but what about the flashlight do not tell me? I didn’t apply any effects; this happens when you shine in the mirror.

try setting the color of your light to white. you must have changed it to blue without realizing it or ur bad at trolling because the light is also shining on the wall and it is blue. so your light’s color is set to blue.

[RiotDen]

try setting the color of your light to white. you must have changed it to blue without realizing it or ur bad at trolling because the light is also shining on the wall and it is blue. so your light’s color is set to blue.

I said that I did not use any effects, the standard light is white, I did not change it. Everywhere it shines white, but when you shine in the mirror, everything turns blue. If you do not shine in the mirror, then it is white.

P.S. He asked a serious question, and you write some kind of nonsense about trolling.

[motorsep]

still no fix for scene capture 2d causing lag in VR in packaged builds but runs good in vr preview? ooof. well i guess i’ll wait another 2 months. maybe then they will fix it

Was it ever entered into issue tracker? Do you have UE- number for it ?

[anonymous_user_fb040bbd]

Still no Chaos. Apex does work. Does Chaos work in the compiled version?

[Nocturness]

hi,

on 4.24.2 with htc vive … controller mapping still not working correctly.

on 4.23.1 works with no issue but u know old mapping changed(deprecated) and i cant manage all new mapping inputs. negative and/or positive values not working correctly for almost all.

Just please lookat “MoveForward” “MoveRight” “Throttle” and “Steer” …as u can see in the image keyboard inputs working without issue.

new mapping/my inputs :

https://i.ibb.co/nQJDw9f/mapping2.jpg
https://i.ibb.co/W0MPnX8/mappinghtcvive.jpg

Is that bug still exist or just for me?

Package waiting for this issue.(since 4.24)

Need advice

Thx.

PS: tested all new mapping: trackpadX/Y | Up/Down/Left/Right | Trigger with positive and negative values but It did not work.

[SparkyMcSparks]

@Nocturness

hi,

on 4.24.2 with htc vive … controller mapping still not working correctly.

PS: tested all new mapping: trackpadX/Y | Up/Down/Left/Right | Trigger with positive and negative values but It did not work.

Are you using SteamVR Input? It’s part of the engine in 4.24 so it might be kicking off unless you’re opting out of it. You’d need to generate manifest + binding and then reload them, here’s a tutorial link from the Valve wiki: Quickstart · ValveSoftware/steamvr_unreal_plugin Wiki · GitHub

Also an important note on how Axis Inputs work with SteamVR Input:

Vector2 Actions - As Unreal doesn’t have a concept of a Vector2 action we auto group two vector1 actions with names that end with _X and _Y. For example, to create a mapping for MoveLeft you will need a MoveLeft_X and a MoveLeft_Y that you bind to their corresponding controller axis. See the sample inputs for an example.

So if you wanted artificial movement with your left controller you’d need

• MoveLeft_X with a mapping for Vive(L) Trackpad X
• MoveLeft_Y with a mapping for Vive(L) Trackpad Y

[Vexar]

I saw a fix to the rendering of APEX objects so I am happy about this patch, Thank you awesome folks at Epic!

Update: I had to submit a new bug report the claimed fix for “Fixed! UE-85928 Apex Destructibles are not properly rendered” still broken in this patch.

[gojushin]

Roses are red,
Violets are blue.
Epic Games fixed my problem,
with Hotifx 4.24.2.

Literally spend the last 30 hours trying to figure out why tesselation wasn’t working on landscapes.

[frostic]

Was it ever entered into issue tracker? Do you have UE- number for it ?

yes there is a tracker for it i forget the number

[AlanEdwardes]

Hi,

My Linux players reported a strange flickering effect (similar to Z-fighting) - after digging in, I found the following with 4.24.1 and 4.24.2 using the Vulkan RHI on Ubuntu:

• Spline meshes appear flickery with official Nvidia driver 440.44
• Spline meshes work fine with official Nvidia driver 435.21

I can’t work out whether this is an Nvidia driver regression, or an Unreal Engine bug. I can’t see it being an Unreal Engine bug unless the Vulkan RHI is relying on odd driver behaviour, or is detecting the version and using different logic depending on the driver version.

Here’s a screenshot of the behaviour, the dirt track here is a Spline mesh: https://steamuserimages-a.akamaihd.net/ugc/787502605614049534/BB2A82C470DAC572EE2C7F630812ED41DCD8E2A2/

Is anyone else in the same situation? Have you found any workarounds?

Thanks,
Alan

[frostic]

@Alan_Edwardes

Hi,

My Linux players reported a strange flickering effect (similar to Z-fighting) - after digging in, I found the following with 4.24.1 and 4.24.2 using the Vulkan RHI on Ubuntu:

• Spline meshes appear flickery with official Nvidia driver 440.44
• Spline meshes work fine with official Nvidia driver 435.21

I can’t work out whether this is an Nvidia driver regression, or an Unreal Engine bug. I can’t see it being an Unreal Engine bug unless the Vulkan RHI is relying on odd driver behaviour, or is detecting the version and using different logic depending on the driver version.

Here’s a screenshot of the behaviour, the dirt track here is a Spline mesh: https://steamuserimages-a.akamaihd.net/ugc/787502605614049534/BB2A82C470DAC572EE2C7F630812ED41DCD8E2A2/

Is anyone else in the same situation? Have you found any workarounds?

Thanks,
Alan

this is also happening in VR if you use meshes from engine content maybe they broke a shader or something. ooof. try setting the lightmap resolution higher. it seems to have helped mine a bit. i was using 64 as resolution. 512 seems to have fixed mine. maybe try 1024 for your mesh? experiment with it. let me know if it helps.

[Daffrendo]

Found a bug, occurred in 424.1 as well, but also exists in 424.2:

If I add 2 or more animations for a single mesh on Sequencer, and I make one of the animations have Animation>Properties>When Finished>**“Keep State”, **
when I scrub through the animation, the mesh all of the sudden pops to the Default state and is locked in this default position until I close out the Sequencer and re-open it. Like if I saved a Sequence, I close and reload it. Then I can scrub maybe 2-3 times before it locks up to Default state again. When it locks up it does not play/show any animation at all.

Now, if I only have 1 animation on the sequencer timeline, and set it in Properties to “Keep State” when finished, it can be scrubbed indefinitely.

So, bug involves (a) Keep state when (b) 2 or more animations are on the timeline, leading to a (c) mesh lock-up.

Workaround is saving the sequencer, closing out sequencer, and opening up sequencer again, but it’s a real pain in the Asset.

THX!

[Nocturness]

@SparkyMcSparks

Are you using SteamVR Input? It’s part of the engine in 4.24 so it might be kicking off unless you’re opting out of it. You’d need to generate manifest + binding and then reload them, here’s a tutorial link from the Valve wiki: Quickstart · ValveSoftware/steamvr_unreal_plugin Wiki · GitHub

Also an important note on how Axis Inputs work with SteamVR Input:

So if you wanted artificial movement with your left controller you’d need

• MoveLeft_X with a mapping for Vive(L) Trackpad X
• MoveLeft_Y with a mapping for Vive(L) Trackpad Y

Thx for letting me know, i added some extra mapping (like u said) working now but this is really annoying. i really miss the previous one (deprecated) and this workflow still not stable.

Regenerate from editor still not working. Added new mapping manually from “steam bindings dashboard” .

Hopefully an easier solution will come soon, not easy usable with the current custom mapping workflow.

if it does not come i don’t think of applying more with vive.

Thx again.

[overreal]

When I package my project for UE 4.24.2, is it using dx12 now? It is using dx11 on UE4.23, running on the same system.

[StyleMarshal]

Big thanx for fixing play rate

[Lareon]

@overreal

When I package my project for UE 4.24.2, is it using dx12 now? It is using dx11 on UE4.23, running on the same system.

double check your rhi target in your project settings. (Platforms - Windows - Targeted RHIs)

set the default rhi to DX11

unless you’re saying it’s ignoring this?

[lotodore]

UE-85899 “UAIPerceptionSystem::Tick() has a chance of not being called after level reloading” was (and is still) listed for the 4.24.2 hotfix but still says “unresolved”. Is there some more information available? This issue occurs on dedicated servers and even caused bad Steam reviews due to non-working AI.

[3DMoss]

For those having issues with Play In Editor delays with large landscapes, Epic has been able to reproduce the issue from my bug report Unreal Engine Issues and Bug Tracker (UE-87701). I found a workaround by moving the landscape from the sublevel to the persistent level (or vice versa) will return PIE start times to normal. Just don’t save the level, or the times will skyrocket again.

[AlanEdwardes]

I have reported the Linux/Vulkan spline mesh rendering bug as case #00152785. Here’s a simple project that reproduces this bug, only under Nvidia driver 440.44 (the latest at the time of writing): https://iamestranged.com/distribute/support/SplineBug4-24.zip

It is not related to VR/lightmaps as one user reported above (that must be a separate issue).

I do hope this is an engine bug rather than a driver bug, it feels like the latter would take significantly longer to get fixed…
Alan

[Sarlack]

I was able to compile 4.24.0 and 4.24.1 with no errors. now with 4.24.2 I get these two…

Chaos - C1083: Cannot open include file: ‘PBDCollisionConstraint.ispc.generated.h’: No such file or directory
GeometryCollectionEngine - C1083: Cannot open include file: ‘GeometryCollectionComponent.ispc.generated.h’: No such file or directory

Does anyone know why these files aren’t generated or if they were, why can’t they be found?

I did update VS since last successful 4.24.1 build.
Using Visual Studio 16.4.3 - 14.24.28315 toolchain in Windows 10

Edit: I tried a rebuild and clean in VS but still failed to compile. So I deleted everything in the engine folder and downloaded 4.24.2 source as a zip, extracted it into the folder and was able to compile. I usually just pull the new version with git. So there must of been something left behind in the folders from previous builds affecting the compile.