Description
Currently using Bizhawk 2.8 latest stable release for doing some TAS'ing projects. I'm using the Bizhawk's tool, called Trace Logger.
According to this code here:
The Bizhawk trace logger uses the mGBA disassembler to generate the trace log messages, hence this ticket is reported here.
What I've noticed in the Trace Logger, whenever I wanted to log the disassembler's operands that occurs within a single frame using the mGBA core, I've noticed that some decimal values are always showing up, despite that all other values are formatted in hexadecimal values.
For instance:
00000128: E3A00301 mov r0, #67108864
... some other operands ...
03000068: 1A000008 bne 0x03000090
... some other operands ...
08032190: B083 sub sp, #12
#67108864 is actually 0x04000000 in hexadecimal value.
Some instructions like mov uses decimal numbers when logging, while other instructions use hexadecimal numbers. It makes reading the trace logs inconsistently unhelpful because I have to manually convert the decimal values to be hexadecimal values when I need to actually look into what values are put into certain registers and whether they do bit masking in some areas.
I believed there might be benefits for using decimal numbers in the instructions' operands, therefore this feature request is a request to allow the option to toggle a setting that would convert all decimal values to hexadecimal values during log tracing in the disassembler.