- Welcome to CPCWiki forum.
The ultimate Amstrad CPC community!
News:
Printed Amstrad Addict magazine announced, check it out here!
Recent posts
#1
Quote from: PulkoMandy on Today at 13:05For the connector, I was thinking of using flexible PCB, something like this: https://oliver.st/blog/flexible-pcb-connections/I see no good reason to take that route. The solution with rigid 0.4 mm adapter PCBs and a bunch of wires is much cheaper and at the same time hard to break and easy to fix.
Not sure if there is a place where these can be ordered at a reasonable price (maybe with a large order, it's possible).
You could also try to find an off-the-shelf Flat-Flex cable. They are usually metric, but a 20 conductor cable with 1.25 mm pitch might fit just well enough.
Ultimately, I am going to use flat cable and normal IDC connectors for my own system board, which is why the keyboard has the pin header for an IDC cable.
#2
K
General Discussion - Introductions / Presentation and M4 board ques...
Last post by Kaboom3d - Today at 17:57I would like to introduce myself, I am an 8-bit enthusiast and the Amstrad CPC in particular. I am from Barcelona, Spain and I would like to know how to buy an M4 board for my cpc. I know that a user of this website made them, Duke I think, to whom I sent a private message a few days ago, but he has not answered me yet. Can somebody help me? thanks and regards!
#3
Thanks for the video, but that capture isn't amazing TBH.
The game doesn't play like that thankfully
The game doesn't play like that thankfully
#5
Hi!
Here is a little demo we made for Retro games couple Youtube channel, by converting their images on Amstrad.
The music of the demo is by @manossg from Rodolfo 2.
Thank you!
Here is a little demo we made for Retro games couple Youtube channel, by converting their images on Amstrad.
The music of the demo is by @manossg from Rodolfo 2.
Thank you!
#6
FWIW, having fiddled around enough to get it building in Visual Studio, I think it (and some other) problems stem from the code sometimes treating Xsize and Ysize as if measured in bits and sometimes as if measured in pixels. Probably a bit of a relic of its Spectrum legacy (where the two things are the same).
Changing the CPC specific bits in DrawPhysicalMemoryAsGraphicsColumn to both use memAddr += 2 fixes the viewer, but still leaves other bugs in Mode 0. I suspect it should always just treat them as bits (and thus be memAddr++ as it is for the C64 and Speccy formats). That seems to fix weird issues I was seeing with the hover over address not being right, but doesn't fix how the data looks in the Code Analysis window (which is definitely assuming the values are pixels).
Changing the CPC specific bits in DrawPhysicalMemoryAsGraphicsColumn to both use memAddr += 2 fixes the viewer, but still leaves other bugs in Mode 0. I suspect it should always just treat them as bits (and thus be memAddr++ as it is for the C64 and Speccy formats). That seems to fix weird issues I was seeing with the hover over address not being right, but doesn't fix how the data looks in the Code Analysis window (which is definitely assuming the values are pixels).
#7
This is brilliant!
Really great job.
Really great job.
#8
Why are you making a game with boring graphics, then? 
#9
Someone reported issues with a 6128+.
Looks like sync problems with the split screen. Not sure if is something I did wrong or related to his monitor. I think I'm doing the same split I did in Hyperdrive, and obviously I have tested it with real hardware (but I don't have a lot of hardware to test, definitely not a 6128+).
Any issues, please let me know!
Looks like sync problems with the split screen. Not sure if is something I did wrong or related to his monitor. I think I'm doing the same split I did in Hyperdrive, and obviously I have tested it with real hardware (but I don't have a lot of hardware to test, definitely not a 6128+).
Any issues, please let me know!
#10
I had some thoughts about:
- making a modern graphics card using FTDI EVE hardware. This could output VGA or maybe even DVI/HDMI. With no compatibility whatsoever with anything else, of course, so the firmware will need some patching (can be done with an expansion ROM I think) to display on it, and anything that doesn't use the firmware would have to use its own code (or revert to the Gate Array video output).
- I also looked as the EF9365 family of video controllers from ST Microelectronics. For a more realistic 1980s approach. There are some problems interfacing that with modern SRAM or even DRAM, and it's a bit strange to use (you don't have a direct framebuffer, you don't have tiles, instead you send commands to plot straight lines and dots, and draw characters at arbitrary pixel positions).