Xith3D profiling and debugging

Engines, Libraries and Tools Xith3D Forums
#1

How is the Xith3D profiling and debugging supposed to work?

I thought the following code prints all internal debug messages to a file:


FileLog fileLog = new FileLog(LogType.DEBUG, "/some/path/test.txt");
LogManager logMgr = new LogManager();
logMgr.registerLog(fileLog);

This creates an empty file. My test app only displays a cube and two overlays, but there still should be some debugging information. (Or not?)

If I use

view.renderDebug(canvas3D, "/some/path/test2.txt");

the debugging stuff gets written to the console instead of the file.

If there are already some code examples for debugging and profiling please point me to them.

#2

How does the internals of that work? Not knowing - might I suggest log4j ?

Eric

#3

Yes, internally log4j is used.

#4

Really no one using the builtin logging and profiling functions? Come on, I know you use them. ;D

#5

Nope, not hit any problems where I thought it might help yet. But then the Xith usage I’m doing is fairly trivial I suppose.

Kev

#6

At least the profiling works, if I use Log.log instead of a LogManager. However it doesn’t seem to help to find out something about the performance of the userinterface.