Best practices to debug a geometry shader?

[ryan47]

Recently, I ran into a motion vector problem in my geometry shader.
I tried to dump the resultant mi file with mi_api_debug but got no luck.
Would it be possible to use mi_api_debug if I use obj callback for a placeholder?

Besides, would you guys please kindly share your own experiences in debugging for geometry shaders?
Any idea is welcome. Thank you all!

Ryan

[gunter]

Hi Ryan,
the geometry can easily be dumped, here is a fragment:
FILE * fp = fopen("/tmp/debug.mi", "w");
miEchoOptions opt;
memset(&opt, 0, sizeof(opt));
mi_geoshader_echo_tag(fp, tag, &opt);
fclose(fp);

In the fragment above your result tag is passed, which can be an object, group etc.
Quite useful is also the -echo command line option.

Gunter

Recently, I ran into a motion vector problem in my geometry shader.
I tried to dump the resultant mi file with mi_api_debug but got no luck.
Would it be possible to use mi_api_debug if I use obj callback for a placeholder?

Besides, would you guys please kindly share your own experiences in debugging for geometry shaders?
Any idea is welcome. Thank you all!

Ryan

[ryan47]

WOW!! Thanks for the sharing, Gunter.
mi_geoshader_echo_tag is awesome!!

Ryan