itch.io

ill check that out im mostly using RTG when testing must've missed something , thnx for reporting! two/three :)  questions tho: 

1. After installing, do you powercycle, or reset with Ctrl-Amiga-Amiga?

2.Next time after this happens i'd like you to run C:agastat in a shell and look at [AGA] diagnostics ready, <date> <time> line 1.116 should write Oct 16 2026 21:41:57 (if it shows anything older thats the cause) 

3.When you go to "Chipset" => init do you have any warnings about the kernel built for other Pi?

No not the goal of this project (its baremetal already) , there is other ppl for that :) 

No problem man !

Yes please use Discord link => it will take you to The Commodore Amiga corner => aga-rgb2rtg-corner channel if you dont have discord you can post here ofc. Thnx!

Yep it is emulation :) Emu68 emulates the CPU AGA does the rest, tho updates are needed atm alot of bugs found and some new features too will be available, stay tuned!

thnx ill look into it, cheers! EDIT:going to test this with Reshoot R by Wepl, version 1.1 from 2019 whdload since game is buggy and crashes my pistorm upon entering, if i fix it it'll be in the next update EDIT: its fixed coming in the 0.76

hmm icon i can do for sure ill see about that.Two things when you update: delete the old Raptor 020ECS file and its .info before copying the new files in. A leftover icon still points at the old file, which is why it behaves oddly. Then drag Raptor_020_OCS to the backdrop with Icons. Stack is now correctly set to 200000. Ill upload shortly (v2 version again + icons)

You are exactly right sir, an reverse-engineered 32-year-old naming bug that we inherited verbatim. Shipped defaults are Fire=57 (Space), FireSp=56 (Alt), ChangeSp=29 (Ctrl), MegaFire=54 (Right Shift) — so after this fix the bomb moves from Ctrl to Right Shift, and Ctrl becomes the cycle key Ill fix this in the afternoon

yeah its a leftover i guess from compiling it should've went like this:

Raptor_020_OCS 68020+. USE THIS ONE if you have an accelerator.

Raptor_000_OCS plain 68000, for Spitfire-class machines. but sadly its performance intensive game and it didn work 

Monitors can act strange when below 50hz keep that in mind :) 

LOL, please report issues there is also "lowlag" option yes and "follow amiga" option also flicker fix that can be of use here

Yes 2 cores actually and abit of bus :) , enjoy!

Well that could be difficult thing to make .. you do have "automatic" and switching it OFF gives you stock chipset and full control over the amiga. Ill think on this but its tricky and it kinda defeats the purpose of this ofc you can disable it when wanting to use framethrower or OCS/ECS. Framethrower btw works just fine with this. Still i wouldn't call this a framethrower it is its own thing. And im quite carefull not mentioning it here.

Then it is solved, thnx for the patience and enjoy!

it could be try without HDMI sound (use Amiga outputs) you can enable all of the settings for Pi3 yes 

DO it!

65 is within the spec, also check if force_turbo=1 is on please 

Can you send me a report? (When you hit F10 => expert "report" its gonna end up in your C: )Does your pi get hot? Ill try to replicate this today. When i test stuff its 10 or more games this is standard concerning the difference in the code sometimes there are regression with some riskier code implementation EDIT: im sorry to report i couldn't reproduce the problem i've tried 15-20 different games and demos so far and none of the problems presented itself :/

Thnx man, I apprecite this. I always read comments and suggestions i've found in yours good ideas. Concerning the pinballs (was testing those too) scrolling yes there we've hit a limit on the bus there is an option i've implemented called "Auto 25 when 50 is too much" might get better results with the scrolling on pinballs (same is on pi4 no difference) some games as you mention work pretty good. Mainly its an improvement and that matters, anyways enjoy and thank you for the kind words! 

You are right there's no image try enabling HDMI too for now, i've done extensive changes to HAM so its a regression ill see about the fix, stay tuned. Thank you for reporting ! EDIT: scratch that from alot of changing i was using PI4's kernel that gave the black image, try reinstalling it (new version out 1.115) and then report back

ill check tomorrow i was testing pi3 specifically today and have not encountered any issues, have you checked your cables does it output normal RGB image from the amiga chipset? (With AGA/HAM OFF)

