<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>
Date   : Tue, 19 Mar 2002 23:28:43 +0100
From   : "Isabel Cisternas & Robert Schmidt" <rschmidt@...>
Subject: Re: my previous post

Hmm...
could it be an idea to post a "BeebEm option walkthrough/FAQ" on your site?
My guess is that something is not right with DirectDraw on the systems the
report problems, or that they don't use DirectDraw.
Another option: from my own tinkering with BeebEm a few years back, I
noticed that blitting the Beeb screen to video RAM through the GDI was a
*lot* slower when a non-integer scaling was applied.  Could the bitmap
scaling be off by a few pixels so that an interpolating scale is needed,
which might not be optimized properly on some drivers?

I did manage to make BeebEm run at about 6 fps on my 900 MHz P3 with
Geforce3, by turning OFF DirectDraw, and selecting the largest window size
or full screen (which is more like a window filling the screen).  The moment
I enable DirectDraw, it flies, regardless of window size/full screen.

I've also noticed that using "buffer in video RAM" makes the real-time speed
adjustment unstable.  It seems to cycle between too fast and too slow.

For completeness, users should also try disabling sound and joystick
support:  joysticks can be time consuming to read on some systems (the ones
connected to the parallel port have to be polled very frequently - even by
DirectInput)

I hope this helps anyone...

Cheers,
Robert


----- Original Message -----
From: "Richard Gellman" <r.gellman@...>
To: "BBC Micro Mailing List" <bbc-micro@...>
Sent: Tuesday, March 19, 2002 10:40 PM
Subject: [BBC-Micro] my previous post


> My apologies if that sounded harsher than it should of done.
> And it was not specifically aimed at Tom Walker
>
> But the problem remains, I really cannot understand why so many people
have
> speed problems in such illogical ways.
> 1.4Ghz is twice as much as 667Mhz, but from the reports i get from varying
> sources, you'd think 1.4GHz = 667Mhz x 0.25
>
> It doesn't make sense to me at all, and i re-itterate I have never had any
> speed issues with it, and since 1.3 I've had a change of motherboard and
> processor.
>
> Again, my apologies if I sounded a bit harsh there.
>
> -- Richard Gellman
>
> <Serious bit>
> This email is sent to you as personal communication or to a specific
mailing
> list ONLY, and does not contain any form of comercial advertsing (spam).
By
> replying to this email you legally agree that you will honour this in a
> similar fashion, and you will not send any commercial email to this email
> address, or subscribe this email address to any mailing list without prior
> permission. Failure to adhere to this may result in criminal prosecution
> under the misuse of information laws applicable in all countries.
> <end of serious bit>
>
<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>