Path: chuka.playstation.co.uk!scea!peter_alau@playstation.sony.com From: Gerrit Goossen Newsgroups: scee.yaroze.beginners Subject: Re: Still strugglin' with the basics: broken sprite code (long) Date: Wed, 15 Jul 1998 23:06:05 -0400 Organization: SCEA News Server Lines: 27 Message-ID: <35AD6DE7.11E5@funnytown.com> NNTP-Posting-Host: 38.165.241.13 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.01-C-MACOS8 (Macintosh; I; PPC) >What happens is that when I run the program I get the Yaroze boot-up screen, then the screen flashes briefly before returning to the boot- >up screen. > >What's weird is that in Codewarrior, if I change my data address >in Linker Settings from the default 0x00000000 to 0x80140000, I get a >very large (700K) executable, except this time the screen goes black >and I get a line of garbage along the bottom. Maybe some techies have a different opinion, but it's probably a wise idea to leave the data address at 0L and let the linker figure things out for you? As for what's going wrong, have you explored the Metrowerks debugger at all? There's a handy panel that will let you back-trace through the stack which can help you figure out which function is dying. BTW, I agree with Alex; If you backtrack a bit I'm sure you'll find "GsSortFastSprite" is dying because your OTTags are stored locally and disappearing before you use 'em. Of course because it's such a small app., the code *might* still run fine if nothing writes over where the local variables "used" to exist. (I guess CW does a little more clean-up than GCC :) - Gerrit PS - IMHO, 9 times out of 10, CodeWarrior is the best way to develop applications for any platform. Yaroze included.