I had to make a simple fix on a project, which only had to take a few days, and I ended up struggling to make something really basic to improve a project programmed by someone else for over a week.
Simply put, I can’t seem to be able to make a game with scalable UI to use the full screen on a Samsung Galaxy S8+.
I’m developing on Win10Pro, and had to switch to Mono because IL2CPP doesn’t even compile if I set a Custom Max aspect ratio.
I even tried to tinker with manifest files, but with no results. It either compiles or it’s unusable, but still no 18+/9 fullscreen aspect ratio in any case.
I developed other games in the past, using 2017.x, and all of them worked with the craziest aspect ratios.
Also, when not using Unity Cloud Build, I can’t compile the game because I get this error:
error: ‘2,1’ is incompatible with attribute maxAspectRatio (attr) float.
error: failed processing manifest.
Is it because it should be “2.1” but my locale settings use the comma instead of the point?
I didn’t change anything in the manifest files, and if I do, it just goes worse.
I wonder if leaving it to some integer value like 3 would do the job just the same.
Do you use gradle or an internal build system? I’m not able to reproduce this myself, but your screenshot has given me one idea. Do you get the same result if you specify a whole number? Like for example 3.
And yes, the build doesn’t fail with 3, I’m deploying the app with 3.
Local compile and cloud build don’t seem to differ.
Fact is, even uninstalling the app each and every time, it doesn’t go fullscreen on Samsung S8+ and similar, even putting 3. Even using Native, even using Legacy.
I believe it may be a problem with that feature (I released games which were already supporting the weird S8 aspect ratio about a year ago Unity 2017, right on the S8+ and Oreo launch - no issues with uncommon aspect ratios) — coupled with an issue that makes Unity use the localised numeric format in the Manifest. So, it uses a comma instead of a point.
Could you please help me?
Do you have any temporary workaround to make everything work? I’d need to rollout the app in about 12 hours and… people are not going to be happy to discover that the latest update takes a step back, forcing the letterboxed format.
It’s an app for a national museum and… well, people will be downloading it in mass, also due to media announces and TV/media marketing
Probably I’ve been a bit too zealous to upgrade the whole project to 2018.3, Should have waited for 2018.4 which I really hope is already in the making.
Extra info: I"m using the LW SRP.
Any help is welcome, I already browsed a lot of solutions on the web, potential workarounds, but none worked so far.
Feel free to contact me via PM if needed.
A copy of the project is on Unity Cloud, available for Unity internal staff to reproduce the issue.
I get the same bug on Unity 2019.4.23, is there any chance the bull will be fixed in a 2019.4.x version anytime soon? The issue is closed but it should be fixed in LTS versions, not in Unity 2021 only. @JuliusM
