Hi,

> I've been playing SQ3 and ARTHUR with yesterday's CVS. Some bugs I
> found:
> 
> ARTHUR (v1.001):
>  - when starting the intro:
>    FSCI: kDisposeClone: Warning (kscripts.c L245): Clone a44a was
>    cleared with underBits set
[...]

In theory, this might warrant further investigation. In practice, we
should check for whether these underBits are still allocated as well
(this is a neccessary, but not sufficient for having trouble)

>  - at the castle exit, Arthur can walk trough his horse

Filed as #335.

>  - after giving the hunter a coin or when asking him about his spear, 
>    the box with his answer is slightly out of the screen.

Filed as #336.

>  - after you get the spear from the hunter, the game freezes. This looks
>    like bug #294 isn't fixed after all. Thsi makes this game 
>    unbeatable for now.

Could you re-try this one with 0.3.3, please? There is one change that
might have re-opened this bug in CVS.

> SQ3 (v1.018):
[...]
> - when entering the rail pod:
>   FSCI: _k_make_view_list: Warning (kgraphics.c L1849): Warning: new pic
>   or port used within Animate()!

Should be SCIkdebug for SCIkGRAPHICS (gah, those ancient macros have sick
names, but I've grown used to them, somehow)

> - the music is really weird (ossseq, mt32gm, unix): there are very
>   little notes played (<1/minute) and they seem quite random. Some sound
>   effects (e.g. when placing the warp core thing in the ship, or when
>   getting the reactor and turning off the lights) seem to be played ok,
>   though. In some areas the music does play (e.g. after climbing down to
>   the spacecraft), but it stops after saving a game.

Very strange, although part of this could be attributed to out-of-timbres
problems

> - after plotting a course to Phleebhut:
>   FSCI: ERROR in kmem (kernel.c L349): Error: kmem() without a handle (abba)
>   FSCI: graph_restore_box: Warning (kgraphics.c L219): Attempt to
>   restore invalid handle abba

0xabba is text.954, which is not a valid memory resource; the error
messages are correct, this warrants further investigation (could lead to
memory loss -> #337)


Thanks for your bug reports!

llap,
 Christoph


Reply via email to