Messages

v1.4 out:

• Updated for GPB beta5 (no changes for WRS and KRP).

MaX.

v1.8.0 out:

• Updated for GPB beta5 (no changes for KRP and WRS).

MaX.

Uh, it's already possible sam19 !

Read the (short) description in the link in the first message (MaxTM - A telemetry tool for GPB and WRS).

MaX.

v1.3 out:

• Fix a nasty bug on Close/Delete unselected runs (it was closing/deleting the selected ones ...  )

MaX.

But then again are people going to keep updating software plugins tracks ect with every beta, as there has now been over 11.

Plugins and tracks may not need to be updated every single beta. For plugins it's only if the plugin interface changes (which has been the case from 10 to 11, but not on many other betas).

Anyway, for my plugins and stuff, I'll keep updating them: usually it's just a 2 hours job as most of the time the changes are done by Piboso in order to minimize impact on the plugins.

MaX.

Is this possible to run this on beta 10b, As at the moment we are running SimVibe and that is not able to run with beta 11.

I would have to make a dedicated builld for this, which in turns implies I'd have to fetch piboso's plugin interface for beta10b (I don't have it, maybe somebody has it around or Piboso can fetch it) and adapt some code.
I'd be really happy to avoid doing that as it could become a maintenace nightmare. In any case, one day or the other you'l have to move forward  so ...

What's the problem with SimVibe and beta11 ?

MaX.

how long did it take you to make it?

I didn't count the time spent on it and I've been adding features for a long time.
Despite being a comp. science engineer, I was a bit rusty on development as I no longer work in this field, so I lost quite some time at start.
Right now, when I have to add a new feature it'a matter of a minutes to hours (unless it's something very complex).

How difficult was it to manipulate random's code for PiBoSo's sims?

As always with other's code, it's a bit hard to understand. Random's code was also with very few comments and in a strange language (strange to me at least, not even sure if it was hungarian or something like that).
After having understood it, I've essentially rewritten everything, not sure there's a single line left in.

May inquire to acquire the code so that I can have a shot at a personal hud design?

Random's code no, I cannot send it to you.

My one yes (send me a PM with your email), but  I can warn you from now that if you're not proficient in C++, then you're entering a world of pain: it's 4000+ lines of messy code (without counting blank lines, comments and not even some preprocessor stuff), overcomplicated by the fact it can be compiled for GPB, WRS and KRP.

MaX.

[DOWNLOAD v2.7:]

MaxTM is a telemetry tool for GPB, MXB, WRS and KRP: it allows to display graphs of the telemetry data exposed by GPB/MXB/WRS/KRP. It has two main components:

• A GPB/MXB/WRS/KRP plugin: in charge to generate the telemetry data files.
• A viewer application: in charge of displaying graphically the telemetry files saved by the plugin.

DOWNLOAD v2.7:  <<-- THIS if for GPB beta21, WRS beta14, KRP rel13 and MXB beta18

Love this stuff and you want to show that ? Have too much money at hand and don't knowe what to do with it ? Donations are welcome 
PM me when donations are done, so that I can keep a donors list HERE.



INSTALLATION

