Disassembler auto-update needs improvements

[Mathieu015]

State your operating system:

Windows

DesMuME version

nightly build (same with 0.9.13)

My issues are (most of them with the auto-update enabled):

• Missing T flag so I don't always need to relie on the auto mode
• Auto-update makes the codes moving a lot. Sometimes, I don't know how or why, it doesn't do that but scrolling with the scroll wheel doesn't work anymore.
• Auto-update doesn't jump to address when there's a jump in the code
• Step and refresh (auto-update disabled), scroll the code up
• Don't know what does it mean when it shows the code highlighted in yellow
• Some graphics glitches

[zeromus]

There is virtually no chance of this ever being worked on again. Shouldn't you be using nocash?

[Mathieu015]

I also have issues with no$gba. Issues that DesMume doesn't have. With Sonic Rush Adventure, I wanted to see how it switches the 3D engine when the game uses 3D for both screens at the "same" time. DesMume has that nice feature to set the LCD's with the main (one using the 3D engine) always on top. No$gba has a vram viewer where I can see what's on Engine A. The part that confuses me is that while it takes Desmume 1 frame to switch, no$gba takes 2-3 frames (1/3 for the intro (with audio issues and some graphics glitches) and 2/2 for bosses).

Besides that, I use both of them. Desmume has a better CPU disassember (have to switch CPUs manually) while no$gba has a better graphics tools.

[zeromus]

You are just trying to figure out the basic approach that the game uses? The code follows trivially from the approach. Isn't there a libnds dual screen 3d sample? Whether the game uses an LCD display mode or giant 2d objs depends on how it's managing the vram.

[Mathieu015]

Yes, there is one. My point was about the frame confusion I have with no$gba. The rest seems good.

[zeromus]

Nocash is probably suffering from a combination of gross timing errors and small mistakes in how the 3d command lists are latched and swapped (partly related again to timing). I wouldn't infer anything about how dual screen 3d works from that. The libnds samples should be doing it right.