Jump to content

laoo

Members
  • Content Count

    310
  • Joined

  • Last visited

Everything posted by laoo

  1. I didn't knew about this thread. IMO in the Lynx there is a 6502 because it has the best ratio of versatility to transistor count and it was an option at the time to embed it as a CPU core into the Mikey. Just look at the Mikey die shot: CPU (upper left corner) occupies only about 15% of the entire chip area. Every other reasonable CPU core would be much bigger. The only drawback of using the 6502 in the Lynx I can think of is that it has inadequate addressing modes to handle Suzy's SCB efficiently - SCB is a structure that can be anywhere in the memory and 6502 can't address its fields quickly.
  2. @Linndrum I now see that I haven't actually pushed that branch with ROM export to the repository. On the other hand maybe it would be worth discussing whether to add an option to the Furnace configuration to enable "unofficial" VGM export. Lynx export could be enabled this way and there would be a standalone converter VGM -> LNX.
  3. I'm glad you like it! There is no dedicated VGM export for Lynx, because VGM community took a piss on my proposal and a request for direction. On my development fork I do have ROM export. But it's not in official branch as Furnace does not have mature infrastructure for ROM exporting yet and I got it through hacking. We have to wait for it. You can see some sample export for example here (but it requires real hardware and even Felix can't handle it propely). Eventually I'll try to write some reasonable driver to play songs from Furnace but it will be hard.
  4. It works only in Handy. You can debug it in Felix.
  5. @CharlieChaplin Actually it wasn't packed on purpose - to speed-up loading on compo-machine, that loads data faster than it can be unpacked by 6502.
  6. It's not patented or anything The idea at it's conception was about the very thing - automatic allocation of space for temporary variables on 6502's zero page. The implementation has few hard parts though, like how to be sure that some temporaries aren't accessed at the same time.
  7. It's hard to characterize it in few words, but best I can tell about the main feature is "static memory management for memory constrained system with ability to handle memory reconfiguration". Shortly: an assembler without orgs that can automatically put different things in the same place given they aren't acessed in the same time-frame.
  8. "Now" it's unfinished and it's actually the only reason to being top secret And speaking of "what" it's going to be some sort of multisystem assembler with very unique features which I desire most and could not find anywhere.
  9. LOL. I've actually stumbled upon this issue in my top secret project while I was testing it against RMAC output 🤣
  10. If reading it again does not help you can always read the source code of the emulation.
  11. Are you aware of https://atarilynxdeveloper.wordpress.com/2012/10/14/programming-tutorial-part-8changing-appearances/ and https://atarilynxdeveloper.wordpress.com/2012/10/31/programming-tutorial-part-9advanced-sprites/ ?
  12. Eh, I was actually wrong. There does not seem to exist finite "clipped right triangle subdivision" to that triangle.
  13. I imagine that by drawing tilted / skewed rectangle with clipping on one side you can draw special case of right triangle, but when Suzy needs two blitted triangles to obtain any arbitrary triangle, here you would need four and with potencially big waste of cycles due to clipping.
  14. laoo

    OSSC with 50Hz

    The price is currently virtual: Sorry, no ETA on re-stock due to global component shortages On the other hand Medusa is freshly supplied and there are no signs it should be worse than Tink5x BTW. Sorry for derailing the thread. I hope 42bs will find a solution to his OSSC problem
  15. laoo

    OSSC with 50Hz

    Didn't all 8-bit computers / consoles output only even field indicator? That's the way to signal that the output is not interlaced. Or I'm missing something. I should have Medusa in few days. I'm eager to find how it'll behave with Jaguar.
  16. I noticed the palette issue few times too. It should not be anything complicated. I just have to reproduce it in controllable environment. And of course your support is great! Thanks for everything!
  17. I've appeared here in the eve of 30th anniversary and the activity then was very different. Who knows, maybe it'll happen again someday. Meanwhile it's apparently a good time for a little break to come back soon with fresh energy.
  18. @Pingouin Thanks for asking, and yes, you may call it that way. This is a demanding project and I got tired. I've paused it a little to recharge my batteries and gain some perspective on the direction the project should take. Another thing - this is one of such kind of projects that is fueled by constructive feedback from the community. I sensed that the interest is low, so it was easier for me to switch to my other fun project that desperately seeks my attention.
  19. Driver playing the tune does not exists yet. The cartridge image that plays it has built-in VGM-ish player. Real driver will be rather demanding. I'll try to write it hopefully soon, but it needs some research how Furnace exactly executes the song and instrument data to produce the Mikey register writes.
  20. Actually original controller for PC-Engine has 2 buttons. Good luck playing Street Fighter with that (you change move sets using "select"). There were "pro" controllers with multiple buttons, but it's the same story as with pro controller for the Jag.
  21. I feel that the discussion diverges from the OPs intent. I think that the OP asks to point design decisions that turned out to be wrong. So bugs in RISCs and lack of good toolset aren't design decisions. Using 68000 instead of e.g. 68030 is such decision but I don't think it can be called an obvious design flaw. The system certainly would benefit from better processor (especially from caches, pipelining and 32-bit bus). We know that it was considered, and it ended being against the design philosophy where the CPU is only a supervisor to RISC processors and the increase of final cost of the box had been considered unacceptable. We don't know if the machine would be competitive with better processor. I think that the topic is about things that could have been designed differently without increasing cost too unacceptable levels, and was in reach of Atari engineers. Certainly doubling the amount of GPU RAM should have been easy and maybe not too costly, since DSP already had 8 kB. I'm not sure now about the blitter cache - maybe it was difficult. On the other hand the amount of DRAM had rather big impact on the price so doubling it to 4 MB could have been off the table too.
  22. John Carmack had some theories about it. He's talking big, but maybe just some minimal cache for blitter could be.. maybe not a game-changer but at least huge improvement.
  23. Not yet finished. I decided meanwhile to develop some tools to handle such big project and I'm finishing it. So hopefully we'll finish it soon.
  24. Ethics of such behavior is questionable at best, although "pirated version" of our port of MK to Lynx got at least decent box .
  25. And they even have the audacity to call our thing soccer 🤬 I love the graphics in this game. I even did not know that such thing is possible using 16 colors.
×
×
  • Create New...