Hi Enrico,
sorry for the delay, I had mail problems sending to the list.
On Fri, 2004-07-02 at 04:24, Enrico Borrione wrote:
> not a word:
> simply it falls back to the std OGL pipeline...
> in fact i was wondering whether there is a way to get the shader
> compilation output. Blind flying is a bit tricky..
OpenSG error messages by default go to stdout, so if you don't have a
console window, you don't see them. You can redirect them to a file by
setting OSG_LOG_FILE to the filename you want, or you can redirect them
to a callback function and output them in your program and output them
in another way that works for you, see Source/Base/testLog.cpp for an
example.
Hope it helps
Dirk
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
