PUAE 2.3.1 beta series

[Silver]

Originally Posted by hoberion

Hi, I seem to have an issue with the latest version of PUAE (compiled git @ 20110122) with the audio in project x when I play (music is fine), other games are fine...

Prob best to describe what the issue is, plus your setup: uname, compile options, config.log, uaerc... Etc...

issue is: sound is "flickering"
uname -a: Linux arcade 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 01:41:57 UTC 2010 i686 GNU/Linux
p4 2.4 Ghz 1.5 Gb mem

config.log http://pastebin.com/6Qm0AZp8
compilation:
./build_linux_nojit.sh
./configure --with-sdl-sound

game: projectx se

as soon as I start the game ("destroy waves for powerup" ) and sometimes during the music the sound is stuttering

[Gaula92]

I'm getting the yellowish colors error on 64bit Linux with github sources as of today. Wasn't it already fixed?

commodore ~ # uname -a
Linux commodore 2.6.36-ck-r5 #11 SMP PREEMPT Mon Jan 24 21:40:18 GMT 2011 x86_64 Intel(R) Core(TM)2 Duo CPU P7350 @ 2.00GHz GenuineIntel GNU/Linux

config_description=UAE default configuration
config_hardware=false
config_host=false
config_version=0.8.29
x86.use_tsc=yes
sdl.map_raw_keys=false
sdl.use_gl=true
use_gui=no
use_debugger=false
kickstart_rom_file=/root/amiga/kick31.rom
kickstart_ext_rom_file=
flash_file=
cart_file=
kickshifter=false
hardfile2=rw,DH0:/root/amiga/lemmingscd.hdf,32,1,2,512,0,
#filesystem2=rw,DH1:Stuff:/root/amiga/localhd2,-10
#hardfile=rw,32,1,2,512,/root/amiga/sys2.hdf
#floppy0=/root/amiga/lemm1.adf
floppy0type=0
#floppy1=/root/amiga/lemm22.adf
floppy1type=0
floppy2=
floppy2type=-1
floppy3=
floppy3type=-1
nr_floppies=2
floppy_speed=800
parallel_on_demand=false
serial_on_demand=false
serial_hardware_ctsrts=true
serial_direct=false
scsi=false
sound_output=exact
sound_channels=stereo
sound_stereo_separation=7
sound_stereo_mixing_delay=0
sound_frequency=48000
sound_interpol=none
sound_volume=0
sound_latency=32
joyport0=mouse
joyport1=joy0
bsdsocket_emu=false
synchronize_clock=no
maprom=0x0
gfx_framerate=0
gfx_width=640
gfx_height=480
gfx_width_windowed=640
gfx_height_windowed=480
gfx_width_fullscreen=640
gfx_height_fullscreen=480
gfx_refreshrate=0
gfx_vsync=true
gfx_lores=false
gfx_linemode=double
gfx_fullscreen_amiga=true
gfx_fullscreen_picasso=true
gfx_center_horizontal=smart
gfx_center_vertical=smart
gfx_colour_mode=32bit
immediate_blits=false
ntsc=true
show_leds=false
chipset=ocs
collision_level=playfields
fastmem_size=4
a3000mem_size=0
z3mem_size=0
cachesize=0
bogomem_size=0
gfxcard_size=0
chipmem_size=4
#cpu_speed=max
cpu_speed=original
cpu_type=68000
cpu_compatible=false
cpu_cycle_exact=false
blitter_cycle_exact=false
log_illegal_mem=false
kbd_lang=es
state_replay=no
state_replay_rate=250
state_replay_buffer=20971520
input.config=0

I compiled with:

./bootstrap.sh
./configure --with-sdl --with-sdl-gl --with-sdl-gfx --without-sdl-sound --with-alsa --disable-jit --disable-gayle
make clean
make

regards

[Silver]

@Gnostic

Observing huge number of Alsa sound errors whenever sound is in use on the Pandora build. It appears to have a performance impact. switching sound on/off or from emulated to emulated 100% on the fly provides a second or two of non-stuttery sound. Altering latency and buffer in .uaerc does not help.

