I recently integrated Day Sequence into my project, and everything works perfectly in the editor. However, once the game is packaged, nothing works anymore. For example, after packaging, I’m at sunrise at 6 AM, but the day doesn’t progress. Yet, in the editor, the automatic day/night cycle works just fine.
I tried adding the plugin folders to the packaging settings, as well as some sequencers, but nothing changed. I also noticed that many people on the forums are experiencing the same issue, but no clear solution has been provided:
I am having tha same problem!
I created some key points in the main sequence and after packaging and play, they are executed and changed normally. Only the “circle” of the sun and light do not move, the rest moves and progresses normally.
Hey everyone, thanks for the report. This is an issue specifically relating to Procedural Day Sequences that are used by the SunMoonDaySequenceActor in its referenced DSCA_24Hr collection asset. We’re investigating the issue.
Until we have a fix, the recommended workaround is to remove the Procedural Day Sequence from your DaySequenceCollection asset and replace it with your own standalone Day Sequence. If you’re keen on using the same curves from one of the Procedural Day Sequence you can copy the curves from the procedural sequence in editor into your own sequence by opening the Root Sequence from the viewport Time of Day menu.
Hello,
When i copy the Keyframes from the procedural Day sequence and paste them in another sequence, it only pastes the Keyframes at 0000 and ignores all the others. Is there anything i could be doing wrong?
When i copy the Keyframes from the procedural Day sequence and paste them in another sequence, it only pastes the Keyframes at 0000 and ignores all the others. Is there anything i could be doing wrong?
It’s likely the difference in the playback ranges between the procedural day sequence and your local day sequence. The procedural day sequence for the SunMoonDaySequenceActor is 9000 frames, whereas the default playback range for a new sequence is 150, so it’s likely that it did paste all the keys, but you might need to zoom out to see it all and then either rescale the keys or adjust your playback range to match.
Can you say if the next version is going to have the option to pause/start the sequence (“Run Day Cycle” checkbox) via blueprint? Currently I don’t think there’s a way to do that on the SunMoonSequenceActor.
Also should we expect those fixes in a hotfix or is this 5.6 territory?
There are Blueprint exposed functions on the DaySequence actor that do just that already, inherited from the ADaySequenceActor class: Play() and Pause().
bRunDayCycle only defines how the actor behaves on BeginPlay, it will be BlueprintReadWrite in an upcoming release like the packaging bugfix. This is being exposed primarily because we added the requirement that Play() will only begin playback if bRunDayCycle is true, to serve as an gating mechanism for playback if you have multiple systems that want to trigger playback.
Sorry, I’m not at the liberty to disclose more details on that front.
Why plugin does not work in packaged project?
