RAD Telemetry 1.1k released!

That was quick!

We found a bug in 1.1j that necessitated a quick release with a bugfix.  The bug only affected those who had been using 1.1j either as an upgrade or for evaluation.

EDIT: 1.1k now has WiiU support, including support for the latest Nintendo SDKs.

1.1k does not have WiiU support in it, we're working on separate update with additional WiiU support in the coming week (hopefully).

RAD Telemetry 1.1j Released!

Welcome to the July 2012 release of RAD Telemetry!  This month we've done some bug fixing, incremental updates and support for the Linux and WiiU platforms, and implemented some experimental features specifically requested by our customers!

Run-Time

• Change: The run-time protocol has changed, so be sure to upgrade your server and run-times simultaneously!
• Bugfix: tmGetVersion was returning values inconsistent with the values in telemetry.h
• Enhancement: EXPERIMENTAL, CONTACT US BEFORE USING!  TMCT_USER_PROVIDED callback registration for your own storage and/or transmission of run-time data.
• Enhancement: Additional support for unannounced platform
• Enhancement: Updated WiiU support
• Enhancement: Enhanced Linux and OS X symbolization support

Visualizer

• Bugfix: Starting with 'Autostart Server' disabled resulted in a crash
• Bugfix: Zooming in too far in the Visualizer would make everything disappear in some instances
• Enhancement: Vertical zone scaling (Ctrl-Mousewheel) state is now saved
• Bugfix: 'Import' of data files would sometimes crash if the imported data was very small

Server

• Change: The run-time protocol has changed, so be sure to upgrade your server and run-times simultaneously!

Other

• Change: Cleaned up some obsolete documentation
• Bugfix: Fixed documentation error for some tmPlotXXX variants

RAD Telemetry 1.1i Released!

As promised, continuing our monthly releases with performance tweaks and more platform support.

IMPORTANT: This change requires a full upgrade and rebuild, and the tmPlot API will fail to compile.  We apologize for the minor inconvenience, but we needed to add a parameter to the tmPlot APIs and figured doubling the surface area of those APIs for one parameter was probably not a good long term direction.  The new parameter is a 'flags' parameter that you can just set to 0 and everything will work.

Run-Time

• Change: Protocol change, so make sure server and run-time are both upgraded!
• Change: tmPlotXXX APIs have been changed, an additional parameter is now required -- you must recompile and relink!
• Bugfix/Change: TM_VA_LIST parameter is now expected to be a va_list* instead of a va_list
• Change: Added TM_SLOW define that is set on platforms with very slow networking and timestamp querying (currently iOS)
• Bugfix/Changes: additional support for unannounced platforms
• Enhancement: TMCT_FILE support for iOS and PS3
• Bugfix: GPU D3D crash bug fixed

Visualizer

• Bugfix: certain object path names would crash plot display
• Bugfix: fixed missing newline when printing callstack in tooltip
• Enhancement: symbolization support enhanced for Linux and OS X

Server

• Change: Protocol change, so make sure server and run-time are both upgraded!

RAD Telemetry 1.1h Released!

We're back on our monthly release schedule -- this month we have bug fixes, performance improvements and some new platform support!

BETA iOS SUPPORT IS NOW AVAILABLE!

Run-Time

• Enhancement: we now have iOS support!
• Enhancement: additional support for unannounced platforms, please contact sales3@radgametools.com for more information
• Enhancement: additional enhancements for the WiiU platform
• Enhancement: quad buffering of Telemetry write buffers enabled on all platforms (previously this was only on PS3 and 360)
• Bugfix: RADEXPLINK definition mismatch if NTELEMETRY was defined and another RAD product was included
• Bugfix: PS3 strings were sometimes not sent over properly in some edge cases
• Bugfix: tmShutdown now compiles to TMERR_DISABLED instead of an empty statement when NTELEMETRY is defined
• Bugfix: handshake timeout now honors the timeout parameter to tmOpen instead of being hardcoded to 1s

Visualizer

• Change: removed confusing and vestigial tab 'Memory'

Server

• Bugfix: server is more tolerant of unknown string references sent by the run-time
• Bugfix: when -keeptmp was specified and the server connection crashed, the *.00 file was inadvertently deleted.  Fixed.

RAD Telemetry 1.1g Released!

Hey everyone, new release for Telemetry!  This is a relatively small update but still lots of good stuff going on!

Run-time

• Enhancement: TMOF_NO_PDB_LOOKUP added.  In some cases on Windows tmOpen can take a long time while doing PDB lookups of loaded modules.  This allows you to bypass that delay.
• Enhancement: Significantly better performance in the Telemetry processing thread on PS3, 360 and Windows.
• Change: default Telemetry thread priority increased to avoid starvation