Errors produced continually is:

ALSA lib pcm.c:7234:(snd_pcm_recover) underrun occured

[goldenegg]

I'm unable to get the keyboard to map to joystick keys with PUAE 2.3.1. I'm running on a early-2008 Macbook Pro. Here's my configuration file.

cpu_type=68000
chipset=ecs
collision_level=playfields
chipmem_size=2
bogomem_size=0
fastmem_size=2
gfxcard_size=0
z3mem_size=0
kickstart_rom_file=/Applications/Emulators/PUAE/kick13.rom
sdl.use_gl=true
floppy0sound=-1
show_leds=true

I ran a test earlier today .....

I loaded PUAE with the bare config and put the disks for T-Racer in the drive. My config was set to only 512k of chip RAM at the time, so the game wouldn't load and crashed to AmigaDOS. While in AmigaDOS, I set JOY1 to use WASD for the control. As I understand it, with that configuration, those keys should not respond as regular keyboard input. In AmigaDOS, it accepted W, A, S and D as regular typing input.

What this tells me is, for some reason, PUAE isn't mapping those controls to joystick input. That would explain why games don't see the commands. Any idea what would cause this? The mouse input works fine.

Doing the same in PUAE 2.1 and E-UAE works as it's supposed to.

For the record, I'm using a PUAE 2.3.1 build from Jan 6, 2011 from the following site:

http://www.ultimateamiga.co.uk/index.php/page,13.html

I tried to compile the latest for GIT, but the compile always fails (see attached build log).

As an aside, is there any reason the cursor joystick mapping uses right ALT/CTRL? I think it would be better, especially on laptops, to use the left ALT/CTRL for that mapping. Just my $0.02.

[Silver]

Anyone have any success cross-compiling PUAE? Might be a bit off-topic for this thread, but I'm trying to compile for ARM. (Works fine compiling native).

Compiling on Ubuntu 10.04 x86. toolchain works for other programs. uname:

silver@ubuntu:~/pandora-dev/PUAE$ uname -a
Linux ubuntu 2.6.32-28-generic #55-Ubuntu SMP Mon Jan 10 21:21:01 UTC 2011 i686 GNU/Linux

Error is:

fsusage.c:203:2: warning: function declaration isn't a prototype
fsusage.c: In function 'get_fs_usage':
fsusage.c:373:2: warning: implicit declaration of function 'CONVERT_BLOCKS'
fsusage.c:373:36: error: 'fsd' undeclared (first use in this function)
fsusage.c:373:36: note: each undeclared identifier is reported only once for each function it appears in

Which suggests in fsusage.c it's going down this road:

#if !defined(STAT_STATFS2_FS_DATA) && !defined(STAT_READ_FILSYS)
	/* !Ultrix && !SVR2 */

config.log tests report

configure:8543: result: no
configure:8555: checking for 3-argument statfs function (DEC OSF/1)
configure:8587: result: no
configure:8599: checking for two-argument statfs with statfs.bsize member (AIX, 4.3BSD)
configure:8637: result: no
configure:8649: checking for four-argument statfs (AIX-3.2.5, SVR3)
configure:8678: result: no
configure:8690: checking for two-argument statfs with statfs.fsize member (4.4BSD and NetBSD)
configure:8725: result: no
configure:8737: checking for two-argument statfs with struct fs_data (Ultrix)
configure:8776: result: no
configure:8793: /home/silver/pandora-dev/arm-2010.09/bin/arm-none-linux-gnueabi-gcc -E -DPANDORA 
-Os -pipe -march=armv7-a -mcpu=cortex-a8 -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -ftree-ve
ctorize -ffast-math -fsingle-precision-constant conftest.c
conftest.c:85:24: fatal error: sys/filsys.h: No such file or directory

I'll attach the full config.log:


EDIT: For the record, I've now successfully cross-compiled for ARM. Had to hack up the sysconfig.h file to match various settings autodetected on the host system. There may be a better way or bugs introduced by doing this, but it runs anyway. Going to start exploring some PGO - doesnt run fast enough on the Pandora (yet).

[goldenegg]

