>On May 18, 12:22pm in "The Hog's Back! And this time, he ain't happy!", you >warbled: >] Um, last night I thought I'd try and stick an E-tune on top of my star-field, >] and I had been warned that it would probably go over the 1 frame rate at the >] end of every pattern. But mine just seemed to jump all the time, odd huh? >] (not really, just bad coding on my behalf) > > Jump all the time... now ain't that strange? :-) > >] Originally I had the E-tune at (65536+16384) and my starfield routine at >65536, >] but this just crashed when I called it (god knows why), so I put the E-tune >] in another page, and paged Hi-Men from the screen to the E-tune every frame, >] called it and paged it back. Anny ideas what is happening? I'm pretty sure my >] routine ain't at fault, as it ticks over quite speedily. > > Probably the e-tune code needs to be in page C. This is just bad coding > for such a simple piece of code. Whoever wrote it needs to re-write it.
Is sticking it in page C a universally accepted standard amonst demo coders then? And call me Mr. Thicky but page C is 49152-65535 right? Urg, I am beginning to hate coding (and I ain't even started properly yet. :) ) >] (I am using the Index Register though, is this a particularly slow register?) > > Yes, very much so. Don't use it, if you can help it. That shouldn't be too hard. > Geoff Thanks, Graham
