OESF Portables Forum

Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: Capn_Fish on December 25, 2006, 12:30:20 pm

Title: Psx4zaurus Input Broken
Post by: Capn_Fish on December 25, 2006, 12:30:20 pm

I just got Final Fantasy Tactics, and it runs just fine (15-20 fps non overclocked). The problem is that, while I can use X to click through the talking in cut scenes, I can't seem to control anything in the first battle. Is this a known issue? I have beta 4.3 I believe.

Thanks!

Title: Psx4zaurus Input Broken
Post by: zodttd on December 25, 2006, 04:07:53 pm

 That is a known bug. There is a way around it. Depending which version you have, if you change the VSyncRate or ClockSpeed you can get around that. It seems it was a timing issue. There's only a few decent options available between the emu freezing with that timing option so try them out in the cathedral scene in FF Tactics, and once you get to a battle it will play through the AI sequence if it works. Let me know if you get it working and what setting worked if its successful.

Thanks!

Title: Psx4zaurus Input Broken
Post by: psycoman on December 25, 2006, 05:45:57 pm

Zodttd any new about psx4all to 2.6 ? and fb ?

thnkx

Title: Psx4zaurus Input Broken
Post by: Capn_Fish on December 26, 2006, 11:23:26 am

Thanks! I will try it. I know how to change the VSync, but not the clock. How do I do this?

Just as an afterthought, it seems to me that some PS1 controllers have analog sticks while some do not. These are optional for use I take it? I didn't see anything in the controls about them.

Anyway, I will go try this now, and thanks Zodttd for the awesome emu!

Title: Psx4zaurus Input Broken
Post by: Capn_Fish on December 26, 2006, 12:13:46 pm

I just tried, and changing VSync alone doesn't help. Once I figure out how to change the ClockSpeed I'll try again.

Title: Psx4zaurus Input Broken
Post by: Capn_Fish on December 28, 2006, 03:42:39 pm

No matter how much I change the setting with tab+e and tab+r, I can't get input to work. Which beta is this issue in? Has it been fixed in any other beta?

Thanks!