I'm now able to build PUAE for Mac. I grabbed the latest from GIT and the joystick to keyboard mappings still don't work.

GnoStiC,

If there's anything I can provide you to help debug this issue, please let me know. As mentioned before, the mappings work perfectly in 2.1.

[Wicked_Digger]

Is Picasso work fine in last version?
I'm use patched sources, but whant to revert if it possible.

[Kaffeine]

Originally Posted by goldenegg

I'm now able to build PUAE for Mac. I grabbed the latest from GIT and the joystick to keyboard mappings still don't work.

GnoStiC,

If there's anything I can provide you to help debug this issue, please let me know. As mentioned before, the mappings work perfectly in 2.1.

I think we need to be patient The problem is known and has been reported several times the past few months.

[GnoStiC]

sorry that i wasn't available to reply your reports.

please try my latest push, it should fix *most* of your issues.. (eg. not x64 color issue, i was too busy/lazy to setup a x64 machine)

[Gaula92]

GnoStiC: Do you mean the x64 version won't be fixed?
Isn't there anyone with an x64 machine who uses PUAE?

[goldenegg]

Originally Posted by GnoStiC

sorry that i wasn't available to reply your reports.

please try my latest push, it should fix *most* of your issues.. (eg. not x64 color issue, i was too busy/lazy to setup a x64 machine)

Awesome! Thanks for the update! I just tried it and can confirm the joystick keyboard mappings are working great now!

[goldenegg]

After finally getting all the dependencies in place, I'm having problems compiling PUAE 2.3.1 on Pandora. I'm compiling on the device itself, so no cross-compiling issues here.

the problem is that it's trying to look for source files in a 'dep' subdirectory that doesn't exist. Any ideas what could be going on?

[GnoStiC]

oh, i'll fix it, as soon as i setup a x64 ubuntu.

Originally Posted by gaula88@hotmail

GnoStiC: Do you mean the x64 version won't be fixed?
Isn't there anyone with an x64 machine who uses PUAE?

[GnoStiC]

