0 Members and 1 Guest are viewing this topic.
Cosmo's graphics.library lacks a utility to allocate some "graphics memory" in fast memory on a case by case basis. It can't be done by default because of compatibility reasons but such a utility should be simpler than with FBlit (maybe even FBlit code could be borrowed for such a utility now that it is open source). Cosmo's implementation may not be the best but replacing the graphics.library with blitter free and RTG capable functions is the right idea. Development of a better graphics.library may depend on which way Amiga FPGA hardware goes. The blitter and graphics memory can be much faster on FPGA hardware making the original blitter using code usable again. Graphics memory can be as fast as fast memory so no utility to allocate graphics memory in fast memory should be necessary. A best performance FPGA Amiga may replace the blitter with a SIMD unit in the CPU though.Interesting. I don't see how it can be slower than the original graphics.library. Does it slow down the system compared to the original graphic.library (using the blitter) or compared to a FBlit enhanced system? Have you reported the problems? Have you tried a recent version of graphics.library?I do not use Cosmo's graphics.library and am not suggesting that anyone should but people should be aware of available options. I use a P96 setup where much of the graphics.library code is replaced also (and the gfx hardware is often several times faster than AGA). I do use (a tweaked version for test purposes) ThoR's layers.library which is semi-official, mostly bug free and provides a big speedup for layer (window) operations. However, it doesn't replace the bottlenecks in graphics.library.
