Jump to content

kisrael

+AtariAge Subscriber
  • Content Count

    4,272
  • Joined

  • Last visited

Community Reputation

300 Excellent

3 Followers

About kisrael

  • Rank
    HMBL 2600 coder
  • Birthday March 31

Contact / Social Media

Profile Information

  • Location
    Boston Burbs, MA

Recent Profile Visitors

19,030 profile views
  1. yeah, I should see if it can shut off the FreeSync thing. Other than that I like the monitor a lot
  2. Along time ago I was able to change my rank to "HMBL 2600 coder", from the usual "Chopper Commander" / "River Patroller" etc Is that still something I can edit? I'd prefer it be "HMBL 2600 Toolsmith", but I can't see if there's still a place to change it..
  3. Got the 3 basic assembly kernels (48x1 mono, 48x2 color, 96x2 color) of @RevEng's bB Titlescreen Kernel in, along with an affordance for saying if it's minikernel 1,2, or 3 of that type.
  4. I suspect it's related to this : https://support.apple.com/en-us/HT202580 So don't quite get what's going on, but assuming it IS this, seems like it should be ok (and temporary... I'm sure if it was big enough for Apple to have this support ticket AND it was permanent, we'd be hearing about it a lot more)
  5. TLDR; can 60 FPS flicker kernels in Stella damage a Mac screen? So, I was playing around running the Yoshi flicker kernel on stella: It does a 60 FPS flicker to get multiple colors. So one thing that's funny is that my main monitor (a 32" LG screen) doesn't display the flicker at all; it's like its doing a weird "AMD FreeSync" thing and like just showing every other frame or something. But it DID show up fine on my 2020 (Intel) Macbook Air. But then, as I moved it around a bit, I realized there was a bit of a shadow effect, almost like a hint of old arcade burnin... and a bit later when I stopped it, I realized the area it was at was shimmering a bit (by coincidence, that was a big green patch on my desktop wallpaper, and the Yoshi was kind if turquoise green, it seemed less bad when I put a white background window over the area.) But now it seems ok. Still, kind of scary! Has anyone seen similar?
  6. the aforementioned work is started Three major differences from the old methods: 1. multiplatform because a-b-b is browser based 2. much, much easier than the old techniques - it provides the 1.8 zip, and then the 4 or so critical files (the .asm for the image, the overall templatelayout and templatecolor, an then a launching .bas file) 3. I noticed that my important routine actually isn't great at importing already sized files - so like if you import a 48x?? image, presized, it won't be quite pixel perfect. But it is good at resizing big images and I think the results overall are good-looking! For now it only does the color 48x2 , and for now only the 48x2_1 "location" of it. Plans are to add all non-trivial kernel types, though maybe not the sprite one for now. But I would like to try the animations and the flicker color ones. Thanks to @RevEng for the main work and @Karl G who has helped my tired and not reading carefully enough brain sort through the abundance of files in the zip. (Of course, thanks to Karl's earlier work, a-b-b has many different modes that are already pretty good for making a bB titlescreen And if you haven't been following, this thing supports DPC+ (including per scanline background color changes), has tools for doing gradients and text and various shapes, copy-and-paste, image import, "undo", etc etc. But hopefully while keeping it relatively easy to use, and always with ready to run code.
  7. 10 years ago (yeesh!) @RevEng made The bB Titlescreen Kernel I am working to incorporate full-ish support for this in atari-background-builder... starting with the "48x2" minikernel (currently just one of the 3 "locations" for it) This method should end up being MUCH easier to import images for than the previous steps using windows-only software. Other fixes included a nasty undefined color bug fix, and some internal improvements to accomodate the new kernel types
  8. Yeah I was thinking similar! I guess you could also compre projected sales volumes as well as ballpark money, if that's too crass. And then personal recognition like Activision started using vs Atari's "toil in anonymity, you're roll is similar to the people assembling the cart" Yeah, gaming is a great things in games. That was a weird thing about 4K - at some point you can say... alright that's all about all I know how to pack in there (though of course there are always people who will show you how to get just a bit more in.) But I know I pushed JoustPong to be more than it would have had it just been a "trophy" port of my basic JoustPong concept
  9. Yeah... actually my story is even more of that... the game was JoustPong, which came from a random suggestion in the old Usenet rec.games.video.classic ("The future of gaming can be summed up in two words -- Pong and Joust") and I had previously made in Visual Basic, Java, and even PocketC for PalmPilot. I love that it's a reasonably rich game that just needs one button! (years later FlappyBird discovered the exact same thing) Also it was easy to make a good but not perfect AI component. So limitations came into play in a very good way. (later when i wanted to make it release/purchase-worthy I added in Pterry to mix things up, and the Breakout-like wall modes. Sometimes I realize if I had had batari it would have been a month, not a year, kind of project. But it's not clear I would have pushed to extend it as much as i did) Heh. Thinking more about "trophy" game makers looking to sell CIB stuff... my guilty thought - especially for my art joke "game" Sisyphus - is ... when do we start making NFTs for these? Which game was that, is it around? And yeah. One of my focuses is as a tool maker - (in part because I was only gonna be Just Ok at the gamemaking and i didn't have many brilliant games i was dying to make) and most of my tools or tutorials focus on being able to spit out some runnable code. So for people who view insta-shovelware as a problem... well, I'm an enabler, a bit. In some ways the wonkiness of batari is ALMOST a saving grace would love to see something like @SpiceWare's SpiceC come in and capture the same "don't sweat the kernel" vibe but with a more robust system, not so white space dependent... Cool you're brass too. Actually I was glad I didn't have get to defensive about tuba, you were pretty fair! I remember in college I snagged a "Tubby the Tuba" solo part from a senior, in part because she wasn't able to make enough practices, but also because I was willing to just play it down an octave (hell I've played enough trombone sheets that I barely noticed i was doing that) - but in part , if the damn piece is "Tubby the Tuba", why should it be in that stupid high Euphonium register, as you say.... (that said... well... these days I'm an activist "street player", in it for the fun and not the finesse ) PS I had my reservations about digging up an old contentious thread and knew we'd get some of the same old same old "but if Pitfall 2 did it..." arguments, but I feel some of these tangents have redeemed it!
  10. Sounds like me and "going to the gym" Some great thoughts re "trophy coding accomplishments" and "lowered expectations". I know some of the appeal to me doing JoustPong in 2004 was that you COULD one-person-show the graphics and sound, I had enough pixel doodle and musical background to do an ok job at both, but at the 2600 level and maybe not the NES level. (Interesting seeing how CHAMP games uses a team approach!) Here's what I wrote for "why the atari" back when I made https://alienbill.com/2600/101/ , soon after Joustpong: To connect in a fundamental way with the grandmaster of our misspent childhoods. The challenge of it all. Like writing haiku while drunk and on the back of a charging rhino. Actually, I hate challenges, but there's something cool about making a game out of such simple little pieces, kind of like Legos when they were all square, with maybe a few wheel pieces thrown in. To interact with something you made on a real live TV. The groupies. Ok, I'm kidding about the groupies. Why not program for other, more modern consoles? Despite (or because of) the difficulty of the 2600, there is a community and set of resources for it that I haven't seen for other systems you could potentially homebrew for. (YMMV) Why not just make games for Windows, in VB? Or a more powerful language? Or online, in Shockwave or Flash or Java? Yeah, go on, cry to mama you little wuss! But seriously: most successful modern games are big budget productions done by teams of people. Your program is likely to languish in shareware/freeware hell, ignored by millions, and competing for attention with thousands and thousands of other little games. Make a decent classic game, and you will get a lot of attention from the classic game collectors and their friends. You can even sell copies at shows like CVGE and PhillyClassic, and be duly admired in cash form. (If you work out the hourly rate for your programming efforts, you'd probably be better off flipping burgers, but that's not the point.) So in some ways, some of that is the same kind of "scaled back" stuff you're talking about. Also. Pondering on this question now that you mirrored it, and what I wrote almost 20 years ago I would add: Atari-era games tended to have a focus than the NES era and after: more on motion + physical interaction, vs an emphasis on content and large area exploration. You can still see the old Atari/arcade feel in show up in modern gaming: I think of the perennial Mario Party series, many of the minigames are very much "retro feel in new(ish) clothing". But that's another legit reason to stick on this platform, even beyond nostalgia it is the best home for a certain kind of game interaction - joystick over crosspad, one button and not 2-4. (Also, I think there is something to your "trophy" idea, at least for some coders. Maybe that's some of why batari Basic drove up certain resentment. It made a certain kind of simple game very easy (hell Loaded4Bear was a GameJam weekend, and by getting a good guy on sound and leaning on 2 player fun, it came out ok, IMO 🙂 (later I added AI to it) ) Hey, as a tuba player ( https://kirk.is/tag/tuba ) -- tubas players have the biggest range of all the brass We can play fast and high (though usually we shouldn't)
  11. There's a middle course too, that just wants to make sure there's recognition that it's not a level playing field if you're interested in an accurate view of how much to admire a coder (or, what to admire them for, rather, since it's a different set of challenges and having to learn a wider spread of tech to do a good augmented cart) Of course, if your goal is purely setting expectations of a more fleshed out, detailed game, the scarlet letter would not be of shame but an advertisement of likely extra goodness! yeah, the amended view might be "extra hardware from decades after the retail life of the system is cheating". Or if not cheating, at least a different flavor of challenge for coders.
  12. But, we also said "yes" to progress in the form of whole new systems! So going back to the Atari 2600 as a base is a certain form of "no" - which is why I'm intrigued by people's answers about Why Still Atari 2600, and what if any cart cramming tech advance would make it feel NOT Like Still Atari 2600. Anyway, well put thoughts there, Keatah.
  13. IF THE CART FITS, YOU MUST ACQUIT! (sorry for a very American + 90s reference for a rather 80s gaming system)
  14. For some people who are very aware of the difference, the keyword there is "at the time" You are doing tricks that might have been literally impossible with the technology that was available in the time frame when it was a current system. (and the other question is, are there any limits beyond what you can stuff into a cartridge port... could it have its own rasperberry PI and MAME emulator and own HDMI out?)
×
×
  • Create New...