Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#165 closed bug (invalid)

Busy.mcc speeds

Reported by: Mikhail Malyshev Owned by:
Priority: normal Milestone: 4.0-2015R2
Component: Busy.mcc Version: 4.0-2014R5
Severity: minor Keywords:
Cc: OS Platform: AmigaOS3
Blocked By: Blocking:
Release Notes:


The speed setting is somewhat limited compared to what it used to be.
eg. For me anything faster then 20ms is running at same speed.
Previously Wow! and 1-5 ms speed were very fast.

Something wrong with timing ?

Change History (3)

comment:1 Changed 6 years ago by Thore Böckelmann

Priority: undecidednormal
Resolution: invalid
Status: newclosed

There is nothing wrong with the timing. It just your machine that is too slow.

The timing for the graphical update is done by a simple MUI input handler with the desired timing. If the redraw takes longer than the desired interval there is nothing that can be done against this. This is the limiting factor on how fast the movement can be done. If the system is able to do the full redraw within less than a millisecond, then "Wow" speed is possible, otherwise it isn't.

I tried the old 68k Busy.mcc myself on my WinUAE/AmiKit setup and even that version cannot redraw itself at 1ms = 1000Hz frequency.

comment:2 Changed 6 years ago by Mikhail Malyshev

It's not slow and refreshing a few pixels does not take much resources.
It does not refresh at wow speeds of course (the screen refresh is 100Hz here), but still it is different to original.

  1. It is slightly slower, not a big deal.
  1. The drawing routine is different! And this can be easily seen on the OLD style zebra busy mode. (on others too but not as vivid)

You can actually see the scanline drawing effect (some flicker)
while the original does it very smoothly, as if it is double buffered, but I believe it is not, so some other trick is used.

comment:3 Changed 6 years ago by Thore Böckelmann

Milestone: 4.0-2015R2

The current nightly build has double buffering enabled. This should fix any flickering. But of course this slows down rendering a little bit more due to the additional final blitting. This is all I can do for you.

Note: See TracTickets for help on using tickets.