GoogleVRControllerInputComponent in branch 4.13-google-vr ?

[aussieburger]

@nesrak1;652174

I’m using a regular Pixel, and I just set mobilecontentscalefactor to 2, mobileonchipmsaa never made a difference for me ( I had a toggle and a before and after pic and they were exactly the same )
mobilecontentscalefactor on 2 seems to be fine for me. I never used 0 for that.

BTW I just totally forgot to include the new google vr sdk inside of that fork I doubt that has anything to do with it, but if you want to update it its at Engine\Source\ThirdParty\GoogleVR\

EDIT: I redid the steps from: [GoogleVR] No antialiasing at all? - XR Development - Epic Developer Community Forums
and I have full resolution and AA again I could not get full res and AA to work via the google documented way: https://developers.google.com/vr/unreal/daydream-in-unreal#rendering_resolution

Side note: Seems google made lots of changes in that thirdparty folder for 1.1 not just to the googlevr subfolder :S