mupen64plus debugging 101?

[Dorian Fevrier]

Hi all!

I'm still working on the refactoring of Rice to use a more "modern"
OpenGL approach (and so, will be easier to put in OpenGL ES).

I must confess I almost gave up when I saw how many troubles the
refactoring was providing. So many weird regressions, mainly due that
Rice use a lot of old command (and a old renderer code paradigm) that
make the new Color Combiner (fully GLSL now) redondant at some points
(alpha cutof, alpha blending, etc...) and put the mess everywhere. But
taking problems one by one, I tent to solve them (slowly but certainly)
and I continue my investigations. It will still took a lot of time as
cycle Fill and Copy was using the old OpenGL that doesn't work at all
anymore, and so, need an update to use the GLSL Color Combiner. Lot of
work in perspective...

Anyway, I would like to know if mupen64plus provide debugging tools. I
would like to see what the N64 is trying to do. Something like this:

https://3.bp.blogspot.com/-DoqzJc3Fh14/UFo7G02M-OI/AAAAAAAACFU/DV8JKVnE57I/s1600/dld1.png

I don't need the UI but the list of gbi commands before each draw would
be awesome.

Any idea how to achieve this? Any informations is welcome. :)

Regards,

Dorian

[Richard Goedeken]

Dorian,

Didn't you remove a bunch of old unused Rice debugging code which provided
information similar to this? I think all of this debug info needs to be
logged by the video plugin, because it's the one which parses the display lists.

Richard

[Dorian FEVRIER]

Hello Richard,

I keep the debugging stuff because messages and string used in code really help.

For now I mainly use printf which is highly verbose and can't be stopped

I was mainly thinking about a breakpoint system so I could stop the emulator at each draw call and see what happen (some triangles are not shown at all and I would like to investigate the state of the RDP at this moment).

Glid64 had a wonderfull debug stuff: https://code.google.com/p/glidehqplusglitch64/issues/detail?id=7

I don't really need that, I just would like to list the various ucode used and be able to stop the emulator.

Maybe GDB is just what I need? But as I saw mupen64plus seems to have debugging API I was curious. :)

Thanks in advance!

Regards,

Dorian

--
You received this message because you are subscribed to the Google Groups "mupen64plus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mupen64plus+unsub...@googlegroups.com.
To post to this group, send email to mupen...@googlegroups.com.
Visit this group at http://groups.google.com/group/mupen64plus.
For more options, visit https://groups.google.com/d/optout.