PUAE 2.3.0 beta series

[GnoStiC]

http://github.com/GnoStiC/PUAE

we're almost sync but there is still some stuff left to fix..
thanx to steven saunders for macosx fixes..

[xaind]

Mac build in the zone.

[GnoStiC]

just pushed beta 14 fixes

[chiark]

You're both superstars!

Is there any coordinated effort on the UI front?

Also, when I have tried the 68040 emulation with KS3.1, the emulation just seems to hang (OSX)... I realise that's a useless bug report but I am unsure what bug reporting mechanisms we've got!

[GnoStiC]

68040 + KS 3.1 works fine for me (ubuntu)
maybe xaind can help with osx?

cpu_type=68040
chipset=aga
collision_level=playfields
chipmem_size=4
bogomem_size=0
fastmem_size=4
gfxcard_size=4
z3mem_size=16
kickstart_rom_file=/home/gnostic/amiga/KickRoms/KICK-3.1(40.10).ROM
hardfile2=rw,DH0:/home/gnostic/amiga/System.hdf,32,1,2,512,-10,
filesystem2=rw,DH1:Stuff:/home/gnostic/amiga/harddisk,-10
sdl.use_gl=true
floppy0sound=-1
show_leds=true

[xaind]

Originally Posted by GnoStiC

just pushed beta 14 fixes

Mac build in the zone.

[xaind]

Originally Posted by chiark

Also, when I have tried the 68040 emulation with KS3.1, the emulation just seems to hang (OSX)... I realise that's a useless bug report but I am unsure what bug reporting mechanisms we've got!

Seems to work for me with the latest (Sept 1) build.

Try looking at the log file:

~/Library/Logs/PUAE.log

to see if there is useful info there. Also if the program crashes there should be something in ~/Library/Logs/CrashReporter

[nexusle]

Cool! Must try this at afternoon. I had the same problems with ks3.1 (also with all kickstarts above 1.3).

@xaind: Is the Picasso Bug fixed??

[nexusle]

I've also a bug (tested with Mac OS X) with the keyboard if I have joystick mapping to keyboard. In this case, I can't use my keyboard in the original way... (also with Kicks above 1.3 and with the build from last week (or so))

[chiark]

Thanks - could you post your config file for the 4000? I'm starting from Hi-Toro and suspect that the config might be the issue...

[nexusle]

Hi GnoStiC, Hi xaind

have tested latest PUAE build for OS X and get these errors:

- BSD Socket emu: Crash after Amiga Reset and at quit PUAE
- Amiga doesn't boot if JIT is enabled and CPU is set to 68040
- SCSI doesn't work
- keyboard problem if keyboard is set for joystick
- Picasso96 doesn't work

[GnoStiC]

great, error reports means someone is using

please send your .uaerc or your configuration settings and the steps to reproduce the mentioned errors occur. (except for keyboard problem, i know about that)

Originally Posted by nexusle

Hi GnoStiC, Hi xaind

have tested latest PUAE build for OS X and get these errors:

- BSD Socket emu: Crash after Amiga Reset and at quit PUAE
- Amiga doesn't boot if JIT is enabled and CPU is set to 68040
- SCSI doesn't work
- keyboard problem if keyboard is set for joystick
- Picasso96 doesn't work

[frostwork]

