After some debugging, it works under X11 but not under console.pawelkrak wrote: Amiga reset via : LAMIGA RAMIGA + CTRL not working. When entry in GUI then RIGHT CONTROL reset Amiga and ESC key. When Amiga run is impossible to reset Amiga from keyboard ( PC keyboard or Amiga 1200 keyboard via Keyrah V2)
Can You check it or where I can find solution to fix it ? I checked sources but is different from other old sources. Regards Paul
Hi Chips, with your last build i have the following issues:Chips wrote:I merged the latest version from pandora in github.
The audio/graphics dis synchronization disappearsbut I feel like audio get a little bit worst
EDIT: looks like it's link to the configuration I was loading which has cpu set to more compatibleat least it's not activated by default. Let me know if you feel the same...
Chips wrote:I merged the latest version from pandora in github.
The audio/graphics dis synchronization disappearsbut I feel like audio get a little bit worst
EDIT: looks like it's link to the configuration I was loading which has cpu set to more compatibleat least it's not activated by default. Let me know if you feel the same...
I know, since two pandora delivery startruck is worst than what is was... this problem is more on internal emulation core which is more known by TomB than myself (indeed I never try to understand emulation core)...Shaytan wrote:Hi Chips, with your last build i have the following issues:
Audio plays very slowly and out of synch (tested with Starstruck by TBL and Switchback by Rebels)
The screen in pal mode is not entirely filled (bottom quarter is black), no problem with Workbench using Picasso mode (800x600 or 1024x768)
How did you enable this ? you activate custom control and set up for <B> for ex ? which version was working for this ?noobberrypi wrote:Hi Chips, I ran this latest build of UAE4ARM and custom joystick controls seem to not be working any more.
Previously I was able to assign a button on the joypad to translate to pushing up on the joypad (which is mostly used for jumping on amiga games)
My Pi isn't with me at the moment, but from memory:noobberrypi wrote:How did you enable this ? you activate custom control and set up for <B> for ex ? which version was working for this ?
And which optimizations was thant?amigapi wrote:I also tested the latest build on my rpi 3.
I've altered the makefile to optimize the built for the rpi3-cpu.
Currently I've just tested sysspeed under Workbench an so I get 7 till 8 times the speed of an A4000. That's pretty good.
I also tested Starstruck. The Video ist a little bit stuttering. But I need to switch to a 50hz Video mode.
Also is it not possible to reset the Emulator using Crl-Amiga-Amiga and the drive leds on Keyboard are not working.
So JIT is pretty much useless unless you have CPU set to Fastest, and when you do use it you get sound drop outs and un-smooth scrolling because the Pi doesn't have enough power. (And 68030 and 68040 don't make any difference).JIT enables the Just-in-time compiler. This may breaks compatibility in some games. You will not notice a big performance
improvement as long as you didn't select "Fastest" in "CPU Speed".
Note: In current version, you will not see a difference in the performance for 68020, 68030 and 68040. The cpu cycles for
the opcodes are based on 68020. The different cycles for 68030 and 68040 will come in a later version.
I just added support for DEL, HELP and parenthesis amiga key. I choose the same mapping as of fsuae (HOME is amiga left parenthesis)...deepx wrote:My DEL and HOME keys are not working.
But when I select the old UAE4ARM they are working. (but it keeps crashing on my so I want to use the latest version)
Chips wrote:I just added support for DEL, HELP and parenthesis amiga key. I choose the same mapping as of fsuae (HOME is amiga left parenthesis)...deepx wrote:My DEL and HOME keys are not working.
But when I select the old UAE4ARM they are working. (but it keeps crashing on my so I want to use the latest version)
So this is because of your 'Fastest CPU' speed fix. It breaks double buffering and also affects all other speed settings and not just 'Fastest' ? I hope this can be fixed because that's a huge frame rate drop. So for instance, if a game can only reach 49 fps and not 50 it automatically drops to 25 fps ?Chips wrote:This is explained by the fact that double buffering is deactivated currently. If rpi is too slow for every frame then you drop directly to 25fps (half of the framerate) instead of being able to retrieve frames from time to time...
Users browsing this forum: No registered users and 9 guests