• Download the archive from the link above and extract it somewhere. Inside the main folder you should have 4 extra folders: one for the plugin(s), one for the viewer and 2 folders with sample data.
• Take the viewer folder (MaxTM_Viewer-vX.Y) and the 2 sample foders and put them somewhere (Desktop, Documents, wherever you have write rights). DON'T PUT THEM IN Program Files OR SIMILAR. The viewer is a portable app: it does not write anything in the registry, it requires no installation (in the Windows sense) and it won't ask you if you want to install a stupid toolbar.
• Now run the viewer application (MaxTM_Viewer.exe and check it starts without issues. If it complains for missing dlls, you may need to install:
  
  • Microsoft Visual C++ 2017 Redistributable Package (x64)  for GPB, MXB abd WRS
  • Microsoft Visual C++ 2017 Redistributable Package (x86)  for KRP
• If you want to generate telemetry data from GPB/MXB/WRS/KRP you have to install the plugin: in the plugin folder (MaxTM_Plugin-vX.Y) you have 4 .dlo files (one each for GPB/MXB/WRS/KRP) and a folder named MaXTM_data. Just copy the appropriate .dlo and the MaXTM_data to the GPB/MXB/WRS/KRP plugins folder.
• Restarting GPB/MXB/WRS/KRP and going to the track you should hear a heartbeat sound each time you start a run: this confirm that the telemetry logging is active.
• You can also press 'Z' to see is if logging is currently ON or OFF, and CTRL+Z to toggle it ON/OFF. You can change the key in the .ini file of the plugin (MaxTM.ini, in the GPB/MXB/WRS/KRP data folder).
• Telemetry log data will be saved (2 files per run) in folder MaxTM under GPB/MXB/WRS/KRP data directory (e.g. C:\Users\MaX\Documents\PiBoSo\GP Bikes).

IMPORTANT:

• The telemetry file can be relatively big if you ride a lot. Remember to clean-up the MaxTM folder from time to time.
• If you want to disable the plugin (for whichever reason), you simply rename it from .dlo to .dlo.off (or to .pizza) or edit the .ini file of the plugin (MaxTM.ini, in the GPB/MXB/WRS/KRP data folder) and set 'active' to false.

USAGE:
I'll briefly describe the main features here: there is no user manual yet (and maybe there will never be one), but the viewer is not too complicate.

• The main areas of the main window have tooltips (i.e. little text explanations that appear when you leave the mouse still on them for a while): READ THEM.
• The main areas of the main window have tooltips (i.e. little text explanations that appear when you leave the mouse still on them for a while): READ THEM (intentional repetition)
• Seriously, read the tooltips: in particular the ones of the graphs and track map, as they explain how to interact with the graphs using the mouse. I could resume the thing here, but if I do it then you won't read the freakin' tooltips, so I won't do it 
• On most areas a context menu is available: just right-click with the mouse.
• The worst thing you could do with the viewer is delete some telemetry file: it's not a dangerous app, don't be afraid to try things around.
• The general idea is:
  
  • You can open an arbitrary number of telemetry files at the same time. Each telemetry file will appear as a Run containing some Laps.
  • On the left you have the Runs/Laps as seen via the telemetry data, along with their lap times (as seen by the telemetry).
  • On the right (in the panel named Timings you have the same Runs and more or less the same Laps, with more or less the same lap times (as seen by GPB/MXB/WRS/KRP) and their split times.
  • Telemetry lap times come in two flavours: column "Lap Time" is based on GPB/MXB/WRS/KRP timing, column "Lap Time (w)" is based on an external timer which turns out to be more precise (I think it's some sort of bug, but I have no feedback on it from Piboso).
  • The telemetry lap times should more or less match the "official" lap times (the one in the Timings panel). Small errors are normal (up to 0.1-0.2 sec I'd say), larger ones are not.
  • The number of laps between the Runs/Laps panel and the Timings panel may not be identical: typically due to not completed laps, out of pits laps and so on. It's not too hard to see which lap in Runs/Laps corresponds to which lap in Timings.
  • In Runs/Laps you can select up to 4 laps (each one has a specific color): the 1st lap you you select will be the reference lap.
  • On the right you have (by default) one Graphs panel: here you can have the telemetry data plotted. You can have multiple graphs panels.
• In each graphs panel, using the context menu (right-click), you can:
  
  • customize the number of graphs (as an N by M grid) and their appearance (axis labels, tick labels).
  • customize the each individual graph: delta plot (see later on), join/mark data points, show/position the legend etc.
  • customize what to plot on each graph on the X and Y axes (the variable on the X axis is the same for all the graphs in the panel)
  • Save the current layout of the graphs panel, so that you can reload it next time.
• Delta graphs: a delta graph is simply a graph where instead of plotting (let's say) the speed against the position on the track (centerline) of the selected laps, you plot the difference in speed between the 1st selected lap (the reference lap) and the other selected laps. So if you have 4 selecte dlaps, on a normal plot you'll have 4 lines while on a delta plot you'll have 3 lines, each of them being the speed difference between selected lap 1 and selected laps 2, 3 and 4.
• The viewer app comes with 2 themes: the default "bright" one (almost white background) and a darker one I find very handy at night (did I told you I average 4-5hrs of sleep per day ?).

I'll open another topic to gather your feedback on this: please try to keep this topic clean (just for new versions etc).

MaX.

What software do you use to make this?

You can use any language you want, provided it has a C interface. I use C++.

MaX.

Is your telemetry working for KRP?

As replied on GPB forum:

Not the version currently out (v1.1), but I have one almost ready and it is working with KRP too. So it's gonna come soon ...

MaX.

No sense in showing redundant information. Less distractions.

Well, that's why there's no temp in the plugin, it's already in the dash.

For example I only need temp light (not even the value just a light) an rpm light and splits.

RPM light is in the speed/gear indication: it changes color depending on the RPMs.

Splits are already there in the plugin.

What's missing ?

I can't customize the whole thing to fit anyone's needs (well, except my own ones ), it has to be a sort of trade-off.

MaX.

[please read the .pdf file in the .zip. PLEASE. READ. IT.]

The plugin is great!! Can you add  temperature though?

Temperature is on the dash ? Why don't you activate the dash to get it ?

how to instal

Oh man, what about reading the 1st message ?

For install instructions, plugin configuration, changes in versions and so on, please read the .pdf file in the .zip.  PLEASE. READ. IT.

MaX.

I don't see temperature. Can it be added?  This would be useful for me because I need all the fps I can get so I hve to hide the driver and hud.

There's no temperature because that's normally shown on the HUD. Just show the HUD, no ? I doubt it makes you lose a lot of FPS.

There also to view with the helmet ?

What do you mean exactly ?

There's an option to show/hide the helmet inside (and you can also make it vibrate a bit and put its top and bottom section at different height).

MaX.

[EACH WIDGET CAN BE CONFIGURED AND HIDDEN, YOU DO NOT HAVE TO USE THEM ALL.]

Hi all,
this plugin allows to put on screen a variety of widgets as show in the below images.

EACH WIDGET CAN BE CONFIGURED AND HIDDEN, YOU DO NOT HAVE TO USE THEM ALL.

For install instructions, plugin configuration, changes in versions and so on, please read the .pdf file in the .zip.  PLEASE. READ. IT.

      DOWNLOAD v2.2.7:  <<-- THIS if for GPB beta21, WRS beta14, KRP rel13 and MXB beta18

Love this stuff and you want to show that ? Have too much money at hand and don't knowe what to do with it ? Donations are welcome 
PM me when donations are done, so that I can keep a donors list HERE.





IMPORTANT: If you get a warning/error about missing dlls, or if nothing shows up once on track, install:

• Microsoft Visual C++ 2015,2017,2019 Redistributable Package (x64)

It is a pointer to an array of 4 floats.

Good enough. Should probably be declared as such in the centerline function signature.

MaX.