Do you know RTG autodocs or tutorials?

[doble07]

Hi all!

I am searching information on how to code for RTG (graphics cards, using "rtg.library") in C/C++ or ASM.

Anyone have got information about it?

Thanks

Juan

[thomas]

rtg.library is an internal part of Picasso96. The docs are not available for the public.

This means that you cannot write your own graphics cards drivers. If you rather want to use RTG functions in your program, the library to use is Picasso96API.library. The docs are available here.

The better choice for RTG programs is Cybergraphics because these programs can run on both, CGX and P96. Programs written for P96 can only run on machines where P96 is installed.

CGX docs are available here.

[doble07]

Thanks for the info Thomas!

[Warty]

Resurrecting this thread a bit...

I'm working on an app that I want to work on OCS/ECS/AGA 68020/68030/68040 (and ideally 68000 if I can squeeze the performance out), but also on Amigas with RTG cards.

Historical article:
http://www.lysator.liu.se/amiga/al/guide/al104/gfx.HTML

Cleaned up version of the CyberGraphics API Thomas mentions above (attached)

If you were developing with a target of 68K, for AmigaOS 3.2 and above, would you still aim for the cybergraphics library? Or would you look more at the P96 API? With Individual Computers acquiring the rights to the p96 code, and actually making updates, maybe that's a better bet?

Link to dev info from P96: http://wiki.icomp.de/w/images/e/e9/Develop.lha

I've just looked over the cybergraphics API, and just downloaded the P96 API. At first glance, they look similar in overall concept, but of course different calls.

Edit: another post from EAB with more information:
http://eab.abime.net/showthread.php?t=81379

[thomas]

If your main target is native graphics and it should only run on gfx cards, too, then you should stay away from RTG. Concentrate on graphics.library functions and just follow some easy rules.

Use OpenScreen to get your drawing area.
Use AllocBitMap to get some off-screen bitmaps.
Do not poke into bitmaps but only use graphics.library blit and draw functions.
Use datatypes to load graphics.

Leave it to the RTG drivers to adapt those calls to gfx cards.

[nogginthenog]

In my opinion the Cybergraphics API is still the defacto standard. There are probably cards that P96 does not support so what Thomas wrote in 2009 still stands.

[Thomas Richter]

During 3.1.4 development, we nagged Frank multiple times to update it, but this was a dead end... I wouldn't really bother with it anymore. I am neither aware that there are any cards left P96 does not support anymore, the gap is closed.

Concerning the API: In almost all cases, you are good with the graphics.library. If you need direct access to true color or high-color functions, I would now go with the Picasso96API.library. This will be updated if needed and there is still support for it.

[nogginthenog]

Good point ThoR. I moved from CGFX to P96 simply because P96 is still developed.

[kamelito]

@Thor
Is there plan to merge Picasso96 into graphics.library like what have been done in AmigaOS 4?

[Thomas Richter]

Originally Posted by kamelito

@Thor
Is there plan to merge Picasso96 into graphics.library like what have been done in AmigaOS 4?

The Os and P96 are in different hands. P96 is owned by iComp, the Os is owned by whatdoIknow... thus, I doubt anything will happen as long as this situation continues. There might be some extensions in Os interfaces to ease the integration of P96.

[Warty]

Thanks everyone for info. I'm targeting P96 then for RTG support. I have some specific questions about that, but I'll do them in a separate post.