# Whats up with Matinee?

**URL:** <https://forums.unrealengine.com/t/whats-up-with-matinee/288527>\
**Category:** Programming & Scripting\
**Tags:** unreal-engine\
**Created:** [July 18, 2014, 12:43am UTC](https://forums.unrealengine.com/t/whats-up-with-matinee/288527 "2014-07-18T00:43:33Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![r4ptur3](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@r4ptur3](https://forums.unrealengine.com/u/r4ptur3)\
**Post date:** [July 18, 2014, 12:43am UTC](https://forums.unrealengine.com/t/whats-up-with-matinee/288527/1 "2014-07-18T00:43:33Z")

</div>

Hi guys!

One of the awesome features in UDK is the Matinee editor – It is super easy to use and very intuitive. I have found that the Matinee editor in UE4 is pretty unstable. I’d like to start this post in order to get the ball rolling on some odd problems.

- Duplicating a matinee actor in the viewport with alt+drag will corrupt the current level. The editor will remain functional until it is rebooted.

- Moving a matinee from one level to another will corrupt the current level. The editor will remain functional until it is rebooted.

- There is no way to move the contents of a matinee in local space (relative to the matinee icon). All keyframes seem to be made in world space.

- Adjusting the length of the matinee (red tick mark at the bottom of the matinee screen) while using the snap button (magnet at the top of the screen) will cause the matinee to snap to 0.00. There is no way to accurately snap the length of the matinee to any given time.

- Matinees are not able to be placed in class blueprints. They only seem to be placed in the Level Blueprint.

If you need screen caps or other information on these bugs just let me know 😃

---

<div class="post-metadata">

**Author:** ![Jacky](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/jacky/32/918690_2.png) [@Jacky](https://forums.unrealengine.com/u/Jacky)\
**Post date:** [July 18, 2014, 12:53am UTC](https://forums.unrealengine.com/t/whats-up-with-matinee/288527/2 "2014-07-18T00:53:05Z")

</div>

Regarding the first two corruption issues: Referencing the same object in more than one matinee’s can cause problems, so that might be the issue you are seeing with duplicating it in the same level. And are you fixing the referenced objects in the matinee actor after you place Matinee into the other level?

Also Matinee working with Level BP only isn’t a bug. It’s just a limitation of Matinee. You’ll have to wait for Sequencer for more flexibility.

---

<div class="post-metadata">

**Author:** ![r4ptur3](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@r4ptur3](https://forums.unrealengine.com/u/r4ptur3)\
**Post date:** [July 18, 2014, 1:01am UTC](https://forums.unrealengine.com/t/whats-up-with-matinee/288527/3 "2014-07-18T01:01:42Z")

</div>

Thanks for the quick response !

I was fixing the duplicated matinees as I went – I was hoping to apply the same general movement track to multiple objects, so my workflow was to make a matinee, duplicate it, then hook a new actor up to the duplicated matinee.

Is there any info on the sequencer? What is this awesomeness you speak of?

---

<div class="post-metadata">

**Author:** ![Jacky](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/jacky/32/918690_2.png) [@Jacky](https://forums.unrealengine.com/u/Jacky)\
**Post date:** [July 18, 2014, 1:10am UTC](https://forums.unrealengine.com/t/whats-up-with-matinee/288527/4 "2014-07-18T01:10:18Z")

</div>

It is still some months away from release so not much is known about it really. It will be used in class blueprints as well and have more functionality though. You can see a screenshot of its interface here:

> **[\[Feature Request\] Sequencer (Matinee substitute)](https://forums.unrealengine.com/showthread.php?15144-Feature-Request-Sequencer-%28Matinee-substitute%29)**
>
> Hello Epic folks 🙂 I came to UE4 from 2d/3d motion graphics and video production field. It’s being great so far, we upgraded our workflow pipeline and removed ‘‘rendering’’ steps from it 🙂 As I work with timelines and keyframes all day long, I...

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_759e5c3a](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_759e5c3a](https://forums.unrealengine.com/u/anonymous_user_759e5c3a)\
**Post date:** [July 18, 2014, 6:33pm UTC](https://forums.unrealengine.com/t/whats-up-with-matinee/288527/5 "2014-07-18T18:33:11Z")

</div>

Hi R4ptur3,

I have assigned a technician to look into the first two issues you have mentioned. I do have some information about the other problems that you have pointed out:

> There is no way to move the contents  
> of a matinee in local space (relative  
> to the matinee icon). All keyframes  
> seem to be made in world space.

This is correct, it is a limitation of how matinee works with UE4 currently.

> Adjusting the length of the matinee  
> (red tick mark at the bottom of the  
> matinee screen) while using the snap  
> button (magnet at the top of the  
> screen) will cause the matinee to snap  
> to 0.00. There is no way to accurately  
> snap the length of the matinee to any  
> given time.

This is a known issue. I have personally bugged this issue and assigned it to a developer before. It has unfortunately not been fixed yet.

> Matinees are not able to be placed in  
> class blueprints. They only seem to be  
> placed in the Level Blueprint.

This is a limitation as said. I apologize for any inconvenience that has caused you.

We are currently working very hard on getting Sequencer ready for release. It will solve many of the issues that you describe here.

Cheers,

---

<div class="post-metadata">

**Author:** ![AlwysAnrchy](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@AlwysAnrchy](https://forums.unrealengine.com/u/AlwysAnrchy)\
**Post date:** [July 18, 2014, 7:10pm UTC](https://forums.unrealengine.com/t/whats-up-with-matinee/288527/6 "2014-07-18T19:10:22Z")

</div>

Howdy r4ptur3,

I just had a couple other question for the first 2 issues that you are having with Matinee. What version of the Editor are you currently running off of? Also, Can you provide any repro steps that I could follow on how set up the first 2 issues?

I have attempted the first issue and have been unsuccessful. I created a matinee and duplicated the matinee by Alt+Dragging. I then saved the level and reopened it an was able to work in the level just fine. If I am missing any steps, please let me know.

Thanks and have a great day!

---

<div class="post-metadata">

**Author:** ![r4ptur3](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@r4ptur3](https://forums.unrealengine.com/u/r4ptur3)\
**Post date:** [July 18, 2014, 9:28pm UTC](https://forums.unrealengine.com/t/whats-up-with-matinee/288527/7 "2014-07-18T21:28:09Z")

</div>

Wow thanks for the replies!

Here’s some repro steps (v4.2.0):

1. crate a new 1st person blueprint project (did not include starter content)
2. crate a new matinee
3. place a TemplateCube\_Rounded in the world
4. add a new empty group in matinee with the cube selected. this will change the cube to moveable
5. add a new movement track to the empty group
6. add a few keys to the movement track so the box moves around the scene
7. close matinee and save the level (ctrl+s)
8. click the matinee actor, hold alt+drag to duplicate
9. drag a new TemplateCube\_Rounded into the world
10. open the duplicated matinee
11. right click on the empty group and navigate to actors → TemplateCube\_Rounded → replace actor
12. close matinee and save the level (ctrl+s)
13. close unreal
14. open unreal 4.2.0 and open the project
15. a black crash report should appear. after digging through the log, it looks like the duplicated matinee is the culprit.

I reproduced these steps in v4.3.0 and it looks like the level is no longer corrupted. Instead, the second matinee ceases to function. I can see the second cube moving when I scrub through the matinee, but it will not move when I tell the matinee to play when the level loads (event begin play → play → matineeActor / matineeActor\_2).

Looks like I am running out of reply space, so I’ll write up new repro steps for the other issue in a second post.

---

<div class="post-metadata">

**Author:** ![r4ptur3](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@r4ptur3](https://forums.unrealengine.com/u/r4ptur3)\
**Post date:** [July 18, 2014, 10:04pm UTC](https://forums.unrealengine.com/t/whats-up-with-matinee/288527/8 "2014-07-18T22:04:05Z")

</div>

repro steps for the second issue (v4.2.0):

1. create a new blank project (did not include the starter content)
2. open the levels window
3. right click → add level → create empty level
4. save a new map (mine is called levelTwo)
5. double click on Persistant Level to make it current
6. save the Persistant Level (ctrl+s)(mine is called levelOne)
7. add a new blank matinee to the persistant level and save (ctrl+s)
8. select the matinee
9. right click on levelTwo in the Levels window
10. select move selected actors to level
11. ctrl+s to save all
12. exit unreal
13. launch unreal v4.2.0 and open the project
14. open levelOne.umap
15. a black error report box should appear.

I have not had much time to test this issue, but it seems to be fixed in v4.3.0.

Again, thank you for all the help! UE4 is such a great engine and it is so refreshing to see it being pushed even further.

---

<div class="post-metadata">

**Author:** ![AlwysAnrchy](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@AlwysAnrchy](https://forums.unrealengine.com/u/AlwysAnrchy)\
**Post date:** [July 21, 2014, 3:54pm UTC](https://forums.unrealengine.com/t/whats-up-with-matinee/288527/9 "2014-07-21T15:54:30Z")

</div>

Hey r4ptru3,

Thanks for the reproduction steps for this issue. When setting this up in 4.2, I saw and instant crash when loading the level after replicating the Matinee. I tested this in 4.3 and may have found a way to fix your issue. When you open the duplicated the matinee and add a new TemplateCube to the level, be sure to have the Cube as movable and not static. Also, when changing the actor in the level, have the actor selected in the view-port and select ‘Replace Group Actors with Selected Actors’. Also be sure that the matinee details has ‘Play on Level Load’ checked

Give this a shot and let me know if this helps. Have a great day!

---

<div class="post-metadata">

**Author:** ![r4ptur3](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@r4ptur3](https://forums.unrealengine.com/u/r4ptur3)\
**Post date:** [July 21, 2014, 5:03pm UTC](https://forums.unrealengine.com/t/whats-up-with-matinee/288527/10 "2014-07-21T17:03:11Z")

</div>

Hi !

Is there a way to specify a mesh’s movable mode? UE4 alerts me that the mesh has been changed to movable when I add it to the matinee, but I could not find that option int he mesh’s properties or a “replace with” function.

---

<div class="post-metadata">

**Author:** ![Jacky](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/jacky/32/918690_2.png) [@Jacky](https://forums.unrealengine.com/u/Jacky)\
**Post date:** [July 21, 2014, 5:12pm UTC](https://forums.unrealengine.com/t/whats-up-with-matinee/288527/11 "2014-07-21T17:12:29Z")

</div>

Check the Details panel on the right when you select a mesh and you’ll see Static and Movable buttons under Transform tab.

---

<div class="post-metadata">

**Author:** ![r4ptur3](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@r4ptur3](https://forums.unrealengine.com/u/r4ptur3)\
**Post date:** [July 22, 2014, 1:00am UTC](https://forums.unrealengine.com/t/whats-up-with-matinee/288527/12 "2014-07-22T01:00:35Z")

</div>

that seemed to do the trick! I wonder what the culprit was – the movable thing, or replace group actors? I’ll see if I can debug a little tonight.
