When "trace" is enabled for SuperFX code, the generated trace log doesn't print out the state of the relevant RXX registers. The debugger window already does this when stepping though SuperFX code, so I'm not sure why the trace log doesn't have this information.
You can't set breakpoints for when the RXX registers are read/written to on the SuperFX bus. You can on the S-CPU bus using $3000-$301F as the start address, but that only applies when the SNES CPU reads those addresses. But, that doesn't help when trying to figure out something that's deep within a SuperFX routine.
These two issues combine to make it a nightmare to debug SuperFX code.
When "trace" is enabled for SuperFX code, the generated trace log doesn't print out the state of the relevant RXX registers. The debugger window already does this when stepping though SuperFX code, so I'm not sure why the trace log doesn't have this information.
You can't set breakpoints for when the RXX registers are read/written to on the SuperFX bus. You can on the S-CPU bus using $3000-$301F as the start address, but that only applies when the SNES CPU reads those addresses. But, that doesn't help when trying to figure out something that's deep within a SuperFX routine.
These two issues combine to make it a nightmare to debug SuperFX code.