Uae4arm (arm jit)

[liveevil]

So apparently what I posted above (JIT ON, 25, 14 and 7 Mhz give the same result etc.) you have to reset everytime you change the CPU speed for it to take effect on SysInfo, when JIT is OFF you don't have to reset. And when JIT is OFF and CPU is Fastest it doesn't seem to affect games.

Also, TomB posted a new version.

Would it be possible to compile this uae4arm for PS Vita? (Now it has an option to run homebrews).

[lubomyr]

android port of uae4arm updated
uae4arm-debug-23082016.apk

changes:
- added TomB changes
https://pyra-handheld.com/boards/thr...4#post-1390194
https://pyra-handheld.com/boards/thr...3#post-1390320

- Avoid audio delays in some games/demos
- Automatic switch of freshrate for programmed NTSC/PAL mode change
- Bugfix in JIT which sometimes caused seg faults when enter gui
- Savestates enabled for HD and CD configurations (don't know if this is stable)
- Added option "Wait for blits" from WinUAE

[liveevil]

Thanks for the new version Lubomyr. Now Border Sprites have been enabled the info panel on Banshee now displays, but CPU Fastest when JIT is OFF still seems the Slowest! It never used to be like this. Oh well.

[liveevil]

I asked TomB about the CPU Fastest not working correctly (JIT OFF) and he said :-

"The handling of vsync has changed in latest version and the Android port needs some changes to get correct results. The Pandora version handles CPU fastest as before."

Hi,
Congrats for this wonderful emulator !
A maybe rather naive question but I could not manage by myself. How do you activate the numeric keypad (Other than manually assigning the keys to the joypad). I badly need into play F/A 18 Interceptor...
Many thanks in advance.

[BippyM]

Any chance of adding support for vr headsets like Google cardboard?

Sent from my SM-G935F using Tapatalk

[lubomyr]

Originally Posted by Harlock

Hi,
Congrats for this wonderful emulator !
A maybe rather naive question but I could not manage by myself. How do you activate the numeric keypad (Other than manually assigning the keys to the joypad). I badly need into play F/A 18 Interceptor...
Many thanks in advance.

Numeric keypad with real keboards - works. Or did you mean numeric keyboard with virtual keyboard ?

[lubomyr]

Originally Posted by bippym

Any chance of adding support for vr headsets like Google cardboard?

Sent from my SM-G935F using Tapatalk

If libSDL will support it then uae4arm will support it too. I will try ask Pelya (libSDL dev).

Originally Posted by lubomyr

Numeric keypad with real keboards - works. Or did you mean numeric keyboard with virtual keyboard ?

Yes exactly I mean virtual keyboard... Do you mean it is not possible ?
Many thanks

[lubomyr]

Originally Posted by Harlock

Yes exactly I mean virtual keyboard... Do you mean it is not possible ?
Many thanks

It is possible.

Originally Posted by lubomyr

It is possible.

Thanks ! And... Would you mind telling me how ?

[lubomyr]

Originally Posted by Harlock

Thanks ! And... Would you mind telling me how ?

I mean it is possible to implement.
Current virtual keyboard not contain it.

if you want to fix it yourself. You must disassemble uae4arm (via apkmanager) and manual edit virtual keyboard layout files (res/xml folder, files amiga.xml, amiga_alt.xml, amiga_shift.xml, amiga_alt_shift.xml)

Originally Posted by lubomyr

I mean it is possible to implement.
Current virtual keyboard not contain it.

if you want to fix it yourself. You must disassemble uae4arm (via apkmanager) and manual edit virtual keyboard layout files (res/xml folder, files amiga.xml, amiga_alt.xml, amiga_shift.xml, amiga_alt_shift.xml)

Ouch... Is this on the roadmap ?

[Chips]

I was using 40.3993 RTG and now latest uae4arm android version is complaining that i need at least 40.3994... looks like the picasso code has been updated in latest tomb version... (moreover some resolution weren't working... perhaps due to this "old" version)

Which version do you guys are using for rtg lib ? Taken from where ?

[lubomyr]

@Chips

http://lilliput.amiga-projects.net/Picasso96.htm
v2.1e = 40.4029

[Chips]

Thanks, it works better with 40.3994 or the version you attach.
I just discovered that you need some Z3 memory for very high definition or high color depth

between i tried to merge the same picasso resolution list as you in Rpi but the 1024x600 make my A4000 config with HDD freeze after some HDD access... any idea ?
I'm still based on older Tomb source code than you though...

[lubomyr]

Chips,
I noticed that profile version is unstable. I disabled it on ANDROID.
I saw freeze only when changed resolution or after starting workbench but very very rarely and it can happen with any p96mode.
I agree that 1280x720 or higher mode require more than 16mb rtg memory, because some app not work correct with it.

I had a some problem with slow performance with new TomB code, but solved it with swapping lines in new pandora_gfx.cpp (flush_screen)
SDL_Flip(prSDLScreen);
last_synctime = read_processor_time();

and disabled few lines in drawing.cpp (adjust_idletime)
where lines #ifndef ANDROID

if you have similar reduce of performance with new code, you can do same changes

[Chips]

Following merge, sysinfo give me low value and starstruck doesn't want to start anymore...
Thanks for the line in drawing, they seems to improve things for sysinfo (but the whole synctime should be broken in rpi anyway)
Did you try starstruck on android ?

[lubomyr]

Starstruck run fine on my android device. Only glitches from time to time with unwanted line which appears in top part of screen (after last update of uae4arm).