2024-05-21 06:30 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0006339SecondSamurai[WHDLoad Installs Games] slavepublic2023-12-25 18:32
ReporterSCO 
Assigned ToStingRayProject InfoSecond Samurai (Psygnosis/Vivid Image)
http://www.whdload.de/games/SecondSamurai.html
 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionno change required 
Summary0006339: After finishing the final boss of the game, the credits scroll and ending never triggers.
DescriptionIn the longplay at the end at https://m.youtube.com/watch?v=JeF2oYKlj7c

after the boss, the game asks for disc 3 and shows credits and a ending sequence.

This never triggers in the most recent retroplay install, the credits never happen (or the disc change request but that's supposed to never happen in whdload)
Steps To ReproduceI enabled all life, energy and weapons cheats and the secondary jump button, if it matters, then played through with puae in the 1200 configuration until the end with savestates.
TagsNo tags attached.
MachineA1200
CPU68020
CPUSpeed50
ChipSetAGA
GFXCardNone
ChipMem2 MB
FastMem0 MB
WorkbenchOS 3.0
KickROM40 - Kick 3.1
KickSoftNone
WHDLoad18.9
imported
Attached Files

-Relationships
+Relationships

-Notes

note ~0013430

SCO (reporter)

Wait, I'm a idiot, i used the normal 1.3 install with the automatic puae system, and it defaults to 1200 on 'not a floppy' which lha archives arent. If the game for 1.3 was supposed to work in amiga 1200 3.1 this is a bug, if it wasn't, it might not be.

note ~0013433

SCO (reporter)

On the other hand, whdload is supposed to install to a hd, and only the a1200 and a600 came with it iirc. So I think it doesn't make sense to make a whdload install that only works in a500? Whatever, the retroplay install where this happens is 'SecondSamurai_v1.3_0721.lha'

note ~0013456

StingRay (developer)

I have successfully tested the complete game when I updated the patch, please eliminate the too many unknown factors (i.e. test it on a real Amiga or on an emulator with the correct settings), if the problem still occurs in that case, you can reopen this ticket.
+Notes

-Issue History
Date Modified Username Field Change
2023-12-12 13:38 SCO New Issue
2023-12-12 13:46 SCO Note Added: 0013430
2023-12-13 08:59 SCO Note Added: 0013433
2023-12-25 16:30 JOTD Assigned To => StingRay
2023-12-25 16:30 JOTD Status new => assigned
2023-12-25 18:32 StingRay Note Added: 0013456
2023-12-25 18:32 StingRay Status assigned => resolved
2023-12-25 18:32 StingRay Resolution open => no change required
+Issue History