1) direct RGB 0 lag its the reference actually ... 2) i wouldnt know i dont have it but i assume its close to 0 or around 10 really dont know? on low lag RGB2RTG does 7-9 at the top of the picture 10-14 at the bottom more or less. Turning it off gives you 23-33ms . Emulators tho interestingly give you 40-100ms for sure so you'd feel that 

Cheers!

Sure ill see about improving these , concerning HAM slowness likely stems from the pistorm bus rather then HAM i need to measure it before possible optimization (no promises with HAM tho) , ill make it so too that installer asks for temp_soft_limit but 70 is quite safe and it'll prevent PI3's from throttling down to 1.2ghz (which means less stutter). Hopefully at least PI3's got some performance boost now, cheers! EDIT: done implemented !Also im trying to improve HAM6 situation and i've added a 32 color mode also ... trying to rewrite copper code as we speak since here lies the possible speedup, tried alot of combos since then pi3 only gets hotter :) at least its used if all fails

go to rgb2rtg => settings and try either "follow amiga" or "fixed rate" on "HDMI Sync" (50hz) , please report if that solves the issue 

Ill test HAM6 and report 

the RGB port is Off (by default) this could also happen if you have less than 160kb of chip ram before game starts and you might be using pi4 kernel instead of pi3 (those are now separated) //try running the installer 

From a Shell:

agaboot RGBPORT HAM6 on, HDMI too

agaboot RGBPORT ONLY on, HDMI black

agaboot RGBPORT OFF off

agaboot RGBPORT HAM6 X=-6 Y=-10 on, moved 6 left and 10 up

agaboot RGBPORT 320x256 FIXED25 the standard screen, a steady 25

(384x286 368x280 352x272 320x256,

VARIABLE or FIXED25)

agaboot RGBPORT POSITION the calibration frame

Its already implemented :) (use fill screen + auto) and thanks ofc!

Manually i did it a long time ago but should be straightforward like a cd or zip drive , start here https://aminet.net/package/disk/misc/fat95 .....since then i've gotten used to commodities like caffeine and emu68 imager, hope it helps! Otherwise you can always use the imager or targeted distros for pistorm

did you use emu68 imager? It neatly installs of the needed utils? 

have you tried mounting it ? 

Thnx man appreciated, enjoy!

BIG update for Pi3 users on A1200 try it out now!

Exactly :) But not quite the same on AGA we're emulating whole chipset on RGB2RTG we're interpreting what the real chipset does 

That's a good idea thank you!

Thnx for testing! This is quite detailed yes the pixels look different abit ill see what i can do about this. I already have some fixes ready tho its not related to this. DVI monitors are gonna cause issues yes like everything monitors and their specification vary alot. With time and some more testing this experiment should get better hopefully :)  EDIT: already fixed it will be available in the next version, the vertical axis is unchanged, so in "Fit" mode rows can still be uneven. to fix that it might be a bigger job, stay tuned

Have you tried system wide option? There are some whdload titles that dont trigger AGA since they use a word or two from aga (aka fake aga) then sometimes the algorith just sends them to ECS instead. Ill look into it for sure 

you'll be needing 1.1 beta 1 for this, you could always try intalling it on 1.0.7 it will replace it anyway

There has been some positive feedback yes (but on discord) (make a backup of your card please) 

Thanks! Yes, it adds some latency: RGB2RTG builds each frame completely and then shows it on HDMI locked to the Amiga's 50 Hz, so the picture appears about 25–30 ms (roughly 1.4fps) after the Amiga draws it, plus your TV's/Monitor own processing (input lag). A line-by-line flicker fixer like an Indivision adds less (Its HW). For the eye candy: scanlines (several levels) and smooth scaling are both built in, alongside integer scaling and aspect options.

If i may a suggestion ,you could contact some of the shops in the EU like https://amigastore.eu/ or https://programatory.archi-tech.com.pl/ these are the best/most trusted imho. There might be a competition going on sure (which isnt bad or anything like that => we are all consumers) still your product has something they don't have and that is that it saves you using 2 adapters instead of one not to mention extension cables which are mostly issue for many ppl. My recommendation is you find that discord password (recover it//support) theres alot of ppl with A500's interested//good ppl too. Europe is full of A500's also :)