> ] It certainly changed my opinion on that game. But XAK2 overall was very,
> ] very slow (XAK 3 too). I never finished those. The reason why they load
so
> ] much by the way is because most Japanes MSX computers had only 64k.
>
> XAK3 has a nice feature for on the MSX turbo R: it uses the memory mapper
as
> a diskcache.
Errm... isn't that the whole idea of the phenomenon "diskcache"??? What else
should cache the disk besides the mapper???
And I haven't got a turboR. So it's really nice to hear but too bad...
> Therefore, you only have to wait only onces for a scene or
> whatever to be loaded. It really increases the gameplay. Furthermore, XAK3
is
> not slow on the TR. It seems like having the R800 in stead of the Z80 can
be
> an advantage even for RPGs (I think that they pre-render a lot of the
> animations, etc. in memory in stead of in vram...)
XAK is just slow because it's very badly programmed, as all MicroCabin games
are. Look at YS2 (which even has multiple layers and lots of animations) and
agree with me please...
> I wonder how a game like
> XAK 3 would look on a system where the CPU can directly access the vram...
Probably still slow.
~Grauw
--
>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<
email me: [EMAIL PROTECTED] or ICQ: 10196372
visit my homepage at http://grauw.blehq.org/
>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED]
and put "unsubscribe msx [EMAIL PROTECTED]" (without the quotes) in
the body (not the subject) of the message.
Problems? contact [EMAIL PROTECTED]
More information on MSX can be found in the following places:
The MSX faq: http://www.faq.msxnet.org/
The MSX newsgroup: comp.sys.msx
The MSX IRC channel: #MSX on Undernet
****
