Jump to content

paulscottrobson

Members
  • Content Count

    141
  • Joined

  • Last visited

  • Days Won

    1

paulscottrobson last won the day on November 28 2020

paulscottrobson had the most liked content!

Community Reputation

57 Excellent

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Shows the 65816 issue. Most of the data in X16 hardware is 16 bit, and a 6502 handles that badly. Never mind memory space.
  2. "Given (assumption) that the Mega65 makes sprites easy and sound easy, then speed IS an Ease of Use improvement. " AFAIK it's about the same. Most of the sprite API is fairly straightforward. It's the data and ease of use that's the issue. I've a Python script that builds graphics into a single file with autoscaling and so on, RLE encodes it and indexes it along with size/alignment information. Data is unpacked into $A000 RAM. It works well enough. The other tricky bit is if you want automovement.
  3. I’m a believer in the idea that modern coding wastes cycles, memory etc. I started professionally coding on Windows 3.0 and Word 2.0 (?). Odd thing is it didn’t seem to be much slower if at all, and Word did pretty much the same stuff. I think they’d just added the wiggly line spellchecker.
  4. Thought I’d seen a plug-in replacement board somewhere, bit like the old 65c802 which I think isn’t available, which would give many advantages outside the flat memory
  5. Reality is if there is sufficient interest in Mister/X16 people will just pirate the Rom images as they do on many of the others. The Vera will be reasonably cloneable as most software will be developed on the emulator. Some very precise timing stuff may not work. I understand 100% (and agree) that people should support the project team. Just being realistic.
  6. I converted my old (Falco) HP Chromebook to run Arch (basically upgraded the SSD to 128Gb) and its actually pretty good. Everything seems to work.
  7. Well, you learn something every day. Didn't think they'd ported SDL to Android (if they haven't, it's going to be very limited). It is a *bit* pointless though. I always thought Apple had a flat refusal on emulators, so you couldn't run them without jailbreaking, trying to protect the Apple Store income.
  8. Matt Heffernan has done some good tutorials on youtube specifically for this machine. Any 6502 tutorial will get you started. The 65C02 in the CX16 is *slightly* different to the 6502 found in machines like the Apple 2, C64, Vic20 and BBC Micro, but it is backwards compatible, so any 6502 tutorial will give you extra information if you feel you need it. There are also several books like "how to program machine code on your Vic 20" available for download now (I made this title up !) and much of that will be extremely useful (the sound and graphics are completely different but the basic ideas are the same). And ask here if you get stuck
  9. No, there isn't. It would require a large amount of work to produce one. The browser/Javascript version should work, though you have the obvious non keyboard problem whatever.
  10. Thanks. I (obviously !) didn't know that, I'd just had a casual look at it. Better than I thought.
  11. I always thought it a shame that Stefany and David didn't join forces. Stefany's an awesome engineer ; she's done a huge amount all by herself on the hardware. David is more software, is great at the 'team building' sort of stuff, has a much bigger audience. It's hard going being a one woman hardware machine - and of course there's always the possibility (god forbid) that Stefany could have a mishap or other external events which would probably kill the project. Even if the hardware is open sourced much of it is in her head I suspect. I recall from "Dream Computer #1" that they talked about it and some retro meet somewhere, but they were too far apart, this being David's mark one design - the cheap $50 design with minimal hardware. CX16 has moved much closer to Stefany's sort of design in many ways, as more and more has gone on the FPGA, there's the 6502 RAM/ROM and one of the sound chips (?) and a VIA and most else is in the FPGA. Which isn't far from the Foenix design (though I think it may have DMA, not sure without checking). Too late now, I suspect, to combine forces. I can see why she's produced a redesign but it's in danger of fragmenting the fairly small community.
  12. 16 bit superset. It still as the same basic registers, but A and XY can be 8 or 16 bit in operation, it can mimic a 65c02 perfectly or run in 16 bit mode (where I think it's best, except for 8 bit string and other data handling, which there isn't a huge amount of). There are some extra addressing modes suitable for C and obviously 24 bit versions of them. There are also a few tricks which allow you to move zero page about and the like. If you can program the 6502 the 65816 is no real stretch.
  13. With something like 6502 Pascal there's a reality that while the runtime will be fine to do a great deal, significant chunks of anything speed orientated (e.g. action games) will require assembler linked in.
  14. A healthy ecosystem requires tools and libraries that allow you to easily create a healthy ecosystem. It requires a way in - a more modern BASIC fast enough to program (say) Pacman without 6502 assembler for those who are learners ; they can't start on the godawful MS Basic. There are things like PROG8 and CC65 that sort of work, but no-one has yet solved the basic problem that if you do 16 bit arithmetic on a 6502 it eats up memory and if you have a Sweet16 type design it eats up CPU time. I actually quite enjoy trying to fix it - my language (based on HPs RPL more than anything, though I didn't know this until afterwards) does fix a chunk of it but it's not very newbie friendly. It has to be affordable, the big thing lost from the original design. David's $30 (?) price point was never going to happen but a $60 price point was doable (e.g. the ZX-Uno is about that). I'm not short of cash, but laying out £500 for a virtual machine is non trivial. (so, yes, I'd buy the FPGA version), especially when almost nobody is going to develop on one. In answer to Stephen what I find frustrating is all this is doable and often present but in serious danger of being lost in absurd design decisions. No. 1 here is, as you might have guessed, the desire for authenticity when the majority of the stuff that designs system is already on the FPGA. You have an add on card for the C64 (which some may remember was the initial design)
  15. It's very good at tiles and sprites or simple PETSCII displays, but not very good at direct screen memory access stuff. Michael Steil and I have both written line routines for it, entirely seperately, and they run at about the same speed, a couple of lines a frame in 320x256 mode. I'm sure my code could be made to run quicker but not that much quicker. You could reduce it to 256x256 and do everything in 8 bit data I suppose, but that's no use for OS routines. So I reckon apart from tile maps (possibly scrolling) with sprites type games (or just sprites, it should do Robotron well say !) it's not going to be an improvement on its predecessors. As for static graphics adventures, you've got 320x256 mode with 256 colours, or double a resolution with 16 colours. It's going to be about the same as EGA with the VGA 320x2xx x 256 colour mode. VERA has slightly less memory than a standard EGA card (I think originally there was a 64k version).
×
×
  • Create New...

Important Information

Please review our Terms of Use