• Advertisement
Sign in to follow this  

Unity Target out-dated phones?

This topic is 2089 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi community!

I've been playing with (an idea to make a game for) Android lately and started wondering, whether there still are phones (tables?) out there which would NOT support OpenGL ES 2.0 and GLSL ES 1.0. The game would be a pretty simple thing and probably for free (no big ambitions), however I'm not sure if it ever "pays off" trying to support horribly old devices which can do fixed-function only or are otherwise incredibly crappy. Personally I don't know anyone in my vicinity who'd have a smart-phone which can't deal with GL2 well but I have no idea what kind of people with what HW usually buy indie games on phones at all...

Stemming from DX10/11/GL3/SM4++ world, leaving fixed-function OpenGL far, far away in the deepest past's beginnings, this might probably hurt me :-D

Any insights? :-) Edited by pcmaster

Share this post


Link to post
Share on other sites
Advertisement
As far as I know, all the Android releases have required 3D either through hardware acceleration or through software rasterization of ES 1.0.

There are very few phones I'm aware of that don't have hardware 3D support.

Share this post


Link to post
Share on other sites

I do know that. I'm asking specifically about OpenGL ES 2.0, NOT 1.0.


http://developer.android.com/resources/dashboard/opengl.html

A phone that doesn't support GL ES 2.0 is the G1... more concerningly, many custom ROMs for phones that only support GL ES 1.x actually report that they support GL ES 2.x, but when you try to make any call to an ES 2.0 function, will only trip glGetError with an unsupported error.

Share this post


Link to post
Share on other sites
Thank you very much Ameise, this was exactly what I wanted to hear. What I'm taking from this, for now and such a project, is target 2.0 only :-)

Share this post


Link to post
Share on other sites

Thank you very much Ameise, this was exactly what I wanted to hear. What I'm taking from this, for now and such a project, is target 2.0 only :-)


Make sure you heed my later comments about phones that report GL ES 2.0 support while not actually supporting it. I don't know if they will come up on the Market when you flag in the XML file as "GL ES 2.0 only". You will need create a GL ES 2.0 context, see if that fails, and then make a trivial ES 2.0 only call, and then see if that fails, to be sure.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By bryandalo
      Good day,

      I just wanted to share our casual game that is available for android.

      Description: Fight your way from the ravenous plant monster for survival through flips. The rules are simple, drag and release your phone screen. Improve your skills and show it to your friends with the games quirky ranks. Select an array of characters using the orb you acquire throughout the game.

      Download: https://play.google.com/store/apps/details?id=com.HellmodeGames.FlipEscape&hl=en
       
      Trailer: 
       
    • By Manuel Berger
      Hello fellow devs!
      Once again I started working on an 2D adventure game and right now I'm doing the character-movement/animation. I'm not a big math guy and I was happy about my solution, but soon I realized that it's flawed.
      My player has 5 walking-animations, mirrored for the left side: up, upright, right, downright, down. With the atan2 function I get the angle between player and destination. To get an index from 0 to 4, I divide PI by 5 and see how many times it goes into the player-destination angle.

      In Pseudo-Code:
      angle = atan2(destination.x - player.x, destination.y - player.y) //swapped y and x to get mirrored angle around the y axis
      index = (int) (angle / (PI / 5));
      PlayAnimation(index); //0 = up, 1 = up_right, 2 = right, 3 = down_right, 4 = down

      Besides the fact that when angle is equal to PI it produces an index of 5, this works like a charm. Or at least I thought so at first. When I tested it, I realized that the up and down animation is playing more often than the others, which is pretty logical, since they have double the angle.

      What I'm trying to achieve is something like this, but with equal angles, so that up and down has the same range as all other directions.

      I can't get my head around it. Any suggestions? Is the whole approach doomed?

      Thank you in advance for any input!
       
    • By khawk
      Watch the latest from Unity.
       
    • By GytisDev
      Hello,
      without going into any details I am looking for any articles or blogs or advice about city building and RTS games in general. I tried to search for these on my own, but would like to see your input also. I want to make a very simple version of a game like Banished or Kingdoms and Castles,  where I would be able to place like two types of buildings, make farms and cut trees for resources while controlling a single worker. I have some problem understanding how these games works in the back-end: how various data can be stored about the map and objects, how grids works, implementing work system (like a little cube (human) walks to a tree and cuts it) and so on. I am also pretty confident in my programming capabilities for such a game. Sorry if I make any mistakes, English is not my native language.
      Thank you in advance.
    • By Ovicior
      Hey,
      So I'm currently working on a rogue-like top-down game that features melee combat. Getting basic weapon stats like power, weight, and range is not a problem. I am, however, having a problem with coming up with a flexible and dynamic system to allow me to quickly create unique effects for the weapons. I want to essentially create a sort of API that is called when appropriate and gives whatever information is necessary (For example, I could opt to use methods called OnPlayerHit() or IfPlayerBleeding() to implement behavior for each weapon). The issue is, I've never actually made a system as flexible as this.
      My current idea is to make a base abstract weapon class, and then have calls to all the methods when appropriate in there (OnPlayerHit() would be called whenever the player's health is subtracted from, for example). This would involve creating a sub-class for every weapon type and overriding each method to make sure the behavior works appropriately. This does not feel very efficient or clean at all. I was thinking of using interfaces to allow for the implementation of whatever "event" is needed (such as having an interface for OnPlayerAttack(), which would force the creation of a method that is called whenever the player attacks something).
       
      Here's a couple unique weapon ideas I have:
      Explosion sword: Create explosion in attack direction.
      Cold sword: Chance to freeze enemies when they are hit.
      Electric sword: On attack, electricity chains damage to nearby enemies.
       
      I'm basically trying to create a sort of API that'll allow me to easily inherit from a base weapon class and add additional behaviors somehow. One thing to know is that I'm on Unity, and swapping the weapon object's weapon component whenever the weapon changes is not at all a good idea. I need some way to contain all this varying data in one Unity component that can contain a Weapon field to hold all this data. Any ideas?
       
      I'm currently considering having a WeaponController class that can contain a Weapon class, which calls all the methods I use to create unique effects in the weapon (Such as OnPlayerAttack()) when appropriate.
  • Advertisement