HDM wrote: Phaedrus Nine wrote:
HDM wrote:when I play a racing game, ctr etc, the cross, now automatically stops pressing, and the car stops
happens to someone else?
That doesn't specifically happen to me. Just something similar. Sometimes when I play a game, the controls stop responding. For example, if I'm playing Gran Turismo 2 and I turn right to take a corner, brake, then accelerate again, the D-Pad stops repsonding. I have to take my fingers off the screen, then back on before they start responding again.
I don't quite know under what circumstance this happens. I'll try test some more. It seems to be when I steer, then go from X (accelerate) then press Square (Brake), then back to accelerate again.
It reminds me of an old bug with FpseCE, about release times on the overlays.
to me the problem I mentioned, is the first time that happens to me, only in this 0.10.5, in previous, only the problem that occurred in the first that was sticky, but in this will void the cross and not you can play racing games.
the problem you mention, also in some occasions, but not often and random
I must say the installation is completely new clean t.
What type of phones are you all using? This happens to me and when I play something with extended touchscreen controls and I am on a Droid 2. Unfortunately if you are using a Motorola phone this isn't due to the emulator, its due to the garbage touchscreen on the phone. Motorola phones are only capable of tracking 2 points and there is a vertical axis error that causes the touchscreen tracking to flip points. When this occurs the screen basically spasms and it stops sending a constant contact signal until you remove all fingers and place them back on the screen. Go download the multitouch app off the market (its free) and you can move your fingers around and see the error for yourself. Also you will notice that Moto phones only support 2 finger multitouch where most all other phones on the market support 3+ (most 4+) finger detections. Therefore also if you are holding down the movement pad and holding down say drive, you are screwed. The vertical aliasing error can't be fixed by a software update on these phones (people have tried...). There are some other phones that suffer from this issue also, but it appears to just be a pretty nasty flaw in the hardware itself. It may be of note that this happened to me in SNESoid, psx4droid, fpse, zenonia 1, zenonia 2, and pretty much anything else that uses a touchscreen. For quick presses the issue doesn't seem to be as prominent and if you lift your fingers (like the d-pad) then naturally you probably wouldn't see this problem. Sadly I think the only actual fix for this is to get a new phone that supports better multitouch... its one of the weak points that has somewhat permanently burned me on Motorola's phones since I started seeing it back in the Fall.
Performance overall is great though, and the touchscreen works fine on rpgs and other games so I'm ok on that. I have just resorted to the fact that if I am going to play a racing game I have to slide my keyboard out b/c of Moto's janky touchscreen.