Playmaker Forum
PlayMaker Help & Tips => Android Help => Topic started by: cursed1 on December 08, 2013, 11:11:17 AM
-
hi everyone
maybe stupid question but i dont know it and not understand
how to make game screen size suitable all android devices (etc device 1 = 4.3" screen , 3.7" screen )
how to make it
thanks
(my english bad i m sorry)
-
Though I haven't tried myself, I'd use: 'get / set screen resolution' action. See below thread for idea on how to handle multiple aspects:
http://hutonggames.com/playmakerforum/index.php?topic=5320.msg25573#msg25573
-
change screen size
i use"set/get screen resolution" not working for me
(http://u1312.hizliresim.com/1j/8/vbb04.jpg) (http://bit.ly/c25MCx)
(http://u1312.hizliresim.com/1j/8/vbb0r.jpg) (http://bit.ly/c25MCx)
-
hmm thanks i will try now
-
i can't do this :'(
i could not
-
Post some screenshots of your playmaker setup or explain what your setup is. We can't guess what's wrong from images with no details.
-
Hi,
Do you want to accomodate 3d content or 2d interface elements?
you will face not only a resolution problem, but also a ratio problem, the two are very distinct and solved with different technic.
3d content resolution: it doesn't matter.
3d content ratio : use a safe abstract area that fit between the two most extrem ratio you get get and fill the rest with background and props that are not important, but will occupy space on extrem ratios. I am not aware of any other technic without adjusting the content position itself.
2d content resolution: use a proper 2d framework such as NGUI or 2d toolkit, they have tools and tricks to switch textures. ELSE always design for retina, lower resolution will work ok. ALWAYS make your texture and sprite size multiple of 2 so that when they are downsized ( from retina to non retina), they don't get half pixels.
2d content ratio: use anchoring systems, so that content sticks to corners of your screens. GuiTexture and GuiText can do that, their x,y position ranges from 0,1 covering the whole screen area within that 1 unit position definition.
based on this, if you can refine your needs, I can go more into details.
bye,
Jean
-
Have you looked at using Fragments? Fragments should help make the code more re-usable, and support tablet views and smaller screen views (phones) easier.
See here: http://developer.android.com/guide/topics/fundamentals/fragments.html And here: http://mobile.tutsplus.com/tutorials/android/android-tablet-design/ (for a little tutorial)
You'll need API 3 at least, I believe.