Monday, April 8, 2013

RAD Telemetry 1.1s shipped!

The big update is that we now have "out of the box" support for Linux/ARM, with some caveats.  But by and large if you're working on some kind of embedded Linux/ARM system with reasonable networking then Telemetry should be viable for you.

And of course we have our standard updates, bugfixes, and compatibility stuff!


  • Enhancement: added 'R' (reverse) variants of callstack APIs
  • Enhancement: official support for ARM7/Linux
  • Enhancement: updated SDK/console support
  • Bugfix: Fixed networking bug on PS4
  • Bugfix: Emulated tools version was being reset at tmClose
  • Bugfix: Warnings now with tmSetLockStateMintime if you reuse the same buffer
  • Change: tmEmitAccumulationZone now sets location string of 'leave' to same as enter event


  • Bugfix: fixed timespan rendering bug


  • Changes: updated UE3 integration documentation
  • Changes: fixed examples
  • Changes: minor documentation changes

Monday, April 1, 2013

Telemetry 2 Beta Migration Notes

To make the migration from Telemetry 1.x to 2.0 a little easier, existing customers can provide us test data that we'll verify and, if all looks good, ship out the beta soon after.  The three steps necessary are to ensure you're on a recent version of Telemetry (1.1r or later), enable T2 compatibility, and send data to a file instead of a server.

First, verify what version you're running -- this is can be seen in the Visualizer's "About" pane.  If you need a newer version, please contact us and we'll get it to you.

Second, enable T2 compatibility by adding the following line after initialization but before you call tmOpen:

TmI32 v = 2;
tmSetParameter( cx, TMP_EMULATED_SERVER_VERSION, &v );

Finally, specify TMCT_FILE instead of TMCT_TCP when calling tmOpen.  You should otherwise be able to run normally and when all done a series of TMDATA.000, TMDATA.001, etc. will be created (location depends on your platform).

Zip up those files and contact us for FTP access and we'll verify that they work!

One other migration note: for ideal compatibility during migration, you'll need to change how some path names are done for plots, messages and zones, but we'll get into that later.