Matinee and spawn point bug location

4.9 and 4.10 bug

If you place only one spawn point in the map and a matinee video far away in vertical for example the player spawn in a differnet site and if uncheck the don’t spawn without collisions or find another way spawn wrong too.

In this case i get the problem in my mega jam game if use a spawn don’t spawn in the selected location and if you use a pawn with auto posses work.

Project to test the bug, open the map of the FPS and play https://dl.dropboxusercontent.com/u/28070491/UE/Forums/Preview10_Test.zip

Hey Hevedy,

To clarify the issue you are experiencing is that when you play your game it automatically calls the camera associated with the Matinee Actor?

Are you trying to have both the camera and the player start happen when you play the level but start where the player is suppose to?

After end the matinee the player should spawn in normal way in the spawn find the spawn in the map placed, but spawn in a different site.

*I need check this better because in my project i got a problem but here no, is a problem with the killz location but in my map is not that problem i need check this better

Set your Kill Z, in world settings, back to it’s default. This fixes it. It seems that the Kill was too small of an area and you are killing your player.

Yeah as I’m said that fix that but that is not my original problem i need find the original one from the Jam.

Ok, in the future please provide a test with the actual issue. It is extremely difficult to allocate time and a fix for an issue which is not the one you are reporting.

If you can provide a test with your issue or a link to Dropbox with your Jam that is having the issue I will investigate this further.

I got to report with the updated file when i get the problem.

I doing this for free after report 100 bugs so yeah i miss one.

Is something about the spawn rotation and the matinee video but atm I cannot reproduce the bug in a new project.

Hevedy,

For tracking purposes I will be marking this thread as resolved while you attempt to recreate this issue. As soon as you are able to reproduce this you can post on this thread again. I will then continue to investigate what is causing the bug in the meantime.