hi!
Thank you very much for your hard work on puae!
I'm currently writing a small program "whdrunner" (will be gpl3 and should be very portable), which lets you choose some zipped whdload game (kg rules as cmdline argument and does all the required voodoo, to directly launch this game.
(similar to headkaze's windows-only winuaeloader, just less features ).
I's in early stages, but already works quiet fine with the ancient e-uae on my gentoo.
unfortunately p-uae freezes atm, I guess this is related to the utf-8 bug, right?
does this bug have a high priority on your todo list?

[xaind]

Originally Posted by GnoStiC

great, error reports means someone is using

please send your .uaerc or your configuration settings and the steps to reproduce the mentioned errors occur. (except for keyboard problem, i know about that)

I can post this info for the Picasso96 problem.

I am using this configuration:

sdl.use_gl=true
floppy0sound=-1
cpu_type=68020
cpu_speed=max
chipset=aga
collision_level=playfields
chipmem_size=4
bogomem_size=0
fastmem_size=0
gfxcard_size=4
z3mem_size=16
kickstart_rom_file=kick31.rom
hardfile2=rw,DH0:ClassicWB_P96/System.hdf,32,1,2,512,-10,

The HDF I am using is Classic Workbench P96. When I run this configuration with E-UAE it goes into an 800x600x32 screenmode with no problem.

When I run it in PUAE, I see the message in the attached screenshot, and it stays in a low resolution mode.

Can anyone confirm if this happens with PUAE in Linux?

[wilshy]

Cracking work on this. Keep it up!

I've not been keeping up with the development but just got this working (Mac build from The Zone) and seems solid. My question is in terms of gaming performance, the only reason I really use an Amiga these days, it seems to lag behind E-UAE.

Just tried Bubble & Squeak. That had a load of slowdown once things got busy on screen. ATR had no slowdown but was noticeably more jerky than running it on E-UAE. WinUAE via Bootcamp runs better than that.

Any thoughts on what's happening here?

[chiark]

Try going fullscreen - my macbook pro runs like a dog in windowed mode, dunno why...

Hello,
I am just passing by to say that I highly appreciate the fact that there's an active UAE variant that can run on non-Windows systems.
Especially since the last version of E-UAE was severely broken (at least on my MacBook Pro, it freezes very often and that makes it unusable).
Seeing that you're merging changes from WinUAE also sounds great.

So huge thanks to GnoStiC for doing this project and thanks to xaind for the Mac builds.
Keep up the good work!

PS :
I haven't tried it yet, but the project alone deserves congratulations
By the way I had to spend some time searching before I found this thread and how to access the Zone, I think you deserve more exposure.
Anyway, I might come back with more useful feedback later.

[ascp]

How utterly cool. I've been looking for a good Amiga emu on my Ubuntu.Gotta try it out.

Just a quick feedback after giving it a try :

- There seems to be a mix-up about resolutions : when I change the full screen resolution, it affects the size of the window in windowed mode.
The config file (generated with Hi-Toro 0.5.2) seemed to have correct data.

gfx_width=640
gfx_height=480
gfx_width_fullscreen=640
gfx_height_fullscreen=480
gfx_width_windowed=1024
gfx_height_windowed=768

With these settings, it opened a 640x480 window in windowed mode (or something visually very close) although that's the settings for fullscreen.
Or maybe only gfx_width and gfx_height are used now for both fullscreen and windowed modes?
If you can keep two separate settings, I'd be grateful.

- Sometimes the display can act strangely: the bottom part of the screen is not displayed.
It seems that setting the line mode parameter to normal (gfx_linemode=normal) is broken as (I think) I haven't noticed this in double and scanline modes.
It also seems to depend on the Amiga screenmode as I think I didn't have the problem in DBLPAL on my Workbench while it was present in all the other modes I tested (I haven't tested a lot since it's quite painful to click on the "Use" button when you don't see it ). Although I would have to test that again to be sure.
I played a bit with other parameters (OpenGL usage, aspect ratio, etc) but it didn't seem to affect the results.
I also started from a fresh config file in case my old one was broken but the problem persisted.

- When switching between fullscreen and window mode, sometimes colors become wrong: for instance, the blue component was missing on the whole screen when I tried that on my Workbench making it all yellowish.
It's funny because my old Amiga monitor used to do that and my first thought was "Oh no, my monitor is acting silly again"

- OpenGL display seems broken and will stretch or move the display partially out of the window/screen (and can make LEDs not visible).
It's more noticeable when you set the render resolution to a quite high value (e.g. above 1024x768).

I can provide a more complete bug report if you need it.
I'm just quickly writing to see if you're already aware of these problems before I investigate more.

Otherwise, the frequent freezes I had with E-UAE seem to have been fixed which is great.

Tests done with the Mac OS X build provided by xaind in the Zone ("Mac OS X build of GnoStiC's PUAE 2.3.0 from commit 10d242f (September 1, 2010)").
Config files were generated with Hi-Toro 0.5.2.


EDIT: Investigated a bit more and corrected wrong assumptions.

[GnoStiC]

new version pushed to git.
it includes mostly P96 fixes (it's a quick and dirty hack) but picasso seems to works fine now