Snes ASM testing lem

[deivetru]

Hi yoyofr,I am trying to compile the source code in Code Warrior 9.3, but I am not having success, they lack some commands in library.Do you could indicate me which library and compiler version you are using? The commands that are lacking are:

res=PnoLoadYOYOFR (&pno, pnoPtr);
res=PnoUnloadYOYOFR (&pno);
errors of link:
undefined identifier :
"pincreator
winDisplayChangedEvent ;
pininputareaopen;
pininputareaclose;"
and initromlist out of range.

Thanks!

[JeremySmith]

Beta 7, Zire72, UDMH: FFII still crashes (gives a Fatal Exception) when you tap the screen. Super Metroid works fine.

[StuBee]

Odd...
I suddenly lost the ability to use the "A" button in SNES. I can assign it to different keys...it just doesn't work (ie fire). The "B" button still works...I can even reverse the assignments for A and B buttons and B will work on the other key, but A will not.

A is assigned value "0000008"
B is assigned value "0000010"

-----
"A" still works in NES and GB. Strange....
----
FYI: Before it goofed up, I was trying to assign X,Y,L,R keys to other keys on my keypad (TC)

Any thoughts?

[infinity]

I can confirm that the slowdown is apparent when pressing buttons in other emulators using the Tungsten C as well... Namely Firestorm 1.3.2 and Castaway.

Its just less apparent because (I suppose) the emulation is not as CPU-intensive...

I'm not sure about the slowdown on frodo, but anyways frodo seems to be able to handle the keyboard on some levels as you can type with them normally on the BASIC screen but you cannot bind them to do an action (same problem as here... when you bind one you bind them all -no LOTR pun intended-).

Is the slowdown a T|C specific problem or do other devices with build-in keyboards (Treos, Clies, etc) experience it as well?

[yoyofr]

=> deivetru
you cannot compile ljp right now, since I've done some modification to codewarrior libs (mostly pnoloader & paceinterface).
The next source release will have pace replaced by armlib and the pnoloader by my ownone, so you'll be able to compile ljp.
=> infinity
the slowdown issue seems to be noticed on most devices other than zodiac. In fact, every device which does not support key masking will generate event (to be handled or crash will occur), so slowdown the overall emulation process.
To understand the impact, remember than when you emulate a system running at 60fps, on fast device you are able to generate sometimes 100fps, so you have to put a limit at 60fps and so you still have some cpu processing time left. This processing time can be enough to handle the key event handling.
On slower device, you have to use frameskip to have 60fps, so you don't have much cpu power left. Then when you push a key and an event is generated, your cpu has left process time to spend in emulation, because the event handler takes awful time to execute.
You can check this by playing with the sound on/off and frameskip option in nes/gc module.
On sound off, frameskip=2, there should be no slowdown on msot device. With sound on, frameskip=0, the slowdown will be noticeable on slow device (T|E, ...)

[Skaaj]

Tested Debug 7

Palm: Zire 72
Hacks: UDMH
Launcher: none

Errors:

-Fatal Exception upon accessing menu (tapping on screen

-black screen occured on one game that previously worked on 6b

-speed might have been a little faster(unsure)