Thanks for your help

Yes exactly.tomaitheous wrote: But, if i understand you correctly.. you want to write "overlays" that are in pure ASM, no?.
And you know the problem with huc, some glishes appaers on a real PCE.tomaitheous wrote: If so, then why not still use HuC - but as a container for your ASM. So it's all #ASM code inside a C source file. Compile that to an overlay. Otherwise, I guess contact Chris Covell to see if he solved that problem. Or just write your own libs and ignore mkits libs
I'am not good enought for that ,but i'll try to make ittomaitheous wrote: Or just write your own libs and ignore mkits libs
Well, if you write it in all #ASM, it would be the same as if you didn't use HuC. But, as a side effect - you have wasted space of the HuC library just sitting there... in ram. And, I guess it would be no different than just using PCEAS without mkit libs. So I guess the point is mootAnd you know the problem with huc, some glishes appaers on a real PCE.
I have tried a single screen wiht a copper effect (very simple), and the problem has also appered .
Yes for the moment is just for à 512 colors pics ..tomaitheous wrote: What exactly do you need pure asm for? Just small parts? Just to display pics?
Yes that's cool, or some explanations for writing my own ..tomaitheous wrote: If it's the second approach, maybe Charles, Mooz, and I can help write a custom lib for you. Or just borrow one of our generic ones. But, we'd need a lot of details to get specific stuff for you.
For the moment, only a real RGB->PCE palette converter, and i'am working on a graphic converter, like fragmare's one.tomaitheous wrote: And lastly, are you writing your own PC utilities for PCE? Like map converters, picture converters, sound converters, etc. If so, that helps a lot for all ASM projects.