Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

[4.14 Bug] VR camera doesn't work

I am using the github release branch, currently on 4.14. Whenever I start the game, and if there exists a camera in the scene, in VR the camera will always center to 0,0,0 in world position, OR to whichever possessed pawn's local 0,0,0. Blend view to target doesn't work, having a seperate camera doesn't work...nothing works (I do have locked HMD on). Without VR preview, everything works normally. To replicate this, it's best to make a camera that's top down VR without being 1st person from the pawn.

I didn't have this problem when I tried back in 4.10; I assume this is an engine bug, or does anyone know how to get it to work?

Product Version: UE Github Master branch
more ▼

asked Jan 06 '17 at 04:17 AM in Blueprint Scripting

avatar image

60 8 13 17

avatar image michaeleeli Jan 06 '17 at 05:51 AM

I think I found the answer...for some reason, the VR headset was taking the possessed Camera Component's LOCAL position and translating it to WORLD position. Since the Camera Components were at 0,0,0 in local position (even if they were placed like 1000,1000,1000 in world), it kept forcing it to 0,0,0 in world no matter what.

A current workaround (which hopefully can get fixed in the engine later):

-Create your own playercontroller

-Turn off "auto manage active camera"

-Create an actor with camera component inside (you CANNOT create a camera actor as the local position for the camera component in that is fixed at 0,0,0).

-Click the actor's "self" settings and make sure its "auto manage active camera" is on

-Make the root a scene or anything but the camera

-Move the camera in local position to reflect world position

-Moving the camera through blueprints beyond this point will take stupid workarounds.. like move camera world location won't work, so you have to move the root component's world position + a fixed vector amount you need, or move the camera's local position (which gets messier when you use those vectors to calculate other things)

How do I submit a bug report? I need to get this fixed as soon as possible to continue my project =(

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

0 answers: sort voted first
Be the first one to answer this question
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question