if a RealTime Clock triggers in a forest and nobody sees it, does it really happen?

General Issues and Bug Reporting
, , , , ,
1

Summary

Realtime Clocks only seem to work if you’re staring at them?

I wanted to make an event that started at say, noon GMT “tomorrow” and then repeated every six hours for 99 repetitions.

it doesn’t seem to work. If you’re present for the first one, it does, but if you log in after the initial timer, the clock just reads 0:0:0:00 instead of 0:5:59:59

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Devices

Steps to Reproduce

make a map with a realtime clock in it. set it to some future date/time and have it repeat every, who knows, ten minutes.
wire up an audio device to trigger some sound when the clock hits 0.
make a private version.
play it.
log out, wait 15 minutes, play again

Expected Result

if you log in as the first time hits, you’ll hear the sound play.
if you log out and log back in again, you’d expect the clock to say there’s 5 minutes left. (because you’ve used up half the 10 minutes) and then it would play the song again

Observed Result

clock just reads all 0 and doesn’t repeat when you told it to.

Platform(s)

xbox

Island Code

4970-2691-2291

Additional Notes

lots of islands are doing cool stuff with live events. The documentation makes it sound like the devices should “just work” without verse. They don’t seem to?
Am I doing it wrong?

2

clocks
clocks1920×1080 3.17 MB

here’s a pic of where they are and how I was using them. the one closest to the player should have a replay timer on it, but it stays at 0.

3

I’ve tried multiple reconfigurations of this, and they still seem to just die after the first time they trigger.

5

Thanks! Hopefully if there’s a “working as intended” and there’s some setting I’m using wrong, you can let me know. :slightly_smiling_face:

9

FORT-1033631 has been ‘Closed’. This is working as intended by design.

10

I don’t understand.
”play at this date and time, then repeat event every 4 hours afterward for the next 30 days” is what the settings imply.

The current (unless things have changed) implementation seems to be “play at this date and time, and repeat every 4 hours afterward for the next 30 days as long as you were here when initially triggered, and haven’t left the server, in which case, you’ll never know it happened in the first place”.

Are there any examples of maps that are using this device as a standalone feature, or does it require verse to work properly?

11

image
image951×612 38.5 KB

What is Duration?

  1. The amount of time that this triggered experience lasts, each time it is triggered (because Instant is an option in the pulldown)
  2. The amount of time allotted for the entirety of the experience’s initial and recurring lifetime. All Weekend, for example.

In the case of 1, it is assumed that I could ENABLE a spawner/vfx/etc and that it would remain on until the duration ends. This interpretation seems to be supported by the “On Duration Elapsed Send Event To” event. Which one can assume would then DISABLE the previously enabled objects.

One could see the value of the Second, as it involves less math when determining how many times to repeat the clock’s activation over, let’s continue using The Weekend. You could say “repeat 99 times” but if there’s only room for 11 repeats during the duration, it would only ever happen 11 times.

I’m going to go over to Developer Assistant and give it a hypothetical to resolve and see what it says.

12

This bug has been there for ages, I had made this document some time ago REAL TIME CLOCK DEVICE - Google Docs outlining the issues I had, keep in mind this was made in 2022 so some stuff could be fixed or changed since then.

I would recommend avoiding the real time clock devices repeat functions and if you are on UEFN I would advise using verse since it can get the current time as a float using the GetSecondsSinceEpoch() function.