Jump to content

Tursi

Members
  • Posts

    8,726
  • Joined

  • Last visited

  • Days Won

    9

Tursi last won the day on December 27 2023

Tursi had the most liked content!

6 Followers

About Tursi

  • Birthday 11/29/1971

Contact / Social Media

Profile Information

  • Custom Status
    HarmlessLion
  • Gender
    Male
  • Location
    YYC
  • Interests
    Buy me a Kofi! https://Ko-fi.com/tursilion

    Or fill in my 'SurveyWalrus' and help choose my next task!
    https://harmlesslion.com/cgi-bin/walrusquery.cgi
  • Currently Playing
    Current Project: Website update
  • Playing Next
    Next project (per survey): Finish Super Space Acer ColecoVision

Recent Profile Visitors

34,082 profile views

Tursi's Achievements

Quadrunner

Quadrunner (9/9)

10.3k

Reputation

  1. Frig, I'd go broke paying myself! Must be a good idea!
  2. Since this thread reminded me of that one, I went back and asked it again to do the asterisk program, and it didn't remember.
  3. Just re-read this - you mean multiple GROM bases on GROMs 0,1,2? Pretty sure I added that for you. Maybe I'm confusing intent, but if that's what it was, you set Emulation/bankedConsoleGROMs in the Classic99.ini to 1, then load as normal with G1, G2, etc. That's a hardware mod on a real console, so it doesn't make sense to do it per cartridge.
  4. You can via the INI. We did this just last month for the OPA startup. There's just no /autodetect/ method for doing it, since it expects you are dragging and dropping a cartridge, not an operating system. I need to add the RPK support, and I was toying with supporting Classic99.ini fragments as well, since RPK doesn't support everything Classic99 can load. But, I need time. Someone win the lottery and hire me. Hell, I'd finish V4 rather than continuing to hammer on V3.
  5. This is TI's recommendation too, for very similar reasons. Most applications have a main loop that cycles more than quickly enough for the interrupts to maintain 60hz.
  6. Cute tool! Would have been nice when I was building Classic99. These days if I'm checking one key I don't generally store all 8 bits anymore. It's harder to track which bit to set, but since you usually need to change R12 anyway, you can go direct to the bit you want and save a few cycles. (Very few, true, but still )
  7. Classic99 supports a significant subset of the enhanced graphics, but it does not support the 30 row mode. (I expected more to work than does, though.. odd. I support the BML but none of it appears to show. Oh well, it's not expected to work in Classic99.)
  8. I'd agree with OLD CS1, but I've no idea what the implications are.
  9. Yes, they run through the same return lines.
  10. You could do it with the GPU
  11. Don't need to! Load any software, or run something in TI BASIC. It's hardware, so the joystick will cut out when you press one of the related keys. 10 CALL KEY(0,K,S) 20 CALL JOYST(1,X,Y) 30 PRINT K;X;Y 40 GOTO 10
  12. I don't know if the joystick circuit is different on the QI... but I reckon if the Alpha Lock issue still exists there, this likely holds true.
  13. Yeah, it makes perfect sense now that I know what it is. I tested every combination on hardware here last night, using several pieces of software to make sure it wasn't just software.
  14. I think that's the first proper pic I've seen of it... nice.
×
×
  • Create New...