Cet émulateur est également le plus complet des outils de développements X68000 existant aujourd’hui. Il s’agit d’un fork de l’émulateur XM6 v2.05 de PI avec une pléthore de nouvelles fonctionnalités. Les changements sont pour la plupart liés à l’interface utilisateur et un accent a été mis sur le développement et les fonctions de débogage plutôt que sur l’exactitude de l’émulation, cependant il y a suffisamment d’améliorations pour qu’il soit recommandé d’utiliser cette version plutôt que XM6 v2.06 finale.
Les changements:
– You can now toggle the status bar by double-clicking its left side
(or the approximate area where it would be, if it is currently off).
– You can now toggle the menu bar by double-clicking its right side (or the
approximate area where it would be, if it is currently off, in window mode).
– You can now drag the main part of the window (known as the client area)
if the caption bar is turned off. This feature was added because most people
don’t know how to move a window lacking a caption/title bar. Because it makes
it a little too easy to move the window, it is unavailable while the title bar
is present. (Did you even know you could disable any/all of the three bars?)
– If the window or full-screen display falls short of the VM screen height
by a small margin, the bottom of the VM video frame will be truncated
rather than shrinking it to fit the available window/screen.
– For example, suppose your monitor has a height of 1024 pixels and you are in
full-screen mode. With the status bar enabled, the usable height is reduced
to 1004. Then suppose you run a game that displays a 768×1024 (interlaced)
loading picture. Previously, said picture would be shrunk by a factor of 0.98
in order to fit, which looks ugly. But with this new feature, the bottom 20
pixels will simply not be displayed such that the remainder of the picture
will be undistorted.
– In the above example, if you were to remove the status bar (View > Status Bar)
then the entire 1024 vertical span would be available and truncation would not
be performed. This is optimal, but toggling the status bar can be inconvenient.
-Also note that the View > Win32 > Bitmap subwindow will show a less-than symbol
if truncation is in effect. It will also show the ratio that would have been
used (absent truncation) in parentheses.
– If it looks like something is missing on the bottom, you could try toggling
the menu bar (window-mode only) or status bar, either of which will increase
the height enough to overcome any truncation. Situations where the truncation
feature apply are rare, and even when it does apply, it is unlikely that
anything important would be hidden.
– This feature has no effect on screen shots – they always save the entire frame.
– The resolution-changing feature has been restored even though apparently
nobody uses it. If it weren’t for my policies, I’d remove it entirely.
– There is also a new setting (see the View menu) that blocks changes
to your primary display, so you will need to disable that safeguard
if you only have one monitor/screen and you want to use low-rez mode.
– Furthermore, it no longer tries to change the vertical refresh rate,
because you might have a TV connected and configured for 59.94 Hz
but the API only supports integers (e.g. 60 Hz). Maybe that’s not
really an issue, but 800×600 is so low these days it’s better to
just accept the recommended frequency instead of specifying one.
– Eliminated some graphical garbage during resets and state loading. Not a bug.
– The Smoothing menu item is now disabled at times when smoothing is inapplicable.
– The graphics section of the manual has been revised.
– Double-clicking menu bar items (which is supposed to select the default submenu
item shown in bold, if any) now works more reliably. If there is no default,
the menu bar will now be deactivated instead.
– The driver-bug workaround used in the previous release was resulting
in major slowdown if the client area was obscured, even by menus.
This slowdown was another driver/API defect. A new workaround was
discovered that resolves both issues and more (see below).
– The following item from the trouble-shooting section has been resolved:
« Graphical shimmer or vertical ‘waving’ is visible in some games »
The workaround mentioned above fixed this driver/API defect as well.
Incidentally, there were two completely different sets of hardware
and associated drivers that were involved in all of these problems.
Also, these are not « bug fixes » because this program was not at fault.
Bug fixes:
– Additional casualties scored in the ceaseless war on user interface defects.
– Contrast fading was continuing while paused in rare situations (my fault).
– It was possible for the mouse wheel to switch to the same mode in certain cases.
– It was hypothetically possible for the mouse wheel to fail to activate
full-screen-maximum mode under certain circumstances.
– Full-screen transitions were inesthetic under certain configurations.
