<No update on emulation. >
Increased the instruction cache rate menu item in the simulation model settings.
...
In the past, I used to say, "Since movies are repetitive routine processes, they are easily programmed on the assumption that the instruction cache hit rate is high.
Therefore, there are cases where the number of clocks required per instruction, or in XEBRA terms, the instruction cache rate should be set to a small value.
On the other hand, the CD-ROM that is the source of the movie is not a CD-ROM, but a CD-ROM that is a CD-ROM.
On the other hand, data transfer from CD, which is the source of movies, may occupy main memory for a long time.
If the instruction cache is not hit at that time, the CPU will be stopped for a long time.
The number of clocks required per instruction may become significantly large.
Considering this phenomenon, the Stall Rate (CD-burst) should be changed.
However, it is also possible to replace it by increasing the instruction cache rate to a significantly higher value.
In other words, there are cases where the instruction cache rate should be increased even when dealing with movie freezes.
Since 0x28 was found to be insufficient in some cases, the instruction cache rate can be directly specified up to 0x30.
Incidentally, the number of clocks required per instruction is always set to 1, and even if you consider that the number of clocks required per instruction changes only with the CPU clock frequency, the effect will be the same.
The same effect can be obtained by assuming that the number of clocks required per instruction is always 1 and only the CPU clock frequency changes.
The name of the function may have been intended as a mere fun feature, but it turned out to be an alternative to a real phenomenon.
However, the result is a piece from a gourd that substitutes for a phenomenon that occurs in reality.
