Issues with snesoid and PSX4DROID on Nexus One

[robert_e_leet]

I use snesoid and PS4DROID to play old school RPGs on my Nexus One and one reoccurring problem has been when holding X down to run like in FF7 or Chrono Trigger, about every 20-30 seconds or so it presses triangle automatically and brings up the game menu. I tried making the buttons bigger and try and hold down only on the very bottom edge of the button but it still happens. I've heard reports of Nexus One's having touchscreen issues but it doesn't appear to be a problem outside these emulators but I may be wrong. Any suggestions?? Thanks

 

[StuartTheFish]

That's called shitty multitouch. A lot of HTC handsets are the same unfortunately. It might help if you put the D pad on the bottom left and the buttons on the top right, but it's still not perfect. As soon as the axes of each touch get close enough, they actually snap onto the same axis, causing your random button pressing issue. Sometimes they can actually invert too, meaning it thinks your finger is actually at the opposite corner of the screen! You actually want to make the buttons SMALLER, as then they are a little further away from your other finger, so a little less likely for the axes to snap together on you.

Here's a video to show you what I mean:
http://www.youtube.com/watch?v=5MLUmJL_Px0

The touchscreen is normally pretty good for anything else available, but emulators constantly require more than one finger on the screen at any time, hence why we get problems if our handset uses a poor multitouch setup.

 

[TheTrueSpin]

That's called shitty multitouch. A lot of HTC handsets are the same unfortunately. It might help if you put the D pad on the bottom left and the buttons on the top right, but it's still not perfect. As soon as the axes of each touch get close enough, they actually snap onto the same axis, causing your random button pressing issue. Sometimes they can actually invert too, meaning it thinks your finger is actually at the opposite corner of the screen! You actually want to make the buttons SMALLER, as then they are a little further away from your other finger, so a little less likely for the axes to snap together on you.

Here's a video to show you what I mean:
YouTube - HTC Desire - Multitouch Problems

The touchscreen is normally pretty good for anything else available, but emulators constantly require more than one finger on the screen at any time, hence why we get problems if our handset uses a poor multitouch setup.

yeah, I noticed this to. Never been an issue with any other applications or games, but in FF7 I kept opening the menu, which was annoying.

Just play around with the keypad layout until you find something that works for you.

 

[StuartTheFish]

Thankfully, the newer final fantasy games allow you to only need one finger at a time, as you can select "always run" from the menus. So now if you pressed the run button it makes them walk at normal speed.

 

[Therev29]

You can try the multi button press option in the virtual keypad settings to see if it helps. Not sure what phones are supported with that option but might work for you

 

[StuartTheFish]

That setting won't make any difference, all that does is stop the emulator from registering more than one press at the same time if disabled. The handset DOES support multitouch, but there are hardware limitations to the type of screen used on these phones, causing the issues shown in the video I attached. There is no way round it unless you want to get some kind of gamepad, or make the issue less prone to happen if the buttons are smaller and further away from the middle of the screen.

 

[Therev29]

Lol, just noticed this setting is on snesoid but not on psx4droid anyways.
Coming from fpsece emulator they talked about it a lot, when 2 points are touched that are close on the y axis, it can't differentiate the 2 as seen in the video. Reason behind top and bottom positions for the d pad like you said.

I thought if the multi press was enabled and threshold set for amount of buttons to be pressed, it was supposed to help with this too?? IF not what does it do when enabled and what's the threshold about?