|
|
Post by laxloser on Dec 15, 2006 10:15:58 GMT 1
OK OK OK,
I know you guys are gonna get completely irritated about this post and I apologize in advance for that. Ive been trying to search the old posts but cant find the answer to my issue. I have a Treo 650 and I just learned about this emulator. I downloaded it and everything seems to work pretty ok, except that I cant figure out for the life of me how to get the left and right arrows to work to move my guy. I downloaded contra cause lets be honest its probably the best NES game of all time, and i can make him jump, i can make him shoot, i know where pause is, but I've hit every button on my phone and cant get my guy to move. PLEASE HELP. I realize im retarded when it comes to this kind of stuff and any help would be appreciated.
Thanks alot
|
|
|
|
Post by needhelp on Dec 16, 2006 6:04:55 GMT 1
Hello there, Double check that you set up the left and right arrows to make him move in the configure screen for the NES emulator. For some reason, my config got messed up and I had a similar problem. Try that and tell me what happens. Hope it helps  P.S. There is no need to feel retarded about this, we all have our own problems when we come to running LJP on your palm devices. I keep on getting error messages when I run SNES, but it still works provided I reset my palm first. |
|
|
|
Post by _Em on Dec 18, 2006 17:18:52 GMT 1
The 5-way navigator on older Palm devices uses different key events for left and right than the new ones do. LJP's button defaults are set for the old devices, so you have to configure all your buttons before you try playing a game. I agree that this is something not easily figured out on here without reading a lot of posts in threads that on the surface have nothing to do with this issue. So, now we have a thread dedicated to it for future readers to find |
|
|
|
Post by Tinnus on Dec 19, 2006 14:18:58 GMT 1
I thought the key config screen was the first place to look when you have some kind of key problem. Guess I was wrong  |
|
|
|
Post by chaostheory on Jan 3, 2007 14:07:36 GMT 1
OK OK OK, I know you guys are gonna get completely irritated about this post and I apologize in advance for that. Ive been trying to search the old posts but cant find the answer to my issue. I have a Treo 650 and I just learned about this emulator. I downloaded it and everything seems to work pretty ok, except that I cant figure out for the life of me how to get the left and right arrows to work to move my guy. I downloaded contra cause lets be honest its probably the best NES game of all time, and i can make him jump, i can make him shoot, i know where pause is, but I've hit every button on my phone and cant get my guy to move. PLEASE HELP. I realize im retarded when it comes to this kind of stuff and any help would be appreciated. Thanks alot Yes this is the first thing i found out as well on my Treo 650. Left and right are labeled 04000 and 08000 i think instead of the default nevleft and navright. Those are the only 2 i changed to make the emulator work. Wondered why my little Samus couldnt move when i first loaded up super metroids. The only thing i have trouble with is the events you have to tap the screen corners for. I sometimes have trouble making them only tap once. |
|
|
|
Post by Ryuujin on Jan 3, 2007 16:03:22 GMT 1
The only thing i have trouble with is the events you have to tap the screen corners for. I sometimes have trouble making them only tap once. I've noticed this on my Tungsten X as well. When I hit an on screen button (mainly L/R on SNES), it thinks I'm hitting it INSANELY fast. Even when I press and hold the on screen button, it acts like super autofire. Naturally in games that require you to hold down L and/or R for various gameplay functions (such as running away in Tales of Phantasia, I've reached a point where I can't continue because I need to run away from some enemies that I'm supposed to run away from), those functions are rendered impossible to pull off. I also noticed assigning the Power button to a button does nothing for it. |
|
|
|
Post by _Em on Jan 3, 2007 18:25:58 GMT 1
Do you have some other hacks on your T|X that could be interfering? I don't have any of the problems you mention on my T|X... power button is set to start button, and b1 is set to L (screen area set to R). All three work as would be expected.
|
|
|
|
Post by Tinnus on Jan 3, 2007 20:35:31 GMT 1
And BTW, L+R when L and R are on-screen won't work since you can only press 1 screen button at a time.
|
|
|
|
Post by Ryuujin on Jan 5, 2007 3:16:39 GMT 1
The only hacks I have running on my TX are UnCache, UDMH, Dmitry's freeware 4 MB heap RAM defrag hack for the TX, and WarpSpeed. Well, I also have MultiUserHack, but that's off while I use LJP. I also have DALauncher installed as well as the DBCache DA, and DBCache itself (which is not in the UnCache list). I think I deleted all other hacks already (they were ones useless to me that I got from Palm Powerups). For the life of me I can't figure out why holding down an onscreen button would make the button go on crazy fast autofire instead of staying in a down state until I stop pressing it.
Oh, and after I posted that note, I tried assigning L to my RockerCt button and R to my power button. Surprisingly, the power button does indeed function! Guess it's a small price to pay to not have turbo mapped to a button. Well, actually I can probably map that to onscreen now.
|
|
|
|
Post by _Em on Jan 5, 2007 19:16:27 GMT 1
If you have UnCache installed, you don't need the MemFix hack; all it does is prevent Blazer from loading into cache at soft reset, just like UnCache does if you don't have Blazer in your UnCache list.
One other question: what button do you have autofire set to? If you have multiple functions set to the same button (can you even do that in LJP?), you could have the same issue you're describing.
If you're holding down an ONSCREEN button, then that's probably your issue -- IIRC, onscreen buttons don't "hold down;" rather, the emulator samples screen taps every so often and sends a key down signal if it detects pressure in the appropriate area. There can only be one "screen down" coordinate at a time, and keeping it held down is equivalent to repeatedly mashing a hardbutton. You'll also find that some of those presses don't register (just like when you're in the menuing system).
This sounds like a good location for a cheat hint too -- when I get to a portion of an SNES game that needs super quick reflexes, I switch to 'bullet time' by turning off frameskipping altogether. This allows me to get all my button presses in, where they wouldn't necessarily all make it at regular speed. Good way to get around the button interface limitations of PDAs.
|
|
