4.14.1 Lookup (y-axis) is frozen PIE after selecting Mode tab

Development Programming & Scripting
1

In 4.14.1, when launching a Play In Editor (PIE) session of any project (my current main project, or creating a new C++ first person template), if you have changed Mode using the ‘Modes’ menu - for example if you change to the Landscape tag, then back to Place, the Lookup or Y viewing axis receives no input, so you can’t look up/down.

Steps to reproduce -
Create a C++ First Person Template based project.
Launch PIE with no issues.
Tweak objects in the scene, without having changed to a different Mode tag, launch PIE still with no issues.
Select the Landscape or Vegetation Mode Tag, then reselect the Place Mode Tag, launch PIE - player can no longer look up/down with a mouse or controller.

I have to close and reopen the editor to restore Lookup camera movement PIE.

This has no impact when launching a standalone game.

2

I know this was happening in 4.14, but as I didn’t update my project from 4.13, I didn’t take any time to test for a repo pattern. Doesn’t happen in earlier versions, I’m currently still using 4.13.2 for my main project without seeing this issue.
I’m not developing BP only apps, so haven’t tried that (yet).

3

This DOES happen in a BP only First Person based template, which is interesting.

4

This DOES happen in a blank (BP) project, using the Default Pawn.

5

Hello Gavin1969,

I’ll start looking into getting a reproduction of this. In the meantime, is this new to 4.14.1? What versions did you try previously? I’m assuming from your post that this does not occur in Blueprint Only projects? Does it have to be a template or does it also happen with a blank project using Default Pawn?

6

I’m not seeing the same results when trying to reproduce this. I’ll list exactly what I’m doing so you can point out any possible discrepancies

  1. Create a new project in 4.14.1 based off the Blueprint First Person Template
  2. Press Play to start PIE, click in the viewport to gain control, and turn the camera in all directions without issues
  3. End PIE
  4. Select the Landscape tab in the Modes panel
  5. Select the Place tab in the Modes panel
  6. Press Play to start PIE, click in the viewport to gain control, and turn the camera in all directions without any issues

I’m currently using Mouse and Keyboard.

7

Yep, that’s what I’ve done - in several configurations now, and I lose the Y axis.

Wondering if it could be VR related? I have a Rift DK2 plugged into this PC, not that I’ve been using it at all for any of the above tests (sat on a shelf out of the way). But wondering if the recent VR Editor changes could be related to the issue I’m seeing? So maybe only happens on machines with a headset attached?

8

Yep. So this probably only happens if a VR Headset is attached to the PC.

So, with a blank project and default pawn -
When you first play in editor, the mouse controls the view XY, moving a VR Headset does nothing to the view (as it shouldn’t).
Click the Landscape tab, then back to Place tab.
Play in editor again, now the mouse doesn’t control the Y, but the headset is live and you can look around (which you shouldn’t be able to do?/couldn’t do previously).

9

Ah, that seems to be the issue. That would explain why it wouldn’t work for me but had another team member try it with an Oculus DK2 attached and was able to reproduce the same behavior. I’ll be placing a bug report in shortly.

10

Thank you for your report, Gavin1969. I’ve placed a bug report in for this and you can find it here: UE-39587 You can use this to track the progress as well. The only workaround I can think of is to not have your VR headset plugged in when it isn’t required unfortunately.

Have a nice day!