Visualizer

• Enhancement: "Lock to end" checkbox is now persistent between sessions
• Enhancement: plotted zone times are now in the same plot group so you can compare scales
• Enhancement: Build information passed to tmOpen is now displayed in the session view
• Change: New license key system
• Change: Removed deprecated thread balance pie chart

Server

• Enhancement: a -maxsessions parameter has been added to tmserver so that it can be scriptable.  Now you can launch the server, tell it to capture N sessions, then have it exit when it's done capturing.

Telemetry 1.1f released!

Now that the holidays and GDC are behind us we're going to buckle down and get some pretty significant features and changes that our customers have asked for.  But before that we've released 1.1f with a lot of minor fixes and improvements.

Speaking of GDC, it was great meeting so many of our customers and getting positive feedback on Telemetry -- thanks for stopping by the booth!

Run-Time

• Enhancement: new plot types TMPT_TIME_US and TMPT_TIME_CLOCKS
• Bugfix: crash bug with Windows DX9 tmxgpu
• Bugfix: crash bug with TMCT_FILE and OS X
• Bugfix: tmSetLockStateMinTime wasn't checking some parameters in checked builds
• Bugfix: if the memory arena passed to tmInitializeContext wasn't zeroed out bad things could happen.  Telemetry now automatically zeroes that memory first.

Visualizer

• Enhancement: A very basic "search for zone" is implemented using Ctrl-F.  Does not support wildcards and only searches for zones that are currently loaded in memory.  A better implementation is in the works, but enough people asked for this that we've decided to provide this short term implementation.
• Enhancement: You can now plot a zone's time by right-clicking on it and choosing "Plot zone time".  As with search, you have to make sure that all zones you care about are in memory.  And again, this is a short term solution until we get a global solution in place.
• Enhancement: "lock to end" supported, so if watching live captures the last frame is visible at all times instead of scrolling off screen.
• Bugfix: Slow performance when rendering really wide zones 
• Bugfix: Right-click on some zones and zone types was sketchy
• Bugfix: Intermittent crashes when viewing a session with a combination of very short and very long frames.

Server

• Bugfix: rare race condition when accepting multiple profiling sessions from the same machine in less than one second

Misc

• Bugfix: tmSetLockStateMinTime return values were improperly documented
• Bugfix: tmSPUBindContextToListener function signature documentation was wrong

Telemetry 1.1e Released!

Even though it's been only a couple weeks since our last release we wanted to get another big one out before the holidays. We've made a lot of little enhancements, added support for a new platform, and, best of all, have implemented a very handy feature -- off-line performance capture!

As long time Telemetry users know, Telemetry's architecture is based on streaming data over the network to a server which acquires, processes, stores, and eventually serves up the data. Unfortunately this isn't practical in certain situations. For example, a testing lab may not have network access for security reasons; some consoles have notoriously poor networking performance (even while wired); or a test machine may not have access to a Telemetry server.

To address these concerns we've implemented off-line data capture. The only change you have to make is a parameter to tmOpen -- specify TMCT_FILE instead of TMCT_TCP. Now instead of writing to the network Telemetry will write to disk. When done you take the "tmdata" files and then import them into the Visualizer (or play them back to the server). It's that simple, and in some cases can make a dramatic (5-10x) performance difference.

Run-Time

• Enhancement: Performance improvements for 360 and PS3
• Enhancement: Added TMPI_START_TIME parameter to tmGetPlatformInformation
• Enhancement: Win32: Changed context switch trace management code in an effort to be more robust across a wider range of systems
• Enhancement: Duration of TCP send now has a plot automatically generated
• Enhancement: Added more send buffers to increase performance and prevent stalls while writing to the network
• Enhancement: TMCT_FILE for local mirror of network traffic (i.e. disconnected captures are now possible!)
• Enhancement: BETA support for new platform
• Change: PS3: Telemetry thread now defaults to hwthread 1
• Change: 360: Telemetry thread now defaults to hwthread 5

Server

• Enhancement: Greatly enhanced performance under certain conditions with lots of frames
• Bugfix: Occasional server crashes when open zones spanned a very large number of frames
• Change: removed TM_APP_STRING and TM_APP_TICK console spam

Visualizer

• Enhancement: "Import Data Files" feature added (related to TMCT_FILE support)

Other

• Bugfix: Some documentation was using tmDynamicString improperly
• Enhancement: Cleaned up example files
• Enhancement: Added 'tmimport' command to playback raw net files captured with TMCT_FILE sessions