Item dirkwhoffmann/vamiga#827 discusses implementing a memory heat map feature for vAmiga. Implementing such a feature for VirtualC64 is much easier due to the simpler memory layout. Consequently, I think it's best to start with VirtualC64 and implement it later for vAmiga if it turns out to be a success for the C64.
Here is the plan:
Count all memory reads and writes. Since the address space is only 64KB, we can record the information for each address separately.
Ask the new Heatmap class to update the heat map at the end of each frame. The class will maintain a 256x256 texture similar to this one:
The GUI can grab the texture for preprocessing (e.g., apply a Gaussian blur filter) and superimpose it onto the emulator texture with some transparency effect (similar to the existing DMA debugger).
My goal is to integrate the feature into VirtualC64 5.0b1, which is approaching the finish line.
Item dirkwhoffmann/vamiga#827 discusses implementing a memory heat map feature for vAmiga. Implementing such a feature for VirtualC64 is much easier due to the simpler memory layout. Consequently, I think it's best to start with VirtualC64 and implement it later for vAmiga if it turns out to be a success for the C64.
Here is the plan:
My goal is to integrate the feature into VirtualC64 5.0b1, which is approaching the finish line.