[Openmsx-bugs] [ openmsx-Bugs-2952500 ] Screen update lags too much when running on step-by-step

[SourceForge.net <no...@so...>]

Bugs item #2952500, was opened at 2010-02-16 00:09
Message generated for change (Tracker Item Submitted) made by sd-snatcher
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=421861&aid=2952500&group_id=38274

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Graphics
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: FRS (sd-snatcher)
Assigned to: Nobody/Anonymous (nobody)
Summary: Screen update lags too much when running on step-by-step

Initial Comment:
When openMSX is running on step-by-step mode, the acuracy=pixel doesn't seem to work properly. The screen is updated with an enormous lag from the CPU writes. It feels like the frameskip is set to a high value, even if maxframeskip is set to zero. This is very bad for debugging, as one would hope the excellent accuracy=pixel should work as good as it does when the emulation isn't debug-breaked.
Curiously enough, the accuracy=pixel works fine even with set speed=1 (which means 1% of the real emulation speed). So I wonder why doesn't it work correctly when using "debug break" and "debug step"



Tested with:

open0.7.2-dev11023
Mac OS-X v10.5.8
renderer=SDLGL-PP
maxframeskip=0
z80_freq_locked=on
r800_freq_locked=on

Emulated machines tested: Panasonic FS-A1ST, Panasonic FS-A1WSX, Sony HBD-F1XDJ, Panasonic FS-A1F


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=421861&aid=2952500&group_id=38274