Jump to content

Ed Minchau

Members
  • Posts

    322
  • Joined

  • Last visited

  • Days Won

    14

Ed Minchau last won the day on May 23

Ed Minchau had the most liked content!

Recent Profile Visitors

719 profile views

Ed Minchau's Achievements

  1. I had this in mind when I was making FASTMATH. I think I can find a way to do really fast conversion from 16.8 fixed point to the fractional notation and back so you can take full advantage of it.
  2. Version 1.3.41.0712

    5 downloads

    The META/L editor is a direct assembly language editor. It shares some features of a Monitor program, with extensive use of metadata to take it well beyond anything a Monitor can do. Unlike a text editor that later compiles your code, META/L interprets it as assembly language opcodes as you type it. Unlike a Monitor, you can do things like copy and paste code, move it around, or insert or delete bytes in the middle of your code; the metadata allows the editor to adjust parameters as labels move. Every byte of RAM and ROM is accessible to you on the fly. Download the zip file, unzip it somewhere, and copy everything into the same folder as your r41 emulator. Full documentation is in the file docs/edit.html There are also a number of videos in the forum here
  3. META/L assembly language editor View File The META/L editor is a direct assembly language editor. It shares some features of a Monitor program, with extensive use of metadata to take it well beyond anything a Monitor can do. Unlike a text editor that later compiles your code, META/L interprets it as assembly language opcodes as you type it. Unlike a Monitor, you can do things like copy and paste code, move it around, or insert or delete bytes in the middle of your code; the metadata allows the editor to adjust parameters as labels move. Every byte of RAM and ROM is accessible to you on the fly. Download the zip file, unzip it somewhere, and copy everything into the same folder as your r41 emulator. Full documentation is in the file docs/edit.html Submitter Ed Minchau Submitted 05/28/22 Category Productivity Apps  
  4. I took the month of March off from programming altogether, and then at the end of March r39 dropped with some breaking changes. So I've updated the editor to accommodate those changes, and while I was at it fixed a bunch of minor bugs and added some new features. The download is here:
  5. If the only time you access VERA is during the VBLANK, then great, access it then. But if you're using VERA to store sequential data, like @Jeffrey did with the Wolf 3D wall images, then changing any parameters in VERA can really screw things up in a hurry. So I guess it all depends on how you want to use VERA. Asteroid Commander uses lots of sequential data stored in VRAM for various purposes. If I try updating the screen every VSYNCH or even every third one, it'll stomp all over a whole bunch of things. But if the only time you're accessing VERA is to push data to the screen and PSG/PCM, like I was doing with the Balrog video demo, do it all in the VBLANK.
  6. I'd have the IRQ do as little as possible. For Asteroid Commander it just updates a couple of bytes set aside for flag bits. The main program then checks those bits a couple hundred times a second, each time a major subroutine is finished and at least once for every trip through the main loop.
  7. I'd avoid doing anything with VERA or the RAM/ROM bank pointers during IRQ. Instead I have IRQ set a flag bit, and have the main program do regular checks of such flag bits. Whenever MAIN detects the flag bit set it resets it and handles whatever I need to do in VERA or the RAM banks. It might take a millisecond longer to get around to doing whatever subroutine, but it makes the custom IRQ much faster and there's no danger of messing up VERA addresses or RAM bank pointers this way.
  8. My problem is with Jonathan Swift, who probably coined the term "inflammable" too.
  9. The discussion above is precisely why the META/L editor uses unique 4 character codes for each command, with the fourth character indicating the addressing mode. No ambiguity and no need to parse the parameter to figure out what the command is. And it's through my update to that editor that I was searching through ROM bank 08 and found some code that isn't in any of the documentation. Is that code an extension of CODEX?
  10. Just makes me wanna slap the guy who deliberately came up with these terms. I mean, the obvious interpretation is that the big one would be at the end for big endian. It's like the guy who decided "flammable" and "inflammable" should mean the same thing. English. What a language.
  11. Sonofagun, I've been using those terms backwards. Good thing it doesn't come up often.
  12. Why little endian? VERA and the 65c02 use big endian. Not saying it shouldn't be that way, just curious about the reasoning.
  13. Zsound should probably find a home in ROM, too.
  14. So, for a parametric non-cheating method, 1833 jiffies for J=500 and 1784 jiffies for J=256. Just change the value in J to change the vertical scale resolution. Below J=100 or so it starts looking like a ziggurat. 1 TI=.:DIMX,I,Y,E,C:M=150:N=80:J=256:DIM M(255),D(141),F(J) 2 A=.7071:G=-J/11.2035:L=-0.001*G:SCREEN$80 3 FORI=1TO141:X=I-70:D(I)=X*X:NEXT 4 FORI=0TOJ:F(I)=N*EXP(I/G):NEXT 5 FORO=1TOMSTEP2.5:E=A*O:I=O-70:C=I*I:FORI=1TO141:X=I+E 6 Y=E+F(L*(C+D(I))):IFY>M(X)THENM(X)=Y:PSETX,M-Y,5 7 NEXT:NEXT:PRINTTI:END Interestingly, TI does not scale linearly with J. If J=505, TI=1821. If J=420, TI=1801, almost exactly 30 seconds, but at J=419 and J=421 it's 1808. And at J=319, it's at 1769, breaking the top speed of the cheat.
×
×
  • Create New...

Important Information

Please review our Terms of Use