Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 06/11/20 in all areas

  1. 11 points
    Hi Everyone, If you happened to see David's video on the Color Maximite 2, then you probably noticed that the new Commander X16 PCBs have arrived! David @The 8-Bit Guy just happened to swing by my house the day they arrived, and he picked them up before I was even able to get all of the parts in. I am still waiting on a few things, so I haven't been able to complete assembly yet. The VERA is also not complete for this reason, but I had to mock it up for the pics! Bear in mind, this is not the correct case, this is from an old tower ATX case I had sitting around. It's a nice platform to mount the board and make sure I have the placement of screws, slots & of course the rear ATX panel aligned correctly. I will likely make a few placement tweaks but overall I am quite happy with the physical layout so I just had to post some photos! So far, it's working but my ATX soft-start circuit is a bit squirrelly. Not only that, I kinda wired it wrong and didn't catch it before the run. Worked great on the breadboard, but I will have to revamp that before the final. There are also a few other little things discovered since this proto was run, but the real tests will be coming when @Michael Steil is able to get the Kernal up and running. (I would write some test code, but one part I'm missing is the ZIF socket for the ROM. Should be here in a day or two.) @Perifractic is also sending me the X16 case, so I should be able to install the board in there later this week. Happy Sunday, and Take Care Everyone! -Kevin Williams https://TexElec.com
  2. 7 points
    Hello everyone! My name is Michael Steil, and I'm a member of the X16 development team. I am the lead developer of: the X16 ROM the (advanced) KERNAL operating system our version of the Microsoft/Commodore BASIC interpreter our MONITOR the DOS for the SD card the GEOS port the X16 character sets the X16 Emulator the X16 Reference Documentation I'm thankful for any help on these projects, all of which are Open Source projects on GitHub: https://github.com/commanderx16/x16-rom https://github.com/commanderx16/x16-emulator https://github.com/commanderx16/x16-docs (Edit: Or via this website's Support page: https://www.commanderx16.com/forum/index.php?/forum/17-x16-help-support-lounge/) Technical discussions on these projects should happen in the form of "Issues" on GitHub, but I'm happy to discuss more generic topic here in this forum! Michael
  3. 6 points
    The Emulator and the ROM have been adapted for the new board. You can check out branches x16_board_r2 in the source of the two projects. The official reference manual has also been updated. In short, these are the major breaking changes: RAM and ROM banking is done through magic zero page locations 0 and 1. Up to 512 KB of ROM are now supported. VIA#1 is now at $9F00, VIA#2 at $9F10 YM is at $9F40 All I/O (PS/2, Controllers, Serial) has been moved to VIA#1 PA and PB.
  4. 6 points
    I am an expat professor teaching in English before our students transfer to the US. My first computer was a Timex Sinclair, which turned out to be closet compatible, but the next summer when I had the chance to buy better, I was shopping for the cheapest home computer with a real keyboard and disk drive, which was the C64. I used it to edit my undergrad senior thesis, play a few type in with error check magazine games and get started programming in Forth. I took a Epson Geneva with me to the Peace Corps, and got a C128D when I got back... which I all too soon fried with a power tap for my parallel printer interface which didn't have the block inserted to prevent plugging in upside down and shorting out the datasette lines connected directly to the processor. So it was my old C64 breadbox and portable color TV with bad ghosting on one color which was the computer I took to grad school in the late 80s early 90s. My daisywheel printer was slow but looked prettier than classmates with IBM pcs and dot matrix printers, and my 1581 which survived my C128D dying worked fine with my warpspeed cartridge. But I got a cheap Amstrad double floppy transportable with flip up LCD screen and it was on my PC compatible I did my only serious programming, a brute force maximum entropy estimator of an economic Input-Output model. It took near a day to do a run, while I am sure with the right R package I could do it today in a couple of minutes. I went off for a decade to teach in Australia, and played around with Forth now and again, but if I turned on my PC for research it was mostly using Excel to figure out what suspect games public planning agencies were playing with public transport cost benefit analysis. Now there are no kids in the house, and I have some notions I never followed up on in the 80s which would be a lot more pleasant to play around with on the CX16 than on a C64. So I can't wait to get my hand on a CX16c or e (depending on what I can afford with 8 grandkids to get gifts for).
  5. 6 points
    Hi again! I've been working for quite awhile to get the new layout complete, and I think we are just about ready to run the second prototype! There are quite a number of changes to this board over the previous version, so I do expect a few, ahem, challenges perhaps? That said, a lot of time has been spent testing on breadboards and optimizing so I think we should be close to the final specs on this system. As mentioned, there are code breaking changes with the system. I will post more for the devs out there in a post below. The VERA has also changed quite a bit. Namely, it now has 32 registers, but I'll let @Frank van den Hoef talk more about that when he is ready to post some updates. Also, I made two proto boards to test the bus and get the alignment right for the final design. Progress is being made, thanks for everyone's patience and have a great day!
  6. 5 points
    My path is recounted in my intro in the intro thread, so the quick shortcut version ... Timex Sinclair, membrane keyboard, tape storage, 16KB RAM expansion crashing, into the closet, next comes the C64, an Epson Geneva for my Peace Corps teaching in Grenada in the mid 80s, back to US, a C128D where I fried the processor, back to my C64, off to Grad School where my C64, BusyBee PerfectWriter, Big Blue Reader, 1541 and 1581 drives and daisywheel printer were my paper writing setup for two years, then a cheap liquidation two floppy transportable as hard drive systems were becoming the main thing, then relying on office PCs and cheap two generations old PCs until the present.
  7. 5 points
    Hi everyone I'm Andy (Andreas, actually) from Switzerland. Back in the 80ies I came into computing because of my father. It all started with a Texas Instruments TI99/4A he bought in 1982, I was 12 by then. So I did some Basic programming, even got a little into assembler. The machine was quite limited, but I loved it - it did what I told it to do! Mostly that was also what I wanted it to do... We then moved on to a Commodore SX64 (the 'portable' version of the C64) in 1984, although that was my fathers machine he brought home from the office frequently. The amount of software and games for that machine was quite overwhelming. In 1986 we then got an Atari ST. For me this was just plain magic! With it's large memory, colorful graphics and (not so much sound) capabilities it was just crazy! I there got into programming with structured languages like Pascal and C - there I decided to go into computer science as a profession. Around 1989 onwards the IBM compatibles took over and I started my study. That was the time when computers kind of lost their magic for me... Don't know, but somehow they were just boring tools which did their job. But they were never as exciting again. Just boring grey boxes which initially didn't even compare with the Atari ST. So now I stumbled over this project here - and I get it! 8 bit computers like the C64 or to some extend the original Atari ST were simple and actually easy to understand. My dayjob doesn't involve programming any more - and I miss it. Tinkering with IoT stuff and my smart home setup is fun, yes, but not as rewarding as getting the maximung out of a limited machine. I'm now thinking about getting into developing for the X16 - just don't know what it should be yet... so let's see what happens ...
  8. 5 points
    Agreed! In future we'll try to only make announcement posts here, then paste the link into FB (which will generate a preview of the post anyway). The website will be the go-to #1 source.
  9. 4 points
    Brixx View File This is a Breakout/Blockout/Arkanoid inspired game. . It is early stages, this is my very first try on the X16. You have to use a mouse. I'd also like to improve it with more sound effects, title screen, intro music etc. I've only tested it on the emulator, so if anyone of the few with real hardware can give it a go, I'm eager to know the result. Available power ups: L: adds one live to player M: paddle is magnetic for 30 seconds. Can only hold one ball at a time. Duplicates ball, so now you can have fun with 2... Keyboard commands: 's': sound on/off. Roadmap: - basic sound effects. done - power ups like double size paddle, 3 balls at once etc. done - Joystick support - Intro screen (with intro music?) - High-score screen Let me know what you think... Submitter AndyMt Submitted 06/29/20 Category Games  
  10. 4 points
    Hello I've been slowly trying to learn 6502 assembler by building an X16 game engine. But better than that - you can watch me do it on twitch as I stare confused at my screen whilst mumbling to myself next to a microphone! Please visit the channel and say hi or follow
  11. 4 points
    I started to program as a young child in the early/mid 80's on an Acorn Electron (you may not have picked up on it, but there's a clue to my first favourite game, and most nostalgic). Eventually got an Amiga 500, and soon after that an Amiga 1200 - loved using AMOS, Octamed, Deluxe Paint, WordPerfect (for course work) and of course hundreds of games and demos, which I used throughout college. While at university I had moved on to a 486dx66 with DOS and Windows 3.11 (although I still far preferred the Amiga). The last 20 years I've almost exclusively been using Linux, although I still occasionally use my A1200 and Acorn Electron, both of which have been upgraded to varying degrees since I first got them.
  12. 4 points
    So I've made up my mind what to do. I'll start by implementing a Breakout/Arkanoid alike game in C using cc65 and maybe some assembler . I think this will get me into sprites and tiled graphics. Some very early prototype is already working, showing some sprites, accessing the mouse and switching video modes etc. It was fun digging into the VERA documentation and fiddling with bit fields again... I'll post a Prg when there is something playable.
  13. 4 points
    Y'all know PCB stands for Potentially Could Be Blue. Or is it? PCBWAAAAAAYYYYYY Sorry, had to do it. In any case, it looks pretty cool
  14. 3 points
    Just for fun and because it has been asked a few times I want to explain what would be required to use a VIC-II or SID or really any chips that are too slow under normal circumstances. I’m not saying either of these is really a useful idea, but it makes a good introduction to how to use such things on expansion cards. Also up front this article is going to use layman’s terms but is still geared at those interested in hardware. Since it’s the less complex option, I’ll start with how you would use a SID chip. Probably the best point to emphasis because it affects any chip you want to interface to the bus is the access window. The CPU in the x16 uses half cycle access for memory or IO. This means that in each clock cycle the first half of the cycle is spent doing internal processor stuff and setting this up for the actual bus access. During the second half of the cycle the cpu performs either a read or a write access to memory or IO. This time we will refer to as the access window. And all chips on this bus need to be able to respond to read/write operations within that window. So how long is this access window? Well it is measured in nanoseconds. To give you some context, if you have a clock running at 1 MHz, there are exactly 1000 nanoseconds in that one cycle. So if our cpu was running at 1 MHz our access window would be slightly less than half that, about 500ns. If we increase to 2 MHz that access window decreases to about 250ns. However I’m doing a rough approximation because there are some factors that also affect how much of that access window is really usable. There is address deciding aka glue logic that reads which address the cpu is trying to address and then selects or enables the appropriate chips. This process is not instantaneous, and the amount of time it takes for the inputs address lines from the cpu) to the outputs (chip select lines from the logic) is going to be referred to here as propagation delay. This delay is also in nanoseconds and for the sake of simplicity we are going to state this value as 20ns. So with this value we will then see our usable access window at 1mhz is closer to 480ns and at 2mgz would be closer to 230ns. So let’s consider this for the 8MHz that the x16 runs at. We get an nominal window of 62 nanoseconds but an effective window of 42 nanoseconds. So what this means is that any chip that will connect to the bus, be it RAM, ROM, IO chips, video chips, audio chips, etc. must be able to respond to a read or write in less than 42 nanoseconds in order to work reliably. There are ways around this and I will get to them later, but I’m just making the point that any chip that connects directly to the system bus must be able to respond within that access window. In the case of a SID chip I’m not sure what it’s access time is, but it’s likely in the 150-200nS range. So it would work at 1-2 MHz reliably and might work with 4mhz. But it won’t work reliably on an 8mhz bus without some type of buffering. So if you were to implement one, you have several option on how to go about it. If you aren’t concerned with reading the chip, then you could use latches. You would need to latch the data and the address and implement some type of timer to extend the hold time. What you are doing in this case is that instead of interfacing to the SID directly you are instead interfacing to a simple latch which just captures the relevant address lines and the 8 bit data. This buffer then outputs those values for as long as needed. To enable the chip to be read requires some additional circuitry. This method can actually be used for both reads and writes and involves halting the CPU to extend the access window across one or more CPU cycles. Basically when an access occurs the RDY line needs to be pulled low while the BE (Bus Enable) line is pulled high. This causes the CPU to be halted in its current state. Using binary counters we can hold this state for as many cycles as we need. Keeping in mind for an 8 MHz bus if we extend the acces by just one cycle what we actually get is 42ns+125ns for a total of 167ns and if we need more time we get an additional 125ns for each cycle we extend that window by. Keep in mind this method does require the use of bi-directional tranceivers or equivalent. Now to use the VIC-II chip is quite a bit trickier. Basically the main issues is the VIC-II needs access to memory. Since there is no way you could make it play nice with the X16 memory space you’d need to give it its own memory. You would need to design some kind of circuit that would act as a bus bridge. this bridge would have to facilitate both reading and writing to the Vic-IIChip-II chip itself but would also have to act as an indirect memory window. This is doable but is not a lighthearted undertaking. I’m not suggesting anyone actually tackle this I’m just saying that it is possible and that this is what would have to take place. I feel I should also add though that doing these things would not make the X16 capable of running C64 software. i’m merely laying out what would need to take place to make it possible to interface with these chips not what would need to take place to emulate another system. This is just a fun thought experiment and a good opportunity for me to explain how it would be done. One follow up too, this is by no means a definitive guide on the actual timing requirements. The reality is the timing is probably more forgiving that what I’ve stated here, my 20ns example is more like a worst case scenario. We don’t have hard figures on the actual timing yet, for that we need to finalize all details of the board and measure multiple samples at different temperatures and voltage ranges. . Sent from my iPhone using Tapatalk
  15. 3 points
    The debugger doesn't currently allow you to fill values in memory... that said, I happen to be in the middle of some changes to the debugger based on a separate suggestion to make it possible to dump VRAM, so I think I'll go ahead and add a "fill" command while I'm at it. So hopefully it'd make it into r38, which shouldn't be too far off on the horizon.
  16. 3 points
    Maintenance releases? How about more regular releases? I'll try that!
  17. 3 points
    Im a spanish kid that likes electronics, In 2018 I discovered the retro computer comunity and obviously the 8 bit guy and LGR.
  18. 3 points
    I've been busy with all kinds of other projects for quite a while, but I'm back to X16 development now. I'm currently in the process of changing the emulator and the ROM over to revision 2 of the actual board, which has changed in respect to memory and VIA layout. As for pull requests, that's the next thing that I'll have a look at!
  19. 3 points
    Introducing the new X16 Twitter Bot: send it a program on Twitter (if you have an account) and it will run it! See by yourself: Okay, that was kind of a boring example, but you get it. Once you mention it on Twitter (the messsage must begin with a line number), the bot will take your message, run it in the emulator for 33 seconds, leverage its GIF-making feature and reply to your message with the last 3 seconds of execution. The bot also support binary PRG programs (tutorial coming soon, uses base2048 if you can figure it out, experimental). So in short, it works very similarly as other bots such as @bbcmicrobot or @auto_tweetcart. Very useful to share cool snippets on Twitter, or for practicing yourself at code golf. I kinda want to build a community on Twitter around it as well, so why not? It's also gonna unofficially post the interesting news for those who don't have Facebook. So yeah, try it out and have fun! Note that the same rules apply as here.
  20. 3 points
    Thanks! Also since it's still the 4th of July here... (gotta love the automatic Twitter embeds :))
  21. 3 points
    Another demo update:
  22. 3 points
    For me, it was an Apple //c with an Epson FX-80+. I typed up a lot of papers on that, and made a lot of money doing so, as well.
  23. 3 points
    Having way too much old stuff in my garage, I wanted to have an other 8 bits thing to play with Making electronics and software for more than 30 years now, a new 8bits platform is always a new playground to experiment and keep my assembler skill at level. In this FPGA era I love (cheap FPGA was a dream only 10 years ago), programming on real silicon is always a good thing. Now I'm waiting for the pre-orders .... Keep up the good work ! Olivier
  24. 3 points
    Started 40 years ago with a Sinclair ZX80. I'm very curious to see if a Z80 card can be made that will run on the Commander x16
  25. 3 points
    Hello, everyone! My real name is Vladimir (like in Baron Vladimir Harkonnen from Dune, hehe). I'm from Kyiv (Kiev), Ukraine. I got my first PC at the age of 12. It was POISK, a Soviet not fully IBM compatible machine from the early 90's. With it I got familiar with BASIC and computers in general. I'm very happy that retro computing lives to this day, and has a significant burst in the last several years. I'm following the development of X16 from the very beginning, when David mentioned about his dream computer for the first time. And I'm looking forward to all future events. To the final product... and beyond!
  26. 3 points

    Version 1.0.0

    4 downloads

    A simple snake game I made in W65C02 assembly.
  27. 3 points
    The hardware really only has one output resolution: 640x480. 320x200 isn't a resolution that is natively supported by VERA. As far as I know the kernal has this 320x200 resolution as part of the GEOS drawing code, which Michael didn't yet update to make use of the full 240 lines height. As Stephon Horn showed, you can use the scaling to make the 200 lines cover (almost) the full 480 output lines, but it will give some scaling artifacts.
  28. 3 points
    I've removed the case conversion from the code and it's working again. So it's up to the programmer to take care of referencing files correctly again now.
  29. 3 points
    Hi everyone! I've been following the development of the Commander X16 since its announcement, and I'm very impressed with the progress. I've been trying to teach myself 6502 assembly so I can write software for the X16 at the lowest possible level. I've been a bit busy the past few months, but finally feel I have the time to pick it up again. I have a few ideas for software that I'd like to write, and have started learning the basics so I can make it happen. I'm hoping that the Commander X16 can be my 5 year old daughter's very first computer (we don't even give our kids phones or tablets), so she can explore computing from the ground up. I love the ethos and mission of the project, and feel that this computer is going to be the most approachable way for kids (and adults) to learn about computers. I'm happy and grateful for such a wonderful community!
  30. 3 points
    I popped open the emulator source and it looks like "no", which means it's my fault, in my assembly source I'm specifying filenames in upper-case ASCII, which isn't going to map to unshifted PETSCII. My b. Let me make a new release and see if that fixes things. Edit: Perfect. All fixed up.
  31. 3 points
    Hi everybody, I've had a C-128 in the early 90ies and had my first programming expericene on it. I've been following this project since the beginning, but wasn't on FB. I'm mostly interested in programming C for the CX16, gradually optimizing it as my assembler skills improve. Looking forward to buying the machine, once it goes on sale. So all in all, a big shout out to the CX16 team. You guys are amazing!
  32. 3 points
    Hi, Its been 30 years since I got hooked on programing with my Tandy 2100FD in GW-BASIC... I later watched kids learn stuff online that took me years to figure out! Im starting on a quest to learn assembly for my new-ish Plus4 and maybe teach my kids if they get interested. The Commander X16 is deffinately on my wish list ...and maybe the kids can get one too?
  33. 3 points
    Please, by all means, take full use of my code. It's why I put it up on GitHub with GPL3 licenses, to maximize reuse. If you are scared of coding in BASIC or assembly, you don't have to use either with XCI: https://github.com/SlithyMatt/x16-xci I made a whole video series about how you can make your own game, holding your hand through the whole process:
  34. 3 points
    Well an adventure game might be an easy place to start: https://www.commanderx16.com/forum/index.php?/files/file/18-xci-extremely-compact-interpreter/
  35. 2 points
    This is the exact kind of thing I'm looking for - a little higher level than pure 6502 assembly with the ability to still inline assembly as needed. I'm definitely going to check this out. For those interested, the GitHub for the project is https://github.com/KarolS/millfork EDIT: Since the native version of Millfork on Github is based on a release from April, and doesn't appear to include support for the latest VERA, I just spent the last 3 hours fighting Java/Scala, GraalVM, native-image and Windows to create a native copy of millfork.exe based on the latest commit on master in the repo. I tested it out in VSCode with the CommanderX16 plugin and it runs a simple Hello World app just fine. If you want to grab it, I've popped it in my Google Drive here.
  36. 2 points
    Hello. I'm Jason. Though on the internet I'm known as CyberYoshi64. I'm an almost 16-year old german who enjoys programming in BASIC. Mostly SmileBASIC (3DS/Switch) but also CBM BASIC lately with the CX16. I stumbled upon the 8-Bit Guy in early 2017 when I was wanting to get started on programming and the 8-Bit machines were peeking my interest, so I started programming in SmileBASIC and ended up with SKKBAUI (a Windows-like desktop) and a bunch of fonts that everyone on SmileBASIC Source could use and share. (The 3DS runs BASIC code like the Maximite 2 that David showed off, so a ton of things are possible.) Though for some reason, I want a restriction on what I can do per jiffy with BASIC. So that's why I downloaded the emulator and joined the CX16 community. Now I'd like to write some tools and improve my BASIC knowledge with the different syntax that the CX16 gives me. I'm also wanting to write assembly but that may remain a dream for now. Thanks for reading and letting me being a part of this community and I hope I can bring out some cool BASIC projects that someone may use.
  37. 2 points
    Argis Paint View File "Argis" is a very simple paint program. I i made it mostly to test programming with the VERA chip and it is currently not very well optimized. It supports brush and fill tools and 16 colors from the C64 palette. Instructions: The first button is to select brush tool and the second is to select fill tool. Click on the color on the down right to select a new foreground color. Submitter Zen1th Submitted 07/09/20 Category Graphics Apps  
  38. 2 points
    @Kevin Williams This looks great! I feel like it's 1985 again, and I'm trying to figure out whether to buy the disk drive or the 9" black and white TV....
  39. 2 points
    Have now. Completely missed it first time round sorry. P is what is being prototyped at the moment, phase 1 C is the mini itx version in phase 2 E is the raspberry pi size one in phase 3 Old person brain here, didn't join the dots at first glance. Ta muchly for the redirect to the FAQ.
  40. 2 points
    Vera Graphics Converter View File Version 0.1 This software converts indexed and RGBA images in the formats PNG, JPG or GIF into binary data suitable for the VERA chip in the upcoming 8-Bit Computer Commander X16. Basic usage: Open an image file using File/Open... Configure the settings according to your needs. Export the image using File/Export Bitmap/Tiles/Sprites... Image Modes: You can open either an indexed image with an embedded palette or a regular RGBA image. Depending on the image mode, the software behaves slightly differently. RGBA: In RGBA mode, VGC needs to match the pixel colors to the colors in the palette. This can be done by comparing color similarity in RGB (Red, Green, Blue), HSL (Hue, Saturation, Lightness) or HSV (Hue, Saturation, Brightness) mode. Select the conversion strategy that works best for your image. Ideally load a palette that matches all colors in the image. You can specify the bit depth of the image by changing the pixel mode. 1 Bit per Pixel results in 2 colors, 2 Bits per Pixel result in 4 colors, 4 Bits per Pixel result in 16 colors and 8 Bits per Pixel uses the whole palette of 256 colors. The colors usable by the image depend on the palette offset. Indexed: In indexed mode VGC assumes that all pixels in the image have the correct index. It is still necessary to select the correct palette offset to give a correct export. On export the palette offset is subtracted and the index value capped on the selected pixel mode. Transparency Any pixel in the image that has an alpha value of 255 is set to the index selected in "Transparent Color Index". The minimum value is the palette offset. Image Mode: The VERA Graphic chip has three modes. Bitmap, tiled with a tile dimension of 8 * 8 pixels and tiled with a tile dimension of 16 * 16 pixels. Both tile modes split the image in separate tiles and limit their number to 256, since the VERA chip cannot address more than 256 tiles. It is also possible to limit their number even further. To use a tile mode the width and height of your image must be divisible by 8 or 16. The VERA chips supports 4 different resolutions: 640x480, 320x480, 640x240 and 320x240. VGC does not enforce these resolutions. It is also possible to generate sprite maps. In sprite mode the tiles can have 8, 16, 32 or 64 pixels in width or height. They are however limited to 128 tiles, and similarly, the source images dimensions have to be divisible by the tile dimensions. Sprites can only have a color depth of 4 or 8 Bits per Pixel. PRG File Header It is possible to save the exported binary file with 2 leading bytes. This is necessary for some load routines in the Commander X16 Kernal. Splitting files The exported files can be saved in chunks of a given size. The VERA Video RAM is paged in pages of 2048 bytes. Files can be split at any page, depending on how you want to store or load your data. The PRG File Header is saved to every individual file. The Palette You can load and save the color palette in the Format used by the Gnu Image Manipulation Program (GIMP) Other software like Aseprite can read and save this format too. You can also export the palette in the format used by the VERA chip. The PRG Header option is applied to this as well. The file splitting is not. Analyzing the image. You can double click on colors in the palette to change them. When you hold the left mouse button on a color in the palette, the parts of the image using this color are highlighted. Similarly, when you click on the image the color in the palette is also highlighted. Submitter Sandmage Submitted 07/02/20 Category Dev Tools  
  41. 2 points
    I can think of no reason the gunpowder treason... could possibly have worked after sending a letter to a member of Parliament, Catholic or no, and seriously what's with that alias? "John Johnson"? I mean, there have been some pretty comical attempts at regicide and revolution throughout history, and this is easily one of the best of those worst. (Though my favorite is probably the unknown number of attempts to poison the Pontic King Mithridates VI, which ultimately ended with Mithridates even attempting to poison himself... and still failing.)
  42. 2 points
    Glad to have found this place, I look forward to many happy interactions and I cannot wait to get my hands on one of these dream machines to add to the collection.
  43. 2 points
    Glad I stumbled here. As I don't use Facebook, I had felt out of the loop with the Commander X16, and the murray2.com forum just disappeared, so I found this (almost) purely by chance. Actually, I had built my own Gigatron, as I was really lucky to get one of the last ones including a case. https://gigatron.io/ (yes, the one that The 8-Bit Guy reviewed, along with Dave EEV Blog and Ben Heck)... I can't recommend it enough, for soldering, hacking, software, and the still active community. So, long story short, I found myself here! However, the Commander X16 seems to tick all of the boxes I had in a "modern-retro" device, and it looks like everyone involved here are doing a fantastic job. Looking forward to all and any progress
  44. 2 points
    Hi I'm Tom from Italy, hello everybody Tom
  45. 2 points
    Hey guys, we are doing a brand new jRPG game for Commander X16! Unfortunately our graphic artists has some health problems. That is why we are searching for extra helping hands - pixel artists. If you like games, if you you can draw and if you would like to be a part of team of specialists, that spend hours together every day (for fun and development), please contact me or @SlithyMatt Please prepare some of your work to show. Here you are some more footage and music: https://youtu.be/Fi8ZV2yxz7g
  46. 2 points
    Just noticed no one posted anything unrelated to retrocomputing yet so here you go... I admit it, the girl in my profile pic is obviously not me (...or is it?). Her name is Yuki and she's the heroine of a rather absurd webcomic I created called Horse Life 98. Maybe one day this will warrant an equally absurd adventure game using XCI, but for now, you can read her adventures on this website Hope you like
  47. 2 points
  48. 2 points
    This is so much better than reading the same post on FB
  49. 2 points
    I guess is depends on what kind of game you're thinking about, and what its requirements will be. Also, if this is your first software project on the X16, it definitely does help to start from existing projects, as @Perifrantic linked. (That's probably going to be the most robust starting point right now, because the platform is still very new and changing, and we're all only working on our spare time.) If you're thinking something more action-platformy, C or assembly are probably the way to go, but that's going to be a rough road in any event. @SlithyMatt has created a full game already, which is amazing, and he's made the source code available on GitHub. If you're at least comfortable with 6502 assembly, you could learn a lot from their code.
  50. 2 points
    Hello all, My name is Frank van den Hoef and I am responsible for the design of the VERA module (the audio, video and storage hardware module), which is part of the Commander X16.
×
×
  • Create New...

Important Information

Please review our Terms of Use