2024-07-13 15:41 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0005007Crusaders_AudioX[All Projects] Generalpublic2021-02-11 23:18
Assigned ToStingRayProject InfoAudio X (Crusaders)
StatusresolvedResolutionno change required 
Summary0005007: I think the 1.1 slave isn't fully disabling the RTG screen before launching the
DescriptionGameVersion: english,pal,2 disks
SlaveVersion: 1.1 latest

I think the 1.1 slave isn't fully disabling the RTG screen before launching the demo, and maybe the RTG driver's interrupt is causing trouble. Just changing workbench to a non-RTG mode fixes it here.
Problem shows in MiST, TC64 & MiSTer Minimig with RTG enabled.
1.0 slave does not exhibit this issue.
TagsNo tags attached.
ChipMem2 MB
WorkbenchOS 3.9
KickROM46 - Kick 3.1.4
Attached Files



note ~0009546

Wepl (manager)

Degrading is the task of WHDLoad. So this should not be a slave issue.

note ~0009547

StingRay (developer)

The slave doesn't have anything to do with disabling RTG screen so there is nothing I can do here.

note ~0009548

Wepl (manager)

@raparici please describe what the problem is with the new slave, if there is a WHDLoad error requester make a CoreDump and attach the .whdl_register here

note ~0009549

raparici (reporter)

There is no whdload error requester. The demo just enters in a sound loop at the start.

V1.1 of this whdload fails to run the demo when launched from specific RTG configurations. The demo starts but the music loops the first couple of seconds infinitely. There is no problem when the whdload is opened from a non RTG screen mode neither was in the previous whdload 1.0 no matter the screen mode you open the whdload from. The RTG systems that conflict with 1.1 whdload are MiST, TC64, MiSTer and probably FPGA Arcade. Other RTG systems like Vampire didn’t conflict with 1.1 whdload of this demo. This is a very strange case, I have seen nothing like this before.

note ~0009551

Wepl (manager)

Do you use P96 as RTG system?

note ~0009560

Wepl (manager)

You could set option TRACE and attach the created file .whdl_trace for further analysis.

-Issue History
Date Modified Username Field Change
2021-02-08 13:34 administrator New Issue
2021-02-08 13:34 administrator Status new => assigned
2021-02-08 13:34 administrator Assigned To => StingRay
2021-02-08 13:38 Wepl Note Added: 0009546
2021-02-08 15:31 StingRay Note Added: 0009547
2021-02-08 15:31 StingRay Status assigned => resolved
2021-02-08 15:31 StingRay Resolution open => no change required
2021-02-08 16:18 Wepl Note Added: 0009548
2021-02-08 17:03 raparici Note Added: 0009549
2021-02-09 09:26 Wepl Note Added: 0009551
2021-02-11 23:18 Wepl Note Added: 0009560
+Issue History