dep folders are linked on the fly when you configure
if you use sdl gfx (that's gfx-sdl folder), it'll be linked as gfxdep folder.

as i recall silver compiled puae for pandora already, he may help you with it.

Originally Posted by goldenegg

After finally getting all the dependencies in place, I'm having problems compiling PUAE 2.3.1 on Pandora. I'm compiling on the device itself, so no cross-compiling issues here.

the problem is that it's trying to look for source files in a 'dep' subdirectory that doesn't exist. Any ideas what could be going on?

[kamelito]

with the january build : http://www.ultimateamiga.co.uk/index.php/page,13.html
I always got a guru (8000 0004 or 8000 0002) during boot except if cpu is 68000, removing jit, cycle exact, compatible and many memory options doesn't solve the problem.
kick 3.1
OS X snow leopard with latest update. (macbook unibody)

config_image=
config_description=
config_info=
unix.rom_path=/Users/kml/Documents/Configurations/
unix.floppy_path=
unix.hardfile_path=/Users/kml/Documents/Configurations/
kickstart_rom_file=/Users/kml/Documents/Configurations/kick.rom
kickstart_key_file=
kickstart_ext_rom_file=
cart_file=
kickshifter=false
chipmem_size=4
fastmem_size=0
bogomem_size=6
z3mem_size=0
gfxcard_size=0
log_illegal_mem=true
cpu_type=68000
cpu_24bit_addressing=false
cpu_compatible=true
cpu_cycle_exact=true
cpu_speed=max
cachesize=8192
comp_nf=false
compforcesettings=false
comp_trustbyte=indirect
comp_trustword=indirect
comp_trustlong=indirect
chipset=ecs_agnus
ntsc=false
immediate_blits=false
x86.use_tsc=true
collision_level=full
gfx_width=1024
gfx_height=768
gfx_width_fullscreen=1024
gfx_height_fullscreen=768
gfx_width_windowed=640
gfx_height_windowed=512
gfx_linemode=double
gfx_center_horizontal=smart
gfx_center_vertical=smart
gfx_fullscreen_amiga=false
gfx_fullscreen_picasso=false
gfx_lores=false
show_leds=true
gfx_correct_aspect=true
sdl.use_gl=true
gfx_vsync=true
gfx_framerate=1
sound_output=normal
sound_channels=stereo
sound_interpol=none
sound_bits=16
sound_frequency=44100
sound_latency=100
sound_max_buff=17600
floppy0type=0
floppy1type=-1
floppy2type=-1
floppy3type=-1
floppy0=
floppy1=
floppy2=
floppy3=
floppy_speed=100
hardfile2=rw,DH0:/Users/kml/Documents/Configurations/ASM Programming.hdf,32,1,2,512,-10,
kbd_lang=fr
joyport0=mouse
joyport1=kbd1
input.config=0
input.1.keyboard.0.button.17=JOY1_UP
input.1.keyboard.0.button.11=JOY1_DOWN
input.1.keyboard.0.button.3=JOY1_LEFT
input.1.keyboard.0.button.4=JOY1_RIGHT
input.1.keyboard.0.button.58=JOY1_FIRE_BUTTON
input.1.keyboard.0.button.126=JOY2_UP
input.1.keyboard.0.button.125=JOY2_DOWN
input.1.keyboard.0.button.123=JOY2_LEFT
input.1.keyboard.0.button.124=JOY2_RIGHT
input.1.keyboard.0.button.62=JOY2_FIRE_BUTTON
input.2.keyboard.0.button.17=JOY1_UP
input.2.keyboard.0.button.11=JOY1_DOWN
input.2.keyboard.0.button.3=JOY1_LEFT
input.2.keyboard.0.button.4=JOY1_RIGHT
input.2.keyboard.0.button.58=JOY1_FIRE_BUTTON
input.2.keyboard.0.button.126=JOY2_UP
input.2.keyboard.0.button.125=JOY2_DOWN
input.2.keyboard.0.button.123=JOY2_LEFT
input.2.keyboard.0.button.124=JOY2_RIGHT
input.2.keyboard.0.button.62=JOY2_FIRE_BUTTON
input.3.keyboard.0.button.17=JOY1_UP
input.3.keyboard.0.button.11=JOY1_DOWN
input.3.keyboard.0.button.3=JOY1_LEFT
input.3.keyboard.0.button.4=JOY1_RIGHT
input.3.keyboard.0.button.58=JOY1_FIRE_BUTTON
input.3.keyboard.0.button.126=JOY2_UP
input.3.keyboard.0.button.125=JOY2_DOWN
input.3.keyboard.0.button.123=JOY2_LEFT
input.3.keyboard.0.button.124=JOY2_RIGHT
input.3.keyboard.0.button.62=JOY2_FIRE_BUTTON
input.4.keyboard.0.button.17=JOY1_UP
input.4.keyboard.0.button.11=JOY1_DOWN
input.4.keyboard.0.button.3=JOY1_LEFT
input.4.keyboard.0.button.4=JOY1_RIGHT
input.4.keyboard.0.button.58=JOY1_FIRE_BUTTON
input.4.keyboard.0.button.126=JOY2_UP
input.4.keyboard.0.button.125=JOY2_DOWN
input.4.keyboard.0.button.123=JOY2_LEFT
input.4.keyboard.0.button.124=JOY2_RIGHT
input.4.keyboard.0.button.62=JOY2_FIRE_BUTTON
sdl.map_raw_keys=false
scsi=false
scsi_device=
bsdsocket_emu=false
serial_on_demand=false
parallel_on_demand=false


Kamel

[chiark]

Kamel, get rid of all of that config and strip it down to base... I suspect that the window size may be causing troubles amongst other things, but am not sure.

[kamelito]

I hope one day we'll reach WinUAE

[kamelito]

putting size of jit to 0 solve the pb.
Now I've some keys that do nothing, I'll see that later.

Kamel

[stainy]

Started following this thread as I noticed someone was compiling PUAE for ther Pandora.
Hopefully should get mine in March.
So.. do we have two guys trying to get this working for the Pandy ? and wondering if they could chime in with the status

Thanks guys