Sequencer: GUI rendering performance (6fps single track)

Development Rendering
, , , , ,
1

The sequencer GUI rendering performance is bad even in the small scenarios (Like one transform track recorded for 1 minute).

It is relative easy to optimize to run consistently at 60fps on even low end computers. (I did this in my own custom engine build of 4.13)

But the way the sequencer is currently iterating over the data every frame is making working with it difficult. Sadly upgrading my solution to the latest engine version is not trivial - which is why I have not created a pull request yet. It would be great to see someone taking a crack at that.

My initial modifications when I first discovered some of the bottlenecks can be found here:
Sequencer rendering of little white bars is insanely slow
However this was more of a quick hack than an actual solution to the problem (The actual drawing of the keys for example is also really bad… etc.)

To see the issue:

Record a cube for 1 minute that is constantly moved around by being dragged for example.
Open the sequence in sequencer and expand everything. Activate the viewport FPS so you can see the performance.

Some images that show how bad the performance is with varying levels expansions and clicking objects etc. can be found here:

CLICK ME (IMGUR)

This was done on the latest Razer blade.

Cheers

2

Also: Right now things are made in such away that even having no keyframes at all visible in the GUI still has the same bad performance as displaying all of them.

3

Hi ,

Thanks for reporting this. I’ve entered UE-42018. You can track the report’s status as the issue is reviewed by our development staff. Please be aware that this issue may not be prioritized or fixed soon.

4

Hi !

Thank you for creating an issue for that.
But I would like to know that the ticket does not full justice to the issue (in my opinion).
As you can see in the second to last image in my Imgur Link the performance already drops significantly when just expanding the track without selecting it (although to a lesser degree - this gets worse however when adding additional tracks)

Thank you

5

Hi ,

The underlying problem is the performance drop and that is what we are concerned with. The engineers will find the cause, even if it isn’t the yellow preview track that is the problem. Thanks for your fastidious attention to detail on the bug report itself, but it will sufficiently cover the underlying problem.