Subject: Re: [stella]Re: My demo fixed?, PAL, NTSC :-? From: henitrope@xxxxxxxx Date: Wed, 26 Mar 2003 12:28:52 -0800 |
Thank you for your quick response, Zach! :-) Has anybody else also had a chance to check the PAL, NTSC on my demo? - Weston On Tue, 25 Mar 2003 09:42:31 -0800 (PST) Zach Matley <matleyz@xxxxxxxxxxxxxxxxx> writes: > It looks fixed on my TV. Good job. > > On Tue, 25 Mar 2003 henitrope@xxxxxxxx wrote: > > > > > "Z26 counts the number of scan lines before the next frame." > > > > L O L ! That makes sense to me now! I was indeed "braindead" :-D > > > > Thanks for your help Dennis ( and the others who reponded ) ! I > > appreciate it. I actually modelled my VerticalSync routine based > on yours > > in Climber05 so that's why I had a 200 scanline count. Until now, > I > > thought that "43" and "44" were the ONLY magic numbers to use to > set up > > timing! > > > > ( Actually, every hitchiker knows that the answer to everything is > "42" ) > > ;-) > > > > Okay, after another all-nighter, I think I got it working now. In > z26, I > > got both screens to say "262 " lines in NTSC and "312" in PAL > after I > > fixed my constant variables and added more to Overscan. > > > > If you guys out there with CCs or Superchargers can give my demo > another > > whirl, hopefully it works fine now on the real thing. > > The latest is attached above. > > > > Thank you in advance! :-) > > > > - Weston > > > > > > On Mon, 24 Mar 2003 18:42:55 -0500 Dennis Debro > <ddebro@xxxxxxxxxxxxx> > > writes: > > > Hi, > > > > > > > This sounds illogical! My current values: NTSC VBLANK: $01( 1 > > > count X > > > > TIM64T ), IIRC, this gave my 202 lines. I haven't changed PAL > > > VBLANK yet. > > > > NTSC overscan: also $01! > > > > > > So that says your kernel is ~200 scan lines. > > > > > > > VBLANK is supposed to be 43 or 44 x TIM64T, right? So my > current > > > values > > > > should cause the screen in z26 to ROLL, right? > > > > > > That depends. If you're going for a 200 scan line kernel you > will > > > have adjust your vertical blank and overscan lines accordingly. > For > > > example, Climber 5 has 200 scan lines for the kernel. To stay > within > > > the 262 scan lines for an NTSC display I chopped 4 lines off > > > vertical blank and overscan time. > > > > > > > Does z26 show NTSC 192 lines or does it "display" all 262 > lines? > > > > > > Z26 counts the number of scan lines before the next frame. > > > > > > I hope this helps you. > > > > > > Take care, > > > Dennis > > > > > > > > > ------------------------------------------------------------------------- > > --------------------- > > > Archives (includes files) at > > > http://www.biglist.com/lists/stella/archives/ > > > Unsub & more at http://www.biglist.com/lists/stella/ > > > > > > > > > > ------------------------------------------------------------------------- --------------------- > Archives (includes files) at > http://www.biglist.com/lists/stella/archives/ > Unsub & more at http://www.biglist.com/lists/stella/ > > ________________________________________________________________ Sign Up for Juno Platinum Internet Access Today Only $9.95 per month! Visit www.juno.com ---------------------------------------------------------------------------------------------- Archives (includes files) at http://www.biglist.com/lists/stella/archives/ Unsub & more at http://www.biglist.com/lists/stella/
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [stella]Re: My demo fixed?, PAL, Dennis Debro | Thread | [stella] The coolest thing ever wou, Joe Wiencis |
Re: [stella] Brainstorming: 3D-Corr, Glenn Saunders | Date | Re: Re: [stella]Re: My demo fixed?,, Dennis Debro |
Month |