Unreal Engine 4.25 released!

[SupraGineles]

**UE-40033 **

"Blueprint compile fails after changing the default values of a struct that is part of another struct that makes up a Data Table that is used within the Blueprint."

Still not fixed , but is marked as fixed.

[anonymous_user_82239254]

@barneyw-ud

I have been experiencing this crash too. I think I have narrowed it down to the late update being done for the HMD and controllers, in our scenario at least.

The late update is setting the transform, causing them to be flagged as needing a reflection capture update but something about doing the level load means it is not being updated before ComputeRelevance is called.

It only affects things nested under the motion controller component or the camera that is tracking to the HMD. As a workaround I enabled DisableLowLatencyUpdate in the motion controllers (to stop the late update of the transform) and removed the anything we had nested under the camera (disabling it for the HMD would be more involved).

So far this seems to have worked. Obviously not an ideal long term solution.

I, too, experienced this crash and this fix worked for me. Thanks for this! Just wanted to put more out there that this

ComputeRelevance()

ensure is a bug b/t Oculus and Unreal on Quest with 4.25.1 (for me).

[AstroMoonLander]

With the release of Unreal Engine 4.25, we continue our mission to provide the most complete, flexible, powerful, and proven real-time 3D creation tool. We have further expanded the toolset to include content creation and editing for more areas of game and visualization development, while improving the feature set and refining workflows for existing tools. Our linear media tools are improved to enable even more immersive and efficient production of linear and cinematic content. Support for existing platforms has been further improved and first-class support has been added for the next generation of gaming consoles.

The more removed designers and creators are from the end product, the more difficult it is to realize their visions.With new and improved systems and tools, Unreal Engine 4.25 enables creators from more disciplines than ever to create, modify, and iterate directly in context in the editor on the final content. Niagara visual effects and Chaos physics have been improved and expanded to provide high-quality, high-performance dynamic simulations. Control Rig and Sequencer now work together to enable in-editor animation of rigged characters. Modeling and sculpting tools have been added to facilitate in-viewport building and updating environments.

Unreal Engine continues to be used in new and exciting ways to produce cinematic and linear content mixed with digital elements. The new Movie Render Manager produces higher-quality rendered output with a streamlined workflow for integrating it into any pipeline. The nDisplay multiple display technology is easier to configure and more powerful than ever making LED walls and large venue displays available to virtually any production. There are also improvements to several areas such as in-camera visual effects, tools for broadcast and live events, motion graphics via 3D Text Animation and the addition of support for generating charts and graphs directly inside of Unreal Editor.

We spend a considerable portion of each release focusing on improvements to support all platforms so your projects can be experienced by everyone regardless of their chosen form factor. In this release, we have added support for the next generation of gaming consoles, which include Microsoft Xbox Series X and Sony PlayStation 5. In addition, iOS and Android have both seen significant enhancements to rendering and development workflows. Augmented reality devices, such as HoloLens 2 and Magic Leap, have new functionality as well as improvements to development workflows.

**See the full release notes here **and drop your feedback below!

KNOWN ISSUES
For a complete listing of known issues affecting Unreal Engine 4.25, please see the Unreal Engine Public Issue Tracker.

Discover new issues with this release, please report them using the guidelines in the link: How to Report a Bug.

it seems that AA reflection flickering that has something with SSR, still doesn’t fixed

The Unreal Engine Issues and Bug Tracker

I switched one large project having to switch many plugins over period and then finally, when I resolved all build bugs, and plugin issues and some other UE glitches (like Motion Blur in 4.25 doesn’t work well if FPS is set to 30 - as is by default, but that needs to be zero)

I had that UE-93360 and I can’t update our published game to the latest version as of it, after like months of switching work and debug
Not to say that I had like 20 things that I improved in engine and never mean it will be impossible to finish build

Please Unreal Team, let’s fix this UE-93360 issue, guess many developers who use reflections having same problem.
It never happened that’s impossible to switch to the newer version and now it seems it is.
Please make 4.25.5 hotfix asap

[Boruki]

@LNaej

Quoting myself, but if someone has this bug too (or a UE4 dev knows the answer), maybe this commit on 4.25 branch will fix it?
" Fixed crash caused by the dummy reflection capture uniform buffer being destroyed immediately after it was created."
https://github.com/EpicGames/UnrealE…4ffb93e2f8884a

Currently doing a full engine build in order to try and see (so with my computer it will take a few hours)… Will update this post after the test.

Update: now it fails on “IsValidLowLevelFast()” in LoadMap(). I did not manage to breakpoint using AndroidStudio so I will need to continue to dig in.
Update2: it seems that one of my AI Pawn blueprints placed in map got somehow corrupted with the update. It would fail in **FAsyncPackage::PostLoadObjects() **with if (!Object->IsReadyForAsyncPostLoad()) in the while loop pointing to an invalid memory address (even if IsValid() returns true for the pointer). Removing the instanced blueprint from the map and putting it in the map again seemed to solve the issue.

Hi LNaej,

I seem to have it as an issue now - using a render target for a scope, when it’s made active I get this crash. It was actually working when launched to the Android device (Quest2) originally… and then stopped working! I can’t for the life of me figure it out. I’ve tried various mixtures of Multi-View/HDR/etc all being on and off… but it was working with HDR and Instanced Stereo before.

I’m not sure I follow quite how you got to figure out what was causing the problem. Any input you could give would be great! (I would’ve asked in a new thread, but they don’t seem to get answered much!)

EDIT: It appears that having a widget attached to my camera is causing the problem. I have a widget attached to the characters hand - doesn’t cause any issues. Copied that exact component on to the camera and it causes a crash. So it’s nothing within the widget itself - something to do with the component being attached.