With the 8.3.0 SDK (and perhaps the previous SDK) the camera view can sometimes be distorted within the editor on Windows 10 when running in Unity 2018.2 and Unity 2018.3, but not in Unity 2018.1. And not on OS X. And we have seen this issue only on 2 of 4 Windows 10 computers. We have tested with embedded cameras, external web cams, and remote camera using the Unity Remote 5 Android app. Each of those cameras displays a different incorrect scaling and does not cover the full screen.
I have attached an example image of the video within the editor from a particular Windows 10 machine. The scaling of the image is wrong and there are black borders typically on the right side and top of the screen. We have seen reports of black or missing video in this forum and we are wondering if we are seeing a variation of that.
For now we will continue to use Unity 2018.1 as we haven't experienced these issues with 2018.1.
We downloaded the 8.5 update and retried it with Unity 2018.3 and 2019.1.2. The issues with the camera offset, scaling and cropping are still present. We have posted a video that illustrates the problem - https://youtu.be/wRlie-3N0Q4. This video was made on a Microsoft Surface book 2.
It is at least an inconvenience for us in that we will need to author the Wikitude apps in an earlier editor than we will build the release versions with. And including any features of later versions of Unity (such as the new AR features offered in Unity 2019) will be problematic.
Thank you for the update. The fact that there are multiple reports of this issue and we are still not able to reproduce it is very concerning for us. We're still trying some new things and looking at different hardware, but it might be a while until we find a solution. We might have to send out some custom builds with additional logging just to get some more information about what could be wrong.
I'm not sure if this is a viable option for you, but the 2017.4 LTS releases can also produce 64-bit builds, and I assume this issue is not present there. Of course, downgrading the project might not be possible for you.
We'll let you know as soon as we have some news.
Thank you for your patience,
Yes we are still experiencing this issue. We have noticed other postings that seem to be the same issues that we are experiencing -
This is becoming more of a concern for us. As you know, the Google Play store will only accept 64-bit builds as of August, and we cannot produce 64-bit builds with Unity 2018.1.
Today I asked the team to see if the issue had gone away with Unity 2019.1,2f1, but the issue is still present.
Is this issue still affecting you? I tried on both a Surface and a Lenovo ThinkPad device and still couldn't reproduce the issue. Have you noticed anything else that could help reproduce the issue?
It does seem to happen with the example projects in the download package.
This is a screen image from the unity editor on a second laptop (not the same one from the images above), running Windows 10 and Unity 2018.2.18f1. The laptop used in the previous images was a Microsoft Surface Book 2 and the image above is from a Lenovo ThinkPad X1. The image has a black bar on the side and has incorrect aspect ratio in that it seems stretched vertically or compressed horizontally. This is the scene "Object Tracking - Simple" in the example project.
I found that when embedding the "Game" window in the editor program it would have correct aspect ratio but with black bars on the right and top sides. Popping it out of the editor (as I did in order to to the screen-copy) made the aspect ratio incorrect but with only the black bar on the right side.
We found the same issues with Unity 2018.3.6f1 when testing last week. So for now we will continue using 2018.1.9f2 for our Wikitude projects.
Thank you for reporting this issue. This is the first report we've had with camera frame rendering not working correctly in the Editor, and I don't think it's connected to other reports that happen on specific devices.
We also couldn't reproduce the issue on our devices (Windows 10, Unity 2018.2). Does this issue happen in the example project provided in the download package as well, or just in your project?
This issue also occurs with the 'static image' camera. I have attached an example screen shot.