Notes |
|
(0009546)
|
Wepl
|
2021-02-08 13:38
|
|
Degrading is the task of WHDLoad. So this should not be a slave issue. |
|
|
|
The slave doesn't have anything to do with disabling RTG screen so there is nothing I can do here. |
|
|
(0009548)
|
Wepl
|
2021-02-08 16:18
|
|
@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 |
|
|
|
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. |
|
|
(0009551)
|
Wepl
|
2021-02-09 09:26
|
|
Do you use P96 as RTG system? |
|
|
(0009560)
|
Wepl
|
2021-02-11 23:18
|
|
You could set option TRACE and attach the created file .whdl_trace for further analysis. |
|