TheHoboInYourRoom

This page has a chart that even includes the illegal opcodes.

No, I don't. I'm not very skilled at programming the VCS, plus Jinroh is the only one who has access to the source code. I'm just bringing the framerate issues (which are quite hard on the eyes) to his attention.

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.

Oh wow, I forgot I'd even made this thread. That's pretty cool to hear! Thanks for sharing.

Awesome!

I'm excited already! My two cents is that I'd prefer a transfer method that doesn't require extra hardware. Do you plan to release the PC-side software under a free software license? It'd be better that the code not be restricted to just one or two operating systems.

You can click the "[source]" links on their Pouet pages: TIM1T http://www.pouet.net/prod.php?which=62944 Ascend http://www.pouet.net/prod.php?which=64492

If you listen closely, there's already a slight rumble when the robots burst.

Wow, this is good. This is definitely a game that you can get into the zone with. It works well in Stella with a DualShock-type USB controller.

The ISC license is compatible with the GPL, though. http://www.gnu.org/licenses/license-list.html#ISC

I'm a bit late, but the homebrew game Omicron has a twinstick firing mode.

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.

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.

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. TIM1T.st0.txt

You might not still need this, jp48, but anyone else who's interested can find transmat's source code from its pouet.net page: http://www.pouet.net/prod.php?which=61492

Yeah, that's what I did. I'll take a look at the code sometime later and see if anything hinky is happening to SWACNT.

Amazing! Thank you very much! This isn't a very big deal, but when I run Coke Zero (from the Harmony Cart menu) while my AtariVox is plugged in, the program sends it some spurious sound data that subsides after a few seconds.

This looks cute; cute is good. I notice the title screen has 10 sprites above and below the logo. I'm guessing you strobed the RESPx registers Galaxian-style to get more sprites?

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

My apologies.

I already know about generating the sync signal. My intention is to blank the display when the sample plays, like how Quadrun does it. As it happens, I added the CLEAN_START macro from macro.h to the beginning of my code, and the updated version actually works as intended now.

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)? scanrate.asm scanrate.bin