New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi-resolution code in the default template is confusing and needs to be changed #18492
Comments
Since the engine has enough open issues, too much in my opinion, I give 2 weeks to this issue, if no one will be interested, then I will close it. |
I will get this on my list of items to review. Ultimately, I would still need engine team members to sign off on anything before a merge. |
@minggo do you have thoughts about replacing this code. Would it be helpful for me to test and post results from a |
@slackmoehrle yep, go forward please. |
@slackmoehrle Well, it is been a while. Any chance that something of this will go into 3.18? |
I think we need this too. I just need to get it done. I can use your ideas above to start. |
Cool.) When do you plan to start working on this? |
Hi guys. Could you give us any status about this issue? |
Hi, guys we are fetching the same issues any solution for that? or any other way so we can solve multi-resolution problem and game can work on every device |
This is not exactly an issue of the engine. The engine gives you the tools to support multiple screen resolutions. But you must choose one of the many combinations that suits your game. In this issue, I only say that the code in the template is bad because Why there is no universal solution? I will try to explain with an example. In my last project I use
And it works great for me! Well, because I remember that the corners of the screen can be rounded, and the speaker can take part of the screen at the top. And now let's go to the Google Play store. Now look here https://play.google.com/store/apps/details?id=com.king.candycrushjellysaga So my advice for you is to read the forum, experiment, or ask slackmoehrle to write this documentation which he has long promised. |
@Priority10 thanks for the explanation. we have found something on the internet and they claim that they are able to solve these issues, can you please look into it, we have tried but we are not getting exactly how they are doing it. link of that PPT (slide number 19-24) |
Sorry, I can not open the link. This site can’t be reached ERR_CONNECTION_RESET My point is that you can find a ready-made solution on the Internet, but without understanding how it works, it is quite possible that you will use it incorrectly. Not because you are not smart, but because every solution has limitations that you need to keep in mind. |
Quick advice on how to figure this out faster
|
Since I did not receive any feedback on the forum, I publish it here. You can do whatever you want with it, use one of the options, or close this issue and forget about it. I do not care.
Short version.
Firstly, I do not think this is the best solution ever, but I think that this is a good option to illustrate how it works.
The aspect ratio of the
Design Resolution
is16/9
to better illustrateNO_BORDER
.Convenient scale factors (
x1
,x2
,x3
).In this case, I just do not like how it works if screen width = resource width, but the screen aspect ratio <
16/9
(only in some cases, like 1920x1200 or 1920x1440 or 960x640 ... ). Maybe I'm just a perfectionist. But this is a good option to illustrateNO_BORDER
. I doubt what to choose.The aspect ratio of the
Design Resolution
is4/3
, not so good to illustrateNO_BORDER
, my inner perfectionist absolutely likes how it works.Convenient scale factors (
x1
,x2
,x3
).The aspect ratio of the
Design Resolution
is4/3
, not so good to illustrateNO_BORDER
, moreiOS
friendly.Personally, I do not like scale factors.
Since there are many similar resolutions like
1920x1080
,1920x1200
,1920x1280
,1920x1440
, I prefer to choose the resources based on the longer side of the screen, in the case of the default template it is width.It is necessary to add 3 folders with resources in the default template.
The text was updated successfully, but these errors were encountered: