• Welcome to MX Bikes Official Forum. Please login or sign up.
November 24, 2020, 01:03:12 PM


MX Bikes beta15b available! :)

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - HornetMaX

Bug Reports / Telemetry bug ? (+ bonus bug, maybe)
January 13, 2020, 10:37:29 PM

In the thread of my MaxHUD plugin there's a report of a strange behavoiur of my LiveTiming (posts from tfc and teeds, from here).

What my LiveTiming does is to save the position (fPos) and time (fTime) in an array all along a lap (your best lap).
On subsequent laps I do the same in a different array and hence I can compute the time gap at the current point on the track, between the ongoing lap and the currently best one.

The RunTelemetry call of the output plugin seems to receive some weird data, here's an example (relevant part only):

@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.763742, fT:154767.734375
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.763926, fT:154788.375000
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154804.046875
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154825.359375
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154843.796875
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154867.578125
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154887.109375
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154907.015625
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154926.875000
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154945.796875
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154965.390625
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154984.546875
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.765946, fT:155003.312500
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.766131, fT:155022.921875

As you can see, fPos is 0.763742 on the 1st call (1st of the ones shown here), then 0.763926 on the 2nd but on the 3rd it goes back to 0.099025 and stays there for a few calls (10 in this case), before resuming with more normal values (0.765946 then 0.766131). This of course screws up my LiviTiming thing (and makes some weird telemetry graphs :) ).

Notice that the point at which this happens has nothing special (no crashed bike).

According to tfc and teeds, this seems to happen only on some tracks. I can reproduce it systematically on Ironman track: drive first lap out of pits and on the second lap (1st "real" lap) it happens always for me. So my LiveTiming of the 3rd lap is screwed.

Another weird thing, likely unrelated.
On Ironman when you go to track from the paddock you don't cross the start/finish line, but the ghost of the 1st lap out of pits is recorded anyway. This is probably unwanted (the 1st lap out of pits is not considered as a valid lap by MXB anyway, in terms of timing).
Question as per title: anybody using Nvidia DSR with PiBoSo's sims ?

I gave it a try and I seem to prefer it.

My usual settings: 1920x1080 @ 120Hz, AAx8, everything else maxed out (1080 is my monitor's native res, of course).
DSR settings: 3849x2160 @ 120Hz, AAx0, everything else maxed out.
Hi all,

I've made a little tool to visualize the tyre model (Magic Formula) used by GPB. If you don't know what the Magic Formula is, the tool is *not* for you :)

NOTE: the tool is very much beta. The equations involved are messy and I cannot grant an error has not slipped in. If anybody with knowledge of this stuff wants to double check, that would be appreciated. I can send you the relevant source code for that, just PM me. Of course, if Piboso could validate all that, that would be ideal (but he probably has other things to do).

It can load two set of parameters (two .tyre files) to compare and modify them (only the Magic Formula parameters). It has 4 tabs, one for each graph:

  • Longitudianl force: as function of longitudinal slip (x axis) and of vertical load, side slip and camber (sliders).
  • Lateral force: as function of lateral slip (x axis) and of vertical load, longitudinal slip and camber (sliders).
  • Aligning torque: as function of lateral slip (x axis) and of vertical load, longitudinal slip and camber (sliders).
  • Lateral force vs Longitudinal  force: as function of vertical load, side slip, side slip and camber (sliders). Line is plotted for longitudinal slip between -1.00 and +1.00.
Any time a value is modified, the graphs are updated. Same any time a slider is moved. Double clicking on a slider will bring it back to its default position.

On each graph there are 4 lines: 2 for the 1st model (in blue), 2 for the second model (in red).
On the longitudinal force graph (for example), it draws (for each model) the line with zero side slip and zero camber (dashed line) and the line with the values of side slip and camber specified by the sliders.

Using shift+mousewheel and ctrl+mousewheel you can zoom in/out of the X/Y axes. shit/ctrl+drag will pan the X/Y axes. A double click will zoom out to full graph.

DOWNLOAD v1.6b (2017/05/16) : <<-- THIS if for GPB beta9/10/11 and MXB beta5/6 (subsequent versions TBC).

INSTALLATION: this is not a plugin, it's a standalone tool. Just copy it in a folder where you have write rights (i.e. avoid "Program Files" and similar). The sample files provided are the ones of the 3 default bikes in GPB beta8.

IMPORTANT: in case of issues like missing dlls or things not showing up, please install Microsoft Visual C++ 2015 Redistributable Package (x86). It's available in the .zip (vcredist_x86.exe) or you can download it at https://www.microsoft.com/en-US/download/details.aspx?id=48145 (download the x86 version, "vcredist_x86.exe", not the x64 version).
Bug Reports / Minibug on Practice Track Short
December 27, 2016, 10:22:50 PM
In the track selection page, there's no image for track "Practice Track Short".
From the example plugin:

/* _iState: 0 = on track; 1 = spectate; 2 = replay. This function is optional */
__declspec(dllexport) void Draw(int _iState,int *_piNumQuads,void **_ppQuad,int *_piNumString,void **_ppString)

But when I start MXB and load a saved replay, the Draw() call has _iState at 1. In GPB it's 2, as expected.
Hi all,

a little tool to edit .scl file (only for GPB beta14 and MXB beta8).

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  8)
PM me when donations are done, so that I can keep a donors list HERE.

DOWNLOAD v1.4 (2018/07/16) for GPB beta14 & MXB beta8

INSTALLATION: this is not a plugin, it's a standalone tool. Just copy it in a folder where you have write rights (i.e. avoid "Program Files" and similar).

IMPORTANT: some samples are provided in the Samples folder (just from GPB, but it's the same for MXB).
Notice that you will be able to load the default bikes (e.g the 'murasama_rc990_03' for GPB) but you won't be able to "play" the sounds, as the .wav of the default bikes are encrypted. The samples are provided anyway:

  • to show how a properly done .scl is: you can replace the default (encrypted) .wav with your own ones and play with them.
  • to show which files are needed by the tool. Basically the .scl, the bike.cfg, the .engn (all of them, if more than one), the tyreset .cfg, all the .tyre and all the .wav referenced by the .scl.

Bug Reports / Skin/font bug ?
March 17, 2016, 12:36:45 AM
Hi all,
just stumbled on this: loaded a skin for the 450xf, it loads fine. Now selecting a font (for the number) reverts to the default skin.

Happens with another bike too, check the videos below. Is it an issue in the skin or a bug ?

https://www.youtube.com/v/8QV0U0z58ME https://www.youtube.com/v/RhxQiCQVrKU
Bug Reports / Not really a bug but ...
May 01, 2015, 10:29:15 PM
... on the enduro track (but I guess it could happen on the others too) I respawned with one of the tires delimiting the track right between my front and rear tyre: impossible to restart (not even "walking" the bike), had to pit. Could be annoying in races, of course.


Bug Reports / Weird skipping in 1st person view ?
March 17, 2015, 09:16:39 PM
Not sure it's a bug.

Was just circling in the pit are of the practice track when I noticed that in 1st person view (both views) there's some skipping / jerkiness happening, never noticed before. It doesn't seem to happen in 3rd person view.

In the video below, I start from the pit pointing north (let's say) and I circle to the left. Each time I read the west-most point (9h on a clock) there's some skipping. Check at seconds 0:09-0:10, 0:18-0:19,  ...


Anyone has the same issue ?

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.2:  <<-- THIS if for GPB beta16, WRS beta14, KRP rel9 and MXB beta11

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  8)
PM me when donations are done, so that I can keep a donors list HERE.

  • 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:
  • 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).

  • 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.

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  :P
  • 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).

General Discussion / Gyro effect and counter-steering
November 30, 2014, 09:58:29 PM
Quote from: Stoneybonezz on November 30, 2014, 05:12:03 PM
Riding a street bike and riding a dirt bike are 2 completely different things other than the gyro effect point blank.
On this forum a lot of people speak about the "gyro effect".
I'm sure 90% of them do not know what this is and just misuse the term.

@Stoneybonezz: what do you mean with "gyro effect" ?

Plugins / MaxHUD plugin
October 01, 2014, 11:02:44 PM
Hi all,
this plugin allows to put on screen a variety of widgets as show in the below images.


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.1:  <<-- THIS if for GPB beta18, WRS beta14, KRP rel11 and MXB beta14

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  8)
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: