AMIGA CD32 EMULATION - HOW TO -

[voljega]

@moshington I don't know about the name of bios files in Ratte's emulation, but the right bios md5 should be those

82a21c1890cae844b3df741f2762d48d kick13.rom
dc10d7bdd1b6f450773dfb558477c230 kick20.rom
646773759326fbac3b2311fd8c8793ee kick31.rom

5f8924d013dd57a89cf349f4cdedc6b1 kick31CD32.rom
bb72565701b1b6faece07d68ea5da639 CD32ext.rom
31e5bd652a7b4f2a818cd7d11a43b8bf cd32.nvr

So in your case the one you're looking for is likely the kick31CD32.rom

[Moshington]

@rustymg Thanks for your reply. I tried superfrog which should run definately.
It´s cue and iso file

[Moshington]

@voljega Thanks to you as well. Hmmm...I have used three:

bb72565701b1b6faece07d68ea5da639 - CD32ext.rom
646773759326fbac3b2311fd8c8793ee - kick31.rom
a1b24d6d921995d8e1a492fa88d4ab91 - 391640-03.u6a ( seems to be a mame cd32 whatever

Then i have no 5f8924d013dd57a89cf349f4cdedc6b1 kick31CD32.rom
That should be the problem, right?

Cheers
Moshi

[voljega]

@moshington yep except kick31CD32.rom is the name i used in my own solution, in Ratte's solution I don't know how this bios filr should be named.

[Moshington]

@voljega Allright. I put that missing one into the bios Folder and did the 755-thing to it.
Unfortunately the games did not work ( Superfrog and Speedball2 )
Black Screen and back to menue after some seconds.

The Cue files refer to the correct Iso-files.
Well..now I really don´t know why.

Does anyone has an idea?

Cheers
Moshi

[voljega]

@moshington To find why it crashes the best thing is to launch manually in putty the command line found in es_systems.cfg and modifying target variables like %ROM% by the real name (in %ROM% case the full path and filenale to the cue file).

The log in the terminal may then help you debug what's going wrong

[Pol]

Hi folks. A little question: does anybody know how to enable integer scaling? is it even possible? The thing is, when you are using CRT tv through composite, the resolution of the PAL modes available is 720x576. Horizontal res (720) is not important, but vertical res (576) is, if you want no scaling artifacts. In UAE4arm menu (F12) you can manually change the resolution BUT there's no possibility of an integer that fits 576 horizontal scanlines (by half should be 288, and the emulator options are 200, 216, 256, 270, correct me if I'm wrong). The normal behaviour of the emulator is stretching the image vertically which leads into scaling artifacts like added blur and uneven doubling of pixels. This is somehow hidden if you use the interlaced mode but it comes into sight with progressive (interlaced hurts your eyes!). Ok hope someone knows about this. Best regards to all.

[voljega]

@pol I'm not sure pixel perfect doesn't seem possible so easily but i know @ironic uses amiga emulation on CRT so mayve he knows ?

[ironic]

Hi.
It's better to use RGB instead of Composite for Amiga but :
If you want to be in integer scale, you must force the resolution in "GameConfigFile".uae

From uae4arm menu you can only up to 270 but in the configfile, you can set :
gfx_width=720
gfx_height=288
gfx_width_windowed=720
gfx_height_windowed=288
gfx_width_fullscreen=720
gfx_height_fullscreen=288

I use a resolution (non interlaced RGB) of 1920x282 and the result is ... perfect
See this video :
Amiga 500 vs Uae4arm Rpi3 CRT
No tearing, no lag, i'm an Amiga coder an i know what is a perfect 50fps scroll

[Pol]

@voljega @ironic You rock so hard!!! ironic, I understand RGB would be better as one can set a nice amount of custom resolutions, timings, etc... I've been following your discussions about that matter, and the people that's been involved in composite and rgb optimization for the rpi. I can't give enough thanks to you people (popcornmix=hero!!!).
There are no SCART tvs where I live so no "pi2scart" for me, only composite and component. I really don't like the idea of hooking 2 or 3 different adapters together, I just like the rpi to be simple, like an old console, so its only composite for me (until maybe I get the money to import a "Retrotink"... but that wold be very expensive, we pay several times the real prices here, plus there is very few people that sell this kind of things). Anyway I'm super thankful

[arkive]

@ironic Any chance for a hint how to run Amiga or C64 on a CRT via Pi2Scart?
With Amiga, the emulator UI is blown up in some super high resolution and I can't do anything.

With c64, it's better, but I struggle to hit 1:1 pixels. The best result I get is 1:1 but with borders on top/bottom in horizontal, and going slightly over left/right in vertical.

Not sure if it's controlled by hdmi_ settings or maybe somewhere in the emu?

[ironic]

Hi @arkive
For C64, you can use VICE emulator but as you said, it will be hard to reach pixel perfect on CRT thru GPIO (like rgp-pi, Pi2Scart). VICE screen option isn't complient with CRT resolution.
I use VICE and it works nicely but it must be setup a lot to have a true fullscreen, no tearing result.
You can try ADVMESS C64 too, but a lot of games doesn't work.

For Amiga and uae4arm, in low resolution you can't use the UI.
For PI2Scart hi resolution ... i haven't one so, i don't know.
I edit each .uae config file with a text editor, it's better went you understand this config file.

[arkive]

@ironic said in AMIGA CD32 EMULATION - HOW TO -:

I use VICE and it works nicely but it must be setup a lot to have a true fullscreen, no tearing result.

Thanks for replying. How do you do that ^^? Also through GPIO solution?

I had a feeling that maybe resolution from Vice is 384x271 (overscan) since it goes outside the screen, despite my hdmi timings being set to 320x240
Could you advise how would I calculate hdmi timings for this (384) resolution? I saw your python script somewhere but not quite sure how to use it.

[ironic]

I use RGB thru GPIO only.
For Commodore Amiga 500/1200/CD32 50Hz i use :
1920 282 49.920410 -10 6 11 48 192 240 5 15625 (for generating hdmitimings with my script)
With configfile (.UAE) :
gfx_width=704
gfx_height=282
gfx_width_windowed=704
gfx_height_windowed=282
gfx_width_fullscreen=704
gfx_height_fullscreen=282
(Only 2 lines are needed but can't remember wich)

For Commodore 64 50Hz(Vice - Combian 64 edition) i use :
hdmi_timings 336 1 10 18 46 288 1 5 6 6 0 0 0 50 0 6400000 1
(so, 336x288)

My hdmi timings generator only works with RGB/GPIO.

[voljega]

Yes only the first two gfx lines are needed

[arkive]

@ironic said in AMIGA CD32 EMULATION - HOW TO -:

For Commodore 64 50Hz(Vice - Combian 64 edition) i use :
hdmi_timings 336 1 10 18 46 288 1 5 6 6 0 0 0 50 0 6400000 1
(so, 336x288)

D**n...I was hoping it would work, but still no luck. Thanks though!
May I ask what settings in Video in Vice do you use? I mean: Size Settings/ Fullscreen Mode/Custom Res/Res limit mode/Open GL
Also, the Border: Full, Normal or None?

My hdmi timings generator only works with RGB/GPIO.

I use pi2scart, do you think it may require different settings from your setup? Also, I use Retropie...maybe the difference is in that Vice Combian 64 edition? I'm downloading it now, will try later.

[ironic]

Thanks @voljega

@arkive
Sorry, it's an Amiga thread.

Have a look to this C64 screens grabbed from my CRT
Scanlines perfect (1920x288), 50fps perfect sync.

Open a Commodore 64 thread if you want more informations...

[Jesús BL]

Does AmigaCD32 addon run in new recalbox 4.1 stable?

I ran this in beta but I can't in new stable version.

[Dragu]

cOOL !
I also just install CD32 Emulation.
Is there a chance that this is part as one of the next Recalbox release ?

[voljega]

@dragu yes it should be sooner or later, but amiberry has a better support of a500/a1200 than cd32 for now