Update (from post#9):
Here is a version that runs with 2.6x (tested in 2.76 as well).
A) download FrameByFrameDebugger2.6_3.blend to your file system
B) Open your game .blend with Blender and link the scene _frameByFrameDebugger.lib from the downloaded .blend (alternative you can link one of the groups).
C) add an instance of the “DebugMode.*” groups.
D) run your game
- DebugMode.autoStart -> Starts debug mode immediatly after scene start
- DebugMode.F1 -> Starts the debug mode after pressing <F1>
The debug mode is enabled when you see the overlay text. With <H> you get some help.
Archive (version 2.49)
Version 2.0 of the FBF Debugger is there :).
What is new?
- much easier configuration
- now with inspection camera using Chasers mouselook explorer (see aareadme)
- all in one File
Where can it be usefull?
- inspecting scenes with physics problems
- inspection scenes with animation problems (animation synchronising etc.)
Just one files:
FrameByFrameDebugger.blend (235 KB)
How easy is it?
- Open the file to be debugged
- Append or link <Shift><F1> the scene debugMode (I recommend linking)
- Select any object (or add a new one) to activate the debug mode
Any sensor can trigger any controller (e.g. an Always to start immediatly, a keyboard sensor).
The controller should activate an scene actuator.
The scene actuator should be in “Add OverlayScene” or “Add backgroundScene” with the linked scene “debugMode”
you will see a little d at the left corner of the sceen when in debug mode.
<F1> leave debug mode
<F2> single frame mode/next frame
<F3> slow motion mode (num pad +faster/-slower)
<F4> normal speed (but still in debug mode)
<F5> toggle between inspection camera and normal camera.
inspection camera controls from Chasers mouselook4:
Mouse movement to look.
You can move with
Q and E to sink and rise.
Shift to modulate speed.
pageup and pagedown to rise and sink.
Numpad zero to modulate speed.
Here is a real example:
I hope it helps