In the matinee editor on the director track, camera cuts cannot be added.
It works in 4.10, but not 4.11. Same project.
When I add a keyframe on the director track and the little box pops up with the dropdown of the cameras, it’s temperamental selecting, and if I do manage to select it, nothing happens when I hit enter! One of the items in the dropdown is DirGroup ! I don’t think that’s supposed to be there is it?
UPDATE:
I’ve discovered this only happens when the matinee editor is on my second monitor…
DirGroup is always on that list, that’s normal. The problem sounds familiar to me though. I guess it is moving the key to the first frame right now. Try changing your snapping value in Matinee and then create the key again.
I haven’t been able to reproduce this behavior in 4.11. Any chance you could screen capture a video of what’s happening or send along an example project?
If you’d rather send those privately, you can PM me a download link on the forums.
I have a clue, it only happens in 4.11 and when the matinee editor is on my SECOND MONITOR.
On my primary monitor, the editor works normally.
Furthermore, if I put the main unreal editor window on my second monitor, the toolbar cinematic button does not function properly either.
It’s like the window loses focus.
Any suggestions?
Thanks for sending the info. From just the screenshot, I can tell that you’re on drivers from July 2015. Please go to Nvidia’s website and update those as a first step. I understand that this worked in 4.10, but things change with each editor update, which is why your drivers need to be up to date as well. If it’s still occurring after that, we can proceed.
For future reference, when requesting a dxdiag, it is generally expected that we receive the txt document created when you hit Save All Information at the bottom of the dxdiag window. I’d still like to receive that as there is additional info that I can use to identify your hardware and determine if this truly is a hardware compatibility issue with 4.11.
Second, can you try setting your external monitor as the primary monitor, then re-attempt this test on both displays?
Hi sorry for late reply, attached the dxdiag. link text
I’ve updated to the very latest Nvidia drivers, same problem.
Also updated the Intel Graphics drivers, but they do don’t support windows 10.
I think that may be the problem, because my second monitor is the intel output.
Not looking forward to spending the time to do it but I ought to roll back to Windows 7, I have strange network issues and also can’t get my DK2 to run since windows 10 either. All was well before.
And I’ve noticed that Windows 10 isn’t supported:
That seems really strange, I have no idea why your laptop outputs the external monitor from the Integrated Graphics. Windows 10 is supported, but has presented compatibility issues when users with laptops upgrade without the laptop manufacturer or Intel creating Win10 Drivers.
Hi! So I got it working. I rolled back to Windows 7, problem gone. Definatly to do with intel integrated graphics driver and windows 10 not supported by the driver as it turns out, like you just said here.
To clarify - it’s a 5 year old laptop, I don’t use the built in screen I have two monitors each attached to the two monitor sockets, one is the nvidia 525M and the second is the intel - that’s why i only had the issue on the second monitor.
Ah, yeah that makes sense. If it’s not a recent laptop, many manufacturers will not release specific drivers for that hardware. We’ve found this happens a lot when people go get the generic drivers from Intel/Nvidia/AMD, but find that it doesn’t handle the GPU switching very well.
I’m glad it’s working for you in Win7, but it’s unfortunate that laptop manufacturers aren’t updating their drivers very well.
