You mean altering the 3dmodel complexity at runtime? I already made the models less complex, but making them even more complex would result in very ugly weapons.
Now i got a OutOfMemoryException when it runs on some phones. So i'd rather not publish for those phones. Point is that the market needs something like this. B.t.w: why is there such a delay in posting something and seeing it here? On Nov 23, 3:24 pm, Warren <warrenba...@gmail.com> wrote: > This is not a direct answer to your question, but have you tried > altering your models and images for less capable phones? > > I've tried something like this with acceptable results. Probe the > screen size or do a CPU calculation check at startup, then reduce your > texture sizes or model detail accordingly. Not ideal, but it works. > > Warren > > On Nov 20, 4:06 pm, Dutch Android Guru <dutchandroidg...@gmail.com> > wrote: > > > > > > > > > What i need is target hardware like Memory, CPU, and OpenGL 2. > > > I read a comment on this > > articlehttp://androinica.com/2010/05/12/dear-google-please-let-android-devel... > > > I really like this comment: > > > *"The problem here is not (and should never be) fixed by blocking specific > > devices. If anything, because the list of devices will soon be too large for > > a single person to handle. * > > * > > It should be handled by requiring the correct hardware, if the Market > > doesn't already support that. Barcode Scanner, for example, could require > > auto-focus camera (there are already means for requiring a camera, for > > example; we just need a requirement for auto-focus). Raging Thunder 2 should > > ask for OpenGL ES 2, or a certain amount of VRAM, or whatever. > > > * > > *tl;dr the Market needs many improvements, but blacklisting or whitelisting > > devices is a horrible solution. Check for hardware capabilities.**"* > > * > > * > > Basically android already supports this partially with the <uses-feature in > > the xml manifest. However there should be more support for the hardware > > types i mentioned. > > > So: How should i do it now? And how is this going to be supported in the > > future? > > My only option now is to detect it on startup and give an alert box to the > > user that it doesnt work on their phone. > > However then my whole sale-model is ruined. > > > 2010/11/20DutchAndroidGuru<dutchandroidg...@gmail.com> > > > > I have an application that loads a 3dmodel and renders it. These > > > models are rather big and i can only get it to work fast on faster > > > hardware phones such as the Nexus One. However there is no way to > > > target faster hardware phones. > > > Now i get very good ratings (on phones where it work) and very bad > > > rating (on slow phones). > > > > Also: i would like to know the phone type when a user comments. In > > > this way i can test it and check whether the user had a valid point or > > > not. > > > Could you please add this? Same for error reports. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
