Jump to content

TheHoboInYourRoom

Members
  • Content Count

    416
  • Joined

  • Last visited

Posts posted by TheHoboInYourRoom


  1. Um... the demo is almost unplayably jittery. The framerate is not stable at all. Every screen transition jumps to a new number of scanlines. The picture jitters everytime the screen scrolls, very slightly when the fireball in the castle flies up, and also very slightly whenever Jinny's shots are on screen. Using the scanline counter in Stella, I see the demo never settles on 262 lines per frame. All of this also happens on real hardware.


  2. Two, a long-rainbow Junior and a 4-switch Woody. I haven't used the Woody for a while because one of the controller ports is dodgy and needs replaced, plus I don't have room to connect it.


  3. Oh wow, I never knew score mode worked that way. I don't have a PAL monitor or PAL Atari, but I looked at the footage from the Revision 2014 Oldskool Demo compo, and sure enough the blockiness is actually there.

    Never mind, then, I guess. :)


  4. I discovered a weird regression in graphics behavior while rewatching TIM1T (http://www.pouet.net/prod.php?which=62944). It shows up in the credits sequence about 2 minutes 44 seconds in (savestate attached; just remove the .txt extension). I hadn't updated Stella since 4.6.7, but I've checked earlier versions and this bug first appeared in 4.7.

     

    The attached images show the expected behavior in 4.6.7 (first) and the bug in 4.7.1 (second). The playfield appears to have priority over P1 and M1 on the lefthand side of the screen, but the program doesn't touch CTRLPF during the credits. TIM1T is F4-bankswitched and the checkerboard rendering happens in bank 6 in two routines starting at addresses $DA02 and $DB02. Very strange.

    post-6010-0-38787100-1457164581_thumb.png

    post-6010-0-26943800-1457164599_thumb.png

    TIM1T.st0.txt


  5. You will run into trouble on so some modern TV's if you blank the display and let go of handling VSYNC. I have a Toshiba 55" LED TV, and when it looses sync it mutes the sound. There is no setting to stop that. I discovered this when I was testing iesposta's speech strings for the Dr Who hack of Berzerk. I would see a black screen with no sound, and then the gameplay would return. Ultimately We went with a kernel that blanked the screen while still keeping sync to solve the problem. If you're updating the audio every line, or every second line, then it is easy to do. Dr Who was a little more work as it was every 4 lines, and 262 is not divisible by 4. I didn't want to do 260 or 264 line game. I've read of some TV's rolling while being off by only 1 scanline. It's best to do things to maintain maximum compatibility whenever you can. :)

    Well, you've convinced me. I'll find a way to include VSYNC.


  6. I know that sample playback is not exactly "for newbies", but I'm having some trouble even getting started with it. I decided to push out a sample on every scanline, so I threw together the attached program to put out a square wave and confirm that I'm on the right track (also to directly measure the NTSC Atari's HSync frequency, but I've already found the answer to that question). It works in Stella, but when I run it on my real VCS, I hear a tiny beep and then my TV completely loses sync (photo attached). I should note that Pitfall II and DPC+ audio demos do actually work on my TV.

    Stepping through the code in Stella's debugger, the write to AUDV0 is taking effect on the third cycle of every scanline. So my questions are:

    - When is the earliest safe time to write to AUDVx?

    - What part of the TV signal is being interfered with (if anyone knows)?

    post-6010-0-08373200-1452674401_thumb.jpg

    scanrate.asm

    scanrate.bin


  7. Cool.

    So, putting together what I've learned from all the links I've followed, I could fashion my own USB adapter with, say, one of these cables (http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm) with the TX and CTS signals on pins 1 and 2 as shown here, and use FT_PROG to invert CTS, turn off high-current IO, and allow up to 100 mA from the bus. Am I missing anything?

     

    EDIT: I already have a copy of an "Avox_USB.xml" programming template that was posted some time ago.


  8. Before I forget to ask:

    Besides the USB adapter specifically designed for the Atarivox, are any other USB-to-serial adapters known to be compatible with it? I'd assume something with an FTDI chipset would be a pretty good bet.

     

    Also, Richard, what software was included in the AtariVox_utils package?

     

    Thanks for your help, everyone.


  9. Okay, I managed to find driver code and docs from July 2005, which I guess corresponds to AtariVox_docs.zip in the manual. I also found a static allocation table from 2011 (last entry is Indenture). I did not find (or just not recognize) anything corresponding to AtariVox_utils.zip.

    Has anything major been added to the driver in the past 10 years? What's been added to the static allocation area in the past 4?

×
×
  • Create New...