# DateTime + Timespan no longer working in UE5 😠 (works in UE4)

**URL:** <https://forums.unrealengine.com/t/datetime-timespan-no-longer-working-in-ue5-works-in-ue4/1242752>\
**Category:** Blueprint\
**Tags:** unreal-engine\
**Created:** [July 28, 2023, 12:07pm UTC](https://forums.unrealengine.com/t/datetime-timespan-no-longer-working-in-ue5-works-in-ue4/1242752 "2023-07-28T12:07:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![MisterPixel](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/misterpixel/32/629747_2.png) [@MisterPixel](https://forums.unrealengine.com/u/MisterPixel)\
**Post date:** [July 28, 2023, 12:07pm UTC](https://forums.unrealengine.com/t/datetime-timespan-no-longer-working-in-ue5-works-in-ue4/1242752/1 "2023-07-28T12:07:26Z")

</div>

Hi, there!

As always, if anyone wants to check the video version of my explanation, feel free to do so, otherwise continue reading on after the YouTube thumbnail:

[![](https://d3kjluh73b9h9o.cloudfront.net/original/4X/c/c/a/ccaf645e076ab8aaf3c7dc46399003ea5e22c2a3.jpeg "DateTime + Timespan no longer working in UE5 😠 (works in UE4)") ](https://www.youtube.com/watch?v=I3IVU2rPdxw)

So, the UE4 documentation shows to have vast support for nodes that allow for DateTime and Timespan operations, such as the very obvious example of shifting a DateTime to a later one by adding a Timespan chunk on top of it. Here’s one such doc page for the [Add operator](https://docs.unrealengine.com/4.27/en-US/BlueprintAPI/Math/DateTime/DateTime_Timespan/), but many more can be found [one level up](https://docs.unrealengine.com/4.27/en-US/BlueprintAPI/Math/DateTime/). Now try doing the same under the UE5 documentation and you’ll get a nice [Error 404 - Page Not Found](https://docs.unrealengine.com/5.2/en-US/BlueprintAPI/Math/DateTime/DateTime_Timespan/), as upon [closer inspection](https://docs.unrealengine.com/5.2/en-US/BlueprintAPI/Math/DateTime/) we can see that all those operator nodes are now gone.

So, I thought to myself: surely the nodes are missing from the UE5 docs because now we have those generic wildcard operators like the **“Add”** , **“Subtract”** , **“Multiply”** , **“Divide”** etc., which can now be customized to have different types as their Inputs and Outputs. And indeed, you _ **can** _ drag such a node in your Blueprint and customize it accordingly, BUT here’s where it all goes south: you can _ **no longer** _ connect the nodes 😑 If you connect the **DateTime** Input and **DateTime** Output first, you’ll think to yourself “ah, just on more node and I’m done”, but as soon as you try connecting the other **Timespan** Input, the previously-connected **DateTime** nodes will be automatically disconnected, as the **“Add”** operator node decides to convert itself from a **“DateTime + Timespan = DateTime”** node to a **“Timespan + Timespan = Timespan”** node and there’s no way around it apparently ☹

I tried multiple workarounds such as splitting the structs, working with variables, making/breaking **DateTimes** and/or **Timespans** , but to no avail 😮‍💨 Therefore, please let me know if you have any idea how to do this properly, as it seems extremely stupid to no longer be able to add a **Timespan** on top of a **DateTime**. It’s one of the core reasons for why **Timespan** exist, otherwise they’re not that useful by themselves if they can not operate in conjunction with **DateTime** …

Thanks a bunch!!!

---

<div class="post-metadata">

**Author:** ![Everynone](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/everynone/32/1135017_2.png) [@Everynone](https://forums.unrealengine.com/u/Everynone)\
**Post date:** [July 28, 2023, 12:30pm UTC](https://forums.unrealengine.com/t/datetime-timespan-no-longer-working-in-ue5-works-in-ue4/1242752/2 "2023-07-28T12:30:27Z")

</div>

There’s a small bunch of timespan / datetime bugs in UE5, here’s one:

> **[The Unreal Engine Issues and Bug Tracker](https://issues.unrealengine.com/issue/UE-135466)**
>
> Welcome to the Unreal Engine Issue and Bug Tracker. You can check the status of an issue and search for existing bugs. See latest bug fixes too.

The ones i’ve seen have a target fix for 5.3. And yes, it’s a regression indeed.

* * *

These are apparently fixed in 5.3:

> **[The Unreal Engine Issues and Bug Tracker](https://issues.unrealengine.com/issue/search?q=fix%3A5.3%2C5.3.0&resolution=unresolved&component=&sort=votes)**
>
> Welcome to the Unreal Engine Issue and Bug Tracker. You can check the status of an issue and search for existing bugs. See latest bug fixes too.

See if you can find the relevant stuff. Have a look here for more details:

> [@Unreal Engine 5.3 Preview](https://forums.unrealengine.com/t/unreal-engine-5-3-preview/1240016):
>
> Download Unreal Engine 5.3 Preview from the Epic Games launcher, [GitHub](https://github.com/EpicGames), or for [Linux](https://www.unrealengine.com/linux)! Unreal Engine 5.3 continues to refine the workflows and capabilities of its core features, such as Lumen, Nanite, Path Tracing, and beyond. With this release, these rendering features provide more control over performance and yield better-looking results. Users will see reductions in build times with Multi-process Cook, improving the ability to iterate more quickly on projects. There are also a n…

---

<div class="post-metadata">

**Author:** ![MisterPixel](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/misterpixel/32/629747_2.png) [@MisterPixel](https://forums.unrealengine.com/u/MisterPixel)\
**Post date:** [July 28, 2023, 4:39pm UTC](https://forums.unrealengine.com/t/datetime-timespan-no-longer-working-in-ue5-works-in-ue4/1242752/3 "2023-07-28T16:39:15Z")

</div>

@Everynone Yep, it’s a bug and I’ve submitted an issue for all of the nodes, as there are exactly 20x UE4 nodes missing from UE5 at the moment with respect to DateTime and Timespan operations. Here’s a screenshot of all of them:

 ![DateTime_Timespan_UE4_Nodes](https://d3kjluh73b9h9o.cloudfront.net/original/4X/9/7/7/977831bbd7d28c1d60cfb8a376adcdb715d8d676.png)

Therefore, in case anyone else has this issue, I’ve compiled all of those nodes, with nice comments, as a .txt file, so you can use it in UE5 directly:

[DateTime\_Timespan\_UE4\_Nodes.txt](https://forums.unrealengine.com/uploads/short-url/qa7yeapFisxT5PhmC448Ek5R7lW.txt) (60.9 KB)

Just open it, **copy** the contents and then **paste** it into your UE5 BP graph and you’ll have all of them there. Feel free to keep this handy as an easy container from where you can get them later, just in case you need to 😉 OR, you can use this online [BlueprintUE.com](http://BlueprintUE.com) version I made, just in case you find it more accessible:

> **[DateTime & Timespan UE4 Nodes missing from UE5 posted by Mister Pixel |...](https://blueprintue.com/blueprint/thl5_ey3/)**
>
> No description provided

But I won’t mark this thread as resolved just yet, as this is only my patch… I’m still waiting for EpicGames to solve this issue properly by bringing these nodes back (in the docs also) with proper functionality.

---

<div class="post-metadata">

**Author:** ![MisterPixel](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/misterpixel/32/629747_2.png) [@MisterPixel](https://forums.unrealengine.com/u/MisterPixel)\
**Post date:** [July 31, 2023, 5:56pm UTC](https://forums.unrealengine.com/t/datetime-timespan-no-longer-working-in-ue5-works-in-ue4/1242752/4 "2023-07-31T17:56:49Z")

</div>

Here’s the reply I got back for my issue submission on this topic:

> The issue in UE-175959 has been fixed internally and is expected to be available in the 5.3 release.
> 
> If you are a source code developer using Github, you can already access and integrate the fix here: [25373061](https://github.com/EpicGames/UnrealEngine/commit/ddde1e9c359ba4e805c10c65fde2a622895bccbe) .

So, it appears there’s yet another bug submission already present under the ID of [UE-175959](https://issues.unrealengine.com/issue/UE-175959), which indeed appears to be marked as fixed in the upcoming v5.3! 🥰 Therefore I’m eagerly awaiting to see it resolved in the stable release, then if all goes well, I’ll close the topic 😉

---

<div class="post-metadata">

**Author:** ![MisterPixel](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/misterpixel/32/629747_2.png) [@MisterPixel](https://forums.unrealengine.com/u/MisterPixel)\
**Post date:** [September 14, 2023, 1:49pm UTC](https://forums.unrealengine.com/t/datetime-timespan-no-longer-working-in-ue5-works-in-ue4/1242752/5 "2023-09-14T13:49:22Z")

</div>

So, UE5.3 is here and guess what… it’s not fixed 🙂 The same problem occurs, just as before. What’s worse is that they even flagged [UE-175959](https://issues.unrealengine.com/issue/UE-175959) as being fixed, when is completely opposite from the observable reality ☹