Path: chuka.playstation.co.uk!news From: "Peter Armstrong" Newsgroups: scee.yaroze.freetalk.english Subject: Re: negative scrolling on homebrew map routine - need help!! Date: Wed, 21 Mar 2001 19:53:09 -0000 Organization: PlayStation Net Yaroze (SCEE) Lines: 64 Message-ID: <99b11c$cia1@www.netyaroze-europe.com> References: <3AAF7BB2.B427AED3@harbinger.com> <98o38v$ij81@www.netyaroze-europe.com> <98p3qp$rms2@www.netyaroze-europe.com> <98t840$6f5@www.netyaroze-europe.com> <99057g$3ok7@www.netyaroze-europe.com> <3AB6404F.65C9AF1C@harbinger.com> <9961fn$7jl4@www.netyaroze-europe.com> <99624q$7jl5@www.netyaroze-europe.com> <9963bb$7jl6@www.netyaroze-europe.com> <997j6l$7jl8@www.netyaroze-europe.com> <3AB774C7.6B4D8F95@harbinger.com> <998bjc$7jl11@www.netyaroze-europe.com> <3AB8A751.A5D36CCF@harbinger.com> <3AB8DFBA.7BDE2A4E@harbinger.com> NNTP-Posting-Host: host213-122-194-232.btinternet.com X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 "Andrew Partington" wrote in message news:3AB8DFBA.7BDE2A4E@harbinger.com... > Hang on - I think I know why i'm having problems setting the stack to point at the > DCache: > > I was browsing the member homepages and I came across Andreas Schrattenecker's page > - he did something similar, but he was using a couple of global variables to store > the stack pointer in, instead of trying to dump it straight on the stack like the > thick git that I am :-P > > Andreas reckons he's getting a 400% speed increase under CW, negligable speed > increase under GCC - is GCC really that much better when it comes to producing > optimal code? I've been trying to set the stack pointer to the d-cache but havent been having much luck. All my tests have been within the debugger, which seems to have a problem with the new stack pointer. After your post I tried the program in PSComsUtil and it runs fine. Despite the new stack value in the target settings the ny.pxe file still has it's stack set at the default 801FFFF0. I changed this to point to the d-cache and the program runs but in siocons it won't return to the brick screen. CW code does seem to be a little slower than GCC code, I've not really done any proper comparisons but in one instance the GCC compiled code was around 10% faster than CW. > > Thanks Peter, that worked 100%! But now I can't see how many HSyncs/frame I am > > getting - is there any way I can get my VSync(0) value back using callbacks > > without causing another wait for vertical retrace? (calling VSync with values > > greater than 0 doesn't seem to return anything useful) VSync(1) does still appear to return the hsync count, it's just its counter is no longer reset. If you add the relevant lines from the following code you should get the same timing value as before. DrawSync(0); timer = VSync(1) - timer; FntPrint("timer %d\n",timer); wait = 1; while(wait == 1); wait = 2; timer = VSync(1); Regards, Peter